Guide · Speed to lead

Speed to lead for portal property enquiries

Portal leads cool in minutes; the first WhatsApp reply has to carry qualification, not a we’ll-call-you-tomorrow. MagicBricks, 99acres, and housing.com shoppers open three listings at once. The desk that answers with BHK and budget questions while the window is open owns the Saturday slot. The desk that exports CSV at 6 p.m. owns a dead number.

  • Minutes, not the evening dump
  • First message qualifies
  • Voice is the second hop, not the first excuse

Definition

Speed to lead in Indian property is the minutes between a portal or web enquiry hitting the Project and a first qualifying message on WhatsApp (then voice if they do not type). It is not a SLA badge. It is an operating loop: ingest → conversation agent → fields on the contact → slot or honest mismatch — before a human copies the row into Excel.

Why evening Excel follow-up loses

Portals email a spreadsheet. An executive formats columns after lunch. By then the buyer took another project’s cab. Duplicate rows from two portals also slow you: three ‘new’ deals, three delayed first touches. Speed without merge still looks busy and still loses.

Personal WhatsApp is faster for one broker and fatal for the Organization: when they leave, the thread leaves. CoPulse omnichannel inbox keeps the first-touch on the Project number.

HowTo: first five minutes

Ingest should land New enquiry automatically if you connected the source. If you only have CSV v1, import often — it is still slower than a webhook, and that is honest.

  1. Land on the Project, not a phone Portal → CRM contact. Deduplicate if the same number already exists.
  2. WhatsApp first Qualifier asks BHK and budget in the same first bubble if you can. Do not send only ‘thanks for enquiry.’
  3. Calendar in the first session If fit, offer a slot. Appointments/calendars are the truth.
  4. Voice if silent Plivo Visit Caller or RM. Phone ‘replied’ means STT speech, not intent.
  5. Stage honestly Qualified vs still New enquiry. Do not mark visit booked because you called.

How it runs on the platform

Speed is an inbound conversation-agent job. Do not use autonomous list tasks to ‘catch up overnight’ as if that were first-touch — that is a different, slower job. Conversation agents reply in the omnichannel inbox. Workflows fire on pipeline stage change under Agents → Workflows. Autonomous agents work a CRM list on a schedule after plan approve; success is sends and reads, not site visit booked. Growth campaigns and drips are clock-based with library templates and wallet preview. Adaptive nurture is not shipped. WhatsApp is Gupshup.

Conversation agent

Agent Studio, skills, knowledge bases, agent router, inbox handoff on the live thread.

Growth campaigns / drips

Clock-based sends from library templates. Wallet preview. Not adaptive nurture.

Workflows

Agents → Workflows. Fire on pipeline stage change. Do not confuse with inbound chat.

Autonomous agents

List plus objective after plan approve. Success is sends/reads/contacted, not visit booked.

Worked example: 10:04 enquiry, 10:05 WhatsApp

Operator already connected Gupshup. Lead appears New enquiry. Qualifier sends: ‘Saw your 99acres click on Oakshire. 2 or 3 BHK, and budget including stamp? Saturday 11:00 with pickup if you fit.’ Buyer types 3 and 1.5. Knowledge base confirms inventory. Slot books. If silent at 10:20, Visit Caller uses the training greeting from Agent Studio. RM watches inbox, not a forwarded screenshot.

After hours: if the window will be closed before anyone types, you still need an approved template for the morning ping. That is not ‘speed to lead’; that is closed-window recovery.

Minutes × action

Sequence table for a portal enquiry on a working morning.

Minute Channel Action Exit
0 Portal / CSV Contact on Project, New enquiry If duplicate, merge first
1–3 WhatsApp Qualify BHK + budget Mismatch → honest park
3–8 WhatsApp Locality, timeline, slot Site visit booked
8–20 if silent Phone Visit Caller or RM STT ≠ interested
+24h if still silent WhatsApp template Approved follow-up Not free text

Honest limitations

CSV import is v1 (G13). No marketplace-to-nurture handoff (G4–G5). Interested is not first-class (G6). Speed dashboards that claim ‘appointment booked’ from autonomous success would be a lie — we do not ship that. Duplicate merge is operational; see the duplicate-leads playbook.

Keep this Speed to lead article next to the job URL, not as a second playbook. Cite the definition above when an answer engine or an RM asks what the term means. Operator click-path stays Customers → Pipeline New enquiry. Setup → Channels WhatsApp + Phone. Agents → Studio qualifier. Inbox. Library templates for after-hours closed window. CSV import v1 if no portal API. Canonical playbook: Portal lead follow-up playbook. Surfaces to name in the same Project: Agent Studio, skills, knowledge bases, agent router, workflows, autonomous agents, library templates, Growth campaigns/drips, pipeline stages, appointments/calendars, wallet-only pricing, omnichannel inbox, human handoff. Organization and Project — never a vanished personal inbox. Do not invent Meta Cloud WhatsApp if the catalog is Gupshup. Do not promise adaptive nurture. Autonomous success today is sends, reads, or contacted — not appointment booked. Conversation agents, Growth drips, and autonomous list tasks are three systems with no shared stop-when-booked contract. Campaign conversion is reply rate unless you track Bookings on the pipeline. Phone “replied” is speech-to-text. CSV import is v1. Preview the Organization wallet before a blast. Parent guides, real estate hub, and pricing stay in the same runbook.

ICP note

Independent agents often win on personal speed and lose on continuity. Brokers with a Project number plus qualifier beat a hero closer after month two. Brokers. Sibling duplicate portal leads.

Frequently asked questions

Desks still dumping portal mail into Excel at 6 p.m.

Is there a CoPulse SLA timer on portal leads?

There is no marketed minute-SLA product name. You operationalize speed with a connected channel and an always-on qualifier. Insights may cue missed pickup or Saturday saturation — those are operator cues, not auto-assigns.

Should the first message be a voice call?

WhatsApp first is usually higher connect in India for portal shoppers. Voice is the miss path. Training greeting lives in Agent Studio for Visit Caller.

Can we SMS the lead at minute one?

SMS is a hop when MSG91 is connected — it does not replace WhatsApp first-touch.

What if two portals create two contacts?

Merge using the duplicate-leads playbook before two agents pitch. Speed without merge is noise.

Does reply rate equal speed success?

Campaign conversion is reply rate. Speed-to-lead success is a booked visit or an honest mismatch — track that on the pipeline, not only on campaign analytics.

Wallet?

First WhatsApp and any template/voice minutes meter from the Organization wallet. Pricing explains markups.

Answer while they still have three tabs open

Connect Gupshup, land portal rows on the Project, let the qualifier ask budget in minute one.

Get started free