No-show recovery agent (kind first, policy second, rebook third)
A 4-message no-show recovery flow: a kind first touch, the warm follow-up, the policy reminder, and the boundary message if it is becoming a pattern.
Fill in the Template
2 / 6 filledYour Built Prompt
Updates live as you typeAct as my no-show recovery agent. A client missed their appointment without a heads-up, and I want to handle it in a way that does not torch the relationship if they are mortified, while still applying the policy if I need to.
Client name + history (new, repeat, regular): {{client}}
Service missed + value: {{service}}
My no-show / late cancel policy in plain words: {{policy}}
What I know about today (sick day, work emergency, ghosted with no signal): {{context}}
Channel I will message on: SMS
Is this the first no-show with this client, second, or pattern? First no-show
Walk me through 4 messages:
1. The first-touch message (sent within 1 hour of the no-show) - 60-80 words. Warm, no judgement, asks if they are okay. Names that I have held the spot. Does NOT mention the policy yet. Asks for a quick reply.
2. If they reply with a reason - the warm follow-up: how to rebook + how the policy applies (no charge / partial charge / full charge depending on context).
3. If no reply by next day - the policy reminder. Calm and clear. States the charge per policy, the link to settle, the door open to rebook.
4. If this is the 2nd or 3rd no-show - the boundary message. Sets the new condition for future bookings (e.g. card hold required, or 50% deposit, or paused for a season).
Plus the internal note: what I update in their record so future me knows the pattern.
AU English. Warm but firm where it needs to be. No "no worries at all" if there is a charge. No "I totally understand" without specifics.Fill in the required fields above to copy or run this prompt.
Tags
Community Feedback
0 commentsRelated Prompts
More in CommunicationShipping delay heads-up message
A 3-line email that gets ahead of the angry-customer email. Apologises specifically, gives a clear new ETA, offers something small.
End-of-term parent update agent
A term-end update that pairs a real-language email with a 60-word SMS version, both ending on the one re-enrolment question that matters.
Re-engagement agent for a client gone quiet
A 5-output re-engagement workflow: a real hook, the message, the 10-day fallback, a graceful "no" reply, and the CRM note that prevents over-chasing.
Mid-project scope creep capture + comms agent
A scope-creep workflow that calls the ask in or out, prices the work, gives the client three options, and produces both the reply and the internal log entry.