All use cases

Engage / Lifecycle

Weekly-injection reminder with missed-dose next-step

GLP-1 is a once-weekly shot on a fixed day — the agent reminds the patient when it is due, and if the dose never gets logged, tells them the safe next step straight from the label.

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

What it does

A once-weekly injection on a set day is easy to forget, and a forgotten dose is a missed week that quietly erodes adherence and results. Most programs send a generic reminder and stop there, so the patient who misses the day is left guessing whether to take the dose late or skip it — and a guess at that moment is where therapy drifts. The agent runs the same-day reminder, watches for the "injected" log, and if none appears inside the window it delivers the label-grounded next step: take it now if you are still inside the allowed window, otherwise skip and resume on your usual day. It holds adherence without ever prescribing.

How it works

  1. 1
    Trigger. a time signal fires on the patient's fixed weekly injection day; a behavioral signal confirms whether an "injected" log has been recorded inside the dosing window.
  2. 2
    Decision. the agent checks memory for the dose-day, the logged status, and the time elapsed, then maps it against the label's single missed-dose rule for this medication — within the allowed window, take now; past it, skip and resume on schedule. The patient-facing wording stays educational and label-sourced.
  3. 3
    Action. a same-day reminder on the channel the patient answers — push, SMS, WhatsApp, or in-app; if the window passes with no log, the missed-dose message with the take-or-skip next step grounded in the label.
  4. 4
    Follow-through. the injection log writes back to memory and confirms the loop is closed; if the pattern is not a one-off — repeated or consecutive misses — the conversation is handed to the deeper missed-dose rules engine and, where warranted, a clinician. Reminders that are no longer needed because the patient already logged are cancelled before they fire. Lift is measured against a holdout.
Example
AgentIt's your injection day. When you've taken this week's dose, tap to log it and you're all set.
CustomerJust saw this — I completely forgot yesterday. Do I still take it?
AgentPer your medication's label, if it's still within the allowed window since your usual day, you can take it now and keep your regular day next week; past that window, skip the missed one and resume on schedule. Want me to confirm which side of the window you're on and log it?

Configuration

How the agent is wired for this use case.

Triggeran injection_day_due time signal from the app backend on the patient's fixed weekly day, paired with the presence or absence of an injection_logged event inside the dosing window.
Tools & actions
  • App backend · provides the fixed injection day, the dosing window, and the medication on file.
  • Patient memory store · reads dose-day, last logged injection, and elapsed time; writes the new log back to close the loop.
  • Knowledge base · supplies the label-grounded missed-dose next-step text (take-within-window vs skip) for this medication.
  • Messaging channel · sends the same-day reminder and, if unlogged, the missed-dose next-step on push, SMS, WhatsApp, or in-app.
  • Clinician escalation queue · receives the patient when misses repeat or a reply raises a concern.
Autonomythe reminder and the single label-grounded next-step send unattended after a quality judge clears them, under frequency caps; the agent restates the label and never sets, changes, or improvises a dose — any decision beyond the published take-or-skip rule, or any repeated-miss pattern, is escalated (detect, then escalate), not decided by the agent.
Channelspush · sms · whatsapp · in-app
Escalationconsecutive or repeated misses route to the missed-dose rules engine and a clinician; any symptom or concern in the reply hands off to the side-effect and escalation rails.

What you need

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

Signals

the fixed weekly injection-day event, the injection-logged event, the dosing-window definition per medication.

Data

patient dose-day and schedule, medication on file, the label's missed-dose rule, memory of recent logs, per-channel consent.

Guardrails

patient-facing text stays educational and label-sourced; no dose-setting or schedule change by the agent; judge gating and frequency caps on every send; repeated-miss and symptom signals escalate; stale-reminder cancellation when already logged; holdout measurement.

Metrics it moves

  • adherenceup, because the on-day reminder plus a clear, safe next step keeps the weekly dose from silently slipping.
  • churndown, as missed doses that compound into disengagement get caught at the first miss.
  • ticket-deflectionup, the "I forgot my shot, what now?" question is answered in the moment instead of becoming a support contact, measured against the holdout.
  • dau-mauup, the reminder opens into a logging interaction rather than a passive notification.

Related use cases

Engage / Lifecycle

Missed-dose recovery rules engine

the deeper multi-branch logic this reminder hands off to on repeated misses

Engage / Lifecycle

Between-doses lull check-in

the mid-week sibling touch between two injection days

Retain / Save

Adherence guardian for medication programs

the broader risk-signal guardian this dosing reminder feeds

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