Twenty-Six Questions Every Practice Should Ask
Healthcare software demos are polished, and healthcare buyers are busy. These are the questions that surface the constraints that will matter in month three, integration depth, clinical boundaries, accessibility, and what happens when you want to leave.
Ticks save in this browser, so you can run the same list past two or three vendors and compare like with like rather than from memory.
Vendor Evaluation Checklist
Twenty-six questions. Get the answers in writing.
Your ticks are saved in this browser, so you can work through the list over several sessions.
01Integration with your systems
0/6The section that determines how much work actually disappears.
02Clinical safety and boundaries
0/6The right answer is recognise and escalate, never answer.
03Accessibility and patient experience
0/6The patients who struggle most often need you most.
04Data handling
0/4Short form, run the full privacy checklist alongside this.
05Pricing and commercial terms
0/4A total number at your real volume, not a starting price.
06Support, reliability and exit
0/4What happens when it breaks, and what you keep.
General procurement guidance for Australian healthcare practices. It is not legal, clinical or regulatory advice. Where a product may influence clinical decision-making, seek specific advice on any applicable regulatory obligations.
What Separates Vendors
Most vendors selling into Australian practices can demonstrate a convincing booking flow. The differences that actually matter emerge in three places that never come up unless you raise them.
Integration depth, not integration claims
Almost every vendor claims to integrate with the major Australian practice management systems. Far fewer read live availability and write a confirmed booking. The rest send a notification and leave your reception to type it in, which saves considerably less than it appears to.
Where they draw the clinical line
Ask what the system does when a patient describes a symptom. A good vendor has thought hard about this and will describe a clear boundary and escalation. A vendor who treats it as an edge case has not deployed into enough real practices.
How they handle vulnerable patients
Elderly patients, patients needing an interpreter, patients in distress and patients with hearing difficulty are a substantial share of most practice populations. Ask specifically. The answer tells you whether the product was designed for healthcare or adapted to it.
The Six Sections
Twenty-six questions grouped so each section can be handed to whoever in the practice is best placed to judge the answer.
Integration with your systems
Whether it genuinely reads and writes to the practice management software you actually run, at the version you run.
Clinical safety and boundaries
What it does with clinical questions, urgent presentations and distressed callers.
Accessibility and patient experience
How it performs with the patients most likely to struggle, who are often those with the greatest need.
Data handling
The privacy questions in short form. The full version sits in the dedicated privacy checklist.
Pricing and commercial terms
What it costs at your real volume, and what changes cost once you are live.
Support, reliability and exit
What happens when it breaks, and what you keep if you leave.
The Answers That Should Give You Pause
None of these are automatically disqualifying, but each one predicts a specific kind of friction later.
"We integrate with all the major systems"
A general claim without specifics usually means a webhook or an email. Push for the precise mechanism with your software, at your version, and ask to watch a booking created in your own system during the demo rather than in their sandbox.
- Ask which specific systems and versions are supported in production today
- Ask whether it reads live availability or only submits a request
- Ask to see a booking created in your own system, live
- Ask how existing patients are matched to avoid duplicate records
"It handles clinical questions intelligently"
This is the wrong answer. You want a system that recognises clinical questions and hands them to a person, not one that answers them well. Any vendor presenting clinical capability as a feature in an administrative product deserves careful scrutiny.
- The right answer is recognise and escalate, never answer
- Ask what specifically triggers escalation, and how it was tested
- Ask what happens outside business hours when no clinician is available
- Ask whether the boundary is configurable by you, and who can change it
"Pricing depends on your requirements"
Reasonable as an opening position, unacceptable as a final one. Before comparing vendors you need a total monthly figure at your actual volume, including overages. Practices with seasonal variation should also model a peak month.
- Insist on a total monthly cost at your real call and appointment volume
- Ask what a busy month costs, not an average one
- Ask what a configuration change costs after go-live
- Ask what happens to pricing at renewal, and the notice given
"Everything is included in the managed service"
Convenient framing that often means you own nothing. If the configuration, call flows and captured data live entirely in the vendor’s environment, leaving means starting again. Establish ownership before signing, not at renewal.
- Ask whether you can export call records, transcripts and captured contacts
- Ask what documentation you receive at handover
- Ask what happens to your configuration if you terminate
- Ask about minimum term, notice period and early exit cost
Next Steps
Healthcare AI Privacy Checklist
The fuller privacy and governance assessment to run alongside these questions.
Open the checklist →Practice AI Savings Calculator
Once you have real quotes, check the numbers actually justify the change.
Run the numbers →How to Choose Healthcare AI Software
The longer written guide to running a fair evaluation and trial.
Read the guide →Frequently Asked Questions
How many vendors should a practice evaluate?
Three is usually right. One gives you no sense of what is normal in the market, and beyond three or four the evaluation becomes a project that competes with running the practice and tends to stall. Run the identical twenty-six questions past each vendor, insist on hearing real call recordings from each, and record the answers in writing. The meaningful differences almost always appear in the integration and clinical safety sections rather than in the feature lists, which look nearly identical across the market.
Should we run a trial before committing?
Yes, and design it deliberately. A useful trial routes a genuine slice of real traffic, after-hours calls are ideal, since those currently go to voicemail and the downside is close to zero, for at least two to four weeks. That exposes the system to real patients with real accents, real urgency and real questions. Agree in advance what success looks like in numbers: proportion of calls handled without escalation, booking accuracy, and the number of times a patient asked for a person. A trial judged on impression rather than measurement tends to reward the smoothest salesperson.
What should we ask about accessibility specifically?
Ask how the system performs with elderly callers who speak slowly or pause frequently, with patients whose first language is not English, with patients using hearing aids or a speech-to-text relay service, and with patients who become confused partway through. Ask what happens when someone simply does not respond. These groups are a substantial share of most practice populations and frequently have the greatest clinical need, so a system that handles them poorly creates an equity problem rather than merely an inconvenience. A vendor with real healthcare deployments will have specific answers; one adapting a generic product usually will not.
Is a healthcare-specific vendor better than a general one?
Usually, though not automatically. Healthcare-specific vendors tend to have thought properly about clinical boundaries, practice management integration, recall workflows and the patient populations discussed above, and they generally understand Australian privacy expectations around health information. General vendors are sometimes cheaper and more capable technically, but frequently require you to specify the healthcare-specific safeguards yourself. If you evaluate a general vendor, weight the clinical safety and accessibility sections of this list heavily, and be prepared to define the boundary rather than assuming they have.
What contract term should we accept?
Twelve months or less is prudent in a market changing this quickly. The capability difference between what is available now and in a year is substantial, and locking in multi-year terms for a modest discount trades flexibility you will probably want for savings you probably will not notice. Pay attention to the notice period as well as the term: a twelve-month agreement with a six-month notice requirement is effectively an eighteen-month commitment. If a vendor will only discount meaningfully on a long term, that often signals concern about retention.
Who in the practice should be involved in the decision?
At minimum the practice manager, one clinician and one reception staff member, and each brings something the others cannot. Reception knows which calls are routine and which need a person, and their input produces materially better configuration. Clinicians need to own the clinical boundary, because it is their professional obligations that are engaged when it is drawn wrongly. The practice manager owns the commercial and operational assessment. Decisions made by one person in isolation tend to miss one of these three perspectives, and the gap usually shows up after go-live.
Ask Us All Twenty-Six
We would rather answer the difficult questions in writing before you commit than have a practice discover the answers once patients are already interacting with the system.