An agent that books, reschedules and reminds over WhatsApp inside the clinic’s rules, collects intake before the visit, and hands anything symptom-shaped to a nurse without attempting to triage.
Reference build — a working agent and a worked example, not a client deployment
A typical outpatient clinic with three doctors handles around sixty booking-related messages and calls a day. Each takes about four minutes of a receptionist’s time once you count finding the slot, confirming it, typing the patient into the system and sending the reminder. That is roughly four hours a day, and it is the part of the job that cannot wait, so it always wins over the patient standing at the counter.
The WhatsApp inbox makes it worse rather than better. Messages arrive at 9:40 pm and sit until 8:10 am; by the time the desk replies with two slot options the patient has either booked elsewhere or stopped checking. Reschedules are the same two-minute job repeated thirty times, and a slot that opens at 10:40 stays empty because nobody had time to work the waitlist.
Why an agent, and not a chatbot or a Zap: A form cannot hold a conversation ("Thursday is bad, anything Friday morning?"). A scripted chatbot breaks the moment a patient writes two things in one message. A Zapier flow cannot decide that "my daughter has had a fever since Saturday" is not a booking. The agent reads the message, decides which of five tools applies, and is forbidden from everything else.
The tool list is the permission list. If a capability is not here, the agent does not have it, however it is asked.
| Tool | What it does | What it may touch |
|---|---|---|
check_availability | Lists open slots for a doctor and date range within the rules | Reads the practice calendar |
book_appointment | Books a slot for a named patient, returns the confirmation | Writes to the appointment book only |
reschedule_appointment | Moves or cancels an existing booking within the reschedule limit | Writes to the appointment book only |
send_intake_form | Sends the intake link to a new patient; answers land as a draft record | Creates a draft patient record |
escalate_to_staff | Flags the conversation to a named person with the transcript and a reason | Writes to the staff queue; sends the approved urgent-care text |
| Staff time on bookings, per day | ~4 hours → ~1.2 hours | Worked example |
|---|---|---|
| First reply to a patient message | Next morning → under a minute | Worked example |
| Share of booking conversations completed by the agent | 70% (design target; measured in a pilot) | Target |
| Escalation of red-flag messages | 100% by design; tested against a 60-message red-flag set before each change | Worked example |
Assumptions
What a pilot measures that this page cannot
A pilot runs it on your data in two to three weeks for a fixed fee, measured against your own baseline. Thirty minutes to scope it, free.