WhatsApp lead management for real estate: from enquiry to a visit request

Property buyers often want project details they can read later or share with family. WhatsApp can be useful for that exchange, but messages alone do not make a managed sales process.

A useful system keeps the buyer's question, project interest and next step together, even if a different executive handles the follow-up.

Avoid the brochure-and-silence pattern

Sending a large brochure may not answer the buyer's actual question. Start with the configuration or project they asked about, then point them to the relevant information.

Before offering a price, confirm which project and unit type it refers to. Before discussing possession, use the approved project-specific source. Do not infer current availability from an old marketing page.

Distinguish the routes into WhatsApp

A click-to-WhatsApp ad opens a WhatsApp chat with your business. A tracked Serviti link opens Serviti's hosted AI conversation. A WhatsApp handoff from the widget opens a human conversation.

Plan your campaign around the route you actually use. A QR code can link to your agent, but scanning it alone does not capture the person's contact details or book a visit.

Choosing the route per campaign

Different placements deserve different routes, and the decision is usually about who needs to be available.

Hoardings and print work well with a tracked agent link behind a QR. People scan these in the evening and at weekends, when your site office is closed, and the assistant can answer configuration and location questions immediately.

Performance ads for an active launch can use click-to-WhatsApp with the WhatsApp AI Agent add-on on Growth or Scale. Connect the destination business number for native replies and lead capture, with pre-sales available to take over. Without that add-on, staff or your existing system must reply. Check campaign attribution on the actual route rather than assuming every DM contains its source.

The project website should use the widget, with human handoff available on Growth for buyers who want a person.

Channel-partner links need distinct tracking per partner, or you will not be able to tell which relationship is producing enquiries.

Decide this before the campaign goes live. Changing the destination mid-flight makes the source data uncomparable.

Build a useful buyer handover

Capture preferences that help the team respond:

• Project and configuration.
• Budget range, if the buyer wants to share it.
• Buying timeline and purpose.
• Preferred visit time or callback request.
• Contact details and the original question.

Keep uncertainty visible. "Interested in Sunday" is different from "Sunday confirmed."

A handover template

Whatever system you use, the record an executive opens before calling should answer five questions without them having to ask the buyer:

Project / configuration : ..............................
What they actually asked : ..............................
Timeline & purpose       : ............ (as stated, not inferred)
Preferred contact time   : ..............................
Source                   : ..............................
Status                   : request | contacted | visit requested |
                           visit confirmed by staff | closed

The status line matters more than it looks. "Visit requested" and "visit confirmed by staff" being the same field value is how developers end up reporting site visits that never happened.

What Serviti can do

Serviti answers from the project content you supply and can capture a buyer's enquiry in the lead CRM. Campaign links help retain source context.

On Growth, the agent can offer human WhatsApp handoff and the team can receive real-time lead alerts. Scale includes Lead Intelligence and supported BSP integration. A BSP connection does not by itself turn every WhatsApp conversation into a native AI conversation.

Serviti can collect a site-visit request; it does not automatically reserve a live calendar slot. Staff must check availability and confirm the visit. Follow-up reminders for your team are not an automatic customer messaging sequence.

An illustrative exchange

The following is a hypothetical conversation written to show the boundary between a request and a confirmation, not a customer transcript.

A buyer asks on Saturday evening about 3BHK availability and says they could visit on Sunday.

Overpromising: "Your site visit is confirmed for Sunday at 11 AM." Nobody has checked the schedule. If Sunday at 11 is already full, the buyer arrives to a queue or an apology.

Honest: "I've noted your interest in a 3BHK and a preferred visit on Sunday morning. Our sales team will confirm the time with you — they work from the live schedule. Is this the best number to reach you on?"

The second version sets an expectation the team can meet. It also gives pre-sales a reason to call on Sunday morning with something useful to say.

Keep the company record up to date

Assign the lead, record whether the buyer was reached, and update the outcome after a visit. That makes the next interaction useful and reduces dependence on one executive's memory.

For post-sale support, the AI HelpDesk add-on can capture issues and answer approved FAQs. It should not claim to have checked a buyer's payment or title records without an actual supported connection.

Common questions

Should we run click-to-WhatsApp ads or send traffic to the agent? It depends on the connected channel and your campaign. Click-to-WhatsApp can reach the native AI agent when its add-on is enabled for your business number; otherwise your team or existing system must reply. A tracked agent link opens a browser conversation. Test answers, lead capture and available attribution on the route you choose.

Does a BSP integration mean AI replies on our WhatsApp number? BSP integration alone does not activate AI replies. Native customer conversations require the separate WhatsApp AI Agent add-on on Growth or Scale and a connected business number. Your team can take over when the buyer needs a person.

Can the assistant tell a buyer which units are still available? Only if that is in your approved content and current. A website knowledge base is not a live inventory feed. For anything that changes daily, the assistant should say it needs confirmation and route the buyer to your team.

How do we stop leads living on one executive's phone? Route enquiries through a tracked link or the widget so they land in the CRM with context, and make the status field mandatory. The technical part is easy; the discipline of recording outcomes is what actually fixes it.

What should we measure? Four separate numbers: enquiries received, buyers actually reached, visit requests, and visits confirmed by staff. Collapsing these into "leads" is what makes campaign comparisons meaningless.

Read next: real estate lead leakage and the follow-up checklist.