Most clinics don't have a new-patient problem. They have a patients-who-never-came-back problem. Someone is due for a check-up, a booster or their next treatment session, nobody reminds them, and they quietly drift away. No one notices, because a patient who doesn't book doesn't show up anywhere.
I've built automated recall systems in GoHighLevel for a dental clinic, a veterinary clinic and a chiropractic and physiotherapy clinic. The details differ, but the backbone is the same. Here's how it works and what I've learned building it.
What a recall system actually replaces
Before automation, recall usually looks like one of these:
- A paper recall book that someone works through when they have time
- Vaccine or check-up due dates tracked from memory
- Front-desk staff making reminder calls between patients
- No follow-up at all once a patient stops rebooking
All of these depend on someone remembering, during the busiest part of the day. That's why recall is one of the first things to slip, and one of the most profitable things to automate.
The recall pipeline, step by step
- Self-booking. Patients book their own slot from live availability, matched to the right appointment type and provider.
- Confirmation and reminders. A layered SMS and email sequence confirms each booking. In the chiropractic build, reminders go out at 48 hours and again at 2 hours before the session.
- The clinician treats the patient. This stays entirely human: examination, diagnosis and treatment.
- The next due date is set. Once the clinician logs the recommended follow-up interval, the next visit is scheduled automatically.
- Recall fires on time. When a patient is due or overdue, they get a recall message with a booking link.
- Reactivation for the lapsed. Patients who've gone quiet for a longer period get a structured reactivation sequence instead of being forgotten.
Three versions of the same idea
Dental: replacing the paper recall book
For the dental clinic, overdue patients are now surfaced automatically and sent a recall campaign. The cancellation waitlist became automatic too: when someone cancels, the next waitlisted patient is offered the slot before the chair sits empty. Automated confirmations and reminders cut no-shows by 27%. Read the dental case study →
Veterinary: recall per pet, per species
Vet recall is harder than it looks, because the next due date depends on the visit type and the species. After each visit, the system calculates the pet's next vaccine or wellness check and schedules the reminder. Prescription refill reminders go out before medication runs out, so that revenue stays with the clinic instead of a pharmacy down the road. Read the vet case study →
Chiropractic and physio: catching drop-off mid-plan
Here the goal isn't yearly recall, it's finishing a treatment plan. If a patient hasn't rebooked within their expected window, staff get a drop-off alert while there's still time to step in. That build led to 42% more patients completing their full treatment plan. Read the chiropractic case study →
Where GoHighLevel needs custom logic
GoHighLevel handles reminders and campaigns well, but recall often needs a calculation the platform doesn't do natively: a pet-specific due date from a logged visit, or an individual patient's rebooking window based on their treatment plan. In those builds I wrote that logic myself against the GoHighLevel API rather than forcing every patient onto one generic timeline.
Getting the timing right
Timing is everything in recall. Too early feels like nagging. Too late and the patient has already gone elsewhere. A few rules I follow:
- Clinicians set the intervals. In the chiropractic build, practitioners set the rebooking window for each treatment type from their own experience, not an industry average.
- Vets check the rules first. A wrong vaccine interval isn't just annoying, it's wrong information about an animal's care. The vets checked the recall logic against their own protocols before a single message went out.
- Run it silently first. Drop-off alerts ran quietly for a few weeks before any patient-facing message was switched on. In the dental build, the new system ran alongside the old process for a month until staff trusted its output.
- Write like the clinic, not a robot. A warm message from "the team at [Clinic]" gets far more bookings than a generic reminder.
What stays human
Clinical decisions never move into automation. The system books, reminds, recalls and follows up. The clinician examines, diagnoses and treats. That separation is what makes staff comfortable with the system, and it's why patients experience it as good care rather than marketing.
Want this for your clinic?
If your recall still depends on a book, a spreadsheet or someone remembering, it's one of the highest-return systems you can automate. I build recall and retention systems in GoHighLevel, with custom logic for the parts the platform can't do on its own.