You paid for the lead. It arrived from a portal at 9:40 on a Sunday night, along with forty others, and it went to the same shared inbox as everything else.
By the time a site executive works down to it on Monday afternoon, the buyer has spoken to three other projects and booked a Saturday visit with one of them. The lead was not bad. The response was.
Indian residential sales has a specific version of this problem, and the specifics matter, because the generic advice about speed to lead misses what decides the outcome here.
1
The conversion event that matters: a site visit that happens, not an enquiry that is logged.
3+
Projects a serious buyer is usually speaking to in the same week.
2
Languages a single enquiry conversation routinely moves between.
The site visit is the funnel
In most sales processes the meeting is a step. In Indian residential real estate the site visit is close to the whole thing. Buyers who walk the project convert at a different order of magnitude from buyers who do not, because the decision is being made about a physical place, often with family, and often about something not yet built.
That reframes what a lead response is for. You are not trying to qualify budget on the first call, and you are certainly not trying to sell. You are trying to convert an enquiry into a confirmed visit, at a specific time, with the right person, and then make sure it happens.
Which means the two numbers worth instrumenting are not cost per lead and enquiries handled. They are the share of enquiries that become booked visits, and the share of booked visits that turn up.
Portal leads arrive in bulk and decay in minutes
Leads from the major listing portals do not trickle in. They arrive in bursts, weighted to evenings and weekends when buyers are browsing, in exactly the window when your sales team is not at desks.
They also arrive with the buyer having enquired on several listings at once, because the portal interface encourages it. So the first project to reach them frames the comparison, and often books the Saturday slot before anyone else calls. The others are then negotiating for the second visit of a weekend that has already been allocated.
Widely cited lead response research puts the qualification advantage overwhelmingly in the first few minutes. In this market that advantage compounds, because a weekend has a fixed number of visit slots in it and the early caller takes the good ones.
SUN 9:40 PM
Portal enquiry
Buyer enquires on four projects while browsing. Engaged, comparing, no visit booked yet.
SUN 9:43 PM
Call and WhatsApp
Configuration, budget band, and possession timeline. Saturday 11am offered and confirmed.
SAT 8:00 AM
Reminder
Location pin, contact name, and a one tap way to move the slot rather than silently skip it.
Language is not a feature here, it is the conversation
An enquiry conversation in Mumbai, Bengaluru or the NCR does not stay in one language. It starts in English, moves into Hindi or a regional language when the buyer relaxes, and switches back for numbers and technical terms. Families discuss among themselves mid call.
An agent that cannot follow that is not multilingual in any useful sense. Handling a scripted Hindi call is a different capability from staying with a buyer who changes language halfway through a sentence about carpet area. This is worth testing directly rather than taking on trust, and our multilingual guide goes into how it is built.
WhatsApp sits inside the same requirement. In this market the channel is where the relationship continues after the call: the floor plan, the location pin, the reminder, the follow up when a visit is missed. A voice agent that cannot hand the thread to WhatsApp and pick it up again is handling a fragment of the conversation.
The enquiry is not the asset. The confirmed visit that happens is the asset.
the Kaigen team
The second leak: visits booked that never arrive
Teams that fix response speed often find the next problem waiting behind it. Visits get booked and then a meaningful share of them do not happen, and nobody notices until the weekend is over.
The causes are mundane. The buyer forgot, the family plan changed, the location was unclear, the slot was optimistic. All of them are addressable by contact that most teams do not have capacity to make, because reminding sixty people about Saturday is nobody's favourite Friday job.
This is the part where automation earns more than it does on the first call. A reminder that carries the pin and offers a one tap reschedule turns a silent no show into a moved appointment. A follow up on a missed visit within the hour turns it into next weekend rather than into nothing.
What to check before you buy anything
Q1
What is your enquiry to visit rate?
If this is not measured weekly by source, the cost per lead you optimise against is measuring the wrong thing.
Q2
What happens to a Sunday night enquiry?
Trace one honestly, timestamp to timestamp. The gap is usually the whole explanation for the quarter.
Q3
How many booked visits turned up last weekend?
Most teams know the booking number and not the arrival number. The difference is where the budget went.
There is a compliance layer under all of this that is unusually strict in India. Commercial calling runs through registration on the DLT platform, promotional and service calls use different number series, and enforcement is by disconnection rather than fines. If you are planning outbound at any scale, read the TRAI rules before you build, not after.
For the mechanics of how a speed to lead front line is assembled, there is a worked teardown in the speed to lead deep dive, and the real estate page shows the shape of the deployment.
KEY TAKEAWAYS
- The site visit is the conversion event. Measure enquiry to booked visit and booked visit to arrival, not enquiries handled.
- Portal leads arrive in evening and weekend bursts, and the first caller takes the good weekend slots.
- Real multilingual capability means following a buyer who switches language mid sentence, not reading a script in Hindi.
- WhatsApp is where the thread continues. Voice that cannot hand off to it is handling a fragment.
- Reminders and missed visit follow ups often return more than faster first response, and almost nobody has capacity for them.
MAP YOUR FUNNEL
Want to see where your portal spend is going?
Twenty minutes tracing one weekend of enquiries end to end, from portal timestamp to who walked the site.
Book a 20 minute audit →FAQ
Can an AI agent handle a buyer who switches between Hindi and English?
The capable ones can, and it is the right thing to test in a trial rather than accept on a datasheet. Reading a script in a second language is straightforward; staying with a buyer who changes language partway through a sentence, and keeping the numbers and technical terms straight across the switch, is the harder capability and the one that matters on an enquiry call.
Should the agent try to qualify budget on the first call?
Lightly. The purpose of the first conversation in this market is to convert an enquiry into a confirmed site visit, because that is where conversion happens. Enough qualification to route the buyer to the right project and configuration is useful. A full financial qualification on a first call tends to cost more visits than it saves.
What about visits that get booked and never happen?
That is usually the second largest leak after response time, and often the cheaper one to fix. A reminder carrying the location pin and a one tap reschedule converts silent no shows into moved appointments, and following up within the hour of a missed slot recovers a share of them into the following weekend.
Are there rules about calling leads in India?
Yes, and they are strict. Commercial communication runs through sender and template registration on the DLT platform, promotional auto dialed calls use the 140 series while service and transactional calls use 1600, and senders must notify their access provider in writing before using an auto dialer. Enforcement is by barring and disconnecting telecom resources rather than by fines.
