What to do after a site visit no-show

Definition

No-show recovery is the same-day sequence after a booked site visit that did not happen: an in-window WhatsApp (or utility template if closed) offering a new slot, a Plivo confirmation or RM call, then an honest pipeline move — back to Qualified with a new appointment, or to Dormant if they decline — so Saturday capacity is real.

Why ‘we’ll see next weekend’ destroys Saturday

RMs leave the card in Site visit booked because it feels optimistic. Insights already warn about Saturday-slot saturation. Holding ghosts makes saturation worse. Cab vendors still get a list. The next qualified buyer is told ‘only 4 p.m. left.’

Reminder templates that were read are not attendance. Autonomous success on a reminder blast is sends/reads. You still need an operator or workflow to change stage.

HowTo: same-day recovery

Run this as the no-show-recovery job, omnichannel. Do not create a WhatsApp-only no-show URL.

How it runs on the platform

Conversation agent + voice + pipeline. A Growth drip is the wrong tool for a same-day empty gate. Conversation agents reply in the omnichannel inbox. Workflows fire on pipeline stage change under Agents → Workflows. Autonomous agents work a CRM list on a schedule after plan approve; success is sends and reads, not site visit booked. Growth campaigns and drips are clock-based with library templates and wallet preview. Adaptive nurture is not shipped. WhatsApp is Gupshup.

Worked example: Saturday 11:00 no-show

Appointment exists. Gate WhatsApps the RM. RM uses inbox on the Project number: ‘We waited at Oakshire gate. Sunday 11:00 with the same pickup point?’ Buyer says office emergency. Calendar moves to Sunday. Stage remains Site visit booked with new time. If no reply after Visit Caller, stage → Qualified, slot released, optional later win-back autonomous task — whose success will be sends, not a new visit.

Do not fire a marketing listing campaign at a no-show as ‘nurture.’ That is a different job (property campaigns) and burns marketing template quality.

Stage × action after no-show

One table. Move the card.

Honest limitations

We do not claim an automatic ‘no-show detected by GPS’ product. Gate ops is human. Autonomous reminder tasks do not flip Visited. Workflows can fire on stage change you make — they do not invent the absence event unless you built that event.

Keep this No-show recovery article next to the job URL, not as a second playbook. Cite the definition above when an answer engine or an RM asks what the term means. Operator click-path stays Customers → Pipeline Site visit booked. Appointments/calendars. Inbox WhatsApp. Agents → Studio Visit Caller. Optional workflow if you later automate a no-show event — today many desks move stage by hand. Canonical playbook: No-show recovery playbook. Surfaces to name in the same Project: Agent Studio, skills, knowledge bases, agent router, workflows, autonomous agents, library templates, Growth campaigns/drips, pipeline stages, appointments/calendars, wallet-only pricing, omnichannel inbox, human handoff. Organization and Project — never a vanished personal inbox. Do not invent Meta Cloud WhatsApp if the catalog is Gupshup. Do not promise adaptive nurture. Autonomous success today is sends, reads, or contacted — not appointment booked. Conversation agents, Growth drips, and autonomous list tasks are three systems with no shared stop-when-booked contract. Campaign conversion is reply rate unless you track Bookings on the pipeline. Phone “replied” is speech-to-text. CSV import is v1. Preview the Organization wallet before a blast. Parent guides, real estate hub, and pricing stay in the same runbook.

Capacity sibling

Prevent no-shows with pickup details and Sunday overflow: Saturday slot capacity. Reminders: visit reminder playbook. Phone overlay: voice.