MILabs
Integrations

Booking assistant for Cliniko

Booking assistant for Cliniko clinics that answers requests, checks the diary and hands off anything outside the rules to staff.

Updated 2026-02-09

Booking assistant with Cliniko

Clinics that run on Cliniko keep their diary, client records and invoices in one place, so a booking assistant has to work from that diary rather than around it. MILabs would start by agreeing with the owner or team lead which appointment types, clinician schedules and notice periods the assistant may use. Those rules become the basis for offering open times. When a requester asks for a slot, the assistant checks the proposed time against the rules, collects the contact details and reason for visit, and sends a confirmation message. Requests that fall outside the rules, such as urgent symptoms or a clinician's full day, pass to a named staff member. Cliniko remains the place where bookings are confirmed, and the assistant only writes to it through credentials the clinic creates and scopes in its own account. Because the API permissions decide what the assistant can reach, the first working session confirms those permissions before any build begins.

How it works

  1. Map the diary rules by listing appointment types, clinician schedules, notice periods and the requests that must reach a person.

  2. Confirm Cliniko API access by creating credentials in the clinic's account and checking which records they can read and write.

  3. Connect the chat channel to the diary, with Claude handling the conversation and a Make workflow carrying availability checks and confirmed bookings to Cliniko.

  4. Route any request outside the rules to a named staff member, with the conversation attached so nobody repeats the questions.

  5. Run sample requests before launch, compare each proposed time with the diary, and sign off the results with the team.

good questions, straight answers

Frequently asked questions

Do I need a developer to connect a booking assistant to Cliniko?
Usually, yes, for the connection itself. Cliniko offers an API that other software can call, so the work involves creating credentials in the clinic's account, setting how the assistant reads and writes, and building the link between the chat channel and the diary. Staff without developer skills can still own the rules, approve the wording and review the hand-off queue. The clinic keeps control of its account.
How does a booking assistant stay in step with Cliniko?
The assistant checks the diary at the moment a requester asks for a time, so it does not keep its own copy of open slots. Each confirmed booking is written back to Cliniko, which remains the record of truth. Staff changes in Cliniko are picked up on the next check. Clinics should also agree what happens when a slot is taken before confirmation.
How do I know a booking assistant works with Cliniko?
Check it against the diary before any patient sees it. Run a set of sample requests, covering a normal booking, a request outside the rules and a slot that has just been filled, and compare each proposed time with what Cliniko shows. A pass means every confirmed booking appears in the diary with the right appointment type and clinician. Staff should sign off the results before the assistant goes live.
Can I start with a part of a booking assistant on Cliniko?
Yes. The first stage can answer common questions about opening hours, locations and appointment types from approved text, which needs no write access to the diary. Diary lookups come next, and confirmed bookings follow once the rules have been tested. Each stage can run while staff review its results, so the clinic widens access step by step.
How does MILabs test a booking assistant against Cliniko?
MILabs tests the assistant with sample requests that mirror the questions the clinic actually receives. Each reply is checked against the diary, the calendar rules and the hand-off route, and every mismatch is logged and fixed before the next round. The clinic reviews the results with its own team and decides when the assistant goes live. Testing also confirms that the API permissions allow only the reads and writes the clinic approved.
let's make something happen

Custom development: how we can help

Choose how you want to work on this with MILabs. Both options start with an enquiry.

Discovery is free, no obligation from the first chat.

Let us build it for you

We build it and look after it.

Build it yourself, we'll help

You build it with our direction, teaching and a weekly check-in.