All use cases

Prevent / Care

Pre-procedure GLP-1 hold reminder

A patient mentions a colonoscopy next week and never connects it to their weekly injection — the agent catches the overlap and gets the timing question in front of their care team before the procedure date.

Get aheadBehavioral triggerRisk triggerChatPushWhatsAppGLP-1 & PeptidesHealth & Telehealth

What it does

GLP-1 medications slow gastric emptying, which raises the risk of aspiration under anesthesia, and guidance now points to holding the medication for a window before a procedure. Most patients have no idea the two are linked: they book a surgery, a colonoscopy, or any sedation, mention it in passing, and turn up still dosing on schedule. The cost lands on the day — a cancelled procedure, or a real safety event in theatre. The agent listens for any mention of an upcoming procedure, recognizes the peri-operative risk, and surfaces the hold question with the evolving guidance attached. It does not set the hold itself — it puts the timing decision in front of the clinician and the anesthesia team, who own it.

How it works

  1. 1
    Trigger. a patient mentions an upcoming surgery, colonoscopy, sedation, or anesthesia in any conversation, or a procedure date appears in the patient record.
  2. 2
    Decision. the agent recognizes the peri-operative trigger, confirms the active GLP-1 medication from memory, and reads the encoded pre-op guidance — commonly a hold of around seven days, but a clinician call, not a fixed instruction it issues.
  3. 3
    Action. a quality-gated message that names the link plainly, surfaces the hold question, and routes the patient to confirm timing with their clinician or anesthesia team; the agent never tells the patient when to stop.
  4. 4
    Follow-through. the clinician handover carries the procedure mention and medication; the agent logs the surfaced question to memory and, if the procedure is cancelled or the timing is confirmed by the care team, cancels its own now-stale reminder.
Example
PatientBit nervous about my knee surgery next Thursday, but glad it's finally booked.
AgentGood that it's set. One thing worth raising before then: your weekly medication slows stomach emptying, and the guidance is usually to pause it for a window before anesthesia — but the exact timing is your surgical and anesthesia team's call, not mine. I've flagged the question to your care team so they can confirm whether and when to hold before Thursday. Want me to nudge you once they've come back?

Configuration

How the agent is wired for this use case.

Triggera mention of an upcoming surgery, colonoscopy, sedation, or anesthesia in conversation, or a procedure date in the patient record, on an active GLP-1 medication
Tools & actions
  • Messaging channel · detect the procedure mention across chat, push, or WhatsApp and surface the hold question
  • Memory store · confirm the active medication and stage, log the surfaced question and the care team's response
  • Knowledge base · read the encoded peri-operative hold guidance for the drug class
  • Clinical/EHR system · route the timing question to the clinician or anesthesia team with the procedure mention attached
  • Scheduling · read the procedure date where available and cancel a now-stale reminder if it changes
Autonomydetection and the judge-gated surfacing run unattended under a clinical triage policy — the agent surfaces the question only; it never sets, recommends, or confirms a hold or a dose change, and the clinician decides the timing
Channelschat · push · whatsapp
Escalationthe hold-timing decision hands to the clinician or anesthesia team in every case; if the patient asks the agent to confirm when to stop, it declines and routes to the care team

What you need

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

Signals

in-conversation mentions of upcoming procedures, anesthesia, or sedation; procedure dates in the patient record where available

Data

active medication and stage, the encoded peri-operative hold guidance for the drug class, persistent patient memory, consent state

Guardrails

clinical triage policy — surface the question only, never set or confirm a hold or dose change; the clinician and anesthesia team own the timing; judge gating on every message; stale-reminder cancellation when the procedure or timing changes; full audit trail of every surfaced question

Metrics it moves

  • safe-escalation-rateup, because a high-liability peri-operative risk that no form asks about reliably reaches the care team before the procedure
  • contact-ratemeasured as procedure mentions caught and routed for a timing decision ahead of the date
  • csatup, since a patient who is steered to the right question before surgery feels looked after rather than caught out on the day

Related use cases

Prevent / Care

Clinical red-flag detection and safe escalation

the general safety rail this extends to the peri-operative moment

Prevent / Care

Pregnancy and conception washout safety stop

a sibling life-event trigger that surfaces a stop question and routes to a clinician

Prevent / Care

Pancreatitis and gallbladder red-flag detector

the acute-symptom hard-escalate alongside this anticipatory one

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