Real estate follow-up on WhatsApp: work every lead, call the ones who are ready

Follow-up fails on timing and context, not on wording. A buyer who asked about a project on Tuesday evening does not need a fourth call on Thursday at noon. The fix is to work every lead on WhatsApp and to call the buyers who are engaging, in that order.

This guide is for marketing heads and presales heads at residential developers in India: what to send, when, who to call first, and how to measure it to the site visit.

Why does WhatsApp beat calls for follow-up in India?

Most follow-up in Indian residential presales still runs on the phone. The executive dials down a list, logs "RNR" or "call back later", and moves on. Buyers enquire during the working day and evaluate in the evening, with family. A call at eleven in the morning interrupts someone at work. A missed call leaves nothing behind.

A WhatsApp message does three things a call cannot.

It waits. The buyer opens it at nine at night, or on Sunday, when they are actually thinking about the home.

It carries what the buyer asked for. The project page, the price band, the floor plan, ready to forward to a spouse or a parent.

It shows who is engaging. The developer sees which buyers are engaging with the project page they asked for, and which never opened it. A call log cannot tell you that.

Across 10 residential projects in Bengaluru and Hyderabad, 7,451 personalised links went out to 6,655 buyers over three months. 36.7% of those buyers engaged with their page. The page said who was serious.

What does a good first message look like?

The first WhatsApp message sets the tone for every message after it. Four things make it work.

It arrives fast. If the enquiry came in after dinner, the message should be there before the buyer closes the portal, not the next morning.

It says who is sending it. The message comes from the project's AI assistant and says so in the first line. A buyer told upfront does not mind; a buyer who finds out later feels tricked.

It carries the content the buyer asked for. The project page for the configuration they enquired about, with the price band and the payment plan. Not the whole brochure stack. Not a generic "thank you for your interest".

It offers one next step. A site visit slot this weekend, or a question the buyer can answer in a word.

One more thing decides whether the message can be sent at all: consent. The developer collects it when the lead enquires, on the portal form, the ad form or the walk-in sheet. Follow-ups go only to buyers who agreed to hear from the project, and every sequence respects an opt-out the moment it arrives.

How often should you follow up without becoming spam?

Every presales team eventually automates WhatsApp, and most discover the same thing. Reply rates on blast messages collapse within weeks and a few buyers block the number. The usual conclusion is that buyers dislike automation. The evidence says otherwise: buyers dislike messages that ignore what they just did.

Most sequences are schedule-based. Day one, day three, day seven, the same messages for every lead regardless of what the lead is doing. Behaviour-based follow-up inverts this. The message goes out because of something the buyer did, and it carries what the buyer asked for.

Five triggers that earn a message or a call:

• The buyer asks about price or the payment plan in a reply. Send the payment plan and offer a call.
• The buyer is active on the project page several times in a day. Alert the rep: this is the call to make today.
• The buyer goes quiet for a week after asking questions. One soft check-in about the unit they asked about.
• The buyer comes back to the project page after weeks of silence. Alert the rep the same day.
• The buyer brings the family into the decision. Alert the rep: this is the call to make, and offer a weekend visit for the family.

A message triggered by behaviour arrives as help, not as marketing. That is why it gets a reply.

Then the rule on volume. Count unanswered messages, not total messages. Two consecutive messages with no reply is the signal to stop and hand the lead to a human decision: one call, or park it. Sequences that keep firing into silence get numbers blocked, and a blocked number is lost for every project the developer launches next.

Which buyers should you prioritise, and how do engagement signals help?

On paper, calling every lead feels right. More calls, more conversations, more site visits. In practice, three things happen.

Attention spreads thin. Curious buyers, comparing buyers and buyers nowhere near a visit all get the same effort, paid for by the one who was ready this week.

Context gets dropped. Volume forces standard scripts, and the buyer hears what they heard last time.

The ready buyer gets called late. On a queue, timing is accidental: the buyer evaluating right now is reached next Tuesday, the one who is not ready is called four times.

The cost of calling blind never shows up in the activity report. It shows up in a site visit count that stays flat while the team gets busier.

