All use cases

Onboard / Activate

Baseline-labs chase before first injection

A motivated patient is ready to start, but a quality program won't prescribe until the baseline labs are in — and that gap is where weeks of momentum quietly leak away.

Close the loopGet aheadSystem triggerBehavioral triggerEmailPushChatSMSGLP-1 & PeptidesHealth & Telehealth

What it does

Responsible GLP-1 programs require a baseline panel — kidney and metabolic function, thyroid, lipids, blood count — before a clinician will prescribe. Skipping it is a known telehealth quality gap; requiring it creates a stall, because the patient has to book a draw, get it done, and have results land before therapy can begin, and any one of those steps can drag for weeks. The agent owns that gap: it explains in plain terms why the labs matter, helps the patient book or complete the draw, and chases an incomplete panel until it is done, so the clinician can prescribe safely without the patient cooling off in the wait.

How it works

  1. 1
    Trigger. a patient clears screening and a baseline panel is ordered but not yet complete, or an ordered panel has been sitting unfilled past its expected window.
  2. 2
    Decision. the agent checks which markers are outstanding, reads where the patient is stuck (not booked, booked but not drawn, drawn but results not back), and picks the next concrete step — recalling prior nudges and channel consent so it never repeats itself or over-contacts.
  3. 3
    Action. a specific, encouraging chase goes out on the patient's channel — what is still needed, why it protects them, and the exact next move (book a slot, find a nearby lab, what to expect at the draw) — with the clinical "why" kept plain and reassuring rather than alarming.
  4. 4
    Follow-through. when results land the agent confirms the panel is complete and routes the patient straight on toward the prescribing review; reminders stop the moment the labs arrive; the agent never interprets a result — interpretation and the prescribing decision stay with the clinician.
Example
AgentYou're almost set to start — the one thing left is your baseline blood test. It checks your kidneys and a few other markers so your clinician can prescribe safely. Want me to find a lab near you and book a slot?
CustomerOh, I didn't realize that was still open. Yes, somewhere near work would be ideal.
AgentDone — I've found three near your office and held the earliest for Thursday morning. Once your results are back I'll let your clinician know straight away so we can keep things moving.

Configuration

How the agent is wired for this use case.

Triggera baseline panel is ordered but incomplete after screening, or an ordered panel has sat unfilled past its window — an order_pending / labs_incomplete signal from the lab or clinical system.
Tools & actions
  • Lab system · read which ordered markers are outstanding and detect when results land.
  • Scheduling system · help the patient find a nearby draw site and book or rebook a slot.
  • Messaging channel · send the specific, plain-language chase (what is needed, why it protects them, the next step) and resume on reply.
  • Clinical/EHR system · confirm the completed panel and route the patient on toward the prescribing review, writing the chase trail back.
Autonomydetection, booking help, and the chase run unattended, judge-gated on every outbound message and capped for frequency; under a detect-and-escalate clinical policy the agent never interprets a lab result and never makes the prescribing decision — both stay with the clinician; stale reminders are cancelled the moment results land.
Channelsemail · push · chat · sms
Escalationa result the patient asks about, or a panel that cannot be completed, hands off to the care team; interpretation and the prescribing call are always the clinician's.

What you need

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

Signals

baseline-panel order_pending and labs_incomplete events, draw-completed and results-received events, stalled-panel detection.

Data

which markers the program requires and their order status, the patient's location for nearby-lab lookup, contact details and channel consent, prior-nudge history.

Guardrails

detect-and-escalate clinical policy — no result interpretation, no prescribing decision; judge review on outbound chases; frequency caps per patient; the required-panel definition is clinician-owned; stale-outreach cancellation when results arrive; every chase logged for audit.

Metrics it moves

  • intake-completionup, because a specific, supported lab chase loses far fewer ready patients than an order left to sit on its own.
  • time-to-resolutiondown, by moving patients from "labs ordered" to "labs complete and prescribing review" without weeks of dead air.
  • conversion-rateup, since a motivated patient who completes the panel reaches their first injection while the intent that brought them in is still warm.

Related use cases

Onboard / Activate

Contraindication and boxed-warning intake screen

the safety gate just before labs are ordered

Onboard / Activate

First-injection onboarding and technique coach

the next activation beat once prescribing clears

Onboard / Activate

KYC/KYB onboarding with document chase

the verification-chase analogue in fintech

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