Physio & innovator. Founder of Avilo.
I built Avilo because I was the receptionist, the practitioner, and the person trying to spot patient SMS replies between back-to-back appointments. It wasn't working — for me, my team, or the patients we were quietly losing.
I work in a busy practice. Every practitioner has heavy patient engagement, and keeping on top of who's responded to a reminder is a constant, tedious task. You're treating back-to-back all day. A patient texts back to reschedule — to the reminder that literally says "do not reply", because everyone messages these days — and you don't see it for hours.
They don't show up. You've got a gap in your diary. Worse, if a couple of days pass before anyone replies, the patient thinks you ignored them. Sometimes you can't even get them back. That's not just a missed appointment. It's lost revenue that could have easily been recaptured, and a patient relationship that's now a little colder than it needs to be.
I kept hearing the same thing from colleagues at other practices. The problem isn't Cliniko — its reminder system is excellent. The problem is that when a patient replies, there's nothing built to catch it. Avilo is that missing piece.
I'm a physio first. But I've always loved technology and the way a small system tweak can give a whole team hours back. I'm at a clinic with no on-site reception — physios check their own messages — so I built the first version of Avilo for me and my team, to take the admin burden off our plates between sessions.
What I didn't expect was how much better it made things for patients. Even practices that do have reception benefit — receptionists stop watching incoming messages all day and get back to being the warm welcoming smile patients actually came in for, focused on the urgent things that keep people happy.
Avilo is built by a working physio, in a working clinic, for the people who do this every day.
A patient should never know they're talking to software. A practitioner should barely notice Avilo is running. If it draws attention to itself, it's doing too much.
A patient who replies and hears nothing for six hours doesn't feel valued — they feel forgotten. Responding fast isn't a tech metric. It's how trust gets built.
Avilo only handles what it's certain about. Anything ambiguous, clinical, or emotional stops the automation and pulls a human in. A confident "I don't know" is worth more than a confident wrong answer.
Every feature gets filtered through one question: does this give the team their time back? If it doesn't, it doesn't ship.
Connect on LinkedIn, or book a demo — I'll personally walk you through Avilo running in a real Cliniko sandbox.
We'll walk you through Avilo running in a real Cliniko environment. No sales pitch.