All use cases

Retain / Save

Hormone-pellet re-insertion recall and rebooking

Pellet therapy runs on a body clock, not a calendar — when the dose wears off the symptoms come back, and that is the moment to re-pellet. The agent catches it, books the procedure and the bloodwork, and keeps the patient on therapy.

Get aheadTime-based triggerBehavioral triggerPushSMSEmailIn-appGLP-1 & PeptidesHealth & TelehealthSubscription

What it does

A hormone pellet is implanted and then quietly releases for a few months until it runs out — and unlike a pill or a pen, there is no refill to miss that signals the gap. The patient just starts feeling the old symptoms return, decides the program stopped working, and drifts, when the real fix is an in-clinic re-insertion that needs a gating blood panel first and a follow-up draw weeks later. Most clinics rely on the patient to notice and call, so the wear-off window is where pellet patients silently churn. The agent tracks each patient's re-pellet window, reframes returning symptoms as the expected end of a dose rather than a failing program, and books the procedure slot together with the labs that gate it and the follow-up draw that confirms it.

How it works

  1. 1
    Trigger. a time signal that a patient is entering their re-insertion window on the pellet wear-off clock (typically every three to six months), or a behavioral signal that returning symptoms are being reported as the dose fades.
  2. 2
    Decision. the agent reads memory for the last insertion date, the patient's typical interval, and whether the pre-insertion panel is current, then decides whether to open the recall, surface the gating labs first, or chase a window that is slipping toward a lapse.
  3. 3
    Action. it sends the recall on the channel the patient answers — frames the returning symptoms as the expected wear-off, offers the procedure slot, and books the pre-insertion bloodwork in the same flow so the visit is not wasted on missing labs.
  4. 4
    Follow-through. the booked procedure and labs write back to the scheduling and clinical systems; after the insertion the agent schedules and chases the follow-up draw a few weeks out. A patient who declines or goes quiet past the window escalates to the care team as a save case, and any symptom that reads as clinical rather than expected wear-off routes to the clinician rather than being coached. Lift is measured against a holdout.
Example
AgentYou're coming up on the window where your last pellet starts to wear off, so it's normal to feel some of your old symptoms creep back around now. That's the cue to re-pellet, not a sign it stopped working. Want me to hold a re-insertion slot and book the quick blood panel that has to come first?
PatientYeah, the fatigue is definitely back. Why the bloodwork again?
AgentYour clinician checks the standard panel before each insertion to set the visit up safely — I'll book that first so your appointment isn't held up by missing labs, then your re-insertion, and a follow-up draw a few weeks after to confirm you've settled. Booking all three now so nothing falls through.

Configuration

How the agent is wired for this use case.

Triggera reinsertion_window_open time signal on the pellet wear-off clock from the scheduling system, or a behavioral signal of returning wear-off symptoms reported by the patient.
Tools & actions
  • Scheduling system · read the re-insertion window, hold and book the procedure slot, and schedule the follow-up draw.
  • Lab system · order the pre-insertion panel and the post-insertion follow-up draw, and track completion.
  • Clinical / EHR system · confirm the last insertion date, the patient's interval, and that the gating labs are current.
  • Patient memory store · read insertion history and typical interval; write back booked procedures, labs, and recall state.
  • Messaging channel · send the wear-off recall and the rebooking on push, SMS, email, or in-app.
  • Care-team escalation path · route a declined or lapsing window to the care team as a save case.
Autonomythe recall, the procedure-slot hold, and the gating-lab booking run unattended behind judge gating with the booking prepared for one tap; the agent handles recall, scheduling, and lab logistics only — the clinician performs the insertion and reads every panel, and the agent never interprets a result or advises on a dose (detect the wear-off window and book; clinical reads stay with the clinician).
Channelspush · sms · email · in-app
Escalationa patient who declines or goes silent past the re-insertion window hands off to the care team as a save case; a reported symptom that reads as clinical rather than expected wear-off routes to the clinician.

What you need

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

Signals

the re-insertion-window-open event, returning-symptom reports, lab-completed and procedure-booked events, patient-initiated bookings for cancellation.

Data

last insertion date and typical interval, pre-insertion panel status, procedure and lab history, membership and renewal state, patient memory, channel consent.

Guardrails

the agent books and chases only — it never interprets a panel or advises on a dose, and clinical-reading symptoms route to the clinician; judge gating on every send; frequency caps; stale-recall cancellation when the patient self-books; holdout measurement.

Metrics it moves

  • renewal-rateup, because the re-pellet visit that keeps the membership alive gets booked on the body clock instead of waiting for the patient to notice and call.
  • save-rateup, by catching the wear-off window where pellet patients silently quit and reframing it as the expected re-dose moment.
  • adherenceup, the procedure and its gating labs land on cadence so therapy is continuous rather than restarting from a gap.

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