The gap Avilo fills
What Avilo adds on top of Cliniko.
Cliniko was built for sending. Everything that comes back is left to your team. Here's the difference, job by job.
| What you need | Cliniko on its own | With Avilo |
|---|---|---|
| Send appointment reminders | Yes | Cliniko keeps sending them |
| Show who's confirmed, who hasn't and who needs a chase | A list to read by hand | Confirm: one list, status written back |
| Chase the quiet ones by text | No | Confirm: automatic nudges |
| Flag a "can't make it" the moment it arrives | Sits in the inbox | Confirm: read and flagged |
| Reply to reschedules and move the booking | No | Avilo AI |
| Offer freed slots to the waitlist | No | Avilo AI |
| Run recalls through to a booking | Sends only | Avilo AI |
| Answer the phone after hours | No | Avilo AI |
Avilo doesn't replace Cliniko. It does the work Cliniko was never built to do.
How the integration works
Your Cliniko diary stays the single source of truth.
Avilo never asks you to run a second system. Your team keeps working the way they do now.
Reads replies and availability
Reminder replies, practitioners, appointment types, locations and open slots come in through the API. Avilo only works with what's genuinely in your diary.
Writes back where your team looks
Confirmation status goes into the appointment. Once Avilo AI is on, reschedules, cancellations and bookings land in the diary the moment a conversation resolves.
Data stays in Australia
Patient data stays on Australian-hosted infrastructure, is never used to train models, and your API key can be revoked from Cliniko at any time.
What Cliniko practices ask us.
Does Avilo use the official Cliniko API?
Yes. Avilo connects through Cliniko's official API with a key you create under an admin user. Nothing is installed in your browser or on your computers, and you can revoke the key at any time from Cliniko. Avilo is an independent product and isn't endorsed by Cliniko.
Does Avilo replace Cliniko's reminders?
No. Cliniko keeps sending reminders exactly as it does today. Avilo reads the replies, shows who's confirmed, and chases the quiet ones.
What does Avilo write into Cliniko?
On Confirm, confirmation status goes into the appointment. Once Avilo AI is on, confirmed reschedules, cancellations and new bookings are written to the diary as they happen.
Does Avilo use Cliniko's waitlist?
No. Cliniko's waitlist isn't available through its API, so Avilo keeps its own. Your team adds patients who want in sooner, and Avilo offers them freed slots once Avilo AI is on.
What if my clinic isn't on Cliniko?
Avilo works with Cliniko today. Tell us what you use in the form above and we'll let you know if that changes.
Getting connected
Where do I find my API key?
Three steps, about two minutes. You'll need to be logged in to Cliniko as an admin user.
Open your API keys in Cliniko
Log in as an admin user. Click your name (bottom left) to open My Info, then choose Manage API keys.
Add a key and copy it
Click Add an API key, name it "Avilo", and copy the key Cliniko shows you. It's only shown once.
Paste it into Avilo
Paste the key into Avilo on your setup call. Practitioners, appointment types and locations import on their own.
You can revoke the key from Cliniko at any time, and Avilo stops reading straight away. How we protect your data →
Avilo works with Cliniko today. Tell us which system you use; demand shapes what we build next.
We use these details only to tell you if Avilo comes to your system. See our Privacy Policy.
In Sydney? We'll come to your clinic and set it up with your team.
Cliniko is a trademark of Red Guava Pty Ltd. Avilo is an independent product and is not endorsed by Cliniko.