Cliniko's reminders and diary are excellent, but when a patient replies, calls, or goes quiet, everything falls back on your team. Avilo sits on top of your Cliniko diary and handles the conversations, live.
Read & write in real time · No data migration · Set up in ~15 minutes
Avilo never asks you to run a second system. It connects through Cliniko's official API and works directly on the diary your team already lives in.
Practitioners, appointment types, booking rules and open slots import automatically, so Avilo only ever offers times that are genuinely free.
Bookings, reschedules, cancellations and confirmation statuses land in the diary the moment a conversation resolves, with reminders re-scheduled automatically.
Patient data never leaves the Cliniko / Avilo perimeter, stays on Australian-hosted infrastructure, and is never used to train models.
Cliniko was built for outbound: reminders and recalls going out. Everything inbound, and every real conversation, is left to manual handling. Here's the difference, feature by feature.
| What you need | Cliniko native | With Avilo |
|---|---|---|
| Send appointment reminders | Yes | Uses Cliniko's reminders |
| Track who's confirmed vs unconfirmed | Sends only | Tracked reliably, non-responders nudged |
| Flag likely no-shows for a call | No | Auto-flagged the day before |
| Handle reschedule & cancel conversations | No | Full conversation by SMS |
| Route replies to the right practitioner | No | Automatic routing + Slack/Teams/SMS alerts |
| Update the diary automatically | No | Real-time write-back |
| Answer inbound calls after hours / on overflow | No | Coming soon |
| Run recalls & reactivation to a booking | Sends only | Coming soon |
| Fill cancellations from the waitlist | No | Coming soon |
Avilo doesn't replace Cliniko. It does the work Cliniko was never built to do.
One API key from your Cliniko settings. Practitioners, appointment types and booking rules import automatically.
We scan your website for FAQs and policies, confirm every answer with you, and set your escalation rules and routing.
No engineering, no data migration, no downtime. Most practices run their first real patient conversation the same morning.
Yes. Avilo connects through Cliniko's official API, reading availability and writing appointments without moving patient data outside the Cliniko / Avilo perimeter. Your diary stays the single source of truth.
No, it works with them. Cliniko keeps sending reminders exactly as it does today. Avilo handles everything that comes back: replies, reschedules, cancellations, confirmations and questions, writing every outcome back to the diary.
Barely. Your team keeps working in Cliniko as normal, and Avilo's work simply shows up there. Escalations arrive wherever your team already is: Slack, Teams, Discord or SMS.
About 15 minutes. One API key, automatic import, a short call to confirm your policies. Most practices handle their first real conversation the same day.
Avilo is built on Cliniko today. Support for other allied health practice management systems is on the roadmap. Tell us what you use; demand directly shapes what we build next.
A 30-minute walkthrough on a live Cliniko environment: reschedules, confirmations and escalations, handled end to end in front of you.
Book a demo →No commitment · No credit card · Built in Sydney for allied health
