AI receptionists for clinics: seven checks before you switch one on

It's 7.10pm on a Tuesday. Someone has done their back in lifting a toddler out of a car seat. They ring the physio around the corner. Voicemail. They ring the next one. Voicemail. The third clinic picks up and books them in for 8am.

The first two clinics will never know that call happened.

That's the problem an AI receptionist is meant to fix. Most clinics don't lose new patients at the front desk. They lose them in the hours nobody is at it: mid-session, at lunch, after close.

We built an AI receptionist for a multi-disciplinary clinic in Sydney's inner west. Before it, after-hours calls went unanswered and everything around a booking was done by hand. Here's what we learned about getting one right.

What it should do

Four jobs.

1. Answer every call, in a natural voice.
2. Book, move or cancel the appointments you allow, at the times you allow.
3. Put callers through to the right person during the day.
4. Tell your team what happened, as it happens.

At the clinic, that last job runs through Slack. Every new booking lands in the team's channel. Nobody has to check another system to see what came in overnight.

What it must hand back

This matters more than anything it does.

• Clinical questions. "Should I ice it or heat it?" is not a question for software. It takes the details and passes them to a practitioner.
• Emergencies. It tells the caller what to do and flags the call.
• Complaints and billing disputes. A person handles these.
• Anything it doesn't understand. It takes a name and number and promises a callback. It never loops the caller through the same question.

Seven checks before you switch it on

1. Where does the booking land?

In your practice software, against the right practitioner and appointment type. If it emails someone who re-types it the next morning, you've moved the work, not removed it. Ask for a test booking and watch it arrive.

2. What is it allowed to book?

Initial assessments, or follow-ups only? Which practitioners? Does a new patient need a longer first slot? A referral first? Write the rules down.

Most booking mistakes come from rules nobody wrote.

3. What does it say to a clinical question?

Ring it yourself and ask one. Then describe something that sounds serious. Listen closely to both answers.

4. Who gets which call during the day?

And what happens when that person is mid-session? Decide when it transfers and when it takes a message.

5. Where do the recordings go?

If it records or transcribes calls, you're holding health information. Ask:

• Where is it stored? In Australia?
• Who can see it, and for how long?
• Is any of it used to train the vendor's AI?
• Does the caller hear that they're talking to AI?

Health service providers are covered by the Privacy Act whatever their size. We cover what that means in Can you put client details into ChatGPT?

6. What happens when it gets stuck?

A bad line. A strong accent. Three requests in one breath. Every receptionist meets calls it can't handle, human or not. Test this on purpose before launch.

7. Is the booking form behind it protected?

Bots love booking forms. Left open, they'll fill your diary or inbox with fake requests. At the clinic, the online booking forms are protected against floods of fake requests, so only real people reach the team.

Will it replace your receptionist?

People ask Google this a lot. For most clinics, the answer is no.

Your front desk greets people, takes payments and handles the hard conversations. The job the AI took at the clinic we worked with was the one nobody was doing: answering when everyone was busy or had gone home.

Buy one, or have one built?

There are plenty of AI receptionist products in Australia now, and some are good. A product may be all you need if your practice software is on its supported list, your booking rules are simple, and you only want answering and booking.

A built receptionist earns its place when the phone is one piece of a bigger admin problem. At the clinic, the phones sit alongside new-starter paperwork, certificate checks, contractor reminders and enquiries flowing into the CRM. One system, instead of a pile of tools to look after. Read the full case study.

Before you call any vendor

Keep a list for one week. Every call that went to voicemail. What each caller wanted. What your team did about it the next day.

That list is your brief. It tells you what the receptionist must handle, and what it must hand back.

Want a second pair of eyes on it? Start with an audit. We'll walk through how your clinic runs and give you a short, written list of what's worth handing to an agent first. Or read how we run one in the admin audit.