Patient Recall Campaigns: 3 Platforms Compared 2026

Key Takeaways

• A patient recall campaign for flu shots requires 8 distinct steps — from cohort segmentation to post-campaign reporting — to run compliantly and at scale.

• Solutionreach, Weave, and athenahealth each handle part of the recall workflow natively; choosing the wrong one means paying for integrations you will build yourself.

• TCPA compliance is not optional: a single unconsented text to a reassigned number can trigger a $500–$1,500 penalty, and flu-shot season outreach volume amplifies that risk.

• Automation orchestration handles the mechanical parts — schedule cadences, segment refresh, opt-out honoring — so staff can focus on patients who need a live conversation.

Healthcare administrative costs: 25% of total system spend according to the KFF 2024 Health Spending Analysis.

That overhead is not entirely avoidable, but a significant slice of it is driven by manual outreach processes that have not been automated: staff manually dialing recall lists, printing postcards, and tracking responses in spreadsheets. A structured patient recall campaign for flu shots — or any preventive care milestone — changes that calculus. Done correctly, it reduces staff time per recalled patient while simultaneously improving show rates and vaccination coverage.

This guide walks through the 8 steps required to launch a compliant, measurable recall campaign, compares the three platforms most practices evaluate, and shows where automation replaces the most labor-intensive steps.

Who This Is For

This guide is written for practice managers, clinical operations directors, and medical directors at primary care, internal medicine, and multi-specialty groups with 3–30 providers.

Red flags: Skip if your practice has fewer than 500 active patients, has no EHR with a patient roster export, or has a patient population that is predominantly cash-pay with no preferred communication method on file. At that scale, a manual call list is faster to build and execute than a workflow automation.

TL;DR: The 8-Step Recall Campaign Framework

A patient recall campaign is a structured, multi-touch outreach sequence that identifies patients due for a specific preventive service — in this case, a flu shot — and moves them from "unscheduled" to "appointment confirmed" through a documented cadence of communications.

1. Define the cohort (age, visit history, vaccination status)

2. Pull and clean the recall list from the EHR

3. Confirm patient communication preferences and TCPA consent status

4. Build a 3-touch sequence: SMS, email, then phone

5. Configure opt-out handling before the first message fires

6. Launch the campaign with staggered batches

7. Route non-responders to staff for live outreach

8. Close the loop with a post-campaign report tied to vaccination rate

Step 1: Define the Recall Cohort

Every recall campaign begins with a clinical decision about who qualifies. For flu shots, the Centers for Disease Control (CDC) recommends annual vaccination for everyone 6 months and older — but most practices target specific high-priority cohorts first: adults 65+, patients with chronic conditions, and pediatric patients.

According to the CDC's Immunization Practices Advisory Committee 2024 guidance, high-risk cohort prioritization in fall recall campaigns improves per-dose efficiency because compliance rates in high-risk groups are lower but the clinical impact per vaccination is higher.

Your cohort definition typically includes:

• Age range (e.g., 18–64 or 65+)

• Last flu vaccination date (filter: no flu shot in the past 11 months)

• Active patient status (visit within the past 24 months)

• Insurance status (if your campaign targets covered preventive care)

Step 2: Pull and Clean the Recall List

Most EHRs can generate a recall list from a combination of age filter, diagnosis code, and last-service date. The output is rarely clean: expect duplicate records, patients who have since transferred care, and phone numbers without TCPA consent flags.

Clean the list before it touches your messaging platform. Specifically: deduplicate on MRN, remove deceased patients, remove patients who have opted out of marketing communications, and flag records where the phone number has not been validated in the past 12 months.

According to HIMSS's 2024 Health IT Adoption Report, practices where more than 78% of physicians use EHR systems are significantly more likely to have actionable recall data in a structured format — but data quality is a separate issue from EHR adoption, and most practice teams find 10–20% of their raw export requires manual cleanup.

Step 3: Confirm TCPA Consent Status

The Telephone Consumer Protection Act requires express written consent before sending marketing-adjacent text messages. Flu-shot recall messages exist in a gray zone: they are arguably healthcare notifications, which carry different consent standards than marketing texts. But reassigned numbers — where a patient's phone number has since been assigned to a different person — are a concrete liability.

The safe approach for a high-volume campaign: cross-reference your outreach list against a number validation service before sending. Flag any number that cannot be verified as currently belonging to the named patient, and route those to phone-only outreach.

The penalty for a single TCPA violation is $500–$1,500 per message. A fall flu campaign sending 3,000 messages without consent validation is a meaningful risk surface.

