Playbook

Confirmations and reminders that kill no-shows

By David Saleh · Silas Main · 17 July 2026

A customer books a slot, then doesn't show. That's the failure everyone builds for. There's a second failure almost nobody builds for, and it's worse: a customer cancels, and the business calls them anyway the next morning to "remind" them of an appointment that no longer exists.

One of those looks like a customer's mistake. The other looks like yours. A phantom reminder call tells the person on the other end that your system doesn't actually know what's happening in your own diary. That's a harder thing to walk back than a missed booking ever was.

Both failures come from the same gap: nobody built the whole lifecycle of a booking, just the parts that felt obvious.

An empty slot costs you the time you set aside for it, whatever that slot was worth. A phantom reminder costs something harder to get back: the next time that customer books anything with you, they'll wonder if your system knows what it's doing. One is a lost hour. The other is a lost customer who assumes you're disorganised, when really it's just one missing step in an otherwise decent setup.

A booking isn't one moment. It's four.

Most reminder setups are built around a single idea: send a message closer to the appointment so people don't forget. That's one piece of a four-part chain, and treating it as the whole thing is why so many reminder systems still leak no-shows.

The moment they book. Confirm immediately, while the booking is still the top thing on their mind. Not a day later. Right then.

The morning of. A short reminder, close enough to the appointment that it's still relevant, far enough ahead that they can actually reschedule if something's come up.

If they cancel. The confirmation and the reminder both need to stop. Immediately. Not "eventually." Not "next time someone checks the list."

If they reschedule. Same as a cancellation, plus one more step: the reminder needs to re-point itself at the new time, not fire at the old one.

Most businesses build the first two and stop. The last two are the ones that actually decide whether the system looks trustworthy or looks broken, and they're the ones that get skipped because they only show up as a problem after someone's already annoyed.

Confirm immediately, remind once, say it plainly

The confirmation message isn't the place for cleverness. It's the place for certainty: time, what happens next, and how to change it if they need to. The reminder the morning of does the same job in fewer words, because by then they've already got the details, they just need the nudge.

Neither message should promise anything you haven't actually confirmed. No invented arrival window, no made-up cost, nothing the person answering the phone later has to walk back because the automated message overreached.

The part that actually earns trust: handling the cancel

Here's the reframe worth sitting with. A reminder system isn't judged by how good it is at reminding. It's judged by how fast it forgets a booking that no longer exists.

When someone cancels, two things need to happen in the same moment: pull them out of whatever's queued to remind them, and clear any note that says they're still coming. If that doesn't happen cleanly, the business ends up calling a customer about an appointment they already told you they can't make. That single phantom call can undo the goodwill of a dozen well-timed reminders.

The same applies to a reschedule. It isn't a cancellation followed by a fresh booking in the system's eyes, it's a booking that moved. The confirmation and reminder need to move with it, pointed at the new time, not the old one. Get that wrong and the business either double-reminds them or forgets them entirely.

Not a nicer number. More lead time.

Here's a real decision from a booking system we built: should the morning-of reminder go out at exactly 9am, or is 8am close enough?

The honest answer is that most timing systems that work off a date, not an exact hour, will release whenever their daily window opens, often the start of the morning rather than a specific chosen minute. Chasing the extra hour to land on a nicer, rounder number takes real building work. And the earlier time gives the customer more notice to sort their day out if something's clashed.

We kept 8am. Not because it's the number we'd pick if building from scratch, but because more lead time for the customer beats a tidier number for us. That's the actual question worth asking before you spend hours forcing a reminder onto a specific minute: does the exact time matter, or does the customer just need enough notice? Usually it's the second one, and the earlier time already gives them that.

This is worth knowing before you build anything yourself. It's tempting to spend an afternoon chasing an exact 9am send time because it sounds tidier on paper. Ask first whether the person receiving it would even notice the difference between 8am and 9am. If the answer is no, spend that afternoon on something that actually moves the needle, like the cancellation handling most businesses never get to.

