- Published
- Byline
- GoHighLevel Partners Editorial
- Filed under
- GoHighLevel Automation
How to design a reminder ladder that produces a decision at every send, exits cleanly on a reschedule, and is measured on empty chairs rather than open rates.
Almost every appointment-based business already sends reminders, and plenty of them see no change in attendance. Messages go out, they are delivered, and the same proportion of chairs sits empty. The usual conclusion is that reminders do not work — the wrong lesson from a fair observation.
What is missing is a decision. “You have an appointment tomorrow at 2pm” asks the reader for nothing, so the reader does nothing — including the reader who already knows they cannot make it. The system was built to inform, then judged on whether it changed behaviour.
Building an automated reminder system for appointments that protects the slot
Start from what the empty chair costs. An hour nobody attends was paid for in staff time and cannot be sold again. That changes the target: the system exists to keep slots occupied, not to make people feel reminded. Two things follow that the inform-the-customer framing hides.
A cancellation is a success, not a failure
If someone is not going to attend, the best available outcome is that they say so early enough for the slot to be filled by somebody else. A reminder that produces a cancellation two days out has done its job. One that produces silence and then a no-show has failed — though the second looks better in any report counting cancellations as a negative.
Report it three ways for clients: attended, cancelled with enough notice to refill, and lost. Collapsing the middle category into the bad column hides what the system is actually moving, and pushes clients toward heavier messaging that suppresses cancellations rather than no-shows.
Every send should carry an action
Give the recipient something to press: confirm, reschedule, cancel. All three are useful. Confirmation proves the number and the person are real; rescheduling moves the revenue rather than losing it; cancelling releases the slot. Silence is the only response you cannot act on, and an actionless message guarantees it.
Reschedule is the one most often left out, usually because it is the hardest to wire up, and the one that saves the most: the person clicking it still wants the service and has only hit a diary conflict.
The ladder: how many sends, and how far apart
Three positions cover most cases, and they are defined by what each one can still change rather than by a fixed number of hours.
The booking confirmation goes out immediately. Its real job is validation, not courtesy: a wrong mobile number or a mistyped email surfaces here, days before it matters, while a human is still in the conversation to correct it.
The planning reminder lands while rescheduling is still easy — before the person has arranged their day around the appointment and before you have committed staff to it. This send generates most of your recoverable cancellations.
The final reminder lands close enough to survive short-term memory. It drives attendance rather than recovery.
The refill window sets the last useful send
Work backwards from how long it takes to fill a released slot. If filling from a waitlist takes about a day, a reminder two hours out cannot recover anything — whatever it produces, the slot is gone. It still helps attendance, so send it; just do not expect recovery from it, and do not drop the earlier send that can.
The gap between sends matters more than the count. Three messages inside the final twelve hours read as nagging and leave no window in which acting is easy. Two spread across the booking horizon do more work.
Channels, and what each is good for
Channel choice trades how fast a message is read against how much it carries and how much setup it needs first.
| Channel | Best position in the ladder | What it needs first | Main limitation |
|---|---|---|---|
| SMS | Final reminder | Sender registration and recorded consent | Short, no formatting, per-message cost |
| Booking confirmation, planning reminder | Authenticated sending domain | May sit unread for hours | |
| Planning reminder | Approved templates and an open session window | Template rules restrict free-form sends | |
| Voice call | High-value or repeatedly missed slots | Staff time or a call workflow | Does not scale, easy to mistime |
SMS earns the final slot because it is read quickly, but it cannot be switched on casually — the registration and consent side of SMS has to be settled before volume sending, and an unregistered sender tends to degrade quietly rather than fail loudly. Email carries the detail SMS cannot: location, parking, what to bring, who to ask for. Confirm the authentication records are in order before leaning on it for anything time-critical, because a confirmation in a spam folder is worse than none — it has created an expectation on your side. WhatsApp sits between the two, with template and window rules governing what you may send outside an active conversation.
One channel handles a case the ladder cannot: someone who tries to call and gets no answer. A missed call text back turns that into a conversation instead of a lost enquiry, and it belongs alongside the reminder system rather than inside it.
Exits, and the bug almost everyone ships
The ladder has to stop when it stops being relevant. Cancelled, rescheduled, already attended, appointment deleted — each should remove the contact immediately, not at the next scheduled step. Implement it as a goal event the workflow watches continuously, not a filter checked when the next message is due.
The specific failure worth naming is rescheduling. Moving an appointment has to do two things: cancel the ladder attached to the old time, and start a fresh ladder against the new one. Systems routinely do the first and not the second, so a rescheduled client gets no reminders at all — and the people who reschedule are exactly the population most likely to miss the new slot.
The second half fails for a reason unrelated to reminders: many automation platforms will not run the same contact through the same workflow twice by default, so if the ladder is one workflow the second enrolment is dropped silently. That is what the re-entry setting governs. Check it explicitly, because the symptom — no reminders after a reschedule — does not point at it.
Time zones, quiet hours and the calendar itself
An appointment has a time in the calendar’s zone; a contact reads the message in theirs. If those differ and the reminder quotes a raw stored time, you have sent a confidently wrong number. Render times from the appointment’s own zone, and name the zone when a business books across more than one. Quiet hours are a separate constraint: a send computed as “twelve hours before” lands at three in the morning for an early appointment unless something clamps it into waking hours — clamp forward to the next acceptable hour rather than skipping it.
The calendar’s configuration also limits what the ladder can promise. A reschedule link offering slots the business cannot staff creates a booking you will cancel yourself, which is worse than the no-show. Understand how availability is counted on the calendar behind the link before putting that link in front of customers.
What to measure
Open rate is the wrong instrument here. It tells you a message was rendered, not that a chair was filled. Track instead:
- No-show rate by appointment type — a first consultation and a follow-up behave differently and need different ladders.
- Cancellation notice — the average warning you get. This is what the planning reminder moves, and what decides whether a released slot is recoverable.
- Confirm rate per send — which position is actually producing decisions, so you can drop the one that is not.
- Inbound replies the system created — a question that sits unanswered until after the appointment is a reminder system manufacturing no-shows. A response SLA on that inbox is part of the build, not an extra.
Where these builds usually go wrong
The recurring failures are structural rather than editorial: reminders that keep sending after a cancellation, because the exit was a filter and not a watched condition; duplicate ladders, because entry fires on every update rather than on creation; reschedule links pointing at a calendar with no availability; confirmations sent from a number nobody can reply to, so every question dies.
None of those are fixed by better copy. They are fixed by treating the ladder as a state machine with one entry, explicit exits, and a defined end — and then watching the no-show number rather than the send count.
Frequently Asked Questions
How many reminders should an appointment ladder send?
Three positions cover most businesses: an immediate booking confirmation that validates the contact details, a planning reminder while rescheduling is still easy, and a final reminder close to the appointment. The spacing matters more than the count — three messages crammed into the last half-day read as nagging and leave no window in which acting is convenient.
Is a cancellation a failure of the reminder system?
No. If someone was not going to attend, an early cancellation is the best available outcome, because the slot can be refilled. Report attended, cancelled-with-notice and lost as three separate categories. Folding cancellations into the negative column hides what the system is actually improving.
Why do rescheduled appointments often get no reminders?
Rescheduling has to cancel the ladder on the old time and start a new one against the new time. Many builds do only the first. The second half also runs into platform re-entry rules, which by default may refuse to run the same contact through the same workflow twice, so the new enrolment is dropped silently.
Should reminders go by SMS or email?
Both, in different positions. Email carries detail — location, what to bring, who to ask for — and suits the booking confirmation and planning reminder. SMS is read quickly and suits the final reminder, but it needs sender registration and recorded consent before any volume sending.
How far before the appointment should the last reminder go?
Work backwards from how long it takes to refill a released slot. If filling from a waitlist takes about a day, a reminder two hours out cannot recover the slot whatever it produces. It can still improve attendance, so it is worth sending — just do not let it replace the earlier send that can still recover.
What should each reminder ask the recipient to do?
Offer confirm, reschedule and cancel. All three produce usable information: confirmation validates the contact, rescheduling keeps the revenue, cancelling releases the slot. Reschedule is the one most often omitted and the one that saves the most, because that person still wants the service.
Which metric shows whether the system is working?
No-show rate by appointment type, plus average cancellation notice. Open rate only shows a message was rendered. Also watch inbound replies the reminders generate — an unanswered question sitting in an inbox until after the appointment turns the reminder system into a source of no-shows.
We build your GoHighLevel account for you
CRM, pipelines, funnels, SMS and automation — configured for your business, not left for you to figure out.
- Setup (one-time)$850
- Ongoing (per month)$38.80
No obligation quote · reply within 1 business day
This site is independently operated and is not officially affiliated with, endorsed by, or sponsored by HighLevel LLC. We do not receive referral commissions — this is our own flat-fee implementation service.