A WhatsApp AI agent for a clinic with several branches

The short answer. A multi-branch clinic needs an agent that reads the question, matches the right doctor at the right branch, holds a real slot in the calendar, and takes the deposit, all inside the WhatsApp thread the patient already opened. Helm builds and runs that workflow. The rules it may never break are agreed and signed before it is built.

Why clinics end up asking this

Before Helm went live on the clinic accounts we run, we read 3,457 conversations by hand. 53% of them arrived while the office was shut, and the median wait for a reply from the clinic's own staff was 1 hour 36 minutes. A clinic's front desk works the hours the clinic is open. Its patients write at 11pm, after the children are asleep, and they ask the same three things: is the doctor free, how much is it, which branch is closer.

With one branch, a receptionist and an away message can almost keep up. With three, the question «is Dr. Hana free tomorrow?» has three possible answers. The patient who gets no answer books somewhere else.

What the agent finishes, in the thread

Three jobs cover most of a clinic's inbox:

1. Triage, doctor match and a slot held with a deposit. The agent reads the symptom or the specialty, matches the right doctor and branch, offers slots it can see in the real calendar, and holds the chosen one against a deposit. It gives no clinical advice at any point.
2. Reminders and recall. The day-before reminder, the six-month recall for regulars, and the reschedule when the patient can't make it. These go out as approved WhatsApp utility templates.
3. Insurance, price and branch questions. Answered from the clinic's published list. Anything outside the list goes to the branch that owns it, with the conversation attached.

What it never does

This part decides whether a medical team can say yes. Before the build, the clinic signs three rules, and every conversation trace shows them being applied:

• It never gives clinical advice.
• It never confirms a booking it cannot see in the calendar.
• It hands the patient to a named nurse the moment a symptom keyword appears.

A tool that answers from a knowledge base can describe a clinic. It cannot hold a slot, take a deposit, or stop itself at the right moment. Those three things are the job.

Several branches, one number

Patients don't care which branch's WhatsApp they wrote to. The agent answers on one number for every branch. It reads each branch's calendar and routes anything it may not handle to the right branch's named owner. The branch manager sees their own queue. The clinic owner sees all of them.

The number to judge it by

Agree one number before the build: booked and attended, with no-shows counted against the deposit rule. Replies sent and messages handled are activity, not outcomes. A clinic is paid for patients who walk in.

What to send to start

The appointment book, in whatever form it lives today: a calendar, a sheet, a printout. Add the price list and the branch addresses. A first, single workflow is typically live within five working days once we have them. Integrations with an EHR or a hospital system take longer and are scoped separately.

The clinics and hospitals page shows the desk working. You can also message it on WhatsApp in your own language.