Conversation agent
Agent Studio, knowledge, appointment skill, router by stage. Human handoff keeps the thread.
WhatsApp is where qualification, brochures, and slot offers happen, then voice and email continue the same buyer timeline. It is not a standalone CRM. CoPulse keeps Buyers & Tenants and Bookings on one contact: session chat inside 24 hours, approved library templates when the window closes, wallet debit per send.
Property teams live in WhatsApp, then lose the thread when a broker leaves, when the 24-hour session ends, or when a launch needs an approved template. CoPulse connects the Business number under Setup → Channels (live catalog is Gupshup, not an invented Meta Cloud WhatsApp hop). Library templates sync for proactive sends. In-session, the conversation agent in Agent Studio can free-text with knowledge (brochures, floor plans). Outside the window, the same job must use an approved template or the send fails. Autonomous planners do not auto-provision an opener plus in-session plus closed-window pair today — operators still pick templates. SMS is a separate hop, not a WhatsApp-window fallback.
Capture may start on web or Meta. WhatsApp is usually hop two: qualify BHK, budget, locality, send collateral, offer the appointment skill slot. Voice confirms. Email holds the long list.
Conversation agent on WhatsApp. Growth campaigns for launches. Workflows on stage enter can send a template. Autonomous outbound may use WhatsApp after plan approve — success is sends/reads, not site visit booked. Template families: failover or sticky A/B among sendable members; paused, rejected, or red-quality templates are skipped (up to two backup variations).
Agent Studio, knowledge, appointment skill, router by stage. Human handoff keeps the thread.
Submit/sync for approval. After 24 hours this is the only WhatsApp path that works.
A family can hold a primary plus backups. Strategy is failover or sticky_ab. If nothing is sendable, outbound should fail closed — not invent a new template.
Launch teasers and win-back. Preview wallet. Gupshup sends. Not SMS.
Organization wallet, Project number, Real Estate labels (Buyers & Tenants, Bookings).
Setup → Channels (WhatsApp / Gupshup) → Library (templates and variations) → Agents → Studio → Router → Pipeline → Growth with wallet preview. Do not add SMS.
A buyer messages during session. The qualifier writes budget and BHK on the deal, offers Saturday from the appointment skill, and sends the floor plan. Tomorrow the session is closed: the T-24h reminder is a utility template from Library, optionally a variation if the primary is paused. Voice still confirms pickup. Email is unused unless this is a launch digest audience. That is one playbook (site-visit booking), not a WhatsApp-only microsite.
For a launch, Growth selects matched Buyers & Tenants, shows wallet cost, and sends a marketing template. Replies reopen a session; the qualifier triages. Autonomous win-back of 60-day dormant contacts can send WhatsApp too, but you will count sends and reads until success criteria include visits. Nurture planners will not magically pair session plus template for you (GTM gap G9).
Four jobs, same channel, different exits.
| Job | This channel | Other hops | Exit |
|---|---|---|---|
| Qualify | Four questions + brochure | Voice if quiet | Qualified |
| Book visit | Slot offer in session | Voice T-1 | Site visit booked |
| Launch | Marketing template | Email digest | Replied / visit |
| Win-back | Inventory template | Voice | Re-engaged |
Each playbook is the full omnichannel job. This channel is one step, not a second URL tree.
How this hop sits in the omnichannel job.
Guide →BHK, budget, locality on WhatsApp, then CRM.
Open playbook →Slots in chat, confirm on voice.
Open playbook →Matched teaser; replies stay on this number.
Open playbook →Dormant 60d template, then a call.
Open playbook →Sessions, templates, Gupshup, wallet.
Free-text agent replies in the session fail for proactive outbound. Use an approved library template. Operators must choose it; autonomous planning does not auto-build the pair today.
The live WhatsApp provider in catalog is Gupshup. Connect it under Setup → Channels. Product overview: /channels/whatsapp.
A template family can include a primary and up to two backups. Failover skips paused/rejected/red-quality members; sticky_ab hashes a key across healthy ones. If none are sendable, do not send.
No. Wallet per send.
No. Voice, email, web, and Meta complete the job. This page is the overlay; playbooks are the jobs.
Coming soon. Not a live hop.
Hub, sibling hops, product channel page, and the surface operators actually open.
Buyers & Tenants, Bookings, ICPs, and jobs.
Back to hub →Visit confirmation and no-show recovery.
Open →Digests and construction updates.
Open →WhatsApp sits on the same Buyer as voice and email.
Explore →WABA, templates, campaigns — product channel page.
Product channel →Each session or template send debits the Organization wallet.
See pricing →Setup → Channels, sync templates, put the qualifier in Agent Studio, and keep voice on the same Booking.
Get started free