Conversation agent
RE Qualifier skills: intent, budget, locality. Handoff to the assigned broker with full thread. Router can split by locality or listing.
Portal speed-to-lead without personal WhatsApp chaos
Brokers stop losing portal leads in personal WhatsApp and instead qualify BHK, budget, and locality in a shared inbox before the site visit. CoPulse keeps Buyers & Tenants on a Booking pipeline so the desk, not one agent's phone, owns the thread.
- Shared inbox
- Multi-project qualify
- Visit confirmation calls
Personal WhatsApp is not a brokerage
Portal leads expire in minutes. When they land on a personal number, the firm cannot audit SLA, cannot hand off, and cannot train a qualifier on multiple projects. A shared omnichannel inbox plus Agent Studio means the first reply still feels fast, but the Booking lives on the Project. Multi-project brokers need knowledge bases per listing cluster — not one hallucinated inventory.
Omnichannel journey
Portals and web forms in, WhatsApp qualify across listings, voice to confirm the visit, email for the weekly digest of saved searches.
- Portal and web 99acres, MagicBricks, Housing, and your site create enquiries. Duplicate detection belongs on new enquiry so three portals are not three RMs.
- WhatsApp Qualify BHK, budget, locality against several projects. Send the right brochure from knowledge, not a zip of everything.
- Phone Confirm the visit when WhatsApp goes quiet. Training greeting in Agent Studio is the spoken opener on inbound voice.
- Email Weekly listings digest for buyers not ready this weekend — same contact as the WhatsApp thread.
How it runs in CoPulse
The conversation agent is the speed-to-lead surface. Drips handle the weekly digest. Workflows fire when a portal lead is created. Autonomous lists are for 60-day dormant buyers — sends/reads only.
Shared inbox
Omnichannel inbox so the firm sees WhatsApp, Messenger, email, and voice on one Buyer. Personal WhatsApp forwarding is the failure mode this ICP exists to kill.
Library templates
Approved WhatsApp templates for the first ping after 24 hours. Gupshup is the live WhatsApp path.
Workflows
On New enquiry from a portal source, assign the qualifier. On Qualified, offer slots. Humans take negotiation.
Operator setup
Create the Organization, then a Project for the brokerage (not one Project per agent unless you truly isolate books).
Setup → Channels → Library templates → Agents → Studio (multi-project knowledge) → Agents → Router by locality → Pipeline stages → Growth drips for saved-search digests. Wallet-only: the firm tops up, not each broker seat.
What speed-to-lead actually is
When a 99acres enquiry hits the Project, a workflow can assign the qualifier immediately. The first WhatsApp asks BHK, budget, and locality against several listings in knowledge — not a single developer brochure. If the buyer goes quiet after the 24-hour session, an approved library template is the next hop, not free text. If they still do not reply, voice confirmation is the Visit Caller pattern, not a human dialer farm. The assigned broker opens the omnichannel inbox and sees the thread, not a forwarded screenshot. Duplicate portal leads merge so two brokers do not fight over Priya. That is the brokerage; personal WhatsApp is how you lose the audit trail when someone quits.
Train the qualifier on what you actually list this month. A stale PDF is worse than no bot. Router by locality so Whitefield leads do not hit the Navi Mumbai specialist. Wallet-only means the firm tops up once; you are not buying a CRM seat per broker.
Portal lead hops
Speed-to-lead is the first WhatsApp reply, not a call logged tomorrow.
| Hop | Channel | What happens | Owner |
|---|---|---|---|
| 1 | Portal / web | Lead in under a minute | Capture |
| 2 | BHK, budget, locality | Qualifier | |
| 3 | Phone | Visit confirm if no reply | Voice agent |
| 4 | Inbox | Broker handoff | Human |
| 5 | Listings digest | Campaign |
Playbooks for this team
Jobs are omnichannel. Each link is one URL, not a WhatsApp-only clone.
Guide: Developer vs broker scripts
How-to for this desk. Playbooks remain the jobs.
Guide →Portal lead follow-up
48-hour path from portal enquiry to booked visit.
Open playbook →Lead qualification
BHK, budget, locality, timeline before a Saturday slot.
Open playbook →Duplicate leads
One buyer from three portals, one conversation graph.
Open playbook →Frequently asked questions
Brokerages, portals, and shared inboxes.
Can agents keep using personal WhatsApp?
They can, and you will keep losing SLA. CoPulse is the shared inbox and CRM. Handoff is designed so the human still sounds local.
Multiple builders at once?
Yes — knowledge per cluster, router by project or locality. Do not dump every brochure into one agent without structure.
SMS reminders?
Use WhatsApp templates and voice for confirmation today.
Does autonomous stop on visit booked?
No. Sends and reads only. Book visits with the conversation agent and appointment skill.
Seat licenses?
No. Wallet-only pricing for the Organization.
Where do portal leads enter?
Integrations, forms, or import into CRM, then the qualifier. The playbook is portal-lead-followup.
Related
Parent hub, sibling teams, and product surfaces this ICP actually uses.
Real estate hub
Buyers & Tenants, Bookings, site visits — directory of ICPs and jobs.
Back to hub →Developers
Single-project launches and inventory.
Open →Independent agents
Solo wallet-only qualifier and scheduler.
Open →Omnichannel inbox
WhatsApp, email, web, voice — one Buyer thread.
Explore →Wallet-only pricing
The brokerage wallet pays usage, not a seat per broker.
See pricing →Move portal leads off personal WhatsApp
Connect the number to the Project inbox and let the qualifier ask BHK before a human spends the weekend.
Get started free