What slows down a clinic front desk?
In most clinics, dental practices, physiotherapy centres and diagnostic labs we speak to, the front desk juggles the same tasks all day: answering "what are your timings?", "is the doctor available on Saturday?", "how much is a consultation?" and "where do I park?", while also confirming appointments, handling walk-ins and calling patients who didn't show up. WhatsApp has become the main channel, often on one shared phone.
Which clinic workflows can be automated safely?
- Appointment requests: collect name, preferred doctor, date and time window, then create a request for staff to confirm, or book directly into a shared calendar or sheet where rules are clear.
- Reminders: approved utility templates the day before and on the morning of an appointment, with buttons to confirm or reschedule.
- Repeat information: timings, address, parking, doctors' schedules, what to bring, and test preparation instructions approved by your clinicians.
- Report-ready notifications for diagnostic centres, with the report shared through your secure system rather than pasted into chat.
- Follow-up nudges: "it's time for your review visit", sent only to patients who opted in.
- Missed-call follow-up: a WhatsApp message when a call to the clinic goes unanswered.
What must a clinic agent never do?
Healthcare needs the strictest stop rule of any industry. Our default for clinics:
- Never answers questions about symptoms, diagnosis, medication or dosage. It replies that a staff member will call back, and hands over at once.
- Never interprets test results.
- Always hands over if a message suggests an emergency, with a clear instruction to call emergency services or come in.
- Doesn't ask for medical history in chat; that belongs in your clinical system.
- Fee quotes come only from an approved fee list, or go to staff.
How do data protection rules apply?
Health information is sensitive. We minimise what the bot collects, limit access to front-desk staff, define how long conversation logs are kept and document which vendors process data. Read our DPDP basics for chatbots and take advice from your legal adviser.
Which tools does this connect to?
Usually a WhatsApp Business Platform number, your appointment calendar or practice-management software (where it has an API), or simply a Google Sheet for smaller clinics. See Google Sheets to WhatsApp.
The agent drafts, routes and escalates. A person decides. Before anything is built we write down what the agent may do alone, what needs approval, and when it must stop and hand over with the full context attached.
How is the agent team put together?
Every team we build uses the same architecture: a team lead agent that plans and assigns work, specialist agents with narrow jobs and permissions, a shared task board where every task and approval is visible, tools and connectors limited to what each agent needs, scheduled routines for recurring checks and reports, and approval gates wherever money, customers, data or irreversible changes are involved. Every action is logged, live systems are backed up before edits, and a daily summary arrives in chat so a person always knows what happened.
It is the same pattern we use in-house for our 14-bot SEO team, ads agent and site ops agent on the owner's own businesses (in-house systems, not client results). For a new team we start small, usually a specialist, a reporter and the team lead, and add agents only once the first ones are trusted. See how we build agent teams and real in-house use cases.
What should you prepare before talking to us?
You don't need a technical brief. A useful first conversation needs only a few things, and gathering them is valuable even if you never work with us:
- The process in plain words: what triggers it, who does what, and where it usually goes wrong.
- Rough volumes: how many messages, orders, tickets or invoices per week. A one-week tally is enough.
- Your tools: WhatsApp app or API, CRM, sheets, accounting or helpdesk software, including versions or plans where you know them.
- Three real examples: typical messages or cases, plus one awkward one, with personal details removed.
- What must never happen: the mistakes that would hurt most. These become the first lines of your stop rule.
- An owner: the person who will review the workflow once it runs.
Send these on WhatsApp or by email, or run the pilot scorecard first.
How do you know whether the pilot worked?
We agree the success measure before building, and it should be something your team can count without a dashboard project. Typical measures include the share of enquiries logged the same day, time to first response, the number of follow-ups that actually happened, hours spent on the task per week, or the number of escalations that were correctly flagged. We count the baseline before launch (even by hand for a week) and again after a few weeks of running.
We also review the qualitative side with the people involved. Do they trust the drafts? Are handovers arriving with enough context? Are customers asking for a person more or less often? A pilot can hit its number and still need tuning, or miss it and teach you something important. Either way, the decision to keep, tune, expand or stop is yours, made on evidence. We don't publish generic success figures, because results depend on your process, volumes and team.
How does a pilot with us work?
Every engagement follows the same four steps. Consult: you walk us through the process, the tools and where it breaks. Pick the pilot: we choose one workflow and write down its inputs, outputs, tools, stop rule and success measure. Ship: we build it into the tools you already use and test it on real cases. Review: your team checks what the agent did and what it escalated, then decides whether to tune it, expand it or stop. Read the full pilot process.