Summarise this article with:
On this page
- Real estate lead management on WhatsApp: the lifecycle map
- Qualification and routing: a Flow instead of a phone screen
- Site visits: reminders, and the warm follow-up call
- The real estate WhatsApp template set
- Broker-network broadcasts and the quality-rating risk
- What to measure
- What most real estate teams get wrong
- Get started with InfiQ
Ask a sales head at a Pune developer where the leads go and you get a confident answer about the CRM. Ask what happened to the 99acres enquiry that landed at 9:40pm on Saturday, and the answer changes. It sat in a portal dashboard, reached an inbox nobody reads on weekends, then went into a WhatsApp group of six channel partners on Monday, where two of them called the same buyer four minutes apart.
That is the sector's real problem, and it is not lead generation. Indian real estate buys leads well, responds to them badly, and loses them in the handoffs. A personal-phone process has no institutional memory either: when a sales manager resigns, every live buyer's history leaves with them.
Doing this on the WhatsApp Business API is a different exercise from doing it on personal phones. The first message to a portal lead is business-initiated and needs an approved template. Site-visit reminders have a cost category. And a broker broadcast can damage the number you send everything else from.
Key points
- A portal enquiry from 99acres, MagicBricks or Housing arrives as a phone number, not an inbound WhatsApp message, so first contact needs a Meta-approved template.
- A WhatsApp Flow is a multi-screen interactive form inside the chat, supported on Android 6.0+ and iOS 12+, that collects budget, configuration, locality, timeline and loan need in one submission.
- Site-visit confirmations and reminders are utility templates, and utility messages inside an open 24-hour customer service window are free until 1 October 2026, when Meta resumes charging.
- Business-initiated WhatsApp calling is supported in India, with the daily limit raised to 100 calls per day in December 2025, so the warm post-visit call runs on your chat number.
- Broker broadcasts carry real estate's biggest quality-rating risk, because channel partners sit on many builders' lists and quality rating moves on blocks and report taps, not delivery.
Real estate lead management on WhatsApp: the lifecycle map
Leakage here is structural. One enquiry crosses four or five systems owned by different people, and each transition drops the timestamp, the source, the configuration asked about, or the buyer. Assignment usually happens on a schedule rather than on arrival, which produces the state every funnel report hides: assigned but not answered.
| Stage | WhatsApp touchpoint | Message type |
|---|---|---|
| Enquiry created | Acknowledgement naming the project enquired about, inside 60 seconds | Template if portal-sourced; free-form if the buyer messaged first |
| Qualification | Flow: budget, configuration, locality, possession timeline, loan need | Interactive, inside the open window |
| Routing | Named sales manager introduces themselves, then sends the floor plan their answers imply | Free-form reply and media |
| Site-visit booking | Slot picker showing only windows your team can staff | Interactive |
| Confirmation | Date, time, tower, contact person, map pin, reschedule button | Utility template |
| Reminders | T-24h with what to bring; T-2h with directions | Utility template |
| Post-visit | Same-evening summary of units seen, then a warm call next day | Free-form, then Calling API |
| Booking | Cost sheet, payment schedule, receipt | Utility template plus documents |
| Post-booking | Construction milestones, demand letters, registration, possession | Utility template |
Read the message-type column as the cost and compliance column. A message that starts a conversation needs an approved template; a message sent while the buyer's own reply has opened a 24-hour customer service window can be free-form. Category — marketing, utility or authentication — sets the price, which the template categories guide covers.
The first message is business-initiated, and that changes everything
A portal enquiry gives you a name, a number and an interest, delivered to a dashboard. It does not give you an inbound WhatsApp message. So first contact with a 99acres or MagicBricks lead is business-initiated: it needs an approved template, it counts against your messaging limit, and its category is set by its content.
Teams get this wrong by writing a first-contact template that reads like a brochure — three configurations, a price band, an amenities list — then finding it categorised as marketing, or reclassified later. Meta has run auto-recategorisation since 1 July 2024, usually moving utility to marketing, and since 16 April 2025 repeat offenders get no advance notice. Penalties escalate from a warning to rate limiting for at least 7 days, then a utility restriction of 7 to 30 days, then a portfolio-wide restriction of 30 days. Write the template as what it is: one enquiry acknowledged, one question attached.
Consent is separate. A portal form gives you details to answer that enquiry, not permission to broadcast your other projects next month. India's DPDP regime requires valid consent with a notice of purpose, so ask for marketing opt-in explicitly while the buyer is engaged — the opt-in and DPDP guide has the mechanics. This is not legal advice; take your own.
Qualification and routing: a Flow instead of a phone screen
A tele-caller asking five questions works, costs money, and fails on most leads because they do not answer an unknown number. A Flow replaces the phone screen with a two-minute in-chat form the buyer completes at 11pm if that is when they are looking.
| Flow field | Why it decides what happens next |
|---|---|
| Budget band (single-select ranges, never free text) | Maps the buyer to a project and configuration you actually have |
| Configuration (1BHK / 2BHK / 3BHK / 4BHK+ / plot / commercial) | Sets available inventory and which floor plan you send |
| Preferred locality (single-select, your real micro-markets) | Routes to the team sitting at that site |
| Possession timeline (ready / 12 months / 12–24 months / investment) | Separates urgent buyers from watchers |
| Loan requirement (pre-approved / needs a loan / self-funded) | Triggers the banking desk now instead of at booking |
Five single-select screens submit as one structured payload: fewer messages than a bot asking five questions across ten turns, fewer drop-off points, and clean data instead of free text to parse. Non-endpoint Flows hold their logic client-side and suffice for static option lists; endpoint Flows call your own HTTPS server, which is what a slot picker reflecting live availability needs. The WhatsApp Flows implementation guide covers that choice and the version tracks where drift breaks Flows in production, and InfiQ Flows builds one by drag-and-drop rather than hand-authored Flow JSON.
The round-robin problem
Round-robin routing is a rule that assigns each new enquiry to the next salesperson in a fixed rotation, regardless of availability, language or project fit. It is fair and auditable, and it is why leads sit unanswered: it optimises for equal distribution, not speed of first human response. A Kannada-speaking buyer asking about a Whitefield project goes to whoever's turn it is, who is on a site visit in Sarjapur and opens the thread three hours later. The report says every lead was assigned inside a minute, which is true and useless.
Three changes fix it. Automation answers inside 60 seconds and runs the Flow, so the buyer is engaged whoever is awake. Routing then works on skills — project, locality, language, budget band — with an acceptance SLA and automatic reassignment on breach. And the shared inbox, not anyone's phone, is the record, so an unanswered thread is visible to a manager. Never route a lead to a personal number, even temporarily: you lose the record and control of what was promised.
Site visits: reminders, and the warm follow-up call
The site visit is the conversion event in residential real estate, and the no-show is its tax. Most no-shows are not lost interest. They are Sunday logistics, an unconfirmed slot, or a buyer who could not find the tower gate.
A utility template is a template message whose content is limited to a transaction the customer already initiated — a confirmation, reminder, receipt or status update. Site-visit messages sit there, as long as offers stay out. Add "and get ₹50,000 off if you book on the visit" and you have written a marketing template, at marketing rates, with a marketing consent requirement.
- Offer slots rather than asking preferences. A slot-picker Flow showing three or four staffable windows beats "when would you like to visit?", which turns every answer into a negotiation.
- Confirm immediately in one utility template: date, time, project, tower or gate, the name and number of the person meeting them, and a map pin.
- Put the reschedule button in that same message. Reopening the slot picker turns a would-be no-show into a moved appointment.
- Remind at T-24 hours, including what to bring. ID for site entry is common, and learning that at the gate is a poor first impression.
- Remind at T-2 hours with directions. This is the one that reduces no-shows, because it lands while the decision to leave the house is being made.
- Log arrival in the thread. A sales manager marking the visit attended is what makes your funnel numbers real.
- Summarise the same evening, naming the units seen and the single next step, free-form inside the open window.
- Send assets one page at a time. The floor plan for their configuration beats a 40MB brochure, and versioning matters because a price sheet sent in March is a commitment you will be asked about in June.
Timing decides cost. Utility templates and non-template messages sent inside an open 24-hour window are currently free under the per-message model that replaced conversation pricing on 1 July 2025. A T-24h reminder to a buyer who last replied three days ago is outside that window and billed at the India utility rate. From 1 October 2026, Meta resumes charging for service messages and for in-window utility messages, both free today, per Meta's non-template messages documentation.
The warm call, on the same number
The WhatsApp Business Calling API provides VoIP voice and video calling with screen sharing over Cloud API, on the number that already carries your messaging. Business-initiated calling is available everywhere except the USA, Canada, Egypt, Vietnam and Nigeria — India is supported. The daily business-initiated limit rose to 10 per day in October 2025 and 100 per day in December 2025, and G.711 codec support arrived in March 2026. Calling is priced separately from messaging.
The pattern is narrow: chat first, escalate with context, never cold-call. The day after a visit the sales manager writes in the existing thread — "Can I call at 6pm about the 3BHK in Tower C you saw?" — then calls from a recognised number at an agreed time. Screen sharing does what a phone call cannot, walking a buyer through a floor plan or payment schedule while both of you look at the same document. It earns its place on post-visit follow-up, cost-sheet and loan-eligibility calls, and NRI buyers. It does not earn its place on cold outreach, and 100 calls a day is a capacity limit, not a tele-calling quota.
The real estate WhatsApp template set
Categories below follow Meta's rule that content, not intent, decides category. Verify each at submission, because the call is Meta's.
| Template | Likely category | Note |
|---|---|---|
| Enquiry acknowledgement | Marketing in most phrasings | A price band or amenities list makes marketing certain |
| Qualification nudge | Utility if it references their own enquiry only | Send once, not as a drip |
| Site-visit confirmation | Utility | The highest-value template in the set |
| Reminders at T-24h and T-2h | Utility | Include a reschedule button in both |
| Cost sheet and payment schedule | Utility | State GST and charges treatment explicitly |
| Booking confirmation and receipt | Utility | Attach the receipt document |
| Demand letter or payment due | Utility | High-value, low-risk automation |
| Construction milestone update | Utility | Builds trust across a three-year build cheaply |
| New launch announcement | Marketing | Requires an explicit marketing opt-in |
| Broker inventory update | Marketing | See the quality-rating section below |
Watch the caps: 250 templates per WABA if the parent business portfolio is unverified, 6,000 if verified with an approved display name. A multi-project developer running localised variants reaches 250 sooner than expected. Avoid duplicate content too, since the same body plus footer wording as an existing template is a standard rejection reason, exempted only for authentication templates.
RERA-conscious communication: good practice, not legal advice
Every message above is a communication from a promoter or agent about a registered project. What follows is operational good practice, not legal advice — clear your communication design with your own counsel and your state RERA authority's requirements.
- State facts, not projections: carpet area as registered, possession date as per the registered agreement, price with charges and GST treatment stated.
- Do not promise yield or appreciation. Remove "assured returns", "guaranteed rental yield" and "prices will rise after launch" from every template; they also fail Meta's review often enough to be a practical problem.
- Carry the project registration reference where your promotional communication requires it, and keep the creative version that carried it.
- Control what channel partners send under your brand. A broker forwarding an unapproved creative with an inflated claim is a risk you carry.
- Keep the record. A shared inbox makes every commitment retrievable with a timestamp and an agent name, and the DPDP Rules require notices stating purpose and retention.
Broker-network broadcasts and the quality-rating risk
The broker broadcast is the use case real estate teams reach for first and regret fastest. A developer with 400 channel partners wants weekly inventory and pricing pushed to all of them. The information is valuable and the recipients are business contacts, so it looks safe.
It is not, for one reason: a channel partner is on twenty builders' lists. Their WhatsApp is already full of this exact message, and the cheapest response available is to mute, block or report. Quality rating is driven by user feedback rather than delivery success, so a broadcast that reaches every recipient can still move a number from GREEN to YELLOW, whose documented meaning is that it "may soon be paused or disabled". A template that hits low quality is paused 3 hours, then 6 hours, then disabled. The WhatsApp quality rating guide has the recovery runbook.
A second ceiling catches broker broadcasts specifically. WhatsApp dynamically caps how many marketing templates any single user receives across all businesses, based on that user's recent read rate and inbox load, per Meta's per-user marketing limits documentation. It is not a fixed number, it adapts, and India is not excluded. A broker saturated with builder marketing is exactly the profile that gets capped. Throttled sends return error 131049, and retrying inside 24 hours risks further failures.
Four things reduce the risk. Take an explicit opt-in per partner per micro-market and honour opt-outs immediately. Keep buyer transactional messaging and broker promotional messaging on separate numbers, noting that messaging limits sit at business-portfolio level and are shared across numbers, so separation buys quality isolation rather than extra headroom. Segment by micro-market, because a Wakad update sent to brokers working only in Kharadi is noise, and noise gets reported. And invert the model where you can, letting brokers pull inventory through a Flow or keyword instead of pushing weekly — the WhatsApp broadcast guide covers list hygiene, and per-number quality monitoring belongs on the checklist in the guide to choosing a WhatsApp Business API provider in India.
What to measure
Real estate reporting is full of numbers that move nothing: leads generated, calls made, messages sent. What changes revenue is timing and stage conversion, measured per source.
| Metric | Where teams get it wrong |
|---|---|
| Median time to first response | Reporting the mean, which one automated batch flatters |
| 90th-percentile time to first response | Not measuring it, which is where weekend leads live |
| Flow completion rate | Counting opens instead of submissions |
| Assignment to first human reply | Treating assignment as engagement |
| Visits booked per qualified lead, by source | Averaging portals together and hiding the weak one |
| Visit confirmation and attendance rate | Not logging attendance, so reminders have no scorecard |
| Cost per qualified lead, by source | Using cost per lead, which every portal optimises for |
| Opt-out rate per segment and quality rating per number | Discovering YELLOW from a failed send |
There is no verified India benchmark for WhatsApp response rates, lead-to-site-visit conversion or booking conversion in real estate, and the figures circulating in vendor content are unsourced. Build a four-week baseline of your own, name the vendor if you cite one internally, and prove the mechanism instead of assuming it: run the full reminder sequence on a random half of next month's site visits and compare attendance.
Worked example: a hypothetical Pune developer
Take a hypothetical developer with two live projects receiving 4,000 enquiries a month — 2,600 from 99acres, MagicBricks and Housing, 1,000 from Click-to-WhatsApp ads, 400 from the website and hoardings. Every number is illustrative; replace each with your own.
Assume 900 site visits get booked, each carrying three utility templates, plus one reschedule confirmation on the 200 visits that move.
- 900 visits × 3 templates = 2,700 utility templates
- Plus 200 reschedule confirmations = 2,900 utility templates a month
Assume 1,000 land inside an open 24-hour window and 1,900 outside it. Today only the 1,900 are billed. From 1 October 2026 the same pattern bills all 2,900 — a 53% increase in chargeable volume with no change in what the team does. Utility rates fall at higher monthly volumes, with tiers applied per market–category pair across the portfolio and reset monthly. At the current India utility rate of ₹0.19 per delivered message (ex-GST), those 2,900 newly-chargeable messages run about 2,900 × ₹0.19 a month.
Then add first contact: 2,600 business-initiated messages, billed at the highest of the four category rates if that template is categorised as marketing rather than utility. Rewriting one template as a factual acknowledgement rather than a mini-brochure is the difference between 2,600 marketing-rate and 2,600 utility-rate messages every month. Pull Meta's current rate card or use InfiQ's cost calculator before you budget, and the 2026 pricing guide explains the two-layer bill this arithmetic sits inside.
What most real estate teams get wrong
| Mistake | The fix |
|---|---|
| Treating portal leads as inbound conversations, so first contact fails or ships as marketing | A factual first-contact template: acknowledge, ask one question, pitch on the reply |
| Distributing leads in a broker WhatsApp group | Rules-based assignment with an acceptance SLA and automatic reassignment |
| Pure round robin, then reporting assignment speed | Measure assignment to first human reply, not assignment |
| Letting agents work from personal numbers | One business number, shared inbox as the record of what was promised |
| Verbal site-visit confirmation only | Confirmation plus T-24h and T-2h reminders with a reschedule button |
| Putting an offer inside a reminder template | Keep offers in separate, opted-in marketing templates |
| Broadcasting inventory to every broker weekly | Opt-in per micro-market, segment, cap frequency, or let brokers pull via a Flow |
| Cold-calling because the Calling API allows 100 a day | Ask in chat, call at an agreed time, share your screen |
The through-line: real estate teams buy WhatsApp as a broadcasting tool and then discover it is a response-time tool. Nearly all the value sits in the first 60 seconds and the 48 hours around a site visit.
Get started with InfiQ
Real estate does not have a lead-volume problem. It has a Saturday-night problem, a broker-group problem and a Sunday-morning no-show problem, and all three are response and record problems. The teams that win the enquiry are rarely the ones with the better brochure.
Ready to answer every portal enquiry in under a minute? Start your 7-day free trial — InfiQ gets you live on the official WhatsApp Business API in about 2 hours, with InfiQ Flows for in-chat qualification and a shared team inbox that routes each lead with its answers attached. Or book a walkthrough if you want it mapped to your own projects and channel-partner network first.
