Cliniko WhatsApp integration: what is realistically automatable.

Cliniko is one of the practice-management platforms Singapore allied-health and therapy clinics reach for most, so the question we get asked often is: how much of the patient conversation can realistically run on WhatsApp alongside it? This article is a plain answer: what automates well, what already exists in Cliniko's app directory, and where a custom build fits.

What Cliniko is, and where WhatsApp meets it.

Cliniko holds the things a clinic runs on: appointments, patient records, billing, appointment types, practitioner schedules. A WhatsApp layer sits in front of that: it is where the patient actually talks. The realistic automations are the ones that move information between those two places without a person copying it across.

What automates well.

• Intake and booking. A new patient messages on WhatsApp; an agent qualifies the request and prepares the Cliniko booking. We have shipped exactly this. See the Alliance Counselling case study, where a WhatsApp intake agent qualifies enquiries, matches clients to therapists, and prepares Cliniko bookings.
• Reminders and confirmations. Reminders can be sent on WhatsApp (the channel the patient already uses) and tied to the Cliniko appointment so they fire at the right interval automatically.
• Follow-ups. A post-visit message (a check-in, aftercare instructions, a prompt to rebook) can be sequenced from the appointment outcome rather than sent manually.
• Rescheduling and routing. A booking integration can be built to handle a change request ("I need to move my Tuesday slot") as a conversation that routes to the right next step, rather than a phone-tag exchange with the front desk.

What does not automate well, and should not, is anything that needs clinical judgement. Triage of a symptom, a decision about whether a patient should be seen urgently, anything sensitive: the right design routes those to a human instead of attempting them. Automation removes the typing and the waiting, not the judgement.

The compound benefit is that these automations reinforce each other. A bot that handles intake well produces cleaner booking data in Cliniko, which makes reminders more reliable, which reduces no-shows, which lightens the front desk, which frees the team to handle the enquiries the bot routed to them. Each piece is modest on its own; together they remove the friction that runs through the whole patient journey, from first message to follow-up.

There are already WhatsApp-aware apps in Cliniko's directory.

Cliniko maintains a connected-apps directory, and it is worth knowing what is already there before building anything. The directory currently lists around 96 apps, with roughly 34 of them under the "Artificial intelligence" heading (including some eleven or so AI receptionists). There is no separate "WhatsApp" category. The WhatsApp-native options sit within that Artificial intelligence group. Two are worth naming.

MIEA handles patient chats, bookings, and reminders, and supports multiple languages including Malay, Chinese, and Tamil. Vascue handles WhatsApp enquiries and writes information back into Cliniko. Both are real, established options, and for a clinic that wants something off the shelf without a build, either could be the right starting point.

Where a custom build differs.

We are not listed in Cliniko's directory, and we are not competing with a directory app on breadth. Where a custom build is the right choice is when a clinic wants something the directory apps do not quite cover: typically a Singapore-local build tuned to the clinic's exact intake flow, a specific language mix, and a one-to-three-week delivery rather than a generic install.

The honest framing is that directory apps like MIEA and Vascue are excellent when the clinic's needs fit their template; a custom build is the answer when they do not. The Alliance build, for example, was custom because a multi-location counselling practice needed a care-first intake that routed sensitive cases to humans and matched clients across dozens of therapists, the kind of specificity a general app is not built around.

The realistic bottom line.

Connecting WhatsApp to Cliniko is genuinely useful and genuinely doable: intake, reminders, follow-ups, and rescheduling all automate well, and the Alliance case shows it working in production for a Singapore practice. Start with the directory if an off-the-shelf app fits; come to a custom build when it does not. Either way, the principle is the same: automate the administrative middle, keep a human on the judgement calls.