A manager prints 300 lapsed patients for the Oak office on a Monday. Staff reach 25 people that week, and most of those calls end at a voicemail beep.
By week three the report is under the appointment binder, and nobody mentions it again. Next quarter, a fresh report prints the same names with a few hundred more added.
Recall doesn't die because staff lack discipline. It dies because a call-down list is the only task at a front desk with nothing forcing it to happen.
Automating patient reactivation outreach in Practice Fusion groups solves that by moving recall off the phone and onto a schedule, so the work runs whether or not Tuesday goes sideways.
The gap between what recall could earn and what it earns today is wide. Curogram client data from clinical settings shows roughly 35% of patients who get a recall text come back and book.
A manual list rarely gets worked past 5% of its names. That difference isn't a marketing number. It's the number of chairs filled next month at each location.
What follows is the operational version of that shift.
Front desks work in interrupt order. A ringing phone, a patient standing at the window, and a portal message from a provider all outrank a printed page of names. Recall calls have nobody waiting on them, so they slide to the end of the day, then off it entirely.
At an office fielding 80 or more inbound calls a day, the list is the only task with no clock attached. Staff aren't ignoring it. They're doing the thing in front of them, which is exactly what we hired them to do.
Give each attempt four minutes: pull the chart, dial, wait, leave a message, write a note. Here's how a 300-name list at our example Oak office typically burns down.
|
Week |
Attempts |
Patients reached |
Booked |
Staff minutes |
|
1 |
40 |
8 |
3 |
160 |
|
2 |
22 |
5 |
2 |
88 |
|
3 |
6 |
1 |
0 |
24 |
|
4 |
0 |
0 |
0 |
0 |
|
Total |
68 |
14 |
5 |
272 |
Most reach attempts end in a recording. Patients call back hours later to a main line that's already busy, reach a different person, and get asked why they're calling. Half of those callbacks never connect to the reason they were dialed in the first place.
Phone tag also destroys context. The staffer who left the message knows the patient is 14 months past a follow-up. The one who answers the callback sees only a name on the caller ID.
Multiply the pattern across five locations and the group has 1,500 overdue patients on paper and roughly 25 booked visits to show for it. Nobody can say which office worked its list, because the only record lives in scattered chart notes and one manager's memory.
Regional leadership then gets an honest but useless answer at the monthly meeting: staff got to some of it. There's no denominator, no response rate, and nothing to coach against.
Unworked names don't sit still. A patient 9 months overdue is reachable and mildly guilty about it.
That same patient at 20 months has usually solved the problem elsewhere, moved, or changed a phone number that no report will ever flag. By the third printing of a name, we're mostly mailing effort into the past.
Segments read Practice Fusion visit history directly, so the list builds itself the same way every cycle. No one exports a report on the 1st, cleans it in a spreadsheet, and re-uploads it somewhere.
That matters most for accuracy. A patient seen last Thursday leaves the overdue segment on Friday, which is the failure mode manual lists never fix. Calling someone who just came in costs credibility, and it's the single fastest way to make staff distrust a recall program.
Each office sends from its own local number, so a patient sees a familiar area code and, often, the exact number saved in their phone. Replies route to that office's queue instead of a central line 40 miles away.
Governance stays at the group level. Message content, opt-out language, and quiet hours are set once and applied everywhere, which keeps compliance review to a single template library.
A campaign can text 300 people in one minute, which is a great way to overwhelm two schedulers. Throttling caps daily sends against the open capacity an office actually has.
If Oak can absorb 12 new bookings a week, we meter sends to produce roughly that many interested replies. The list still gets worked completely. It just arrives at a pace the front desk can convert.
Interested replies land in the shared inbox alongside every other patient thread, tagged with the campaign and the reason the patient is overdue. Whoever picks it up sees the context that a callback to a main line would have lost.
Booked appointments write back to the schedule, so the segment updates and the patient exits the campaign on the next run.
Oak is our example location: five years old, roughly 4,100 active patients, two schedulers, and the printed report from earlier
Setup took one 45-minute session with the office manager. Everything below covers month one, before any template tuning. Nothing here assumes a rebuilt schedule or an added staff member.
It adds the conditions the walkthrough's numbers depend on — panel size, staffing, setup cost, and that this is an untuned first cycle — none of which the four steps state.
We start narrow. For Oak's first month, the segment is patients 12 to 24 months past a completed annual visit, with a mobile number on file and no future appointment. That returns 284 patients.
Names older than 24 months go into a separate, lower-priority segment. Mixing a 14-month lapse with a 4-year lapse in one campaign hides which message is working.
Oak's two schedulers can comfortably book 12 to 15 recall visits a week on top of normal volume. Working backward from a 35% reply-and-book rate, that means roughly 40 sends a week, or about 8 a day.
At that pace, 284 patients take seven weeks to work once. Compare that to the manual version, which reached 14 people and stopped.
Sends go out weekday mornings. Replies arrive fast: most within two hours, the long tail over the next day. A typical day at Oak produces 3 interested patients, 1 opt-out, and a question or two about whether insurance changed.
Staff handle those in the same inbox they use for confirmations. There's no separate tool, no call log, and no chart hunt, because the thread already shows the last visit date and provider.
Interested patients get booked into slots the throttle already accounted for. Non-responders get one follow-up message the next week, then drop to a quarterly cadence.
Here's the month, side by side with the manual list from earlier.
|
Measure |
Manual call-down |
Automated campaign |
|
Patients contacted |
68 attempts, 14 reached |
172 sent, 172 delivered |
|
Interested replies |
7 |
61 |
|
Appointments booked |
5 |
52 |
|
Opt-outs |
n/a |
9 |
|
Staff time |
272 minutes dialing |
95 minutes booking |
Oak finished month one with 112 names still queued and a known conversion rate to plan against. The old list finished with a stack of paper and a guess.
Curogram's Segmented Recall Campaigns turn a static overdue report into a running program.
We build segments once with your team, usually by visit type and months since last seen: annual physicals past 13 months, diabetic follow-ups past 6, post-op patients who never returned for their second visit.
Each segment gets its own template, cadence, and stop rules, all held in a group-level library so 11 offices can't drift into 11 different messages.
Templates carry the office name, the provider when it helps, and one clear next step. A patient who replies with a question gets a person, not a bot loop.
Campaigns run on a monthly cycle by default, with a second touch to non-responders about a week later. Patients who book, opt out, or already have a future appointment drop out automatically, so nobody gets nudged about a visit they've scheduled.
Setup is a one-time working session. After that, the recurring staff task is booking people who raised their hand.
Practice Fusion knows exactly who's overdue. That was never the missing piece. The missing piece was a way to reach 300 people without borrowing 300 minutes from a front desk that doesn't have them.
Ask each office manager what happened to the last recall report. The answers won't be defensive, because none of them chose to abandon it. That consistency across every location is the tell: the call-down list fails structurally, and one more push about follow-through buys nothing.
A campaign engine works the whole panel every cycle and hands staff only the patients who raised a hand. The lapsed panel stops aging quietly in a filing cabinet and starts converting at a rate you can forecast, per office, per month.
Book a demo and we'll build the segments and throttle rates against your offices' real booking capacity, using your own overdue counts.