Blog / Real estate

Real estate leads: portal enquiry → WhatsApp in 60 seconds

A property buyer doesn't enquire on one listing. They enquire on five, on a Sunday evening, from the sofa. By Monday noon, the broker who replied first and clearly has the site visit — everyone else is a missed call. Real estate is the purest "speed wins" market in India, and it's also the one where most leads still sit in an email inbox until someone checks it.

This is the flow brokers, channel partners and small builders set up on Yantra: enquiry → WhatsApp inside a minute → site-visit slot → reminders → 30-day nurture, with the contact stage updating itself. Scripts are in Hinglish; rules keep you on the right side of RERA. (We build automation in Pune — half our early users sold flats in Wakad and Hinjewadi.)

Where the leads come from — and how to catch them

SourceHow it reaches the flow
99acres / MagicBricks / Housing / NoBrokerLead notification email or portal export → parsed for name, phone, project, budget (paid plans often offer CRM push/API — use it if you have it)
Meta / Google lead adsNative lead-form triggers — instant
Website / landing page formWebhook — instant
Walk-in / callReception adds a row (sheet or table) — same flow starts

Whatever the source, normalise into one contact record: name, phone, project interest, budget band, source, stage = new. Everything below reads and writes that record.

Message 1 — Instant acknowledgement + brochure (within 60 s)

Namaste {{name}} ji 🙏 {{project}} ke liye aapki enquiry mil gayi. Brochure aur floor plans attach hain 📎 Price range: {{price_range}} · Possession: {{possession}}. Site visit ke liye kab convenient hoga? 👇
[ Is weekend 🗓 ] [ Weekday shaam ] [ Pehle call karo 📞 ]

Utility template answering their own enquiry — attach the PDF brochure

Two rules: only quote prices/possession that are on the RERA-registered listing (the flow pulls them from your project table, so nobody improvises), and every message signs off with a real name and RERA number in the footer. "Pehle call karo" routes to an agent with a WhatsApp alert — the flow never pretends to be a human.

Message 2 — Site-visit booking + reminders

A tap on a slot creates a booking (calendar event for the agent, row in the visits table) and confirms:

Done ✅ Site visit: {{date}}, {{time}} at {{project}}, {{area}}. Location: {{map_link}}. Aapke liye {{agent_name}} available rahenge ({{agent_phone}}). Badalna ho toh yahin reply kar dijiye.

Reminder: kal {{time}} baje {{project}} site visit hai 🏢 Aa rahe hain na? 👇 [ Haan ✅ ] [ Reschedule 📅 ]

{{name}} ji, aaj {{time}} baje milte hain {{project}} pe. Sample flat ready hai 🔑 Location: {{map_link}}

This is the same confirm → 24h → 2h ladder we use for clinics and salons — no-shows on site visits drop for the same reason: most were forgetting, not rejecting.

Message 3 — After the visit (the step everyone skips)

{{name}} ji, aaj visit ke liye dhanyawad 🙏 {{unit}} ka detailed cost sheet attach hai (base + parking + GST + registration). Koi bhi sawaal — loan, payment plan, possession — seedha poochh lijiye. {{agent_name}}

Cost sheet the same day, while it's fresh. If they don't reply in 3 days, a gentle "koi update, ya kuch aur dikhaayein?" — then the lead moves to nurture, not to the trash.

Message 4 — The 30-day nurture (where slow buyers close)

Property decisions take weeks. A lead marked not now gets one useful message a week for a month — never a daily blast:

  • Week 1: home-loan eligibility calculator / bank tie-up rates
  • Week 2: construction progress photos (real ones, dated)
  • Week 3: a comparable unit that just got booked ("{{tower}} me 2BHK ka last corner unit gaya — aapka floor preference?")
  • Week 4: genuine, time-boxed offer if any (payment plan, not a fake discount)

These are marketing messages — opt-in required, and a "STOP" reply must silence the flow instantly (that's one route branch). Templates for these are in the 21 Hinglish scripts.

The owner's dashboard: 9am, one message

📊 Leads kal: {{new}} new ({{portal}} portal · {{ads}} ads) · {{visits_booked}} visits booked · {{visits_done}} done · {{hot}} hot. Sabse purani unanswered: {{stale_name}} ({{stale_hours}} hrs) — {{agent}}.

The last line is the accountability lever — nobody wants their name next to "unanswered 26 hrs".

What NOT to automate

Price negotiation, loan advice, and anything after "I want to book" — a human closes. Automation gets the buyer to the site on time with the right documents and keeps the slow ones warm; the agent does the rest. And never invent urgency ("only 2 units left") unless it's true — that's a RERA complaint and a lost reputation in one message.

Setting it up

Trigger (lead email/form/ads) → contact upsert → instant WhatsApp with brochure → route on reply → booking + calendar + reminders → post-visit → nurture. In Yantra that's a template plus your project table; or describe it — "portal se lead aaye toh 1 minute me brochure WhatsApp karo aur site visit slot poochho" — and Mantra builds it. Contact/stage tracking is the built-in Tables-as-CRM pattern; no separate CRM to start.

Be the broker who replied first

Start free — 1,000 runs. Lead triggers, WhatsApp buttons, calendar and Tables included.

Start free

Questions we get asked

Can portal leads reach WhatsApp automatically?

Via the lead notification email/export (or portal API/CRM push on paid plans) — parsed and messaged within a minute.

Is WhatsApping a portal lead allowed?

Replying to their own enquiry with an approved template — yes. Broadcasts need opt-in, STOP must work instantly, and RERA rules apply to every claim.

How fast to respond?

Minutes. First clear reply usually gets the site visit.

Do I need a real-estate CRM?

Not to start — a contact table with stage/source/budget, updated by the flow, covers a small team.