AI Receptionist for Cliniko Practices

An allied health clinic sells hours. Not treatments, not outcomes, hours. And an hour that goes unfilled on a Tuesday is not deferred revenue, it is revenue that never existed, because Tuesday does not come round again. So on a Cliniko practice the phone is not an overhead. It is the thing that fills the diary or quietly fails to, one unanswered call at a time.

We build the Cliniko connection, so this is what happens between a caller asking for an appointment and that appointment sitting in the Cliniko diary.

"Works with Cliniko" can mean a lot of things, so here is the exact one. 2care connects to Cliniko through its REST API, authorised with a scoped key set up during onboarding. Nothing is installed in the practice and no screen is read behind the scenes.

The pieces map cleanly onto Cliniko's own objects. Availability is read from available times per practitioner and appointment type, so an offered slot is genuinely open. A booking writes an appointment against the resolved patient, and Cliniko validates it against its own rules, which is why a slot taken during the call fails honestly rather than being assumed free. The connection carries its own key handling and rate limits, so the load behind it never reaches the caller, and where the Cliniko patient area is in use, a caller and an online booker resolve to the same record, never two.

Cliniko object	What the agent reads	What the agent writes
available times	Open slots per practitioner and type	Nothing
appointments	Nothing	The confirmed appointment
patients	The existing record	A new patient, where permitted
appointment types	The length and who offers it	Nothing
practitioners	Which practitioner does what	Nothing

The value of mapping onto Cliniko's own objects, rather than a scraped page, is that the agent behaves like any other well-built Cliniko client. It respects the same availability, the same appointment types and the same practitioner rules the practice already relies on. There is no shadow copy of the diary that can drift out of date, and nothing that quietly stops working the day Cliniko ships an update, because the connection uses the interface Cliniko maintains for exactly this purpose.

Filling the diary the way an allied health practice needs

Volume matters less here than fill rate, and the two are related: a call that rings out at 8am is an hour that may not sell. There is no per-line limit, so every call is answered on the first ring in about 2 seconds, whether one person rings or forty do after a long weekend. Because the voice pipeline is native, reading Cliniko, reasoning and replying share one budget rather than being relayed between separate systems, so the answer is fast even while the diary is being read live. An urgent call reaches a person in about 3 seconds, ahead of the booking traffic rather than behind it.

Booking a whole plan of care in one call

This is the single biggest driver of a Cliniko practice's numbers, and the one most systems miss. Allied health runs on plans: an initial assessment and a course of follow-ups at a set cadence. Booking the assessment and promising a callback for the rest is how a plan drops off between visits two and three, taking the revenue of the unbooked hours with it.

2care books the plan in one call where Cliniko supports it, placing each follow-up at the cadence the practitioner sets, against someone eligible to deliver it, at the right length. The patient leaves the call with the whole course in the diary, not the first visit and an intention to ring back. On a practice whose income is the sum of its filled hours, a plan booked whole in one conversation is worth more than any single clever feature.

Take a physiotherapy plan of 6 appointments over 8 weeks. Booked one at a time, the later visits are the ones that slip: the patient improves, forgets to rebook, and the course ends early with the outcome half delivered and three hours unsold. Booked as one series at the cadence the practitioner set, all six sit in the Cliniko diary before the first call ends, each with its own reminder, and the plan runs to completion far more often than it lapses.

Catching the drop-off within a day

The other side of fill rate is the patient who was going to come and then does not: a cancellation, a no-show, a plan that stalls after a good week. On most practices that patient disappears into a report nobody works until the month end, by which point the hours are long gone and the patient has moved on.

Because a cancellation and a missed visit are both events the agent sees against the Cliniko diary, they become an action the same day rather than a line on a report. A freed hour is offered down the waitlist within minutes, and a patient who dropped out of a plan is called back to rebook while the gap is small enough to close. Catching the drop-off within a day, rather than a month, is where a surprising amount of a practice's lost revenue actually lives.

The record resolved, and intake captured clean

Before anything is written, the caller is matched to the existing Cliniko record with a date-of-birth check, so a returning patient keeps one file. Where two records are genuinely plausible, the call goes to a person with the candidates gathered, following patient matching, instead of a guess that splits a treatment history in two.

Intake is captured in the same breath: the reason, the referral where there is one, and the contact and funding details, read back to confirm and written to Cliniko as structured fields rather than a free-text note a receptionist retypes. Clean capture at booking is what keeps the front desk clear, and it is the same structured intake that feeds patient intake whether the patient rang, messaged or filled in a form. The funding detail matters more here than in most settings, because an allied health plan often runs against a scheme or a cap, and capturing it correctly at booking is what keeps a course from stalling on an eligibility question three visits in.

