Missed the slot? WhatsApp rebook, same-day voice, move the card

Definition

No-show recovery is the job of detecting a missed appointment, offering a same-day or next-weekend slot on WhatsApp, placing a voice callback, and writing a new calendar event so the Booking does not rot in Site visit booked.

Dead “booked” columns hide empty chairs

Kanban still says Site visit booked on Monday. Nobody calls. Recovery is a job with voice, not a hope. Do not blast a launch teaser at no-shows. Do not SMS. Do not claim the calendar auto-fires this without a workflow you built.

Omnichannel sequence

They already had WhatsApp + voice once. Repeat: WhatsApp reoffer, voice, maybe email if NRI.

How it runs in CoPulse

Conversation agent + voice. Workflow on no-show property. Drip optional. Autonomous list of yesterday’s appointments is possible via appointment_query — success still sends/reads, not “rebooked.” 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

Define no-show. Templates. Voice. Calendar hygiene.

Saturday 11 empty, Sunday 10 recovered

Ops ticks no-show at 11:40. Workflow sends Sunday 10. Visit Caller at 1 p.m. Two recover. Rest wait for visited-not-booked sequence. Click-path: appointments, Booking, inbox, phone.

Library blitz funnel visited 12% vs booked 18% is the gap this job attacks. Pricing: extra template + call on the wallet.

Operators assemble this job on the Project. Click-path remains Customers properties no_show → Workflows → Library rebook template → Studio → Phone → calendars → wallet. Keep the quotable definition in the brief for the team: No-show recovery is the job of detecting a missed appointment, offering a same-day or next-weekend slot on WhatsApp, placing a voice callback, and writing a new calendar event so the Booking does not rot in Site visit booked. 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, Site visit booked, Phone overlay, Brokers, 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 No-show recovery 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)

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

Illustrative funnel (library template estimates)

Closing the visited vs booked gap is the point of the estimates. 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.