Conversation agent
EMI from knowledge. Handoff to RM when numbers get specific.
Visited deals go cold inside 48 hours unless EMI, inventory match, and RM intro fire on the same timeline. Insights’ real-estate deals narrative is explicit: post-visit follow-up going cold, especially for buyers who asked about loans. Suggested cue is EMI calculator at +24h plus relationship-manager intro. You still wire that drip or workflow — the insight does not ship adaptive nurture. This stage is not the post-visit playbook.
Brokers promise “I will WhatsApp the EMI” from a personal phone, then disappear into the next Saturday. The omnichannel inbox should already have the tour thread. If the buyer asked about loans on site, waiting until Monday is how this column dies. Do not blast a launch teaser at visited buyers — that is the launch playbook, wrong audience. Do not claim an autonomous task will stop when they token; it will not even stop when they booked the visit.
Omni playbook ends with WhatsApp post-visit follow-up. Visited is that CRM home.
Conversation agent plus a short drip. Workflow on enter can start the +24h EMI send if a custom property loan_interest=true. Humans own pricing exceptions. Autonomous win-back is for the dormant column, not yesterday’s tour.
EMI from knowledge. Handoff to RM when numbers get specific.
On enter: +24h drip, assign RM, set last_visited_at custom property.
One or two steps you authored. No engagement-ordered email warmup.
RM continues the same thread. Do not open a parallel personal WhatsApp.
Knowledge must include the EMI sheet you are legally willing to send. Wallet covers the follow-up sends.
Agents → Studio (knowledge + RM handoff) → Workflows on Visited enter → Growth drip +24h → Customers pipeline. Library template if the session closed overnight.
Ops moves to Visited at 1:10 p.m. Workflow sees loan_interest and schedules EMI + RM intro for +24h, plus an immediate in-session note if WhatsApp is still open. Ananya picks up in the buyer inbox with the same history. If they ghost, the card does not magically become Booked. After 60 days you use Dormant / re-engage and the win-back playbook, not this stage’s drip stretched forever.
Click-path: Booking → stage Visited; Agents → Workflows; Library if Friday tour and Saturday template; /pricing/ only because EMI WhatsApp still debits the wallet. Human writes the actual token number — automation does not negotiate.
Exit is intent to negotiate or a documented stall, not “drip sent.”
| Stage | Automation | Human | Channel hops | Exit criteria |
|---|---|---|---|---|
| Visited | EMI drip if wired, RM assign | Price, objections | WhatsApp + inbox | Negotiate or dormant path |
| Site visit booked | Reminders | Show management | Voice + WhatsApp | Arrived |
| Negotiation / token | Light nudges | RM | Inbox + voice | Token |
| Dormant / re-engage | Win-back later | New inventory | WhatsApp + voice | Fresh visit |
Post-visit is a job. EMI intro is a job. This URL is the stage they share.
Loan questions, drips, and honesty about Insights.
Only if you attach a workflow or drip. Insights can recommend it; it does not execute adaptive nurture.
They can send. They do not stop on token or booking. Keep RM in the inbox for price.
Saturday follow-up needs an approved library template on Gupshup.
Wrong job. Use inventory match or win-back, not the launch playbook audience.
Visited after a viewing is not a sales EMI loop. Use a leasing pipeline.
Follow-up WhatsApp and any voice debit the Organization. Pricing.
Parent hub, sibling stages, CRM product, and jobs that move this column.
Buyers & Tenants, Bookings, channels, and playbooks.
Back to hub →The column before they arrive.
Open →Human-led pricing next.
Open →Activity timeline plus stage-enter agents on the Booking.
Product CRM →EMI WhatsApp and RM voice, if used, hit the Organization wallet.
See pricing →Wire EMI and RM intro when they asked about loans, and keep the tour on the same inbox thread.
Get started free