No-Show Rescue Playbook
Prevent a missed appointment from automatically becoming a lost qualified opportunity by triggering a structured, respectful recovery sequence the moment an appointment outcome becomes NO-SHOW.
Id
RLR-30
Link
5
Link Name
Booking + Handoff
Role
workflow
Loop Step
Repair
Purpose
Prevent a missed appointment from automatically becoming a lost qualified opportunity by triggering a structured, respectful recovery sequence the moment an appointment outcome becomes NO-SHOW.
Governing Principle
A no-show is a scheduling event, not a verdict. The tone assumes legitimate scheduling friction before assuming lack of interest, and never uses punitive or shaming language. NO-SHOW routes to rescue, not to closure; closure only follows a real disposition.
Consolidation Note
This playbook absorbs and improves any prior ShiFt no-show / reschedule messaging into one canonical recovery sequence. No competing public no-show asset is created.
Trigger
Appointment outcome is recorded as NO-SHOW (the due appointment did not occur and was not cancelled or rescheduled in advance).
Recovery Framework
- no_show_detected
- immediate_outreach
- reschedule_opportunity
- secondary_contact_attempt
- follow_up_sequence
- escalation_for_high_intent_or_high_value
- nurture_or_closure_based_on_actual_disposition
Sequence
immediate no-show SMS
- Timing
- within minutes of the missed start
- Channel
- sms
- Objective
- reconnect warmly and offer an immediate reschedule
- Message
- Hi [First Name], we missed you for your [Appointment Type] today — no problem at all, things come up. Want to grab a new time? [Reschedule Link] or reply here.
- Owner
- automation_or_assigned_owner
- Stop condition
- prospect responds, reschedules, opts out, or reaches attempt cap
immediate/near-immediate call opener
- Timing
- shortly after the missed start
- Channel
- phone
- Objective
- offer a live, friction-free reschedule
- Message
- Hi [First Name], this is [Responder] from [Service] — we had your [Appointment Type] on the calendar for [Requested Time] and wanted to make sure everything's okay. Happy to find a time that works better — do you have a moment?
- Owner
- assigned_owner
- Stop condition
- prospect reached and rescheduled, or no answer
voicemail
- Timing
- if the call is unanswered
- Channel
- voicemail
- Objective
- leave a warm, specific callback path
- Message
- Hi [First Name], it's [Responder] from [Service] about your [Appointment Type]. No worries about today — I'd love to get you rebooked. Call me back at [Callback Number] or use [Reschedule Link].
- Owner
- assigned_owner
- Stop condition
- left; proceed to next touch
reschedule message
- Timing
- same day
- Channel
- sms_or_email
- Objective
- make rebooking a one-tap action
- Message
- [First Name], let's get your [Appointment Type] back on the calendar. Pick any time that works: [Reschedule Link]. Prefer I set it for you? Just reply with a day that works.
- Owner
- automation_or_assigned_owner
- Stop condition
- prospect reschedules or reaches attempt cap
email recovery message
- Timing
- within ~24 hours
- Channel
- Objective
- give a fuller, context-rich reschedule path
- Message
- Subject: Let's find a better time for your [Appointment Type] Hi [First Name], we missed you yesterday and completely understand — schedules get busy. Your spot with [Responder] is still open to rebook. Grab a new time here: [Reschedule Link], or reply and I'll take care of it.
- Owner
- assigned_owner
- Stop condition
- prospect responds or reaches attempt cap
second-attempt recovery
- Timing
- 1-2 days after first attempts
- Channel
- phone_or_sms
- Objective
- one more genuine attempt using prior context
- Message
- Hi [First Name], still happy to help with [Prior Request]. Want me to hold [Requested Time] or find something else for your [Appointment Type]?
- Owner
- assigned_owner
- Stop condition
- prospect responds, reschedules, opts out, or reaches attempt cap
high-intent escalation
- Timing
- as soon as high intent or high value is evident
- Channel
- human
- Objective
- put a person on high-value or urgent recoveries rather than exhausting automation
- Message
- Route to [Responder]/senior owner for a direct, personal outreach and priority rebooking.
- Owner
- assigned_owner_or_escalation_owner
- Stop condition
- human takes ownership
final active recovery
- Timing
- end of active window
- Channel
- sms_or_email
- Objective
- make a clear, no-pressure last active offer
- Message
- [First Name], I don't want you to lose your place for your [Appointment Type]. If now isn't the right time, no problem — reply anytime and I'll get you in. Otherwise I'll follow up down the road.
- Owner
- assigned_owner
- Stop condition
- prospect responds or transitions to nurture
nurture transition
- Timing
- after active recovery is exhausted without a stop signal
- Channel
- system
- Objective
- preserve a still-valid future opportunity
- Message
- Move to Long-Term Nurture (RLR-25) with reason 'no-show, not recovered in active window', owner, and review date. Not a disqualification.
- Owner
- system_or_assigned_owner
- Stop condition
- re-engagement returns lead to active, or explicit stop
explicit stop/disposition rules
- Timing
- whenever a real signal appears
- Channel
- system
- Objective
- stop for the right reason and record it
- Message
- Stop and disposition on: explicit decline, opt-out/do-not-contact, invalid contact, rescheduled+showed, or attempt cap reached. Record the disposition per RLR-21; STOP RESCUE is not the same as DISQUALIFY.
- Owner
- system_or_assigned_owner
- Stop condition
- disposition recorded
Tone Rules
- assume legitimate scheduling friction before lack of interest
- never use punitive, guilt, or shaming language
- make rescheduling effortless at every touch
- escalate high intent to a human rather than exhausting automation
- honor opt-out and quiet-hours on every touch
Tracking
- Fields
- no_show_reason_where_known; recovery_attempts; response; rescheduled_date; recovered_appointment; final_disposition
Handoff From Link4
- Note
- Recovery reuses Link 4 follow-up and nurture instruments (RLR-24/RLR-25) rather than recreating them.
- Consumes
- prior_follow_up_context; owner; recommended_next_action
Handoff To Link6
- Note
- No-show and recovery outcomes feed Link 6 without authoring Link 6 content.
- Exposes
- show_no_show_status; reschedule_status; appointment_outcome; next_stage_outcome
Compliance Guardrail
Every recovery touch respects opt-outs, do-not-contact requests, channel permissions, quiet-hours rules, and the business's approved communication policy and consent controls. The playbook never invents legal requirements or bypasses provider restrictions; jurisdiction- and industry-specific rules are applied by the operator.
What To Measure
Whether missed appointments are recovered rather than lost — tracked via no-show rate, no-show recovery rate, reschedule rate, and recovered-show rate.
Verification Metrics
no_show_rate
- Formula
- no_show / (showed + no_show)
- Description
- Baseline missed-appointment rate.
no_show_recovery_rate
- Formula
- recovered / no_show
- Description
- Share of no-shows that re-engaged and rebooked.
reschedule_rate
- Formula
- rescheduled / no_show
- Description
- Share of no-shows that set a new time.
recovered_show_rate
- Formula
- recovered_showed / recovered_rebooked
- Description
- Share of recovered rebookings that actually attended.
Data Required
Per no-show: detection time, recovery attempts by channel, prospect response, rescheduled date, whether the recovered appointment was attended, and final disposition.
How To Interpret
A rising no-show recovery rate and recovered-show rate mean the sequence is converting misses back into attended appointments. A high raw no-show rate with strong recovery is far healthier than a low no-show rate with no recovery path. Persistent no-response after full recovery routes to nurture, not to a 'not interested' label.
Action That Follows
Rebook recovered prospects, escalate high-intent misses to a human, move unrecovered-but-valid prospects to nurture (RLR-25), and disposition explicit stops per RLR-21.
Owner
The assigned appointment owner (per RLR-32) owns live recovery; automation owns the scheduled touches; escalation goes to the named escalation owner.
How To Implement
Wire the NO-SHOW outcome to trigger the sequence, load the touch templates with variables, set attempt caps and escalation thresholds, and connect nurture transition and disposition writes.
How To Test
Mark a test appointment NO-SHOW and confirm the sequence fires in order, the reschedule link rebooks correctly, high-intent escalation routes to a human, opt-out stops the sequence, and nurture/disposition transitions record correctly.
When To Remeasure
Re-measure no-show recovery and recovered-show rates 14 and 30 days after rollout.
How To Know It Improved
The playbook helped only when re-measured no-show recovery rate and recovered-show rate rise on real records — not because a no-show sequence was installed.
How to implement
Install the change exactly as the playbook describes; log it on the Repair Plan.
How to verify
Installing a workflow is implementation, not closure. QA the repair before you trust it.
Related in this link
Rather not do this part yourself?
You can repair your Revenue Chain yourself with this Kit — or bring in ShiFt at any point. You do not need to finish the DIY path first.
Done with you
Revenue Leak Scan
A ShiFt specialist runs the diagnosis with you and hands you a prioritized repair plan.
Get My Revenue Leak ScanDone for you
ShiFt RevenueOS
ShiFt installs and operates the full Revenue Chain system for you — ConvertOS included.
See RevenueOS