Reducing no-shows: what actually works, and what just annoys people

A no-show costs you the slot, the staff time, and usually the customer. Most practices respond by sending more reminders. That helps a little, and then stops helping, because volume was never the problem.

What actually moves the number is when the reminder arrives, what it asks for, and what happens when somebody replies to it.

Two reminders, not four

The pattern that works across service businesses:

24 hours before. Far enough out that the person can still rearrange their day, or tell you they cannot make it while you can still fill the slot. This is the reminder that saves revenue: a cancellation at this point is a gap you can offer to somebody else.

Two hours before. Close enough to be the actual nudge. This is the one that catches the person who genuinely forgot.

A third reminder a week out gets ignored because it is not actionable yet. A fourth is how you get a STOP. If two well-timed reminders are not working, the problem is the wording or the booking itself.

The reminder has to ask for something

A statement gets read and dismissed. A question gets answered.

Weak:

Reminder: you have an appointment at Bright Smile Dental tomorrow at 2:00pm.

Better:

Hi Dana, reminder of your cleaning tomorrow (Tue) at 2:00pm with Sam at Bright Smile Dental. Reply C to confirm or R to reschedule. Reply STOP to opt out.

The second one does three things the first does not: it names the person and the provider, it gives a reply that takes one character, and it makes reschedule as easy as confirm.

That last point is the one practices resist and should not. Making rescheduling easy does not cause cancellations. It converts a silent no-show into a rebooked appointment. The customer who cannot make Tuesday is not coming on Tuesday either way. The only question is whether you find out in time to use the slot.

Timing in the customer's day, not yours

A reminder sent at 8:55am because that is when your morning admin runs is a reminder competing with somebody's commute.

Two rules:

• Send in the local time of the customer, which for a single-location practice is your time, but stops being true the moment you have locations in two timezones. Cutting "tomorrow" in UTC puts a 9pm appointment in New York on the wrong day.
• Respect quiet hours. Nothing about a reminder needs to arrive at 3am. A system that cannot defer out of quiet hours will eventually send one, and that message costs you more goodwill than the reminder earned.

The consent question, which most articles skip

You may not text everybody on your patient list just because you have their number.

The useful distinction is what the message is for. A reply to somebody who just messaged you is conversational, because they started it. An appointment reminder is transactional, and in practice it needs evidenced consent: a record of this specific person agreeing to be texted, and ideally the wording they agreed to.

The practical consequences are unglamorous and worth planning for:

• Get consent at booking, with an unchecked box and disclosure text next to it. Pre-checked does not count.
• Do not back-fill. Assuming everybody who ever gave you a number consented is the assumption that produces complaints.
• Expect a gap. Every customer who booked before you started recording consent gets no reminders until somebody records that they agreed. That is not a bug in your software; it is the honest state of your records.

A system that silently sends nothing for those customers is worse than one that shows you the skip and why.

Not legal advice. TCPA and state rules carry real penalties. Have counsel review your opt-in wording.

Deposits work, and they are a trade

A deposit, even a small one, reliably reduces no-shows, because it converts a free option into a decision. It also reduces bookings, because some people will not pay one.

For high-value or long appointments, that trade usually favours the deposit. For a fifteen-minute consult, it usually does not. The mistake is applying one policy to every service.

If you do take deposits, state the policy on the booking page before they book. Finding out about a non-refundable deposit afterwards is what produces a chargeback, which costs you more than the no-show did.

What to measure

Not "no-show rate" alone. Three numbers:

1. Confirmation rate: how many reply to the 24-hour reminder at all. Low means your wording is not asking for anything.
2. Reschedule rate: how many move rather than vanish. Going up is good; you are converting silent no-shows into kept slots.
3. No-show rate by service and by staff member. An aggregate number hides the one service or the one provider where the real problem is.

How Frontiva handles it

Reminders are armed at the moment the appointment is created, inside the same transaction, so there is no scheduler sweep that can miss one. 24-hour and 2-hour SMS, deferred out of quiet hours rather than dropped, and sent only to customers with recorded consent.

Two guarantees worth knowing because they are enforced by the database rather than by careful code: an appointment cannot be double-booked, and a reminder cannot be sent twice. The second one is a partial unique index, not a flag somebody remembers to check.

When a customer replies to reschedule, it lands in your inbox as an ordinary conversation for a person to pick up. The AI has no calendar tool and will not offer slots in a text, so the customer rebooks themselves on your public booking page, which shows real availability against the same rotas and buffers your staff calendar uses.

Reminders only help if they are attached to the booking rather than to somebody's memory. See what is an AI receptionist for how the booking gets made in the first place.