What 2care changes for a Cliniko front desk

A Cliniko practice is not looking for a better diary; it has one. It is looking to stop losing the hours that leak out through an unanswered phone. 2care answers every call and turns it into a booked appointment, or a booked plan, without adding front-desk staff. It reads the reason, applies Cliniko's own types and rules, resolves the patient and writes the appointment, in one native pipeline rather than a chain of tools passing a patient between them.

What a practice feels is not a faster booking on the calls it already caught. It is the Saturday enquiries that used to reach voicemail now booked into Monday, the plan booked whole instead of piecemeal, and the diary fuller because fewer callers hung up waiting. 2care keeps the phone at the standard the practice needs to keep the hours sold.

Write-back on Cliniko, and the agreement behind it

A Cliniko booking is not a call that passes through and leaves nothing behind. A transcript is built, a patient is matched, and an appointment is written.

HHS guidance treats a vendor that does that as a business associate, not a passing conduit, so a signed BAA is in place from the first call. The data is encrypted in transit and at rest, the models behind the conversation never see it for training, and each write can be traced and undone. The compliance page sets out the rest, including the frameworks that apply outside the US.

Working the diary between calls

The same Cliniko connection works outbound on the practice's schedule. It rings patients whose plan has a gap opening before the gap stretches, backfills a cancellation from the waitlist within minutes so the hour does not vanish, and confirms the next day's appointments to hold down no-shows. Each result is written to Cliniko, so a filled slot and a completed recall show up in the diary the practice already watches, not on a spreadsheet beside it.

Where this is right for a Cliniko practice

The practices that gain most share a few traits.

A diary that lives or dies on fill rate. The more the practice's income depends on hours booked, the more answering every call is worth, and allied health feels that most directly of any setting.

Types and durations kept current in Cliniko. The agent books what Cliniko holds, so a practice that keeps its appointment types and practitioner rules accurate gets the full benefit from the first day live.

A route for the clinical call. Anything that turns clinical goes to a practitioner, so a practice with that path already in place can move the line over straight away.

Going live on Cliniko

Three steps, over weeks. First, authorise the connection so the agent can read available times and write appointments through the Cliniko API. Second, map your setup: businesses, practitioners, appointment types, durations, the cadence of your plans of care, and the escalation path for a clinical call. Third, test against a test setup with your team listening, then move the line over and watch the first days while the mapping settles against the real call mix.

The first days are for tuning. An appointment type mapped to the wrong length is corrected, a practitioner offered for a class they do not run is dropped from it, and because each escalation carries the trigger that raised it, every change has a reason attached rather than a guess. It steadies inside a fortnight, and patients dial the same number throughout.

The numbers under the diary

The numbers under the diary are what keep the hour sold. The agent replies in about 480 milliseconds, ninety-fifth percentile under 700, on a native voice pipeline rather than a wrapper, so a live Cliniko read costs the call almost nothing. Uptime is 99.9%, the line takes 1000+ concurrent calls, and the appointment write is idempotent, so a network stutter never turns one booking into two on the diary.

Frequently asked questions

Does it book the whole plan or just the first visit?

The whole plan, in one call, where Cliniko supports it: each follow-up placed at the cadence the practitioner sets, against an eligible provider. Booking only the assessment and promising a callback for the rest is precisely the leak it closes.

Can it fill a cancellation from the waitlist?

Yes. When a cancellation frees an hour, the agent offers it down a priority waitlist within minutes, so a slot that opens on Tuesday morning is filled by Tuesday afternoon rather than lost. The result is written straight back into the Cliniko diary.

Will it create duplicate records in Cliniko?

No. A returning caller is resolved to their existing file before anything is written, with a date-of-birth check, and an ambiguous match is handed to a person rather than guessed, so a treatment history stays on one record.

Does it answer weekend and evening enquiries?

Yes, every hour, at any volume, with no busy signal. The enquiries that used to hit voicemail on a Saturday are answered and booked into the week ahead, and anything clinical follows the practice's out-of-hours escalation rules.

Is patient data ever used to train models?

No. A patient's information never becomes training data for any model in the pipeline. It is encrypted on the wire and in storage, retained only for as long as the record needs it, and covered by the BAA that governs every Cliniko call. The conversation quality comes from design, not from mining your patients' data.

Hear it book a full plan of care

The call worth judging on a Cliniko line is an assessment that has to become a whole course of follow-ups, booked in one conversation at the right cadence. That is where filling the diary either holds together or leaks.

See how the same connection runs on other systems across integrations, or hear a plan of care booked on a live call when you book a demo.