Every care coordination team has strong opinions about this, and most of those opinions were formed before anyone had data to test them. The consensus view — usually something like "older patients prefer phone calls, younger patients prefer texts" — is roughly right as a starting point but wrong as a rule. When you look at actual response rates across chronic disease populations, the channel preference picture is more nuanced, and making the wrong choice costs you the intervention window.
I spent eight years as a care coordinator before moving to a role focused on clinical implementation. In that time, I watched countless outreach strategies fail not because the message was wrong, but because it arrived in the wrong format at the wrong time. That's the problem we spend a lot of time thinking about at Patientrig, and what I want to walk through here is what we actually observe — and where the common assumptions break down.
The Age Assumption and Why It Partially Holds
Age-based channel preference has a real basis. Patients over 70 who grew up before smartphones tend to be more comfortable with voice calls and less consistent about checking SMS, especially if they're managing a complex medication regimen and have some degree of health literacy challenge. For a 78-year-old CHF patient managing furosemide, spironolactone, and lisinopril, a nurse call that explains "your scale showed a two-pound weight gain, we want to talk through your fluid restrictions" lands very differently than an SMS that says "Please call your care team about your weight log."
The SMS message requires the patient to: (1) read and comprehend the message, (2) decide it warrants action, (3) initiate a call back to a number they may need to look up, (4) navigate a phone tree. The nurse call compresses that to a direct conversation that can assess the clinical situation in real time. For high-acuity patients with complex chronic conditions, the call wins — not because the patient "prefers" it, but because it's more likely to result in the clinical action you actually need.
That said, the age assumption breaks down in two important ways. First, adults over 65 have substantially higher smartphone adoption than they did five years ago, and this varies considerably by geography and socioeconomic status. Second, and more importantly, condition severity matters more than age for many intervention scenarios. A 70-year-old Type 2 diabetic who has been well-controlled for three years on stable metformin dosing and is just overdue for an HbA1c draw doesn't need a nurse call — that's a routine gap closure that an SMS prompt can handle effectively.
Condition-Specific Channel Logic
The more useful framework isn't age vs. youth — it's acuity + complexity + required action.
CHF and COPD: Call-preferred for acuity, SMS for routine
For patients with CHF or moderate-to-severe COPD, the intervention moments that matter most are clinically urgent: a weight gain pattern suggesting fluid retention, a missed albuterol refill combined with cold weather, a hospital discharge that requires 72-hour medication reconciliation follow-up. These scenarios warrant direct voice contact. The clinical picture needs to be assessed, not just the action item confirmed.
However, the same CHF patient managing well over six months can receive routine appointment reminders and refill nudges by SMS. The channel escalation should be condition-status driven, not fixed to the diagnosis.
Type 2 Diabetes: SMS performs well at scale for low-acuity gaps
For a growing diabetic population — especially patients who are 12 to 24 months post-diagnosis and on a stable metformin and/or GLP-1 regimen — SMS outreach for routine HbA1c reminders, annual dilated eye exam gaps, and refill nudges performs comparably to phone-based outreach in terms of gap closure rate, while requiring a fraction of the care coordinator time. The critical caveat: patients with HbA1c above 9.0% or recent medication changes need a different approach. The SMS-first model works when the clinical situation is stable and the intervention is administrative.
Hypertension: SMS works well when paired with a response mechanism
Hypertension is interesting because the gap closure action — a blood pressure reading — can be done by the patient at home with a cuff, reported back via SMS or portal, and reviewed asynchronously. Outreach to remind a hypertensive patient to submit their home readings is well-suited to SMS. What doesn't work via SMS is assessing whether a patient who hasn't been recording readings has stopped monitoring because they're feeling fine, or because their cuff broke, or because they've quietly run out of amlodipine. That distinction requires a conversation.
The Consent and Compliance Layer
One thing that doesn't get enough attention in channel-selection discussions is the regulatory and consent dimension. Under TCPA, automated SMS to patients requires prior written consent. Under HIPAA, SMS is permissible for appointment reminders but must be evaluated against minimum necessary standard for any PHI content. Organizations that run automated SMS programs without explicit consent management are taking on liability that becomes visible the moment a patient complains or an audit occurs.
This is not a reason to avoid SMS — it's a reason to build consent documentation into your intake and care plan workflows before you scale any automated outreach program. Most EHR systems support a patient communication preference field; very few care management teams have actually operationalized it consistently. The care teams that handle this well treat channel consent as a clinical data element, not an administrative checkbox.
Response Rate Patterns We See in Practice
Based on what we've observed in implementation scenarios, some patterns hold fairly consistently:
- SMS open/read rates are high but action rates vary significantly. An SMS message may be read within minutes but result in no action because the required step (calling back, navigating a portal, filling a prescription) introduces friction. SMS works best when the confirmation action is embedded in the message itself — a Y/N reply, a link to a scheduling page — rather than requiring an outbound call.
- Phone call answer rates during business hours are substantially lower than care teams assume. Patients work. The midday call to a 45-year-old Type 2 diabetic during a shift goes to voicemail. The voicemail describing a care gap goes unreturned more often than not. Callback windows — morning, early evening — significantly change answer rates for working-age populations.
- The escalation sequence matters more than the first-touch channel. A well-designed outreach protocol often combines channels: SMS first (low barrier, immediate, patient can respond when convenient), escalate to phone if no response within 48 hours, flag for care coordinator personal outreach if no response after phone attempt. Treating any single channel as the complete strategy misses the compounding effect of the sequence.
What This Means for Care Management Workflows
We're not saying phone calls are obsolete or that SMS is always the right first move. What we're saying is that a fixed, one-size-fits-all channel policy for patient outreach leaves clinical value on the table. The care team's time is the constraint, and that constraint should drive toward SMS-first for low-acuity, stable-condition gap closure — while reserving direct nurse or coordinator calls for the situations where a conversation is the only way to get the information you need to act clinically.
The patients who generate the most expensive events in a chronic disease panel are rarely the ones who stopped responding to phone calls. They're the ones who didn't get the right signal to make contact — or who got it too late, in a format that didn't match their actual situation. Getting the channel selection right is a leverage point that most care management programs underinvest in.
The right answer for your population starts with looking at your own response data by condition, age cohort, and outreach time of day — and then building the protocol around what those patterns actually show, not what the consensus assumption says they should show.
