Key takeaways
- Your clinic software stays the source of truth. WhatsApp only feeds it complete requests.
- Connect only where the software allows a safe, documented connection. Otherwise reception enters each request from the Inbox.
- Collect the name, doctor or specialty, branch and two preferred times. Leave out the reason for the visit, ID numbers and card details.
- A request becomes an appointment only when staff confirm it, and the patient's WhatsApp confirmation comes after that.
- Reminders outside the 24-hour window go as Meta-approved templates, and only to patients who opted in.
How does a WhatsApp booking request reach your clinic software?
A WhatsApp booking request reaches your clinic software in seven steps, and a person confirms it at step 5. Steps 4 and 5 change when your software is connected after assessment and testing.
- A patient writes, sends a voice note or, where WhatsApp calling is available, calls the clinic's WhatsApp number.
- The assistant answers from your approved information and asks only for the missing details.
- The complete request waits for reception's approval, marked as pending.
- Where the schedule is connected after assessment and testing, the assistant offers only times it shows as free.
- Reception checks the slot and confirms it, or offers another time. Where the software is connected, the approved booking can then be written to it.
- The patient gets the confirmation on WhatsApp: doctor, branch, date, time and a reference.
- Before the visit, an approved reminder goes out, and reception records attended, no-show or cancelled.
Until reception confirms, the assistant never tells the patient the appointment is booked.
Which details should the assistant collect for a booking?
Collect what reception needs to confirm at a glance, and nothing clinical. Agree the list with your clinic manager before launch.
| Detail | Why reception needs it | Note |
|---|---|---|
| Patient's full name | To find the patient file or open a new one | The WhatsApp number arrives with the message, so don't ask for it |
| Doctor or specialty | To open the right schedule | The specialty is enough. Don't ask for the reason for the visit |
| Branch | Each branch has its own schedule and team | The request goes to that branch's reception |
| Two preferred times | Fewer messages back and forth | Offer free times instead when the schedule is connected |
| Insurance or self-pay | Decides what reception checks | Ask for the insurer's name only. Reception checks the card at the visit |
Never ask for national ID, Iqama or card numbers in the chat. WhatsApp's Business Messaging Policy says not to ask for personal ID card numbers or full payment card numbers, or to request health information where local rules prohibit it.
Fixed steps, such as branch and doctor, work well as buttons or a short WhatsApp Flows form. Patients can still type or send a voice note at any step.
Which setup fits the system your clinic uses?
It depends on where your schedule lives today. Six common setups:
| Your system | How a request gets in | Watch for |
|---|---|---|
| Google Calendar | After assessment and testing, approved bookings can be written to the right calendar, and patients see only times that are free. Pending requests wait for staff approval | A calendar for each doctor or room keeps the free times accurate |
| Outlook or Microsoft 365 | After assessment and testing, approved appointments can be written to Outlook or Microsoft 365 calendars. Pending requests wait for staff approval | Microsoft's free/busy lookup works with work or school accounts, not personal Microsoft accounts |
| Calendly | Bookings made through Calendly get WhatsApp reminders, and patients can ask to reschedule in the chat. Requests from WhatsApp wait for staff approval | Patients can still book or cancel on Calendly's own pages, so reception checks Calendly before confirming a change |
| Clinic software with an API | A connection to its documented API, after assessment and testing, limited to the actions you authorise | Test what happens when the software is slow or down, with reception as the fallback |
| Google Sheets | Each request is added as a new row through the Sheets API, and reception updates its status | A sheet has no booking rules, so reception checks every slot |
| No system, or a paper diary | Complete requests wait in the Inbox for reception to enter and confirm | Every request needs an owner and a due time |
In every setup, your software or diary has the final word on availability. If a connection fails, the request falls back to staff approval rather than a guess.
A clinic that books in a shared sheet
Picture a two-doctor clinic in Nasr City that keeps bookings in a Google Sheet. A patient sends a voice note at 11 pm asking for a Saturday evening slot. The assistant takes her name, the doctor and two times, and adds a row marked pending. At 10 am the receptionist checks the doctor's column, confirms 7:30 pm, and the patient gets the confirmation and address on WhatsApp.
The Leak Audit is free, with no obligation. Within 72 hours of the discovery meeting and receipt of the agreed information, we map your current journey, show the gaps the evidence supports, prioritise next steps and demonstrate one agreed workflow in a test environment. You keep the report. If you don't need HumAI, the audit says so.
Get your free Leak AuditHow do approvals and reminders get back to the patient?
Reception confirms in your software or the Inbox, and the confirmation goes back to the same WhatsApp chat. Within 24 hours of the patient's last message it goes as a normal reply. After that, only a Meta-approved template can carry it.
- Confirmed: date, time, branch, doctor and a reference, with Change and Cancel buttons.
- Another time offered: the patient picks one in the chat, and reception confirms again.
- Reminder: a utility template, with no offers in it, sent only to patients who opted in.
- Change or cancel: the patient's reply becomes a request for reception, which updates the software and frees the slot.
Meta treats a template as utility only when it is non-promotional and tied to the patient's own booking. An offer inside a reminder makes it marketing.
Meta charges templates by category and the patient's country. Since 1 October 2026 it also charges replies inside the 24-hour window after a monthly free tier of 1,000 per business number, and Meta's rate card has the current figures.
What should a WhatsApp booking assistant never do?
Whichever provider you use, a WhatsApp booking assistant should never do these five things:
- It gives no medical advice, diagnosis or triage. Medical and urgent messages go to a person, with your escalation wording.
- It never confirms a booking before your staff do.
- It never quotes a price that isn't on your approved list.
- It never asks for ID, Iqama or card numbers, and it takes no payments.
- It never writes to your software beyond the actions you authorised.
What changes for clinics in Saudi Arabia, the UAE and Egypt?
The steps are the same. What differs is the first question patients ask, how they write, the calls the clinic can place and the data protection law.
| Topic | Saudi Arabia | UAE | Egypt |
|---|---|---|---|
| First question before booking | "Do you take my insurance?" | "Do you take my insurance?" | "How much is the visit?" |
| How patients write | Gulf Arabic and English | Arabic, English and other languages the clinic chooses, each tested before launch | Egyptian Arabic, English, and Franco (Arabic in Latin letters) |
| Calls the clinic places | With the patient's permission | Restricted in the UAE, so voice notes do the talking; the assistant answers WhatsApp calls wherever WhatsApp calling is available | Not available from +20 numbers |
| Identity check | ID or Iqama and insurance card, at reception | Emirates ID, or passport if visiting, and insurance card, at reception | National ID card, at reception |
| Data protection law | Personal Data Protection Law (PDPL) | Federal Decree-Law No. 45 of 2021 (PDPL) | Personal Data Protection Law No. 151 of 2020 |
Before patient data moves into a new connection, ask the provider how it handles consent, storage and deletion under your country's law.
Related
Where HumAI fits, and when you don't need us
HumAI is not booking or clinic-management software. Our System integration service connects WhatsApp to the software you already use, after assessment and testing: authorised actions only, failures tested first, and staff approval wherever no safe connection exists.
The connection runs inside the system we manage for you: the AI assistant on WhatsApp under AI Customer Operations, the Inbox and Dashboard for your team, reminders, and marketing when you want it. Your reception confirms every booking.
You may not need us yet. One doctor and a receptionist who replies quickly can run on the free WhatsApp Business app next to the clinic software. If your clinic software already sends WhatsApp confirmations that work for you, start there.
Questions owners ask
Do we need new clinic software to take bookings on WhatsApp?
No. Keep the clinic software you have and let WhatsApp feed it. If it has a documented API, it can be connected after assessment and testing. If not, reception enters each complete request from the Inbox. HumAI doesn't sell clinic software.
Can the assistant see which slots are free?
Only when the schedule is connected after assessment and testing. With a connected Google Calendar, the assistant offers only times that are free. Other calendars or clinic software can do the same if their API allows it and testing confirms it. Without a connection, the assistant takes two preferred times and reception picks the slot.
Can patients reschedule or cancel on WhatsApp?
Yes. The patient replies to the confirmation or reminder, in writing or by voice note, and the change reaches reception as a request with the booking details. Reception updates the software, which frees the slot for another patient.
Can one WhatsApp number serve several branches?
Yes. The assistant asks for the branch and routes the request to that branch's reception in the Inbox, each working from its own schedule. The owner or manager sees every branch in one Dashboard.
What happens if the clinic software goes down?
Requests should fall back to reception instead of being lost or guessed at. Before launch, test the connection against a slow or unavailable system and agree who handles requests in the Inbox meanwhile. HumAI tests these failures first and keeps staff approval as the fallback.
Sources
- Google for Developers: Calendar API, Events: insert
- Google for Developers: Calendar API, Freebusy: query
- Microsoft Learn: Create event (Microsoft Graph)
- Microsoft Learn: calendar getSchedule (Microsoft Graph)
- Google for Developers: Sheets API, read and write cell values
- Meta for Developers: WhatsApp Flows
- Meta for Developers: Message templates
- Meta for Developers: Utility templates
- Meta for Developers: Template categorization
- Meta for Developers: Send messages and the customer service window
- Meta for Developers: Get opt-in for WhatsApp
- Meta for Developers: Pricing on the WhatsApp Business Platform and rate cards
- Meta for Developers: Cloud API Calling
- WhatsApp: Business Messaging Policy
- SDAIA: Personal Data Protection Law (PDPL)
- Personal Data Protection Center (PDPC), Egypt
- UAE Legislation: Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data
- UAE government portal: Emirates ID