All use cases

Prevent / Care

Pregnancy and conception washout safety stop

A patient mentions she might be pregnant, or that she's started trying — the agent doesn't congratulate-and-continue, it declines to wave the program on and routes her to a clinician before her next dose.

Get aheadRisk triggerBehavioral triggerChatPushWhatsAppGLP-1 & PeptidesHealth & Telehealth

What it does

GLP-1 medications are contraindicated in pregnancy and call for a washout before conception, and around dose increases they can reduce the absorption of oral contraception. Any signal of pregnancy or trying to conceive is therefore a safety stop, not a milestone to cheer on. The risk is an agent that reads the happy news and keeps the program rolling. This one is wired the other way: on any pregnancy or trying-to-conceive signal it refuses to wave the program on, tells the patient plainly that the safe step is to speak to their provider before the next dose, and routes them to a clinician immediately. Where the moment fits, it also flags the contraception-absorption caveat — but the decline-and-route rule is the spine, and the clinician owns whether and how the medication stops.

How it works

  1. 1
    Trigger. a pregnancy, possible-pregnancy, or trying-to-conceive signal in any conversation — a stated plan, a "could I be pregnant" question, or a related profile change.
  2. 2
    Decision. the agent treats this as a designated contraindication stop, confirms the active GLP-1 medication from memory, and selects the decline-and-route response over any continuation path; if the context is contraception around a dose increase, it adds the absorption caveat.
  3. 3
    Action. a quality-gated message that declines to affirm continuing and names the safe step — speak to the provider before the next dose — with no clinical detail beyond that, and routes an immediate clinician handover carrying the signal and medication.
  4. 4
    Follow-through. automated coaching and pending nudges on that thread stand down, the signal and escalation write to memory, and the clinician's outcome closes the loop — including a clean path into a conception or off-ramp flow if the program is stopped.
Example
PatientWe've just started trying for a baby, so exciting! Should I carry on with my injection as normal?
AgentThat's lovely news. What I can't do is tell you to carry on as normal — this medication isn't used while trying to conceive or during pregnancy, so the safe step is to speak to your provider before your next dose rather than continuing on your own. If you've recently increased your dose, the timing also matters for contraception, which is exactly the kind of thing to raise with them. I've flagged your care team now with what you've told me so they can guide the next step urgently.

Configuration

How the agent is wired for this use case.

Triggera pregnancy, possible-pregnancy, or trying-to-conceive signal in conversation, or a related profile change, on an active GLP-1 medication
Tools & actions
  • Messaging channel · detect the signal across chat, push, or WhatsApp and surface the bounded decline-and-route message
  • Knowledge base · confirm the contraindication and the contraception-absorption caveat (non-oral contraception for around four weeks after a dose increase) for the drug class
  • Memory store · confirm the active medication and stage, write the signal and escalation back
  • Clinical/EHR system · route an immediate clinician handover carrying the signal and medication
  • App backend · stand down automated coaching on the thread and open a clean path into a conception or off-ramp flow on a clinician stop
Autonomydetection and the immediate decline-and-route run unattended under a clinical triage policy — decline to affirm continuation and escalate only; the agent never green-lights continuation, never issues a stop or dose-change instruction of its own, never diagnoses, and every patient-facing line is judge-gated; whether and how the medication stops is the clinician's call
Channelschat · push · whatsapp
Escalationany pregnancy or trying-to-conceive signal hands off to a clinician immediately and stands automated replies down; if the patient pushes to continue, the agent restates that it can't wave the program on and routes rather than affirming

What you need

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

Signals

in-conversation pregnancy, possible-pregnancy, and trying-to-conceive mentions; related profile changes

Data

active medication and stage, the encoded pregnancy contraindication and contraception-absorption caveat for the drug class, persistent patient memory, consent state

Guardrails

clinical triage policy — decline to affirm continuation and escalate only; never green-light continuation, never issue a stop or dose-change instruction, never diagnose; the clinician owns whether and how the medication stops; judge gating on every message; automated replies stand down once a clinician owns the thread; full audit trail of every escalation

Metrics it moves

  • safe-escalation-rateup, because every pregnancy and conception signal becomes an immediate decline-and-route instead of a continuation the agent affirms
  • contact-ratemeasured as the share of pregnancy and trying-to-conceive signals caught and escalated to a clinician
  • csatup, since a patient steered to the safe step at a tender moment feels protected rather than processed

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