Blog · AI in practice
What the agent needs to know before the first lead
A fast agent that doesn't know your operation just delivers a polite yes. Before the first lead, we record four things with the people who know the house.

Raphael GiovaniniFounder and CEO · · 4 min read
An agent that answers in seconds and knows nothing about your operation just delivers a polite yes. The customer asks if there's a parking spot, the agent says it will check. They ask about price, the agent asks them to wait for a consultant. They ask if they can visit tomorrow, the agent says someone will be in touch. All fast, all friendly, nothing resolved.
That happens because most deployments start with technology and end with technology. Connect WhatsApp, paste in the sales material, turn on the agent. What's missing is context, the part that isn't in any PDF: the knowledge that lives in the heads of the people who sell every day.
Sit down with the people who know the house
Before the first lead, we sit down with the people who know the house. Not the director: the sales manager, the best broker, the support person who has answered the same question a thousand times. And we record four things.
The product: name, price and what makes it different. It sounds obvious, but it's rarely written down. Which project, which floor plans exist, the price range for each, the current payment terms. And above all, why someone would pick this one over the competitor's on the same street. Without that, the agent describes the product the way any brochure would.
The objection that always comes back, and the answer your best salesperson gives. Every operation has two or three objections that come up in almost every conversation. It's expensive. It's far. The construction takes too long. The team's best salesperson already has an answer for each, tested across hundreds of conversations. That answer has to be in the agent, in the words that work, not in a generic text about property appreciation.
The next action every reply has to drive toward. Visit, call or proposal. Every message from the agent should end by pulling toward one of those three. If the customer asked about the two-bedroom floor plan, the reply explains the plan and offers a time to see the model unit. Answering without steering hands the conversation back to the customer, and customers rarely take the initiative.
The limit: the point where the agent stops and hands off to a human. Discount negotiation, special payment terms, complaints from a customer who already bought, legal questions about the contract. Each operation decides where that line sits, and the agent has to recognize it and pass the conversation along with the full context, without making the customer repeat everything.
Why this isn't a detail
Picture a developer with three projects at different stages: one in launch, one under construction and one ready to move in. The same lead could fit all three, but the conversation is completely different in each case. The agent that knows the house sees the customer is in a hurry to move and steers straight to the ready one. The generic agent presents all three and asks which one interests them.
The difference between the two isn't the AI model. It's the four things recorded before the first lead.
Speed is the easy part
Any tool answers in seconds today. Speed is the easy part. What changes results is an agent answering at the level of what the operation knows, with the right product, the objection handled, the next action defined and the limit respected.
If your operation were to put an agent live tomorrow, would those four things be written down somewhere? Or would they live only in your best salesperson's head?
That's the survey we run in the diagnostic, before a single line of configuration.