What this pack gives you

Below are three prompts, one for each moment in the lifecycle that involves talking to the customer: the booking confirmation, the morning-of reminder, and the cancellation acknowledgement. Each one takes your booking details and writes a short, plain message, no invented promises, no filler.

There's also a one-page checklist for the whole lifecycle, the kind of document you hand to whoever's setting this up, whether that's you working manually off a spreadsheet or a system doing it automatically. The checklist doesn't care which. It cares that all four moments are covered, not just the two that are easy to remember.

The prompts

Write a booking confirmation message for [BUSINESS NAME], a [TRADE OR INDUSTRY] business in [SUBURB OR CITY]. The message is going by [SMS / EMAIL] to a customer who just booked [SERVICE OR APPOINTMENT TYPE] for [DATE AND TIME]. This is the first thing they hear from the business after booking, so it needs to do one job well: make them certain the booking is real and locked in.

Requirements:
- Confirm the date, time, and what the appointment is for, in plain language, in the first line.
- State only facts I've given you above. Do not add a price, an arrival window, a technician's name, or any promise I haven't specified. If I haven't given you a detail, leave it out rather than guessing at something plausible.
- Include one plain line on how to cancel or reschedule: [HOW THEY CAN DO THIS, e.g. "reply STOP" or "call [PHONE NUMBER]"]. This line matters as much as the confirmation itself, it's what makes the whole lifecycle work later.
- Keep it under [MAX LENGTH, e.g. "40 words"] if this is a text message, longer is fine for email, but don't pad it out with filler just to fill space.
- Tone: warm, plain, no exclamation marks, no corporate phrasing like "we look forward to serving you" or "your satisfaction is our priority."
- Sign off as [BUSINESS NAME], not a generic "the team" or "customer care."

Write two versions: one for SMS, one for email, even if I only asked for one channel above, so I can compare tone.

Write a morning-of reminder message for [BUSINESS NAME] for a customer with [SERVICE OR APPOINTMENT TYPE] booked today at [TIME]. This message goes out on the day of the appointment, after a confirmation has already been sent when they first booked.

Requirements:
- Assume the customer already has the full details from an earlier confirmation. This message is a short nudge, not a re-explanation of the whole booking.
- State the time and what the appointment is for, and nothing else new. Do not re-explain pricing, location details, or anything that belongs in the original confirmation.
- Include the same cancel or reschedule instruction as the confirmation: [HOW THEY CAN DO THIS]. Use the identical wording so it reads as one consistent system, not two different tools that don't talk to each other.
- Keep it under [MAX LENGTH, e.g. "30 words"]. Shorter than the confirmation, always.
- Do not add urgency language like "don't forget" or "last chance" or "this is your final reminder." State the fact plainly, once, and let it land on its own without pressure.
- If [TIME] is more than a few hours away, note that gently rather than implying the appointment is imminent.

Write a cancellation acknowledgement message for [BUSINESS NAME], for a customer who just cancelled or rescheduled their [SERVICE OR APPOINTMENT TYPE] originally booked for [ORIGINAL DATE AND TIME]. This message replaces every reminder that was ever going to be sent about the original booking, so it has to say that plainly.

Requirements:
- If cancelled: confirm plainly that the appointment is cancelled, and state clearly that no further reminder will be sent about it. Invite them to rebook if they'd like to: [HOW THEY CAN REBOOK].
- If rescheduled to a new time: confirm the new date and time clearly, confirm the old time is no longer active, and note that a fresh reminder will come ahead of the new appointment instead.
- Tone: neutral and warm. Not apologetic on their behalf, and not guilt-tripping them for cancelling. This is an acknowledgement, not a sales recovery message.
- Keep it under [MAX LENGTH, e.g. "35 words"].
- The single most important sentence in this message is the one that says no further message will come about the old time. If you only get one thing right, get that one right.

Questions

Adelaide · ACST · ABN 17 626 827 646