All use cases

Collect / Recover

Refill gap-closer with cold-chain reship

A late reorder is not a late parcel — it is a missed weekly dose. The agent watches the supply clock so the next pen arrives before the current one runs dry.

Get aheadTime-based triggerSystem triggerPushSMSEmailChatGLP-1 & PeptidesHealth & TelehealthSubscriptionE-commerce & Retail

What it does

A GLP-1 program ships a refrigerated pen on a monthly cadence, and the patient injects once a week. If the reorder slips even a few days, or the courier sits on a doorstep in the heat, the patient does not just wait for a parcel — they skip a dose, and a skipped dose restarts the appetite and the doubt the program is built to hold off. Nobody owns the gap between "supply is running low" and "the patient has placed the order," so the revenue you already earned quietly lapses and the therapy breaks at the same moment. The agent watches the supply clock, prompts the reorder before the patient runs out, and when a cold-chain delivery goes wrong it triggers a reship so the weekly rhythm is never interrupted.

How it works

  1. 1
    Trigger. a supply-clock event — the current pen approaching end of supply on the dosing calendar, or a delivery system signal that a shipment is delayed or arrived warm — fires the flow before the patient is out.
  2. 2
    Decision. the agent reads the patient's memory and order state — current dose, ship cadence, last delivery, weeks of pen remaining, consent — and decides whether this is a routine reorder nudge or a cold-chain rescue, picking the channel by urgency.
  3. 3
    Action. it sends a specific nudge tied to the dose date with the reorder prepared for one tap; payment runs through the client's hosted secure checkout. On a delayed or heat-exposed shipment it offers an expedited reship so the next injection day is covered.
  4. 4
    Follow-through. confirmed reorders and reships write back to the order system and memory; if the patient reorders on their own first, the queued nudge is cancelled. A storage or potency question rides to the pharmacy, and an unresolved supply gap on an active prescription escalates to the care team rather than going quiet.
Example
AgentYour pen has about a week of doses left, and your next injection day is Thursday. Want me to send the next box now so there's no gap? Same monthly supply as last time.
CustomerYes please — but the last one showed up warm and sat outside all afternoon.
AgentThanks for flagging that. I'm sending a fresh box on an expedited cold-chain ship so it lands before Thursday, and I've passed the warm-delivery note to the pharmacy to check the current pen. Confirm and pay through this secure checkout and you're set.

Configuration

How the agent is wired for this use case.

Triggeran end-of-supply date on the dosing calendar, or a shipment_delayed / temperature_excursion event from the delivery system, sourced from the pharmacy and the scheduling system.
Tools & actions
  • Pharmacy / order system · read prescription and order state, weeks-of-supply, and delivery status; prepare the reorder; trigger an expedited reship.
  • Scheduling system · read the dosing calendar and the next injection day to time the nudge ahead of the gap.
  • Messaging channel · send the personal reorder nudge by push, SMS, email, or in-app chat.
  • Payment provider · run the reorder through the client's hosted secure checkout; the agent never takes payment itself.
  • Memory store · read current dose, ship cadence, last delivery, and known blockers; write back confirmed reorders.
  • Care-team escalation path · route an unresolved supply gap on an active prescription to the care team.
Autonomyroutine reorder nudges and expedited reships on a logged cold-chain failure run unattended behind judge gating, with the order prepared for one-tap confirmation; the reorder payment is money-moving and runs through the client's hosted checkout; this is logistics and continuity only — any dose decision or potency judgement is the clinician's or pharmacy's, never the agent's.
Channelspush · sms · email · chat
Escalationan unresolved supply gap on an active prescription, or a potency question on a heat-exposed pen, hands off to the pharmacy or care team.

What you need

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

Signals

end-of-supply and replenishment-due dates, the dosing calendar, shipment_delayed and temperature_excursion delivery events, patient-initiated reorders for cancellation.

Data

prescription and order history, ship cadence, weeks-of-supply per pen, current dose, patient memory, channel consent.

Guardrails

judge gating on every unprompted message; outreach bounded to reorder, delivery, and supply topics under a clinical-safety policy class; potency and dose questions routed to the pharmacy or clinician, never answered by the agent; frequency caps; stale-outreach cancellation on self-serve reorders.

Metrics it moves

  • adherenceup, by closing the supply gap before a late reorder becomes a missed weekly dose.
  • recovered-revenueup, restarting monthly reorders that would otherwise silently lapse at the refill moment.
  • churndown, because the weekly rhythm that keeps a patient on therapy is never broken by a logistics slip.

Related use cases

Retain / Save

Missed-refill and replenishment outreach

the general reorder watch this adds dose-continuity and cold-chain reship to

Collect / Recover

Cold-chain order-status and invoice deflection

the "where is my pen?" sibling that answers in-flight status

Collect / Recover

Cold-chain storage-failure delivery intercept

the receipt-side quality intercept on the same shipment

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