GoHighLevel no-show recovery, and the hour that matters

The answer, before the reasoning

No-show recovery is the sequence that runs after somebody fails to attend a booked appointment, with the aim of rebooking them while the day is still theirs to change. It is a distinct job from reminders, which run before the appointment and try to stop the miss happening at all.

Most accounts build the reminders and stop. That is why the recovery work is where the return is: the reminder ladder is competitive territory and the hour after a miss is usually empty ground.

The systems in this library are built to a target of 70% no-show recovery. That is the target the build is written to hold, not a measured outcome from anybody’s account, and it should be read as an engineering aim in the same way a service level is.

Why the hour matters

Somebody who does not arrive at two o’clock is, at three o’clock, a person who knows they missed something and has not yet decided how they feel about it. Contact inside that window is received as diligence. Contact the next morning is received as a complaint, and contact three days later is received as marketing.

There is a practical reason too. Within the hour the customer still knows why they did not come. The reason is fresh, specific and usually mundane: the car, the school run, a meeting that overran. That reason is the thing you need in order to rebook them intelligently, and it decays fast.

The ladder before the miss

Reminders exist to make the appointment feel like an appointment. The mistake is to build them as a countdown of identical messages. Each rung should do a different job.

Rung	When	What it does
Confirmation	On booking	States the time, the place, what to bring and what happens if plans change. Sets the reschedule link as the easy path so cancelling never means silence
First reminder	The day before	Asks for a reply rather than announcing. A message that requires an action gets read; one that announces gets swiped away
Morning reminder	The morning of	Names the practical detail that gets people there: where to park, which entrance, the deposit already paid, the technician’s name
Short-notice nudge	Before the slot	Only where the trade warrants it. A restaurant table on a Friday warrants it; an annual review does not

Two rules govern the ladder. Anyone who confirms should stop receiving reminders, because continuing to remind a confirmed customer is how you teach people to ignore your messages. And every rung must offer rescheduling as prominently as attendance, since a rescheduled booking is a kept booking and a cancelled one you were told about is worth more than a silent absence.

The recovery sequence after the miss

Trigger it on the appointment status changing to no-show rather than on a fixed time after the start, so that a customer who arrives twenty minutes late is not chased for missing an appointment they attended.

Inside the hour, one call. A real attempt at a conversation, not a voicemail drop, and the question is the simple one: is now a bad time or a bad day. If it is a bad day, rebook on the call. If nobody answers, leave something short that does not scold.

Follow with a message the same afternoon carrying two live rebooking options rather than a link into an empty calendar. Choosing between two named times is a decision people make in seconds. Opening a calendar and finding thirty slots is a task they postpone.

Then stop, or nearly. One more attempt the following day at a different hour, because the reason you missed them may simply be that they never answer at that time. After that, the contact stops being a recovery case and becomes a dormant record, which is a different sequence entirely and is handled in working a dormant list without spam.

The arithmetic, with the assumptions on the table

Substitute your own numbers here. Suppose you run forty booked appointments a week and four of them do not arrive. Suppose an appointment is worth two hundred dollars to you. That is eight hundred dollars a week sitting in the missed column, and it is not a marketing problem, since you had already won those customers once.

Now suppose the recovery sequence rebooks most of them, which is what the 70% target is aiming at. The value returned is a function of your own appointment value and your own miss rate, and the only figures above that came from anywhere but this paragraph are your own. That is deliberate. Any supplier quoting a return without telling you what they assumed has quoted you a number about their business rather than yours.

Why the wording is trade-specific

Recovery copy that could belong to any business is recovery copy that persuades nobody, because the reason for the miss is different in every trade.

A dental practice is speaking to a patient who may have avoided the appointment rather than forgotten it, and the recovery has to be gentle about that possibility without ever putting a clinical statement in a text message. The Dental Practice edition is written around it.

A restaurant is not recovering a person at all. It is recovering a table on a Friday evening, the recovery window is measured in minutes rather than hours, and the right action is often to release the cover to somebody else while sending the original guest a reason to come back another night. The Restaurant edition treats a no-show as a covers problem, which is what it is.

Move either sequence into the other trade and it stops making sense. That is how you know it was written rather than assembled.

What to check before you trust it

Deliberately no-show one of your own test bookings and let the whole sequence run against a live number. Confirm the recovery does not fire for late arrivals, that a customer who replies gets a human rather than the next scheduled message, and that opting out of reminders does not silently opt them out of the confirmation they actually need. The full picture of which components carry this work is set out in what lands in a snapshot.