Why property needs this more than other industries
A buyer filling in a form at ten at night has usually filled in three or four. They are not loyal to whoever they enquired with first. They are loyal to whoever answers first, because that is the reply that makes the project feel real.
Your sales team cannot be on the phone at ten at night, and it does not need to be. The bot buys you the twelve hours until someone can call, and in those twelve hours it can do something more useful than acknowledge receipt: it can answer the questions that decide whether the buyer stays interested.
What it should answer, and what it must not
The temptation is to make the bot do everything. That is how you end up with a bot that argues about price and loses a buyer. The line we use is simple: a bot may send information, a human must send judgement.
| Let the bot handle | Keep it human |
|---|---|
| Price band and payment plan basics | Negotiation of any kind |
| Exact location, map pin, drive times | Reading whether a buyer is serious |
| Approvals, RERA number, plot sizes | Anything about a competitor project |
| Possession status and construction progress | Commitments the registration does not support |
| Booking a site visit slot | The site visit conversation itself |
| Sending brochures, layouts, walkthrough video | Legal or loan advice |
Where the real gain is
Builders expect the gain to be in cost saved on staff. It is almost never that. The gain is in leads that would have gone cold.
In the Jaipur accounts we have opened, the pattern is the same: the leads were fine, the first reply was hours late, and the second follow-up never happened. On the programme we run for Sankalp Builders, 19,000+ leads have produced 1,600+ scheduled site visits, and the single change that moves that number fastest in a new account is cutting first-response time from hours to under a minute.
We built and run a WhatsApp AI sales agent for Sankalp Builders, live since June 2026, and the advisor you can open on this page is ours too. When we say the handover is the hard part, it is because we have had to fix it in our own.
What it connects to
A chatbot that does not write to your CRM is a toy. The useful version is one node in a chain.
- Ad or page produces the enquiry, tagged with the campaign that made it.
- Bot replies within seconds, answers, qualifies, offers slots.
- CRM receives the lead with the qualification answers and the source already attached.
- Assignment puts it on a named salesperson with an escalation timer.
- Conversions API sends the qualified-lead and booked-visit signals back to Google and Meta, so bidding starts hunting buyers rather than form fillers.
Step five is the one most builders never do, and it is where the campaign starts getting cheaper on its own.
Being honest is a design decision, not a disclaimer
A property bot that invents a price or a possession date creates a liability, not a lead. We build ours to answer only from a knowledge base you approve, and to say that it will check rather than guess when something is not in there.
We learned this the hard way on our own bot. Asked about a Jaipur corridor it had no data for, an early version invented one that does not exist. We rebuilt it so every number and every local claim has to come from an approved source, and so the honest answer is the default. For a builder the same rule protects your RERA position: the bot never states an approval, an amenity or a date your registration does not support.
What it costs and what it does not fix
A chatbot is cheap relative to the media budget it protects. The build is a one-time cost, the running cost is small, and the sensible way to judge it is against the leads currently going cold, not against a salary.
What it does not fix: a price that is wrong for the corridor, approvals that are pending, or a sales team of two handling three hundred leads a month. If those are the constraint, a faster first reply just gets you to the same wall sooner. We will tell you if that is what we see.