no-show-recoverylisted

# /no-show-recovery — No-Show Re-Engagement Sequence > **Purpose.** When a `Booked → CallHeld` transition fails (prospect didn't show), this skill produces a context-classified re-engagement sequence. Sequence shape varies sharply by no-show context: a first no-show with no notice is most likely a calendar conflict (warm tone, easy reschedule); a second no-show is statistically a ghost (direct tone, final exit-rampup); a proactive cancel WITH a stated reason is a different conversation entirely (respect the reason, route accordingly — sometimes that means archive cleanly, sometimes that means a single-message redirect). > > **Bar.** A first no-show recovered cleanly converts to a held call ~50% of the time when handled in the right tone. Mishandled (guilt-trip tone, generic "missed you" template, or radio silence), it converts <10%. The differential is the difference between $5K-$25K/mo retainer recovered vs. archived. The second-no-show recovery rate is lower (~15%) but worth pursuing once with a final exit-rampup that respects the prospect's time. > > **The 1-of-1 primitive.** Most agencies run one "missed you" template for every no-show. This skill runs **three differentiated sequences** keyed to no-show context — and respects the auto-archive trigger after 2+ no-shows per the FSM. ## When to invoke - **Auto-triggered** by `call.no-show` event on every `Booked → NoShow` transition (per `workflows/divisions/acquisition.md` and `paperclip.manifest.yaml`) - Auto-triggered