AI receptionist for Best Practice and Medical Director: what actually works
Many Australian general practices run Best Practice or Medical Director, and both are desktop systems. That one fact shapes everything about putting an AI receptionist in front of them. It can be done. It is not the same job as connecting to a cloud system, and anyone who tells you it is has not done it.
The short version
Best Practice and Medical Director hold your data on your own server, so anything that connects to them has to be scoped and secured, not just switched on.
There are three levels: taking messages, booking into the appointment book, and running back-office work such as recalls. Know which one you are being sold.
Ask how it connects, who maintains that connection after a software update, and what happens to calls when the connection is down.
We are asked this more than almost anything else: will it work with Best Practice? Will it work with Medical Director? The honest answer is yes, with a condition. We scope the connection with you before you commit, so you know exactly what is possible in your practice before you pay for it.
This is what that scoping looks at, and what you should ask any vendor, including us.
Why desktop systems are a different job
A cloud practice system, such as Halaxy or Cliniko, lives on the internet. It is built to be connected to, and those connections are made online.
Best Practice and Medical Director are installed on a server in your practice, or one hosted for you. Your appointment book and patient records sit there. For an AI receptionist to book an appointment, it has to reach that system safely, through a connection the software supports and your IT provider is comfortable with.
That is why two practices running the same software can get different answers. It depends on the version you run, how your server is set up, and what your IT provider will allow.
The three levels of connection
Level one: it takes a message. The AI answers, captures the name, date of birth, callback number and reason, and sends it to reception to action. There is no connection to your practice system at all. It still stops calls ringing out, and it works with any software from day one.
Level two: it books. The AI can see availability and place the booking in the appointment book. Nobody re-keys anything. This is what most practices picture when they hear AI receptionist, and it is the level that needs the connection scoped.
Level three: it runs the back office. Recalls, reminders, results follow-up and reports, working inside the system you already use. This returns the most staff time, and it asks the most of the connection.
A vendor’s demo often shows level two or three. Ask which level you would actually get on your version of your software, and get it in writing.
Questions to ask before you commit
Does a booking land in our appointment book without anyone re-keying it? If someone still has to type it in, you have moved the work, not removed it.
How does it connect? Through an integration the software vendor supports, or through access to your server? Best Practice publishes a list of partner products on its website, so check whether the product you are looking at is on it, and ask what that means for support.
Who looks after the connection when the software updates? Best Practice and Medical Director both release updates. Ask who tests the connection afterwards, and how quickly a break is fixed.
What happens to calls if the connection is down? A sound answer is that it falls back to taking a message, so no call is lost.
Where are calls and transcripts stored? Health information carries obligations under the Privacy Act 1988. Ask where the data sits, and get it in writing.
What does it do when a patient describes a symptom? It should hand the call to a person, and point emergencies to triple zero. It must never give clinical advice or decide how urgent something is.
A sensible way to start
You do not have to solve the integration before you get any benefit. Many practices start at level one: every call answered, a proper message taken, after hours covered. That works on any system and shows you how your patients respond.
Booking and the back office can follow once the connection has been scoped and tested. It is the same system extended, not a second tool.
How we approach it
We build AI receptionists and back-office automation for Australian medical practices, around the software you already run. Cloud systems like Halaxy and Cliniko connect directly. Desktop systems like Best Practice and Medical Director are scoped with you first.
Every conversation is logged and reviewable, the system and its records are hosted in Sydney, and a person handles anything that needs judgement. Evolaition is independent of Best Practice Software and MedicalDirector. Their names are used here only to describe what we work with.
For more detail, read connecting AI to your practice management system, or see the AI receptionist we build for medical practices.
Running Best Practice or Medical Director?
Tell us your version and how your server is set up. We will scope what is possible with you before you commit to anything.