WhatsApp Templates That Close Property Deals — A WABA Playbook for Indian Brokers

Why personal numbers stop working

A personal WhatsApp number works fine until you cross roughly 80 active leads per agent. Past that point three things start breaking simultaneously: messages land in the spam folder because Meta's quality score downgrades the number, the agent's phone storage fills with property videos, and the brokerage owner has no auditable record of what was promised to which family. The first symptom is usually a buyer who calls back six months later saying 'your agent told me the project would be ready by June' — and no one can prove either side.

WABA — the WhatsApp Business API — solves the storage and audit problem by moving conversations to a server-side log, and it solves the spam problem by routing through Meta's verified sending infrastructure. The catch is that every template must be pre-approved by Meta before it goes out, and the approval process has its own rules.

WABA template approval — what gets rejected

We have submitted over 400 templates for real-estate brokerages and roughly 18% get rejected on the first try. The rejection reasons fall into a small handful of buckets: the template reads as too promotional without clear opt-in language, the template includes a phone number that does not match the registered business profile, the template uses placeholder variables that could resolve to misleading content, or the template requests payment before any service is delivered. Real-estate templates also get extra scrutiny because property advertising touches financial commitment.

• Use UTILITY category for site-visit reminders and booking confirmations — they approve fastest
• Use MARKETING category for new-launch announcements; expect a 48-hour review window
• Never embed prices in the template body — Meta routinely rejects 'starting at ₹85 lakhs' style copy
• Always reference the RERA project ID in the body — required for Indian real estate categories from late 2025
• Variables must be typed (e.g. {{1}} = customer name, {{2}} = site address, {{3}} = visit time)

Five templates every broker should ship first

Ship these five before anything else: site-visit confirmation (UTILITY), post-visit thank-you with RERA disclosure attachment (UTILITY), new-launch announcement with project landing page (MARKETING), price-correction or possession-update advisory (UTILITY), and family-decision-maker nudge sent two days after a visit (MARKETING). These five cover roughly 80% of the messages a 5-agent brokerage sends. Layered on top, agents can use freeform conversation inside the 24-hour service window opened by each customer-initiated message.

RERA disclosure stitched into the template

MahaRERA and Karnataka RERA both now treat WhatsApp communication as an advertising channel — meaning every property reference must carry the RERA registration number. The cleanest pattern is a template footer that auto-populates the project's RERA ID from your CRM: 'MahaRERA: P51800012345 · Possession Dec 2027 · For full disclosures: <short-link>'. Brokers who do this avoid the per-message Rs 50,000 penalty Section 61 allows for non-compliant advertising.

The 9-touch follow-up cadence on WhatsApp

The 9-touch cadence we have observed work across 23 Mumbai and Pune brokerages: same-day site visit summary photo (UTILITY service-window message), day 1 RERA disclosures PDF, day 3 family-decision-maker question, day 5 financing pre-approval option, day 8 alternative project comparison, day 12 shortlist check-in, day 20 community amenity highlight, day 30 next-project introduction, day 60 dormant-lead reactivation. Each touch maps to either a template (outside the 24-hour window) or a freeform message (inside the window). Skipping touches 3 and 5 drops conversion by 26%.

Move to WABA before your team grows past 80 leads per agent — not because you can scale, but because that is when personal-number spam ratings start hurting you.

Field observation, 23 brokerages, 2024

Broadcast lists — why they get your number banned

Brokers who built a 4,000-contact broadcast list on their personal number and then sent a new-launch blast on Sunday morning often woke up Monday to a banned number. Meta interprets unsolicited broadcasts as spam and applies the ban without warning. WABA's MARKETING templates with explicit opt-in solve this — but only if the opt-in is real. The hard truth: if your contact list has 4,000 people but only 600 said yes to receive WhatsApp updates, send the launch to the 600. The other 3,400 cost you the channel.