1. Appointment reminders that can reschedule themselves
No-shows waste clinician time; phone reminders don't scale.
Trigger: Webhook (scheduled, day-before)
How the workflow runs
- Trigger
Day-before reminder due. A scheduled Webhook trigger fires for tomorrow's appointments.
- Output
Send the reminder. An Output node messages the patient on WhatsApp/SMS with the time and prep.
- Condition
Handle the reply. A Condition node routes 'confirm', 'reschedule', or 'cancel'.
- Tool (MCP)
Update the calendar. A Tool (MCP) node moves or frees the slot in your scheduling system.
Channels & connectors
- Webhook
- SMS
- Tool (MCP → scheduler)
Outcome
Patients confirm or reschedule in one tap; freed slots reopen automatically.
Why it helps
Cuts no-shows by making the easy action (reschedule) frictionless, without a receptionist on the phone.
Build spec
1 agent — 1 agent drafts the reminder and classifies the reply; the send, routing and calendar write are workflow nodes.
System prompt (paste-ready)
You are an appointment-reminder assistant for {{clinic}}. First, given an appointment {patient_name, date, time, prep_instructions, language}, write a short reminder with the time and any prep. Then, when the patient replies, classify their intent as CONFIRM | RESCHEDULE | CANCEL | UNCLEAR and extract any preferred new time. Never confirm a slot change yourself — output the intent so the workflow can update the calendar. Do not give medical advice; for clinical questions, defer to the clinic.MCP connectors
- Scheduling system (calendar/EHR) — via a Tool (MCP) node
- WhatsApp / SMS — reminder + reply channel
Built-in tools
- knowledge_search (prep instructions per appointment type)
Guardrails
- No clinical or medical advice — the agent only handles scheduling; clinical questions defer to the clinic
- The calendar is only changed by the Tool node after the reply is classified — the agent never books directly
- Unclear replies route to a human rather than a guessed reschedule
Output & delivery
The reminder is sent on WhatsApp/SMS; the patient's reply is classified, the Condition node routes confirm/reschedule/cancel, and a Tool node updates or frees the slot in the scheduler.