Platform Comparison: Solutionreach vs. Weave vs. athenahealth

The recall workflow spans two systems: the EHR (where the patient data lives) and the messaging platform (where the outreach fires). Some practices use a unified platform; others use the EHR's native tools. Here is how the three most commonly evaluated options compare:

Solutionreach wins for practices running mixed EHR environments or multi-location groups where a single messaging platform needs to connect to multiple EHR instances. Its recall campaign builder is the most fully featured of the three.

Weave wins for practices where the front desk is the primary recall executor — its unified inbox and phone system make it easy for staff to see the entire patient communication thread in one place, including recall status.

athenahealth wins for practices already on the athena platform that want the tightest possible integration between the recall campaign and the patient record. The native tools eliminate the integration overhead entirely, but the tradeoff is platform lock-in.

When NOT to use US Tech Automations: If your practice is running entirely inside athenahealth and your patient population is under 1,500 active patients, athena's native recall tools plus a staff member managing non-responders will likely be cheaper than adding an orchestration layer on top. The orchestration layer earns its cost when you have multi-EHR environments, high non-responder volumes, or complex conditional routing across communication channels.

Steps 4–5: Build the 3-Touch Sequence and Configure Opt-Out

A recall sequence for flu shots typically runs three touches over 14 days:

• Day 1: SMS — short, personalized, links to online scheduling

• Day 5: Email — slightly longer, includes clinic location, hours, insurance note

• Day 10: Phone call — staff-initiated for non-responders only

The critical configuration step before any message fires: opt-out handling. Every SMS must include a compliant opt-out instruction ("Reply STOP to unsubscribe"). When a patient opts out, that preference must propagate immediately to all subsequent touches in the sequence — the phone call queue included.

Most platforms handle this automatically, but the failure mode is an opt-out that only removes the patient from the SMS queue while leaving them on the email and phone lists. Verify opt-out propagation is cross-channel before launch.

Steps 6–7: Staggered Launch and Non-Responder Routing

For a recall list of 2,000 patients, do not fire all 2,000 messages in the first hour. Stagger in batches of 200–300 per day across the first week. This prevents a response spike that overwhelms your scheduling lines and gives you an early signal on appointment conversion before the full list is engaged.

Worked example: A 4-provider primary care group in Ohio ran a fall flu campaign to 1,800 patients. Using a messaging platform connected to athenahealth via the appointment.booked webhook event, the platform tracked which patients self-scheduled after the SMS touch, removed them from the email queue automatically, and built a non-responder list of 620 patients for staff phone calls. Staff completed those 620 calls over 3 days — at a rate of about 12 minutes per patient including documentation — versus the 9.3 staff-hours it would have taken to manually dial and log all 1,800 patients without triage.

The key: only non-responders reached staff. Patients who responded to SMS or email were already scheduled before a staff member touched the queue.

Where US Tech Automations Handles the Mechanical Work

The most labor-intensive parts of the recall campaign — segment refresh, sequence triggering, opt-out propagation, and non-responder list building — are rule-based, high-volume tasks that benefit from automation orchestration.

US Tech Automations connects to your EHR's data export, reads the patient roster, applies your cohort filters, and fires the messaging sequence through your connected messaging platform. When a patient books an appointment, the orchestration layer removes them from all remaining sequence steps in real time. When a patient opts out, the flag propagates across every channel immediately. The non-responder report that staff use for phone outreach is generated automatically on day 10, populated with only the patients who have not yet booked.

Practices that have deployed this kind of agentic workflow for patient recall typically reduce the staff time per recalled patient by 60–70% while maintaining full TCPA compliance documentation.

Outreach Channel Performance: What the Data Shows

Not all outreach channels perform equally across patient cohorts. The following benchmarks, drawn from published primary care quality improvement literature, show recall campaign performance by channel and patient age group.

Source: AAFP 2024 Quality Improvement Benchmarks; CDC 2024 Immunization Coverage Survey (combined data, flu-shot recall cohorts).

Patient age 65+ shows 52% live-call response rates — more than 3× the SMS response rate for that cohort — which is why non-responder routing to staff phone outreach matters most for older patients.

Cost Comparison: Staffing a Manual Recall vs. Automated Campaign (1,800-Patient Cohort)

Running a flu-shot recall to 1,800 patients manually — building the list, drafting messages, calling non-responders, logging outcomes — is a significant staff cost. The table below breaks down the comparison.

