Healthengine’s Helen or a custom AI receptionist: how to choose
If you run a general practice in Australia and you are looking at AI receptionists, Healthengine’s Helen is probably on your list. It is a ready-made product from a company practices already know. We build the other kind: an AI receptionist made around one practice. They suit different practices, and this is how to tell which one you are.
The short version
Helen is a ready-made AI receptionist from Healthengine, built for Australian general practices. A custom build is designed around one practice’s software and workflows.
A product is quicker to start and simpler to buy. A custom build fits practices the product was not designed for, and can take on work beyond the phone.
The deciding questions are your practice software, your practice type, and whether the phone is your only problem.
A note on fairness first. We build custom AI receptionists, so we are not neutral. What follows about Helen comes from Healthengine’s own public pages at the time of writing. Products change, so check their website for current details before you decide. Evolaition is not affiliated with Healthengine.
We also tell practices to buy a product when a product is the better fit. Sometimes it is.
What Helen is
Healthengine describes Helen as an AI receptionist built for Australian general practices. According to its website, Helen answers patient calls around the clock, handles several calls at once, and books, reschedules and cancels appointments. Healthengine says complex or sensitive calls are transferred to the practice’s reception team, and that a possible emergency is escalated with the caller told to call 000.
Healthengine states that Helen’s integrations are available for practices using Best Practice and Pracsoft. It launched nationally in August 2025.
What a custom AI receptionist is
A custom build starts from the practice, not the product. Someone maps how your calls, bookings and follow-ups actually work, then builds the system around that: your greeting, your booking rules, your practice software, your handover points.
It can also go past the phone. The same system can run website chat, recalls, reminders and results follow-up, because it is built as one system and not bought as one feature.
The cost is time and money at the start. There is a scoping session, a build, and a settling period on real calls.
When a ready-made product is the better choice
You are a general practice on software the product supports. If the product was designed for exactly your setup, you get the benefit of that design without paying for a build.
The phone is the whole problem. If calls ringing out is what hurts and the rest of your admin runs well, a phone product solves it.
You want to start quickly and compare prices easily. A subscription is simpler to buy, and simpler to stop.
If that describes your practice, try the product first. We would rather you bought the right thing.
When a custom build is the better choice
You are not a standard general practice. Specialist groups, pathology providers and allied health practices take different calls. Referrals, results and recalls work differently, and a product designed for general practice may not fit.
You run software the product does not connect to. Halaxy, Cliniko, Zedmed and Genie are common examples. Ask any product vendor for their current list.
The phone is only part of it. If your team is also buried in recalls, reminders, results follow-up or reporting, one system that does all of it will return more time than a phone product alone.
You have more than one site, or your own way of working. Different booking rules per site, per doctor or per appointment type are where products run out of settings.
The questions that decide it
Ask both kinds of vendor the same things, and compare the answers.
Does it work with our practice software, on our version? And does a booking land in the appointment book without re-keying?
What does it do when a patient describes a symptom? Both should hand over to a person and point emergencies to triple zero. Neither should give clinical advice.
Where are calls and transcripts stored? Get it in writing.
Can we review every call? If you cannot hear what it told your patients, you cannot stand behind it.
What does it cost at our call volume, in our busiest month? Compare like with like.
What happens if we stop? Ask about contract terms, and who keeps the data.
How we build them
We build AI receptionists for Australian medical practices, specialist groups and pathology, around the software each one already runs. Every conversation is logged and reviewable, the system and its records are hosted in Sydney, and it never gives clinical advice.
If you are weighing a product against a build, tell us what you run and where the pressure is. If a product is the better answer for you, we will say so. Read more on what an AI receptionist costs, or see the AI receptionist we build.
Not sure which one fits your practice?
Tell us your practice type, your software and where the pressure is. If a ready-made product is the better answer, we will tell you.