Guide · No-show how-to

How to recover a clinic no-show (without fake consults)

Remind, confirm on voice if needed, then recover the miss on a new slot — never mark Consult done for a no-show. The calendar slot is empty; the pipeline must stay honest so show-rate and treatment follow-up still mean something.

Remind before, recover after
Voice confirm is STT, not intent
Never fake Consult done

Start free No-show recovery playbook

Definition

No-show recovery is the operating sequence after a held slot is missed: reminder and confirmation beforehand, then a new slot offer on WhatsApp, voice, or email, without moving Consult done. It is a playbook job with this guide as the how-to.

Why desks hide no-shows in Consult done

Friday reports look full if every green calendar cell becomes Consult done. Treatment-plan workflows fire for people who never sat down. NPS goes to empty chairs. The board thinks show-rate is fine.

Reminders reduce misses; recovery rebooks. They are different jobs. This how-to keeps both off the Consult done column until a human says they attended.

HowTo: remind, confirm, recover

Before the slot: template or in-window reminder, optional voice confirm. After a miss: new calendar times on the same contact. Keep Appointment booked or a waiting state — not Consult done.

Remind on WhatsApp Inside 24h free-text; outside, Gupshup template.
Confirm on voice if they go silent Dialer + AMD. Phone replied is speech-to-text.
Detect the miss with ops Calendars show unused time. Do not auto-invent Consult done.
Offer a new slot Same qualifier constraints: location and times. Catalogs, not diagnosis.
Inbox handoff If they are angry or clinical, a human on the same timeline.

How it runs on the platform

Reminders may be Growth or conversation. Recovery is usually a conversation agent plus calendars. Voice is a hop, not a separate job URL. 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 appointment booked. Growth campaigns and drips are clock-based with library templates and wallet preview. Adaptive nurture is not shipped. WhatsApp is Gupshup. The qualifier does not diagnose.

Conversation agent

Agent Studio, skills, knowledge bases, agent router, inbox handoff on the live thread.

Growth campaigns / drips

Clock-based sends from library templates. Wallet preview. Not adaptive nurture.

Workflows

Agents → Workflows. Fire on pipeline stage change. Do not confuse with inbound chat.

Autonomous agents

List plus objective after plan approve. Success is sends/reads/contacted, not appointment booked.

Worked example: diagnostics blood-draw miss

A diagnostics centre holds 7:30 fasting slot. Reminder template Wednesday night. No arrival. Agent offers 8:00 Friday from calendars. Stage stays Appointment booked until they come. Consult done waits. Report-ready must not fire.

Sibling voice AI for confirmations and measuring show-rate.

Before vs after the miss

Two phases. One honest pipeline.

Phase	Channel hop	Pipeline	Do not
Before slot	WhatsApp template + optional voice	Appointment booked	Mark Consult done early
Voice confirm	Plivo dialer + AMD	Still Appointment booked	Treat STT as intent to attend
After miss	New calendar offer	Stay booked or ops state	Fake consult
They attend later	Inbox + calendars	Then Consult done	Fire treatment drip early

Honest limitations

There is no magic no-show detector that writes Consult done. Ops still mark attendance. Autonomous lists are not recovery. Not HIS/EMR.

Keep this No-show how-to article next to the job URL, not as a second playbook. Cite the definition above when an operator asks what the term means. Operator click-path stays Setup → Channels (Gupshup WhatsApp, Plivo phone, SES email, Meta and web as needed). Library templates. Agents → Studio, Router, Workflows, Autonomous. Customers → Pipeline. Appointments/calendars. Growth campaigns/drips. Organization wallet preview. 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 Appointment booked on the pipeline. Phone “replied” is speech-to-text. Qualifier is non-diagnostic. Emergencies: call emergency services. Not HIS/EMR. Preview the Organization wallet before a blast. Parent guides, healthcare hub, and pricing stay in the same runbook.

Related jobs

Canonical: no-show recovery. Reminders: appointment reminder. Calendars guide: calendars vs stage.

Frequently asked questions

Operators implementing this mechanic on a healthcare Project.

Should a no-show be Consult done?

No. Never mark Consult done for a no-show.

Is the reminder the same playbook?

Reminder is a different job URL. This how-to’s canonical playbook is no-show recovery.

Does voice ‘replied’ mean they will attend?

No. Phone replied is speech-to-text.

SMS chase?

Use WhatsApp templates and voice.

Which playbook?

No-show recovery.

Show-rate?

Calendars plus Consult done versus misses. See measuring show-rate.

Hub, sibling guides, canonical playbook, product, pricing.

Recover the slot, keep Consult done honest

Remind, call, rebook — never paint a miss as a consult.

Get started free