All use cases

Retain / Save

Vaginal-estrogen adherence-decay nudge

She feels better, so she quietly stops the twice-weekly dose — and the symptoms her therapy was holding back come straight back. The agent re-ups her before the relapse, not after.

Get aheadBehavioral triggerTime-based triggerPushSMSIn-appEmailGLP-1 & PeptidesHealth & TelehealthSubscription

What it does

Maintenance vaginal-estrogen therapy only works while it is being used: the relief depends on keeping the restored tissue environment, so the benefit lapses the moment a patient lets the twice-weekly schedule slide, and the symptoms return weeks later. The trap is that feeling better is exactly what makes someone stop — there is no supply emergency and no complaint ticket, just a quiet adherence decay that the program never sees until the patient has relapsed and churned. The agent watches the cadence and the refill clock for that drift, and sends a "this keeps working only while you keep using it" re-up tied to the next refill, before the gap turns into a relapse. It frames the why, never adjusts the regimen, and routes any symptom or medical question to the care team.

How it works

  1. 1
    Trigger. an adherence-decay signal on a maintenance vaginal-estrogen patient — the twice-weekly cadence slipping or a refill going unactioned past its due window, read from logged use and the pharmacy clock.
  2. 2
    Decision. the agent reads the pattern as a feel-better-so-I-stop drift rather than a one-off late reorder, checks memory and consent, and picks a low-friction channel for a maintenance nudge.
  3. 3
    Action. it sends the continuous-use reframe — relief lasts only while the schedule holds — with the refill prepared so the patient just confirms; payment runs through the client's secure hand-off.
  4. 4
    Follow-through. a confirmed re-up writes back to the pharmacy and memory; if the patient refills on their own first, the queued nudge is cancelled; any symptom or medical question routes to the care team rather than being answered in the flow.
Example
AgentYour twice-weekly dose has drifted the last couple of weeks. Because this one keeps working only while you keep using it, the relief usually fades a few weeks after the schedule slips — not right away. Want me to line up your refill so you stay ahead of it?
PatientOh — I'd stopped because everything felt fine.
AgentThat's the most common reason people drift off this, and feeling fine is the therapy doing its job. I've got your usual refill ready — confirm and pay through this secure link and you'll stay on track.

Configuration

How the agent is wired for this use case.

Triggerthe twice-weekly cadence slipping or a refill unactioned past its due window on a maintenance vaginal-estrogen patient, sourced from logged use and the pharmacy clock
Tools & actions
  • App backend · detect the cadence drift and adherence-decay pattern from logged use
  • Pharmacy system · read refill status and prepare the next refill for one-tap confirmation, write back the confirmed re-up
  • Messaging channel · send the continuous-use reframe by push, SMS, in-app, or email
  • Payment provider · run the refill payment through the client's hosted secure checkout
  • Memory store · read regimen, consent, and prior drift; write back the touch and outcome
Autonomythe maintenance nudge runs unattended behind judge gating, bounded to adherence and refill topics; the refill payment is money-moving and runs through the client's hosted checkout; the agent never adjusts the regimen and routes any symptom or medical question to the care team — detect, then escalate; no dose advice.
Channelspush · sms · in-app · email
Escalationany symptom report, relapse, or medical question hands to the care team rather than being handled in the adherence flow

What you need

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

Signals

twice-weekly use logs, refill-due and missed-refill dates, self-serve refills for cancellation

Data

the continuous-use requirement for the therapy, regimen and refill history, persistent patient memory, channel consent

Guardrails

outreach bounded to adherence and refill topics; no regimen change and no symptom advice in the flow; care-team routing for any medical question; judge gating on every unprompted message; frequency caps and one-follow-up rule; stale-outreach cancellation on self-serve refills; secure payment hand-off

Metrics it moves

  • adherenceup, by closing the cadence gap before the feel-better drift becomes a stop
  • churndown, as a patient kept on a working maintenance therapy has no symptom relapse to quit over
  • renewal-rateup, because the refill habit, once protected, carries the maintenance subscription forward

Related use cases

Retain / Save

Missed-refill and replenishment outreach

the supply-out reorder this specializes for a feel-better drift

Engage / Lifecycle

Quarterly-retest reminder and re-engagement loop

the same maintenance-loop watchfulness on the retest cadence

Retain / Save

Adherence guardian for medication programs

the clinical-safety sibling of the same adherence watch

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