The way out is a signal that separates "ready now" from "still thinking", and the clearest one is engagement with the project page. In the 10-project portfolio above, engaged buyers were 2.9x more likely to walk in: 16.6% of engaged buyers visited, against 5.8% of buyers with no signal. 37% of the buyers produced 62% of the site visits. A portfolio of 5 projects in Bengaluru showed a 4.2x gap (11.4% against 2.7%). A portfolio of 6 projects, also Bengaluru, showed 2.4x (19.5% against 8.2%).

The signals, strongest first:

• Asked about price, payment plan or availability in a reply.
• Came back to the project page a second or third time.
• Replied fast to a message.
• Opened the page once.

No signal yet is not a dead lead. The assistant keeps working it while the rep spends the morning on the top of the list.

What should the follow-up messages say?

Patterns, not scripts by day, each sent by the project's AI assistant, which says so. The project names are fictional.

Recap after the first call

Hi Rohan, this is Cedar AI, the AI assistant for Cedar Court. Thanks for speaking with Anita today. Here is the page for the three-bedroom units you asked about, with the price band and payment plan: [link]. Reply with any question and Anita will call you back.

Price band and payment plan

Hi Meera, Harbour AI here, the AI assistant for Harbour Heights. You asked about the payment plan, so here it is: [link]. Would a call from Suresh to walk you through it help? Reply YES and he will call within the hour.

Visit proposal with slot choice (after hours)

Hi Arjun, this is Meadow AI, the AI assistant for Meadowfield. Thanks for your enquiry tonight. Here is the walkthrough you asked for: [link]. Would you like to see the unit this weekend? Reply A for Saturday morning, B for Saturday evening or C for Sunday morning. Reply STOP any time to opt out.

Soft check-in after a quiet week

Hi Kavya, Northgate AI here, the AI assistant for Northgate Towers. It has been a week since you asked about the garden-facing unit. Anything you would like to know before you decide? One question is enough. Deepak will take it from there.

One-tap reschedule

Hi Rohan, Cedar AI here. Your visit to Cedar Court is set for Sunday morning. If the time no longer works, reply with a new day and time and I will update it. Anita will meet you at the gate.

Three rules run through all five. Name the assistant as AI. Refer to what the buyer asked for. Offer one next step with a named human attached. And tell the buyer how to opt out, once per sequence, in plain words.

Which follow-up mistakes push buyers away?

Four show up in almost every audit of sent messages; the CRM automation mistakes post covers the wider set.

• "Any update?" It asks the buyer to do the work. Say what is new: a slot, a price, an answer.
• Blasting the brochure stack. Five PDFs and no answer to the one question the buyer asked.
• Ignoring what the buyer said last time. Budget and timing came up on the call; the next message pitches a different configuration.
• Sending into silence. Two unanswered messages is the stop sign. The third gets the number blocked.

When does the human take over?

Automation handles timing and context. Humans handle conversation. The assistant opens the door with the recap, the nudge or the slot proposal; a named rep walks through it within minutes when the buyer replies. A buyer who replies and then waits four hours for a human has had the worst of both worlds.

The handover rule in full:

1. The assistant introduces itself as "<Project> AI", the project's AI assistant. It never pretends to be the rep and never signs with the rep's name.
2. It carries the project page, answers factual questions and proposes the visit.
3. A reply, a question about price, or a request for a person puts the lead on the rep's phone within minutes, with the context the buyer already gave.
4. The assistant stops after the number of unanswered messages agreed with the developer, for example two. The lead goes back to the rep for a decision.
5. The rep confirms the visit. The assistant handles the reminder and the reschedule.

In the 10-project portfolio, 523 re-engaged leads had still not visited at the cut-off. They need a conversation, not another message.

How do you measure follow-up to site visit?

Five numbers, reviewed once a week. None of them is a call count.

1. Share of new leads that got a first message within minutes.
2. Reply rate to that first message.
3. Share of buyers who engaged with their project page. The two portfolios that measured it saw 36.7% and 27.7%.
4. Lead-to-visit rate for engaged buyers against buyers with no signal. The gap was 2.9x, 4.2x and 2.4x in the three portfolios.
5. Time from link to visit. Median 2 days, 77% inside a week, in the 10-project portfolio. Half the attributed visits within 2 days in the 5-project one.

Then one number for the marketing head: the share of conducted site visits that came from engaged buyers. In the 5-project portfolio it rose from 6.4% in month one to 16.5% in month two and 17.9% in month three. Nearly 1 in 5 visits. It says the system works before the site visit numbers move.