Guide · Qualify on WhatsApp

How to qualify buyers on WhatsApp

Five questions in order — BHK, then budget, then locality, then timeline, then slot — before you spend a broker Saturday. A WhatsApp ‘hi’ from MagicBricks is not qualified. If the agent offers inventory first, you will fill the site with browsers and miss the 1.5-crore 3BHK who could have come at 11:00 with a cab.

Order beats charm
Write fields, do not ‘remember’ them
Slot last, after fit

Start free Lead qualification playbook

Definition

WhatsApp qualification is a short, ordered interview on the live customer-care window that captures BHK, budget band, preferred locality or project, occupancy timeline, and a visit slot, then writes those fields on the CRM contact and moves the deal from New enquiry to Qualified when the answers fit inventory — or parks the contact honestly when they do not.

Why ‘send brochure’ fails as qualification

Portals dump a name and a project click. Brokers reply with a PDF. The buyer never states budget. Saturday arrives with six families who wanted 2BHK rental. The Insights cue about Saturday saturation is an operator warning, not an auto-fix: you still have to stop offering slots to unfit chats.

WhatsApp also expires. If you spend the 24-hour window on a brochure dump, the follow-up that asks budget may need an approved library template. Qualify in-session while free text still works.

HowTo: five questions in order

The conversation agent on WhatsApp should refuse to book until the first four answers exist as contact fields. Knowledge bases answer inventory FAQs after BHK and budget, not before.

BHK 2 / 3 / 4. If they say ‘villa or plot,’ branch — do not keep a 3BHK script.
Budget including charges Ask all-in. A 1.2 quoted as 1.6 with stamp is how visits explode later.
Locality or project constraint One cluster. Brokers: which of our listed projects. Developers: which tower/stack they already clicked.
Timeline Ready vs 18 months. NRI timezone comes later; first get occupancy intent.
Slot + pickup Appointments/calendars. Confirm cab only after fit. Then move Qualified.

How it runs on the platform

RE Qualifier is a conversation agent. It is not a Growth drip and not an autonomous list task. 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: 99acres click at 10:07

Lead lands New enquiry from portal CSV or webhook you configured. Qualifier on WhatsApp asks the five questions. Buyer says 3BHK, 1.5 Cr, Whitefield, 6 months. Agent cites the knowledge base stack (not a generic 3BHK). Calendar offers Saturday 11:00. Operator sees the thread in inbox. Stage → Qualified, then Site visit booked when the slot confirms. If budget is 70 L against a 1.8 Cr tower, the agent says so and does not burn a Saturday slot.

If the window closes before question four, send an approved utility or marketing template that re-opens with ‘reply 3BHK or 2BHK’ — do not free-text. See the 24-hour window guide. Wallet meters the template send.

Question × field × stage

Map chat answers to CRM fields so the RM does not re-ask on the call.

Question	Write on contact	If missing	Stage effect
BHK	BHK custom property	Ask once more, then park	Stay New enquiry
Budget all-in	Budget band	Do not send price list yet	Stay New enquiry
Locality / project	Preferred cluster	Offer two options max	Stay New enquiry
Timeline	Occupancy window	Assume ‘exploring’ if vague	Qualified only if inventory matches
Slot	Appointment	Wait — do not fake a booking	Site visit booked after confirm

Honest limitations

‘Interested’ is not a first-class CRM state; a reply is not a qualification (G6). Campaign conversion is reply rate. The agent will not auto-stop drips when Qualified. You configure workflows if stage change should silence a campaign. SMS is not a live qualifier hop.

Keep this Qualify on WhatsApp 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 Setup → Channels → WhatsApp (Gupshup). Agents → Studio → qualifier skill + knowledge base. Agent router. Customers → Pipeline (New enquiry → Qualified). Appointments for the slot. Inbox for RM handoff. Canonical playbook: Lead qualification 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.

Brokers vs developers

Developers qualify against one project knowledge base. Brokers need either per-project files or honest ‘I will check two inventories.’ See developer vs broker scripts. Scoring from BHK and budget is a sibling: lead scoring. Overlay: WhatsApp for property.

Frequently asked questions

Operators who currently dump PDFs into WhatsApp.

Can the qualifier send the brochure first to ‘warm them up’?

It can, but you will waste the 24-hour window. Attach brochure after BHK and budget, from the knowledge base or library, then continue questions.

What if they only reply with a voice note?

Phone/STT is a different hop (Visit Caller or inbound voice). On WhatsApp, ask them to type BHK and budget or offer a Plivo call. Do not treat any speech as ‘interested’ by default.

Does qualification equal site visit booked?

No. Qualified means fit. Site visit booked is a calendar confirm. Pipeline stages are separate.

Where does the RM take over?

Omnichannel inbox handoff when objections, discounts, or NRI documents appear. Pass the five fields — see the RM handoff checklist guide.

Library templates during qualification?

Inside 24 hours, free text is enough. Outside, use an approved template. Autonomous tasks cannot create that template for you.

Wallet impact?

Inbound replies are metered per channel rates. Template re-opens cost more than in-session text. Preview the Organization wallet. Pricing has the markups.

Hub, sibling guides, canonical playbook, product, pricing.

Qualify before you gift a Saturday

Put RE Qualifier on Gupshup WhatsApp, write the five fields, then offer a calendar slot.

Get started free