Automate eCW Reactivation Outreach | End Call Lists

A multi-location practice sent SMS recalls to patients overdue for follow-up care. Within a month, 35% of the people who got one booked an appointment.

Based on our internal data, that single effort brought back 1,240 patients who were already on the books and simply hadn't returned.

Now compare that to the recall report sitting on the printer at your busiest site.

The report is real. The intent behind it is real. What's missing is the labor to work it. Recall by phone competes for the same hands that answer the ringing line, sort a copay dispute, and check in the 9:15. Triage wins, every time, at every location.

We've watched this play out across ambulatory groups running eClinicalWorks. A manager prints 400 lapsed names in January.

By early February, maybe 40 have been dialed. Most of those were voicemails. In April, a fresh report prints the same names plus a few hundred more.

Nobody on that team is lazy. The task is structurally unwinnable when it's assigned to people whose day is already spoken for.

Automating patient reactivation outreach in eClinicalWorks networks fixes the labor problem rather than the motivation problem.

Campaigns go out on a schedule, segmented from visit data, sent from each site's local number, and paced to match how many slots that site can actually fill. Staff never dial a lapsed patient again. They book the ones who write back.

This article covers what the call-down list really costs, how a reactivation campaign workflow for a medical group is built, and what changes at the front desk when the yeses arrive instead of the list.

The Call-Down List

Recall by phone is honest work. It also loses to triage daily. A patient at the window needs an insurance card rescanned, line 2 is a pharmacy, and line 3 is a parent asking whether a rash needs a visit. The lapsed-patient report waits through all of it.

That waiting has a pattern. Calls to overdue patients are the only task on the desk with no one standing there to escalate it. A missed refill request generates a complaint. A missed recall call generates nothing at all, which is exactly why it keeps getting skipped.

Managers who track staff time on patient outreach calls find the same shape every quarter. Effort spikes in week one, drops off in week two, and disappears by week three. No meeting fixes it, because the constraint isn't attention. It's hours.

What 400 Names Actually Costs

Run the arithmetic on a single location's list. Each attempt takes a few minutes: pull the chart, dial, wait, leave a message, note the attempt. Most calls reach voicemail, and a voicemail is not an outcome.

Here's the attrition pattern we see repeatedly across sites. Figures below are illustrative, drawn from the shape of manual recall work rather than a single measured campaign.

The Same Names Print Again Next Quarter

Nothing removes a name from that list except a completed visit. So the January report prints again in April with the untouched 360 still on it, plus everyone who lapsed in the meantime.

A group with six locations doesn't have one abandoned list. It has six, each growing independently, each with a manager who assumes the other sites are somehow keeping up.

The list also gets stale between prints. A patient who moved, switched plans, or already booked online stays on the sheet until someone dials and finds out. Staff burn attempts on names that shouldn't be there.

By the third print, most teams stop reading it closely. The document becomes a formality that exists to prove recall is being handled.

Reactivation Stalls Below 10% Execution

Reactivation carries the strongest return of any outreach a group runs. These patients already chose you. They're in the system, their insurance is on file, and they don't need to be acquired.

Yet it's the outreach most likely to go unexecuted. Reminders fire automatically. Balance notices go out with statements. Recall depends entirely on someone finding a free hour that doesn't exist.

The gap between the value of the task and the odds of it happening is what makes overdue visit outreach automation worth building.

Every unworked name is a scheduled visit that never gets scheduled, at a slot that stays empty, at a location that could have filled it.

The Panel Recovery Engine

Recall call list automation for eCW groups begins where the printed report begins: visit history. A segment is a rule, not a document.

Patients seen for an annual over 13 months ago, with no future appointment and an active phone number, belong in one group. Post-op patients missing a 6-week follow-up belong in another.

Rules refresh on their own. When a patient books, she leaves the segment. When another patient crosses 13 months, she enters it. Nobody re-runs a query or exports a spreadsheet.

That single change removes the staleness problem. Messages go to people who are actually overdue on the day the campaign sends, not on the day someone last pulled a report.

Segments can also be narrowed by provider, visit type, or site, so a dermatology location isn't sending skin-check reminders to a family medicine panel two towns over.

Local Numbers, Templates Approved Once

Patients answer numbers they recognize. A text from the 626 number they already have saved reads differently than one from a national short code. Each location sends under its own identity while the network keeps control of what's said.

Templates are written and approved once at the group level. A site manager can adjust which segments run and how fast, but can't rewrite compliance language or drop the opt-out instruction. That split matters when 12 locations share one brand and one legal exposure.

Language variants live in the same template set. If a location's panel is 40% Spanish-speaking, the segment sends accordingly without a separate campaign build.

Throttling Keeps Replies Bookable

Sending 2,000 texts on a Monday morning creates a different problem than the one you started with. Campaign throttling matches booking capacity, releasing messages in batches sized to what schedulers can handle.

Reply estimates above are illustrative. Caps get tuned against each site's real capacity during setup, then adjusted as the schedule fills or opens up.

A saturated location can run at a trickle. A new site with an empty book can run wide open. Same campaign, different valve setting.

Replies Land in One Place

A patient who writes "yes, can I come in Thursday?" arrives in the shared inbox with her name, her last visit date, and the campaign she responded to attached. No one hunts for context.

Booking is done in the normal flow, and the confirmed appointment goes back to the eCW schedule. The patient exits the segment automatically.

Per-Location Recall Reporting

Per-location recall reporting turns recall into a funnel with real numbers: messages sent, replies received, appointments booked, revenue attributed. Each site sees its own figures. Network leadership sees all of them side by side.

That's the report worth printing. It shows what happened rather than what should have.

How Curogram Runs Recall Without Running Your Staff

Segmented Recall Campaigns handle the part of reactivation that never gets done by hand. Curogram builds the segment rules against eCW visit history during setup, so the list defines itself and refreshes every cycle without an export.

Each location sends from its local number under templates your network approves once. Site managers control cadence and which segments run at their location, while the message content stays governed centrally. That structure holds up when you add a seventh or twelfth site.

Throttling is set against each site's real open capacity, not a guess. If your North office has 60 slots over three weeks, the campaign releases messages at a pace that keeps replies inside what one scheduler can book in a morning.

Replies land in the unified inbox with the patient's history and campaign attached. Your team books from there, and the appointment writes back to the eCW schedule. The patient drops out of the segment on her own.

Reporting closes the loop by site. Sends, response rate, and booked appointments attributed to each campaign, month over month. When a location manager asks whether recall is working, the answer is a number rather than an impression.

Setup is a configuration project measured in hours, not a change-management program. Once segments, templates, and throttles are set, ongoing staff involvement is the booking work your schedulers already do every day.

Conclusion: Never Print the List Again

The call-down list doesn't fail because your team lacks discipline. It fails because it asks people mid-triage to do cold outreach, and that assignment loses to the ringing phone in every clinic we've worked with.

eCW already knows who's overdue. That record is yours, and it's accurate. What it can't do is reach out on its own.

Try this before your next quarterly review. Ask each location manager what happened to the last recall report they printed. Count how many names were called. That number is your business case, and it will be smaller than anyone expects.

Then decide whether 400 names deserve another quarter of good intentions.

Schedule a demo and we'll map segment logic and throttle rates against your locations' actual booking capacity.

Frequently Asked Questions