Included in No-Show Shield
Reminder & recall automation
The three messages that decide whether an appointment happens
$900 build, +$40/moDays 8–14 of the build; recall sequences layer on at Tier 2
The leak
No-shows that were decided in the 48 hours before the appointment, and recall visits that were never rebooked at all.
Confirmation on booking, a nudge at 48 hours, a final one at 24. Then the recall sequences that create the next appointment entirely on their own.
Where this sits
This module is part of No-Show Shield. It is not sold on its own, because the handoff between it and the module beside it is where revenue actually escapes.
Journey stage 3 · The appointment waits
Between booking and arrival, life happens. Without a confirmation, a 48-hour nudge and a 24-hour reminder, the decision to not show gets made in silence.
Industry no-show rates run 10–25% of booked appointments. Each empty slot is 100% lost revenue with the staff time already spent.
Handoff · Confirmation
Medium leakUnowned: Verbal. Nothing in writing.
Owned by this module: Automation layer
Handoff · Reminder
High leakUnowned: Sent if someone has time that day.
Owned by this module: Automation layer
What gets built
The deliverable, stated the way the contract states it
Email and SMS sequences that run without anyone starting them. Reminders protect the appointments you have; recall and reactivation sequences create the ones you do not have yet.
At a glance
- Itemised value
- $900 build, +$40/mo
- Build window
- Days 8–14 of the build; recall sequences layer on at Tier 2
- Sold inside
- No-Show Shield
Yours at handover — domain, accounts, data and source code.
How it works
The mechanism, not the marketing
Trigger on the left, the rule the system applies in the middle, the consequence on the right. Read it as the logic your practice would otherwise be running in someone's head.
admin.yourpractice.com/sequencesIllustrative interface
| Trigger | Message | Sequence stops when |
|---|---|---|
| T+0 · on booking | Confirmation over email and SMS | The appointment exists in writing |
| T−48h | Reminder over email and SMS | Client confirms, reschedules, or books nothing new |
| T−24h | Final reminder | Client confirms or reschedules |
| Due date reached | Recall message with a booking link attached | Client books |
| Past expected return window | Reactivation sequence | Client books |
| After the visit | Review request | Runs once, on schedule |
- Quiet hours respected
- Conditional, not blanket sends
- Wording editable
Capabilities
What it does, and why that matters commercially
Three-touch reminder sequence
On booking, at 48 hours and at 24 hours — over email and SMS. This is the window where attendance is actually decided.
Recall that fires on due dates
Vaccination due dates, six-month hygiene, care-plan visits. When the date arrives the message goes out with a booking link attached, whether or not anybody pulled a report.
Reactivation for clients who went quiet
Clients past their expected return window surface automatically and enter a reactivation sequence, instead of sitting in a database nobody queries.
Post-visit review requests
Review requests go out on a schedule after the visit, so your public reputation stops depending on someone remembering to ask.
Conditional logic, not blanket sends
Sequences stop when the client books, respond to appointment type, and respect quiet hours. Over-messaging costs trust and deliverability.
Implementation
How this gets built, and when it is done
Same standard as every module: a milestone you can verify yourself, not a status report.
Timeline
Days 8–14 of the build; recall sequences layer on at Tier 2
Definition of done
The build is accepted when the client can complete a live booking, receive a reminder, and complete a test payment without error.
Built on
- Node.js workflows
- Twilio
- SendGrid
Deployed on infrastructure registered in your name. You hold the accounts, the data and the source code when the build completes.
Who it matters most for
The practices where this leak is largest
Every practice loses something here. These are the ones where it is the dominant loss rather than a minor one.
Dental practices
Two separate leaks: same-week no-shows, and recall appointments that were never rebooked at all. The second one is larger and almost never measured.
Dental systemsVeterinary practices
No-shows sit around 10–12% of booked appointments. Each one is a slot that was staffed, prepared and then paid for by nobody.
Veterinary systemsPhysiotherapy & chiropractic clinics
Cancellations concentrate mid-plan. The patient feels better around visit four, cancels visit five, and never reschedules the remaining seven.
Physio & Chiro systems
This module on its own is a smaller answer
It closes one leak. The reason it is sold inside a tier is that the next leak sits immediately beside it, and an unowned handoff costs the same whether or not the module beside it is good.
Questions
Automation layer, in detail
Who pays the SMS costs?
You do, directly to the provider. Third-party fees are excluded from the Care Plan by design, so you are never paying a markup on your own message volume.
Can we change the message wording?
Yes. Message content is editable and changes fall inside your Care Plan change-request hours.
Is this the same as an AI receptionist?
No, and we do not sell an AI receptionist. These are deterministic sequences with defined triggers. If a capability is not built and tested, we do not put it in a proposal.
Next step
Find out what your booking flow is costing you
Send the four numbers your practice already has. You get a written figure for the monthly revenue your current flow is leaking, and a recorded teardown of where it goes. Three business days, no obligation, no call required.
- 20 minutes discovery call, only if you want one
- 90-Day No-Show Recovery Guarantee
- 3 new practices a month