Omnichannel inbox
RM continues WhatsApp and logs voice. Activity on the Booking.
Negotiation and token is a human-led stage with nudges and RM context, not an unsupervised blast. CoPulse can keep WhatsApp, voice, and email on one Booking, park the offer in the inbox, and fire a workflow when the card enters this column. It should not auto-discount inventory or declare Booked because an autonomous task hit a read threshold. This is not the RM-handoff playbook; that job explains the transfer. This column is where pricing lives.
Luxury and even mid-market buyers negotiate parking, floor, and payment plans. If a conversation agent keeps improvising price, you have a compliance issue. Agent router should already have handed this stage to humans. Light Growth nudges (“token window Friday”) are fine with an approved template. Autonomous outbound on a negotiating list is how you accidentally stack two offers. SMS is not the closer either — it is not live.
Voice and inbox dominate. WhatsApp is the paper trail. Email may carry the payment-plan PDF.
Human in omnichannel inbox is the primary runtime. Workflows on enter notify the RM and stop the qualifier bot via router. Drips for deadline only. Autonomous tasks are the wrong system here.
RM continues WhatsApp and logs voice. Activity on the Booking.
By pipeline stage: no qualifier, no launch bot.
On enter: assign RM, optional deadline drip, set negotiation_open.
Token-window utility if the 24h session is closed.
Router rules are the product. Without them the qualifier will keep asking BHK on a token thread.
Setup → Customers → Pipeline → Agents → Router (stage = negotiation → human) → Workflows → inbox. Knowledge holds payment-plan PDFs, not invented discounts.
Card enters Negotiation / token. Workflow assigns Ananya and pauses campaign enrolment for that contact if you configured it (you may still need to exclude them from Growth lists manually). She answers in the buyer inbox. Friday 11 a.m. a utility template nudges the window. Token received, ops moves to Booked — a human click or a workflow if you trust a custom property token_paid. Autonomous report still happily counts reads on some other list; it did not close this deal.
Click-path: Agents → Router; Customers → Booking; inbox; Library for the nudge. Sibling stage Booked starts welcome and docs. Pricing: nudges debit the wallet; RM time does not add a seat fee.
If automation is the hero row, you mis-set the router.
| Stage | Automation | Human | Channel hops | Exit criteria |
|---|---|---|---|---|
| Negotiation / token | Deadline nudge, assign RM | Price, holds, paperwork | Inbox + voice + email PDF | Token paid or walk |
| Visited | EMI intro | Objections | Ready to price | |
| Booked | Welcome / docs | KYC | WhatsApp + email | File open |
| Autonomous list | Sends/reads | Approve plan | WhatsApp/email/phone | Not token |
Handoff is a playbook. This stage is the column the RM lives in.
Router, nudges, and what not to automate.
No. Keep price with the RM. Knowledge can hold approved payment-plan PDFs.
Yes: assign RM, switch router, optional deadline drip. Agents → Workflows.
If they remain on a launch list, yes. Exclude negotiating Bookings from campaigns.
Not a success criterion today. Pause or exclude the audience yourself.
Not live.
Same column, tighter human. Affordable may token faster; still not a bot close.
Parent hub, sibling stages, CRM product, and jobs that move this column.
Buyers & Tenants, Bookings, channels, and playbooks.
Back to hub →Previous column.
Open →After token.
Open →Inbox, activity, and stage-enter assignment.
Product CRM →Deadline WhatsApp templates debit the Organization wallet.
See pricing →Router by stage, workflow assign, nudge the token window — and keep discounts in human hands.
Get started free