Conversation agent
Knowledge + appointment skill. Router keeps luxury RM bots off mass housing cards if you configured it.
Qualified means four fields — then you may spend a Saturday
Qualified means BHK, budget, locality, and timeline are on the deal before a broker spends a Saturday slot. Insights will later blame Saturday-slot saturation when too many “qualified” buyers were never actually qualified. This page is the column, not the qualification playbook and not the WhatsApp overlay. Growth also has a Qualified leads bar — that count is campaign analytics, not a promise this kanban card is clean.
- Four fields on the Booking
- Then offer slots
- Router by stage
Brokers fly to site with a name and a portal screenshot
Teams mark Qualified because someone replied “interested” on a launch teaser. Conversion_rate in campaigns is still reply rate. Phone “replied” is speech after the script, not budget confirmation. If the appointment skill offers Saturday 11 to everyone in this column, Insights’ real-estate narrative is exactly what you will see: fewer qualified buyers converting to site visits — Saturday-slot saturation and missing pickup details. Fix capacity on the calendar; do not ask autonomous tasks to stop when a visit is booked — they cannot.
Qualify, then hop to calendar
WhatsApp qualify + brochure, then phone to schedule. Qualified is the CRM gate between those hops.
- Read the four fields If any are missing, the card still belongs in New enquiry.
- Match inventory Knowledge base floor plans. Humans still pick the tower if two 3BHKs exist.
- Offer slots Appointment skill. Pickup note on the Booking. Sunday mornings if Saturday is full.
- Exit Move to Site visit booked when the calendar event exists — not when they said “maybe Saturday.”
How it runs in CoPulse
Conversation agent plus appointment skill. A drip that says “are you still looking?” is a different job (nurture), and it is not adaptive — you set the steps. Workflow on enter can notify the inventory owner. Autonomous win-back should not run on freshly qualified buyers.
Workflows
On enter: notify RM, set intent score custom property. On exit to visit booked: start reminder drip.
Growth drips
Only if they went quiet after qualifying. Clock-based, not smart send-time.
Inbox handoff
When they argue about floor rise or vastu, a human takes the thread.
Operator setup
Project calendars and pipeline names must agree with what brokers say on the ground.
Setup → Customers → Pipeline → Agents → Studio (qualifier + appointment skill) → Router → calendars under appointments → wallet for WhatsApp.
Whitefield 3BHK that was “interested” but not qualified
Launch campaign shows Replied. Ops refuses to move the card until the qualifier writes 3BHK / 90L / Whitefield / 60 days. Agent Studio knowledge sends Tower B plan. Appointment skill offers Saturday 11 and Sunday 10 because Insights already flagged Saturday saturation last week — the operator added Sunday, the model did not. Pickup from metro goes in the note. Workflow moves to Site visit booked when the calendar confirms. Visit Caller is the next stage’s job.
Click-path: Customers → Booking → stage Qualified; Agents → Workflows to see the enter trigger; Growth only if you are staring at campaign Qualified, which is a different number. Pricing stays wallet-only for the brochure send and later voice confirm.
Gate before the visit column
If exit is “they replied,” you are still on campaign analytics.
| Stage | Automation | Human | Channel hops | Exit criteria |
|---|---|---|---|---|
| Qualified | Slot offer, knowledge | Inventory / vastu exceptions | Calendar event created | |
| New enquiry | Qualifier | Dedupe | Four fields | |
| Site visit booked | Reminders + Visit Caller | Capacity | WhatsApp + voice | Showed |
| Campaign Qualified | Funnel bar | None | Launch | Not CRM |
Jobs that create real Qualified cards
Do not confuse this stage URL with a WhatsApp-only qualifier page — that overlay is a hop.
Frequently asked questions
What Qualified is allowed to mean in CoPulse.
Can the agent mark Qualified without a human?
Yes if a workflow or operator rule says the four fields exist. Do not key off campaign Interested — that state is not first-class yet.
Appointment skill here or next stage?
Offer slots here; the card becomes Site visit booked when the calendar holds the time.
Luxury desks?
Same four fields, tighter router, earlier inbox handoff. Do not skip qualification because the ticket size is high.
Adaptive nurture until they qualify?
Not shipped. Use a drip you authored or keep the conversation agent on the thread.
Meta Cloud WhatsApp?
Catalog is Gupshup. Connect under Setup → Channels.
Does autonomous stop at Qualified?
No. Sends/reads only.
Related
Parent hub, sibling stages, CRM product, and jobs that move this column.
Real estate hub
Buyers & Tenants, Bookings, channels, and playbooks.
Back to hub →New enquiry
Previous column.
Open →Site visit booked
Where slots become commitments.
Open →Pipeline & CRM
Bookings kanban plus appointment records on the contact.
Product CRM →Wallet-only pricing
Brochure and slot WhatsApp messages debit the wallet.
See pricing →Stop spending Saturdays on unqualified names
Hold this column until four fields exist, then offer real calendar capacity — including Sunday if Insights already told you Saturday is full.
Get started free