GLP-1

Month 2 Churn in GLP-1 Programs: Why Patients Drop and How to Recover Them

A practical operator playbook for reducing month-2 churn in GLP-1 telehealth programs through better expectation setting, refill workflows, and recovery automation.

Why month 2 is where retention is won or lost

In many GLP-1 programs, month 1 benefits from novelty and high motivation. By month 2, operational friction starts to matter more than initial intent.

Patients drop when the experience becomes uncertain:

  • they are unclear on next refill timing
  • side effects are unmanaged or unanswered
  • cost expectations change unexpectedly
  • follow-up feels slow or disconnected

Month 2 churn is usually not a single event. It is a sequence of small failures across communication, refill operations, and handoffs.


The four most common churn drivers in month 2

1) Refill uncertainty

Patients are not sure when they can refill, what is required, or what happens if they miss a check-in.

2) Side-effect support latency

Questions arrive, but response speed drops once the first month onboarding push is over.

3) Cost surprise

The patient understood month 1 pricing but does not have clear month 2 expectations.

4) Workflow fragmentation

CRM stage, support messages, and clinical queue state are not aligned, so patients receive mixed signals.

These are operational issues, not demand issues. They can be fixed with process design.


Diagnose churn by cohort, not aggregate rate

A single churn percentage hides the real leak. Break month-2 churn by:

  • acquisition channel
  • intake branch path
  • response time bucket for support
  • refill cycle timeliness
  • provider queue delay

This quickly shows whether churn is driven by specific workflow paths or systemic quality issues.

If your stage definitions are unclear, start with Telehealth CRM Pipeline Design: Stages, Owners, and SLAs.


Build a month-2 recovery system around triggers

Most teams run generic win-back campaigns. A better model is trigger-based intervention tied to patient state.

Trigger A: Refill not initiated by expected date

Action: send a short refill-readiness message and create an owner task if no action within 24 hours.

Trigger B: Support question with no resolution inside SLA

Action: escalate to clinical ops and send a clear interim update to the patient.

Trigger C: Missed follow-up milestone

Action: move patient into a structured re-engagement path with one primary CTA.

Trigger D: Payment or billing friction event

Action: route to billing support and pause churn labeling until contact attempt is complete.

This approach increases recovery because each outreach is tied to a specific friction point.


The communication sequence that performs better in month 2

In month 2, tone and timing matter more than volume.

A high-performing sequence usually includes:

  • one proactive message before refill window opens
  • one readiness confirmation near follow-up deadline
  • one escalation message if required steps are missing
  • one re-engagement path for lapsed patients

Messages should answer one question: what is the next action right now? Long educational copy performs worse than clear operational instructions at this stage.

For pre-visit timing patterns, see Reducing No-Shows with Pre-Visit Communication Automation.


Weekly metric stack for month-2 retention

Track these as a single operational scorecard:

  • month-2 active retention rate
  • refill initiated on-time rate
  • refill due to refill complete cycle time
  • support first-response time for active patients
  • percent of patients with unresolved follow-up tasks
  • reactivation rate from lapsed state

If retention drops while support SLA breaches rise, prioritize support and queue reliability before changing marketing or pricing strategy.


30-day implementation plan

Week 1: define month-2 risk triggers and ownership.

Week 2: implement automation for refill and follow-up triggers.

Week 3: add escalation rules and breach reason tagging.

Week 4: review cohort data, close top two root causes, and publish updated retention baseline.

Run this cycle continuously. Month-2 churn reduction is usually iterative, not one release.


Final takeaways

Month-2 churn in GLP-1 programs is mostly an operations reliability issue. Teams that win this phase do three things well: predictable refill workflows, fast support resolution, and trigger-based recovery.

If you want retention to compound, make month 2 a dedicated operating system, not a generic follow-up campaign.

To operationalize this flow, connect triggers and ownership across Telehealth CRM, Patient Portal, and Billing Engine.

More from GLP-1