Clinic automation: WhatsApp replies, reminders and one patient record
Clinic automation is a set of rule-based workflows that run a clinic's repeated back-office work. It covers reply drafts for WhatsApp questions, appointment reminders, cancelled slots returning to the diary, post-visit messages and one patient record. ALTAI Digital builds these flows on the clinic's own rules. Drafts come from sources the clinic provides, and a person decides what is sent. The system takes no part in diagnosis or treatment. Health data is handled under GDPR Article 9. The first live flow opens within four to eight weeks.
Clinic automation is not a website project. It takes the work that repeats every day at the front desk and puts it on rules. At half past eight the phone rings, a patient at the desk wants to check in, and WhatsApp holds last night's questions. Opening hours, parking, preparation for an appointment, moving a booking: the same questions arrive every day. The answers already exist in the clinic. They are simply typed again each time. Automation takes over that repetition and leaves every decision with a person.
A WhatsApp message sent at night waits until someone picks up the phone in the morning. With the WhatsApp Business API, several staff answer from the clinic's single number. The history stays with the clinic, not on one person's phone. Reply drafts for common questions are prepared from sources the clinic supplies: opening hours, which clinician works which day, preparation notes. Each draft goes to an approval queue. Nothing reaches the patient until a person sends it. A question the sources do not cover becomes a handover to a named person, not a guess.
Two rules shape every message. Under GDPR Article 9, health data is a special category of personal data. Where a form or a message processes health information, the patient sees a privacy notice and gives explicit consent, recorded with a date. Messages stay informational: a reminder, a care note the clinician has approved, a notice that results are ready. The system does not diagnose, suggest treatment or answer questions about medication. Those messages go straight to the clinician, or to the person the clinician names.
Missed appointments, or DNAs (did not attend), are the quiet cost. A reminder goes a day and two hours before each appointment, by WhatsApp, SMS or email, with a cancellation link. A cancelled slot returns to the diary and the waiting list is told. At month end the clinic sees occupancy, the DNA rate and the most requested times. Below are the scope, the four steps and common questions. We work from Rotterdam and Istanbul. Pricing follows the discovery call, in euros or pounds sterling.
What goes wrong today
- 01
Reception is on the phone all morning
The morning starts with calls about bookings, changes, directions and results. While one call is answered, the next patient hears the engaged tone. The same person is checking patients in at the desk. Routine questions take the time that patients in the room need.
- 02
WhatsApp runs on one person's phone
The clinic's WhatsApp sits on a receptionist's own phone. Nobody else sees the conversations, and night messages wait until that person is back. When the receptionist leaves, the history leaves too. The tone of each reply depends on who happens to write it.
- 03
Reminders depend on someone remembering
Tomorrow's list is printed in the afternoon and patients are called one by one. On a busy day the calls stop halfway. A patient who forgets leaves an empty slot. Nobody records the DNAs, so the cost never shows up at month end.
- 04
Cancelled slots stay empty
A patient cancels in the morning for an afternoon appointment. Someone on the waiting list would take the slot, but nobody tells them. The list sits in a notebook or in one person's head. The diary no longer matches the real shape of the day.
- 05
Web enquiries land in a shared inbox
Enquiries from the website arrive in a general inbox with no owner. Some wait for days; others get two different replies from two people. Whether an enquiry was answered, and by whom, is not recorded anywhere the clinic can check.
- 06
Patient details live in four places
Messages sit in WhatsApp, bookings in the diary, form answers in email and consent on paper. Answering one question means opening four screens. Finding a consent record for an audit or a patient request takes time. Matching the pieces by hand is where mistakes creep in.
Scope of the build
WhatsApp reply drafts from the clinic's own sources
Several staff answer from one clinic number, and the history stays with the clinic. Drafts come from sources the clinic supplies: opening hours, clinician days, preparation notes. Each draft waits for approval. Uncovered questions, and anything on diagnosis, treatment or medication, go to a named person without a draft.
Reminders, cancellations and the waiting list
Reminders go a day and two hours before the appointment, by WhatsApp, SMS or email. Each carries a cancellation link. A cancelled slot returns to the diary and the waiting list is notified. The diary syncs both ways with Google Calendar or Outlook. The clinic decides which channel each patient receives.
Post-visit messages on approved templates
A follow-up date, a clinician-approved care note or a results-ready notice goes out on a trigger. If the patient has not written in the last 24 hours, only a Meta-approved template can be sent. The clinic signs off each template first. The wording stays informational, with no promotional language.
Enquiries routed to the right person
Enquiries from the web form, email and WhatsApp land in one queue. A rule assigns each one by treatment or topic, and it appears on that person's screen. An enquiry that waits longer than the clinic allows moves to the top, and its owner is notified. Everyone sees who is on what.
One patient record
A patient's messages, bookings, form answers and consent record sit together on one record. When a draft is prepared, earlier messages and appointments open beside it. A connection to the clinic's existing patient system is assessed at discovery. Clinical notes and diagnoses stay out of these flows and remain in the clinic's clinical record.
GDPR: privacy notice, explicit consent and data location
Where a form or a message processes health information, a privacy notice is shown and explicit consent is recorded with a date. Forms that need no health data never open that field. Where data must stay in-house, flows run on n8n on the clinic's own server. Conversations are not used to train models.
Monthly report and flow log
Each month the clinic receives occupancy, the DNA rate and the most requested times. The same report shows each flow's success rate, average run time and pending errors. Every run is written to a log. A failed step is queued, reported and retried. Flows are handed over in the clinic's own account, with documentation.
How the set-up runs
- 01
Discovery (1 week)
We map where questions arrive, how the diary runs, where patient details live and what each form asks. Every point that touches health data is marked for consent.
- 02
Build
Reply sources are written and the handover list is agreed with clinicians. Reminder and post-visit templates go to Meta for approval. Each flow is documented with its trigger, steps and error handling.
- 03
Trial
The team tests every flow on their own phones first. Drafts are read, reminders arrive, cancellations and the waiting list are checked in use. Rules that get in the way are corrected.
- 04
Launch and measurement
The first live flow opens within four to eight weeks. At the end of month one we report occupancy, the DNA rate, reply times and flow errors.
Clinic back-office automation
- WhatsApp Business API: one number, several responders, approval queue
- Reply drafts from the clinic's sources, with handover to a named person
- Appointment reminders, cancellation link and waiting-list notices
- Meta-approved post-visit templates
- Web enquiries in one queue, assigned by rule
- GDPR privacy notice and dated explicit consent
- Monthly report: occupancy, DNA rate and flow health
Pricing is given after the discovery call, once the scope is clear.
Products used in this build
Request handling
Requests from five channels collect in one list, the draft reply arrives ready, and the decision to send stays with you.
Online booking and scheduling
Online booking for clinics, salons and hotels; reminders and cancellation handling close the empty slot.
WhatsApp Business integration
Notifications, order tracking and customer conversations gather in the business account; the history stays with the company.
Workflow automation
Repeating processes run in the background; the process picks the tool, and a failure does not stay quiet.
Terms used on this page
- Clinic automation
- Clinic automation is a set of rule-based workflows for a clinic's repeated replies, reminders, records and reports. It takes no part in diagnosis or treatment.
- Reply draft
- A reply draft is an answer to a patient's question, prepared from sources the clinic supplies. It is not sent until a person approves it.
- WhatsApp 24-hour rule
- The WhatsApp 24-hour rule allows free text for 24 hours after a patient's last message. After that, only an approved template can be sent.
- DNA rate
- The DNA rate is the share of appointments in a month where the patient did not attend and gave no notice. It appears in the monthly report beside occupancy.
- Special category data
- Special category data is personal data that GDPR Article 9 protects more strictly, health data included. Processing it on a form needs explicit consent.
clinic automationFrequently asked questions
No. The system does not diagnose, suggest treatment or answer questions about medication. Those topics head the handover list, so the message goes to the clinician, or the person the clinician names, without a draft. The system handles admin questions only: hours, directions, preparation notes and bookings. Clinical decisions stay with the clinician.
By default, every reply draft waits in an approval queue until a person sends it. The clinic can switch on automatic replies for narrow topics such as opening hours. Reminder and post-visit templates are approved by the clinic first, then by Meta. Who approved each message, and when it went, is logged.
After a patient's last message, the clinic has 24 hours to reply in free text. Once that window closes, only a template approved by Meta can be sent. That is why reminders and post-visit messages are written as templates. Approval usually takes a few days, and no unapproved text goes out.
Health data is a special category under GDPR Article 9. Where a form or a message processes it, the patient sees a privacy notice and gives explicit consent, stored with a date. Where data must stay in-house, flows run on n8n on the clinic's own server. Conversations are not used to train models.
Yes. The clinic's existing number can move to the WhatsApp Business API. It then leaves the personal WhatsApp app. After the move, several staff reply from the same number and the history stays with the clinic. The move is planned at discovery for a quiet day in the diary.
By default a reminder goes a day before the appointment and again two hours before. The channel is WhatsApp, SMS or email, and the clinic decides which patient gets which. Each reminder carries a cancellation link. A cancelled slot returns to the diary and patients on the waiting list are told.
It takes routine questions off the phone line. Hours, preparation notes and booking changes are handled on WhatsApp with drafts, and reminders go out without a call. We do not quote a figure before measuring your clinic. The first monthly report compares reply times and DNAs with the weeks before launch.
Set-up starts with a discovery week, and the first live flow opens within four to eight weeks. The number of flows, the channels and any link to a patient system set both time and price. Pricing is given in writing after the discovery call, in euros or pounds sterling.
The process first, the proposal after
In a short discovery call we map the process together and tell you plainly whether it is worth automating. If it is not, we say that too.
30 minutes · no preparation needed
