Before you buy
an AI receptionist.

What is an AI receptionist for a clinic?

An AI receptionist is a voice or messaging system configured to handle approved front-desk tasks: collecting contact details, answering administrative questions, passing appointment requests to the team and, where a tested integration permits it, making bookings.

It should have a clear route to a person. For a clinic, administrative automation must be separated from clinical advice and decisions about treatment suitability.

What changes when you have several locations?

The system needs more than a general greeting. It must distinguish branches, services, opening hours and the right owner for each request. Start with a branch directory maintained by a named team member, and define what happens when the caller has no preferred location.

• Which branch offers the requested service?
• Which branch should receive an existing patient's administrative request?
• Can an enquiry move to another branch without starting again?
• Who receives a task when booking is unavailable or the integration fails?

Can it work with your existing booking system?

Possibly, but do not assume a supplier's integration logo proves the exact workflow you need. Ask it to demonstrate the complete journey in a test environment with your appointment types, practitioners and location rules.

Cliniko's official documentation supports multiple business locations and location-specific appointment calendars. Its API documentation exposes location and availability operations. Pabau describes multi-location management and lead pipelines. These capabilities are reasons to inspect your current system first; they do not establish that WebVortex or another supplier has completed an integration for your account.

Keep your practice management system as the authoritative booking record unless you deliberately agree otherwise. A separate lead inbox should not silently become a second appointment diary.

Five tests to request from a supplier

1. A caller asks for a service that only one branch offers.
2. Two callers request the same slot. Confirm how conflicts are prevented or reconciled.
3. An existing contact calls again. Confirm how staff see context without creating a duplicate.
4. The calendar connection fails. Confirm the enquiry becomes a visible task rather than a false booking confirmation.
5. The caller asks for a person or raises a clinical concern. Confirm the approved handoff works.

How much does a clinic AI receptionist cost?

Compare the total cost for your actual call volume and group structure. A low headline subscription can exclude configuration, usage, integrations or ongoing support. Ask for a written quote using the same assumptions for every provider.

A useful calculation is: total monthly operating cost = subscription + usage + messaging and phone charges + recurring support + retained staff time for exceptions. Keep one-off implementation costs separate, or spread them over a clearly stated comparison period. Do not count every captured call as additional revenue.

Should you replace reception staff?

A narrower pilot is often more informative: cover overflow or after-hours administrative enquiries while staff retain local relationships and exceptions. This is my recommended test approach, not a claim that one staffing model outperforms another in every clinic.

Measure staff effort as well as caller outcomes. If the system creates more correction work than it removes, improve the workflow before expanding it.

What should happen to clinical questions and patient information?

Agree the permitted scope with the clinic before launch. Clinical decisions, treatment suitability and urgent concerns need the clinic's approved human escalation process. Collect only the information needed for the administrative task and review recordings, access, retention, supplier terms and privacy information.

The ICO explains that privacy information should tell people how their personal data is used. Its AI transparency guidance is under review following changes in law, so check the latest guidance during implementation.

How do you know the pilot is working?

Agree the baseline, eligible enquiry definition and review period in advance. Compare the same process, not all business revenue before and after a new tool.

1. Record enquiries received by branch and channel.
2. Report automatic acknowledgement separately from a meaningful response.
3. Track correct assignment, successful contact, bookings and completed handoffs.
4. Record corrections, unresolved tasks, staff time and total costs.
5. Review the outcome with reception and branch managers before a rollout.

Some bookings would have happened anyway. Claims about incremental revenue need a comparison method and actual payment outcomes; a call count or booking count alone is insufficient.

A decision checklist for a 3–5-location group.

• One agreed branch directory and named process owner.
• A demonstrated booking or request workflow in the current system.
• Clear human handoff and integration-failure handling.
• A written cost breakdown with usage assumptions.
• A data-handling review and suitable privacy information.
• A measurable pilot with a review and exit route.

Sources and scope

This guide combines an operator's recommended buying checklist with first-party product documentation. It is not a completed comparative study or a claim of a specific live integration.

• Cliniko: adding a business location
• Cliniko: official API reference
• Pabau: multi-location management
• Pabau: lead management
• ICO: the right to be informed
• ICO: transparency in AI

Start with your enquiry process.

If you operate a UK clinic group with 3–5 locations, share how enquiries currently move between branches. We can discuss where a measured pilot would be useful.

Related: centralised or branch reception?