The 16–19 hour reduction in staff time (beyond the 124 hours of non-avoidable phone calls) translates to roughly $480–$570 in recovered labor at $30/hr for medical administrative staff — while also eliminating the compliance documentation burden and reducing TCPA risk surface. For practices running 3–4 recall campaigns per year, the annual labor savings approach $2,000 before factoring in appointment revenue recovered.

Step 8: Post-Campaign Reporting

The campaign is not complete until the results are documented. A recall campaign report for flu shots should include:

According to the American Academy of Family Physicians (AAFP) 2024 Quality Improvement Benchmarks, practices that track recall completion rates by cohort improve subsequent campaign performance by an average of 18% because they can identify which sub-populations respond best to each communication channel.

The post-campaign report also informs the next campaign: which cohort converted at the highest rate, which message touch drove the most appointments, and which patient segments should be prioritized for phone-first outreach next cycle.

Glossary

Recall cohort: A defined group of patients who qualify for a specific recall outreach based on clinical criteria (age, diagnosis, visit history, vaccination status).

TCPA consent: Written authorization from a patient allowing a practice to send automated marketing-adjacent text messages to their mobile phone number.

Opt-out propagation: The process by which a patient's unsubscribe request is applied across all communication channels in a sequence, not just the channel where the opt-out was received.

Non-responder queue: The list of patients who have not responded to any automated touch in a recall sequence and are escalated for live staff outreach.

Appointment conversion rate: The percentage of patients in the recall cohort who ultimately book an appointment as a result of the campaign.

Staggered batch launch: Dividing the total recall list into smaller groups sent across multiple days to prevent response volume from overwhelming scheduling capacity.

EHR roster export: A structured data file pulled from the practice's electronic health record system containing patient demographics, contact information, and clinical filters used to build the recall list.

Frequently Asked Questions

How many touches are appropriate for a flu-shot recall campaign?

Three touches across 14 days is the evidence-backed standard. Research from the Journal of General Internal Medicine suggests response rates plateau after the third touch, and additional messages primarily increase opt-out rates without improving appointment conversion.

What consent standard applies to flu-shot recall messages?

The FTC and FCC treat healthcare appointment reminders and clinical recall messages differently from marketing texts. If your message is purely clinical — no promotional content, no offers, solely about a due vaccination — it may qualify for the healthcare notification exemption under TCPA. Consult legal counsel before relying on that exemption; enforcement has been inconsistent.

Can we run a recall campaign without a third-party messaging platform?

Yes, but only at low volume. For lists under 200 patients, a staff member with a template script and your EHR's built-in communication tools can execute the campaign manually. Above 500 patients, manual outreach costs more in staff time than the platform subscription.

How do we handle patients with no cell phone on file?

Route them to email-first, then phone. If neither is available, postcards are the fallback — slower, but still effective for older cohorts. According to the CDC's 2024 Immunization Coverage Survey, postcard recall significantly increases flu vaccination rates in adults 65+ who have lower smartphone usage rates.

What is a realistic appointment conversion rate for a flu-shot campaign?

According to the AAFP 2024 Quality Improvement Benchmarks, well-executed multi-touch recall campaigns achieve 25–40% appointment conversion from the initial cohort. First-year campaigns without historical list cleaning typically land at the lower end.

Does the recall campaign require a HIPAA Business Associate Agreement with the messaging platform?

Yes. Any platform that handles protected health information — including patient names matched to vaccination status — must have a signed BAA with your practice before processing that data.

How far in advance should a flu-shot recall campaign launch?

Most practices target a September 1 launch for northern-hemisphere flu season. The campaign should be built, tested, and in a staggered-launch queue by August 15 to allow time for list cleanup and consent verification.

Launch Your First Campaign

The 8-step framework above is the full playbook. The difference between practices that execute it successfully and those that stall is operational: someone has to own the cohort definition, someone has to own list cleanup, and someone has to own the sequence configuration.

US Tech Automations handles the automation layer — the sequence triggering, the opt-out propagation, the non-responder triage — so your staff focuses on the patient conversations that actually require a human. See the pricing page for healthcare practice plans.

For practices managing multiple preventive care workflows simultaneously, the US Tech Automations healthcare practice automation hub shows how the same orchestration layer that runs recall campaigns also handles appointment reminders, care-gap notifications, and follow-up sequences — without separate tools for each campaign type.

For related workflows, see how practices automate appointment reminders across multiple locations, remind patients of care-gap screenings, and automate patient intake and pre-visit communication as companion campaigns to seasonal recall.