All use cases

Retain / Save

Compounding wind-down transition manager

Your patient has been paying a low monthly price for a compounded medication for a year — and now the program is being told to move everyone onto the brand-name version, often at several times the cost, and the first many of them hear of it is a price they did not agree to.

Close the loopGet aheadSystem triggerTime-based triggerRisk triggerChatEmailPushIn-appGLP-1 & PeptidesHealth & TelehealthSubscription

What it does

When a compounding pathway is wound down, every patient on the cheaper compounded medication is forced toward the pricier brand version, or their pharmacy simply closes. Left to a billing email, that is a price shock that drives a wave of silent cancellations across the whole book at once — patients who were doing well clinically leave purely on cost, and a program that spent heavily to acquire them watches them churn in a single window. This agent runs the transition as a managed retention event instead of a surprise. It reaches each affected patient ahead of the change, explains plainly what is happening and why, surfaces the clinically-appropriate covered and lower-cost paths for the clinician to approve, re-prices the plan against the real options, and books the transition consult — so the patient moves to the next step on therapy rather than off it.

How it works

  1. 1
    Trigger. a wind-down or pharmacy-closure event flags a cohort of patients on the compounded medication for forced transition, with a hard date attached, before any of them have been told.
  2. 2
    Decision. for each patient the agent reads memory — current medication and dose, plan and price tier, what they have told the coach about cost sensitivity — and assembles the candidate routes (covered brand, manufacturer savings, an annual or lower-cost form), ranking the cheapest legitimate path that fits their clinical picture for a clinician to approve. A judge reviews every unprompted message before it sends.
  3. 3
    Action. an honest, personal message lands on a channel the program keeps owning, naming the change before the bill does, framing the value of staying on therapy, and offering the approved options plus a one-tap link to book the transition consult; any payment runs through the program's own secure hand-off, never the agent.
  4. 4
    Follow-through. the clinician approves the route, the new plan is re-priced and the consult booked; cost-versus-clinical questions split to the right channel; if a patient transitions or cancels, queued touches are cancelled automatically, and saved-versus-churned patients are measured against a holdout so the lift is proven, not assumed.
Example
AgentI want to get ahead of a change to your program. The compounded version you've been on is being phased out, so we need to move you to the brand medication — I know the price difference is the part that stings. I've lined up the lowest-cost route your clinician can approve, including a manufacturer savings option, so this doesn't have to mean stopping. Can I book you a short transition consult this week?
PatientHonestly the brand price is the reason I was about to quit.
AgentThat's exactly why I reached out before the bill did. The savings route I've queued for your clinician brings it well below the list price, and your dose and history carry over so there's no restarting. Let's get the consult booked and lock in the cheaper path together.

Configuration

How the agent is wired for this use case.

Triggera compounding wind-down / pharmacy-closure event flags an affected patient cohort for forced compounded-to-brand transition with a transition date (compounding_winddown cohort event), sourced from the program / pharmacy system.
Tools & actions
  • Pharmacy system · receive the wind-down / closure event and identify each patient on the affected compounded medication
  • Clinical/EHR system · read current medication, dose, and clinical picture to shortlist clinically-appropriate transition routes for the clinician
  • Billing system · re-price the plan against the approved route and present the lowest legitimate cost path, with payment handled by the program's secure hand-off
  • Scheduling system · offer and book the transition consult with the care team
  • Messaging channel · deliver the judged transition message on a program-owned channel and pull the patient into the coach chat
  • Memory store · read cost-sensitivity and conversation history; write the transition outcome back for follow-up
Autonomycohort detection, the proactive transition message, and re-pricing against approved routes run unattended and judge-gated; the clinician approves the medication route and the patient confirms any payment through a secure hand-off; the agent never selects or advises a dose and never takes payment itself (clinical and money-moving steps are confirmation-gated, detect → surface → human approves).
Channelschat · email · push · in-app
Escalationany clinical question or route decision hands off to the clinician; billing disputes route to the billing team; if the patient transitions or cancels, queued touches are cancelled automatically.

What you need

The inputs this use case runs on. Your channels stay yours; the agent supplies the judgment.

Signals

the compounding wind-down / pharmacy-closure cohort event with a transition date, the affected medication, and each patient's current plan tier.

Data

current medication and dose, plan and price tier, approved transition routes and savings options, channel consent, coach-chat memory of cost sensitivity.

Guardrails

judge review on every unprompted message; the clinician approves the medication route and the agent advises no dose; payment only through the program's secure hand-off, never the agent; honest framing of the change, never pressure; frequency caps; suppression on transition or cancellation; holdout measurement of the saved cohort.

Metrics it moves

  • churndown, by converting a program-wide forced switch from a wave of silent cancellations into a managed, supported transition.
  • save-rateup, by reaching each affected patient with an approved lower-cost path before the price shock lands.
  • ltvup, as patients carried through the transition stay on already-paid high-CAC acquisition rather than leaving at the switch.

Related use cases

Retain / Save

Titration-cliff cost-shock save

the sibling save fired by a dose-tier price step rather than a forced supply change

Onboard / Activate

Compounded-to-brand supply-transition concierge

the operational pharmacy-flow walkthrough that onboards the new supply this card decides

Retain / Save

Coverage-loss bridge save

the parallel save when a payer, not compounding, removes the cheap path

See it on your own customer journey

Bring one drop-off, one churn cliff, or one silent segment. We will show you what a proactive agent with memory and judgment does with it.

Book a demo