Sound familiar?
You've worked on recall before. Here's why it didn't stick.
None of these are dumb — each covers one gap. They leak because nobody measured which gap was actually draining the file.
"We rebook everyone at checkout"
The gold standard — for the patients who book. The system's whole weakness is the "I'll call you" exit, and checkout rebooking has no answer for it except hope. Measure what share of your checkouts leave unbooked; that share is your quiet file's intake valve, and it needs a sequence, not a promise.
"Our software sends recall reminders"
Probably one touch, on the due date, into the channel configured five years ago — and nobody watches whether it lands or what happens after. Owning recall software and running a recall SYSTEM are different facts; the most common discovery finding is a tool faithfully sending touches nobody receives.
"We did a reactivation blast once"
One email to the whole lapsed list, eighteen months ago, decent response, never repeated. That response WAS the evidence — the file is alive — but a blast is an event, and lapsing is a process. The patients who lapsed since have never been asked. Reactivation only compounds when it runs continuously.
"Front desk calls the overdue list"
When there's time — and the measured version of "when there's time" in a busy practice is a third of follow-ups never happening. Calls also reach voicemails at dinner. Human touches are the premium layer of recall; they can't be its foundation.
"We send postcards"
One channel, no reply path, and unmeasurable — nobody knows which cards worked. Fine as a warm accent for the right patients; as the system, it hands your cheapest revenue stream to the postal service and memory.
What measuring changes
Each attempt covers one gap. The measurement shows which gap is actually draining YOUR file before you spend again. That's the whole service.
Find your draining gap
The free score names it. The $500 discovery proves it with timestamps.
Score your recall