RM gets the thread, fields, and visit — not a forwarded “hot”

Definition

RM handoff is the job of moving a Booking from bot-led qualification or post-visit into a human-owned inbox thread with fields, knowledge, and visit notes intact, switching the agent router so the qualifier stops quoting price.

Forwarded “hot lead” texts create RERA-shaped mistakes

Bots improvising discounts. RMs without EMI context. Handoff is inbox + router + workflow assign. Not a new URL per WhatsApp. Not unsupervised close.

Omnichannel sequence

All prior hops already on the contact. RM continues WhatsApp/voice/email in one inbox.

How it runs in CoPulse

Inbox is the runtime. Router + workflows. Drips for token window only. Autonomous is the wrong closer. Do not use autonomous tasks as the inbound qualifier. Conversation agents, Growth drips, and autonomous list sends are three systems with no shared stop-when-booked contract. WhatsApp live catalog is Gupshup, not an invented Meta Cloud hop. Phone is Plivo; email is SES. Wallet-only pricing: preview the Organization wallet before a blast. Organization and Project — never a shared inbox that vanishes when a broker leaves.

Operator setup

Router rules are the product. Without them the qualifier keeps asking BHK.

1.74 Cr, token Friday, qualifier silenced

Stage enters negotiation. Router blocks bot price. Ananya answers in buyer inbox. Friday utility nudge. Token → Booked. Click-path: Router, kanban, inbox, Library.

Luxury: earlier handoff, same mechanics. Illustrative closed 2% on launch template is unrelated — do not use it as RM win rate. Pricing: nudges debit wallet; RM time is not a seat fee.

Operators assemble this job on the Project. Click-path remains Agents → Router → Workflows on stage → inbox ownership → Library deadline template → exclude from Growth lists. Keep the quotable definition in the brief for the team: RM handoff is the job of moving a Booking from bot-led qualification or post-visit into a human-owned inbox thread with fields, knowledge, and visit notes intact, switching the agent router so the qualifier stops quoting price. Do not use autonomous tasks as the inbound qualifier. Conversation agents, Growth drips, and autonomous list sends are three systems with no shared stop-when-booked contract. While you implement, keep the parent playbooks directory, Negotiation / token, WhatsApp overlay, Luxury, Agent Studio, Growth campaigns, and wallet-only pricing in the same runbook. Do not invent Meta Cloud WhatsApp if the catalog is Gupshup. Do not promise adaptive nurture. Human handoff stays in the omnichannel inbox. Appointments and calendars are the visit truth when this job books time. Library templates are required outside the 24-hour WhatsApp window. Workflows fire on pipeline stage change only when you attach them under Agents → Workflows. The agent router keeps the wrong bot off this thread. Knowledge bases hold PDFs you uploaded. Preview the Organization wallet before a blast. Property managers should not paste sales token stages onto leasing jobs. The RM handoff playbook never forks into a WhatsApp-only or voice-only child URL. Funnel percentages on some leaves are library template estimates from Site-visit booking blitz, New project launch teaser, or Cold-buyer win-back — not an SLA and not Insights. If this job mentions money, the Organization wallet is the meter. If it mentions a Saturday slot, Visit Caller and T-24h templates are in-product; cab dispatch is not. That is the honest operating manual for this URL.

Channel sequence (one job, not extra URLs)

Handoff hops. There is no nested playbook-by-channel path.

Illustrative funnel (library template estimates)

Handoff quality sits after visited 12% in the blitz story. These percentages come from CoPulse library playbook templates (Site-visit booking blitz, New project launch teaser, or Cold-buyer win-back). They are not your project's Insights chart.