All use cases

Onboard / Activate

Compounded-to-brand supply-transition concierge

The clinician has decided to move them to brand-name supply — now someone has to actually walk them through a new pharmacy, a new device, and a new bill.

Close the loopNext best thingSystem triggerBehavioral triggerChatWhatsAppEmailIn-appGLP-1 & PeptidesHealth & Telehealth

What it does

When a provider moves a patient from compounded medication to brand-name supply, the clinical decision is the easy half. The operational half is where patients drop: a different pharmacy flow to set up, a dosing form that changes from a drawn-up vial to a fixed pen (or the reverse), an insurance and cost picture that suddenly looks different, and a timing question about when the old supply ends and the new one begins. Left to a portal link and a "your prescription has changed" email, a meaningful share of these patients simply stall and lapse. The agent runs the switch as a guided, clinician-confirmed onboarding so the transition is a step forward, not a drop-off point.

How it works

  1. 1
    Trigger. the clinician confirms a compounded-to-brand transition in the record, or a fulfilment event signals the supply source is changing — the agent opens the walk-through rather than leaving the patient to decode it.
  2. 2
    Decision. the agent reads the new prescription, recognises the dosing-form change (vial to pen or pen to vial), pulls the patient's coverage and cost context, and sequences the steps that actually unblock this person; it answers questions in session and surfaces clinically-appropriate covered or lower-cost paths only for clinician approval. Every unprompted message passes a quality judge first.
  3. 3
    Action. a chat, WhatsApp, email, or in-app conversation walks the new pharmacy set-up, explains the new device with technique pointers, lays out the cost and insurance options, and confirms the timing so there is no gap between the last compounded dose and the first brand dose. Where a payment is needed, the agent hands off to the client's secure hosted step rather than taking it.
  4. 4
    Follow-through. the transition-completed event writes back to the program; if the patient completes a step on their own, the queued nudge is cancelled before it sends; a dosing question, a cost the patient cannot clear, or a clinical concern routes to a clinician or the care team, and lift is measured against a holdout.
Example
AgentYour prescriber has moved you to the brand-name pen, which is good news for your supply going forward. The main change for you: instead of drawing up a dose from a vial, this is a pre-set pen — fewer steps. I can walk the new pharmacy set-up and the pen with you now. Want to start with cost or with the device?
CustomerCost, honestly — I'm worried it's about to get expensive.
AgentFair concern. Based on your plan there are two covered paths your prescriber has already okayed; I'll lay both out with the monthly number for each, and there's a secure page to confirm whichever you choose. Your current supply covers you until the new one arrives, so there's no gap.

Configuration

How the agent is wired for this use case.

Triggera transition_confirmed event from the clinical/EHR system (compounded → brand), or a supply_source_changed fulfilment event.
Tools & actions
  • Clinical/EHR system · read the new prescription and the dosing-form change; write back the transition-completed event.
  • Pharmacy/fulfilment system · guide the new pharmacy set-up and confirm timing so old and new supply do not leave a gap.
  • Billing system · present the clinician-approved covered or lower-cost options and hand off to the client's secure hosted payment step.
  • Knowledge base · explain the new device with approved technique pointers and the steps of the switch.
  • Messaging channel · run the guided conversation and answer questions in session.
Autonomythe walk-through, the cost-option presentation, and the timing confirmation run under judge gating with frequency caps; covered/lower-cost paths are surfaced for clinician approval, never chosen for the patient; the agent gives no dose or medical advice, and payment is always a hand-off to the secure hosted step.
Channelschat · whatsapp · email · in-app
Escalationa dosing-form question that needs clinical judgement, a cost barrier the patient cannot clear, or any clinical concern hands off to a clinician or the care team with full context.

What you need

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

Signals

the clinician-confirmed transition event and any supply-source change from fulfilment; a completion event when the switch is done.

Data

the new prescription and dosing form, the patient's coverage and cost context, the set of clinician-approved covered/lower-cost paths, device-technique content, consent and notification preferences.

Guardrails

clinically-appropriate options are presented for clinician approval only; the agent never adjusts a dose or gives medical advice and escalates clinical questions; payment is a secure hosted hand-off, never taken by the agent; judge gating, frequency caps, and holdout measurement on every unprompted message.

Metrics it moves

  • activation-rateup, by carrying patients through the new pharmacy and device set-up instead of losing them at the switch.
  • churndown, a guided transition removes the price-and-process shock that drives silent lapse.
  • intake-completionup, the first brand dose lands without a supply gap.
  • adherenceup, patients who clear the operational switch keep dosing on schedule.

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