In short: if your clinic runs Cliniko and you want an AI receptionist that books directly into it, start with Cliniko’s own connected-apps directory — that’s the authoritative list of what genuinely integrates, and it already includes several AI phone options (Lyngo AI, Aeva AI, Intavia, Jubilee Voice among them). The evaluation that matters isn’t “does it mention Cliniko” but how deep the booking integration goes, what happens to patient voice data, and who runs the thing after go-live.
Straight disclosure before anything else: I run AI4SMB, an Australian AI automation agency whose receptionist work is phone-system-first — and we do not have a shipped Cliniko integration today. Booking workflows are scoped per clinic in our founding pilot, wired to a PMS API where it exists. So on the specific question of native Cliniko-first booking automation, the vendors below are ahead of us, and this guide says so. What we can offer is an honest map of the territory, because clinics keep asking us this on audit calls.
Where the real list lives
Cliniko’s connected-apps directory is the source of truth. Anything listed there has an actual integration Cliniko is willing to display — a materially higher bar than a vendor website mentioning Cliniko in a logo strip. As at July 2026 the AI-reception entries include Lyngo AI, Intavia, Aeva AI and Jubilee Voice. The directory changes — check it live rather than trusting any blog post, including this one.
Of those, Lyngo publishes the most specific claims: direct integration that reads live practitioner availability, appointment types and booking rules, and books, reschedules and cancels in real time, with per-call pricing published on its site (checked 18 July 2026). We compared it with the broader Australian field in our field guide to choosing an AI receptionist — for a Cliniko-native, self-serve clinic setup, it’s the obvious first look.
The questions that actually separate Cliniko AI receptionists
- Booking depth. “Integrates with Cliniko” spans a huge range: reads availability and books real appointments (incl. reschedules and cancellations) at one end; “takes a message your front desk types in later” at the other. Ask which one, and ask to watch it book a real appointment type with your actual availability rules.
- Your booking rules. New-patient vs returning, appointment-type durations, practitioner preferences, buffer rules — if the AI can’t respect them, it books wrong things fast. Ask how rules are configured and who maintains them when they change.
- The clinical-triage line. No AI should be assessing symptoms. Ask exactly what happens when a caller describes something urgent — the answer should be a hard-coded protocol (your emergency message, on-call transfer), not “the AI decides”.
- Patient voice data. This one has legal weight: health service providers are covered by the Privacy Act regardless of size, and call recordings with health information are sensitive information. Ask where recordings and transcripts are processed and stored, for how long, and under whose law — the full legal picture is here.
- The phone side. PMS integration is half the job; the other half is how calls reach the AI at all — a forwarding number, or integration into the phone system you already run. If your clinic has an existing phone setup you like, that difference matters.
- Who operates it. Self-serve subscription (you monitor transcripts, you tune it) versus managed service (someone accountable does). Front desks are busy; be honest about which your clinic will actually sustain.
Where we fit — and where we don’t
If your priority is native Cliniko booking automation, self-serve, today: start at the directory above. That’s the honest answer.
Where AI4SMB’s clinic offering is different: we come from the phone-system and operations side — the AI joins your existing number and PBX rather than a forwarding setup, there’s a self-hosted option for clinics whose patient voice data can’t leave their control (a requirement none of the directory vendors currently advertise), and it’s run as a managed service with monitoring, transcripts and an explicit triage protocol. Booking is wired to your PMS API where it exists, scoped honestly during the founding pilot. If a Cliniko-native integration becomes part of that roadmap, this page will say so — and until it does, we won’t claim it.
Either way: run the six questions, insist on seeing a real booking happen, and check whether the economics stack up before anyone’s subscription starts. If you want a second pair of eyes on a shortlist, that’s a normal part of an audit call — including when the answer is “the directory vendor is the right pick”.