Tie each reminder to the visit number, not to a generic schedule: rebook before the patient leaves, send a short reminder the day before, recover a missed visit within hours, and flag two misses in a row for a call from the doctor. GoHighLevel can run the sequence from appointment status and a visits completed field. The bottom line: a care plan only works when patients attend the visits in it, and most of the loss happens in the gaps between visits that nobody is watching.
Why a care plan needs its own reminder logic
A general appointment reminder treats every visit the same, and our guides on reminders that stop on a reply and same day cancellations cover that layer. A chiropractic care plan is different because the visits are a sequence with a purpose. Visit 3 is not like visit 11, a missed visit in week 2 costs more than one in week 6, and the plan ends with a re examination that decides what happens next. The reminder system should know where the patient is in the plan.
The sequence, by visit
| Moment | What goes out | Who acts |
|---|---|---|
| Before the patient leaves | The front desk books the next visit and the workflow sends a confirmation | Front desk |
| Day before each visit | A short reminder with the time and a reply option | Workflow |
| Visit missed | A text within 2 hours offering two times, and a call task the next morning if there is no reply | Workflow, then front desk |
| Two visits missed in a row | A task for the doctor or care coordinator to call | Doctor or coordinator |
| Visit 4 and visit 8 | A short check in: how are you feeling about the plan? | Workflow, replies to staff |
| Visit 12 | Booking link for the re examination, sent a week before | Workflow |
Appointment reminders and the recovery text are treatment related, but they still go through your consent process. The FCC's healthcare exemption conditions for calls and texts, as summarized by law firm guides, include that the message is free to the patient and limited in content and frequency, so keep each message short and avoid anything promotional.
Build it in HighLevel
- Add a contact field called Visits completed and a field called Plan length, and set them when the care plan is accepted.
- Create a workflow with the Appointment Status trigger set to Showed that adds one to the visit count in your system and updates the field. If your account cannot do the arithmetic, have the front desk update the field at checkout.
- Start a second workflow with the Contact Changed trigger on Visits completed. Use If/Else branches on 4, 8, and 11 to send the check in and the re examination link.
- Create the day before reminder from the Appointment trigger with a Wait step, and add an If/Else to skip it if the patient has already confirmed.
- For missed visits, use the Appointment Status trigger set to No show to send the recovery text and add the tag Missed visit.
- Add an If/Else on the tag Missed visit. If it is already present from the previous visit, create a task for the doctor instead of sending a second text.
- Remove the tag Missed visit when the next appointment shows, and turn on Stop on Response so replies reach a person.
A recovery text, written out
Sample: Hi Maria, this is [Clinic]. We missed you today. We have openings tomorrow at 9:15 or Thursday at 4:30. Reply with the one you prefer, or call us at [number]. Reply STOP to stop messages. The text says nothing about the reason for the visit, the condition, or the plan.
Worked example
A clinic that starts 20 new care plans a month with 12 visits each schedules 240 visits a month from new plans (20 times 12). If 10 percent of those visits are missed, that is 24 missed visits (240 times 0.1). A recovery text within 2 hours that rebooks half of them puts 12 visits back on the calendar each month. The 10 percent and the half are assumptions, so replace them with your own numbers after a quarter.
Privacy limits
A reminder that names a condition or a treatment discloses health information to anyone who sees the screen, so keep texts generic. HighLevel's help center describes a HIPAA compliance option that has to be enabled, and you should confirm the business associate agreement and settings before patient messages run through the account.
When the plan changes midway
The re examination at visit 12 is not the only point where a plan changes. A doctor may shorten a plan when a patient improves quickly or extend it when progress is slower. Keep the Plan length field editable by the front desk, and have the workflows read it at each step, so the visit 11 message goes out at the right time for a 16 visit plan. A reminder system that assumes 12 visits sends the wrong message to every patient whose plan differs.
Patients who pause on purpose
A patient who travels for two weeks is not a missed visit. Add a tag On hold with a date field for when it ends, and use an If/Else at the start of each workflow to skip patients with the tag. A Custom Date Reminder on the end date creates a task to rebook, so a pause does not become a drop out.
How this was handled before
A front desk person scanned the schedule each morning for no shows and called them, and the doctor learned about a pattern of misses at the re examination. A visit count and a miss tag move that pattern to the second missed visit instead of the twelfth.
What to measure
Track visits completed per plan, missed visits recovered within 24 hours, plans with two misses in a row, and re examinations booked before visit 12. The share of plans that reach the re examination is the number that matters most.
Questions people ask
How should a chiropractic clinic remind patients about a care plan?
Send a short reminder the day before each visit, rebook before the patient leaves, recover missed visits within hours, and flag two misses in a row for a call from the doctor.
Can a reminder text name the condition?
No. Keep it generic with the time and the clinic's name, since a message that names a condition discloses health information.
How many missed visits should trigger a call?
Two in a row is a common trigger, since one miss is usually a scheduling problem and two suggests the plan is at risk.
To build the visit number sequence, start a GoHighLevel account here. The appointment workflows are shown in our capabilities demo.
