The practice phone rings while the doctor is with a patient and the receptionist is checking someone in at the counter. Nobody answers. The caller may try again, leave a request elsewhere or choose another practice; the proportions have to be measured rather than assumed. That is what pushes practices to ask whether an artificial intelligence system could answer the phone in place of a person.
The honest answer is: partly yes, and precisely where it matters most. But the line between what a virtual receptionist may do and what it must never do, in healthcare, is sharp and not up for negotiation. This article describes it plainly, because it is the only solid basis for a decision.
What a virtual receptionist is
A virtual receptionist may handle written enquiries, missed-call follow-up or, in a separately configured voice service, live calls. Those are different capabilities. A voice system can take a request, give approved information or offer a handover only when its phone routing, permissions and connections have been tested.
A chat widget, a missed-call message and a voice agent should be tested against their own scope. One working channel does not prove that another can answer a call, record an enquiry or update the diary.
None of these systems is indistinguishable from a person in a complex conversation: on straightforward requests they work well, with an anxious caller telling three stories at once much less so. The difference between a successful deployment and a disastrous one lies in the scope assigned to the system, not in the technology.
What it can do
The following are uses to evaluate for a voice service, rather than features guaranteed in every product. Test each one with the practice's phone routing and staff before relying on it.
- Answer out of hours. Evenings, the lunch break, weekends, public holidays: the use case with the clearest value, because today nobody picks those calls up at all.
- Answer when the line is busy. The second and third simultaneous caller hear an engaged tone.
- Take a request for an appointment. Name, contact details, the kind of appointment in general terms, rough availability. The front desk then calls back, or the system offers open slots if it is connected to the diary.
- Give fixed, verifiable information. Address, opening hours, how to reach the practice, what to bring, whether a referral is needed.
- Record cancellations. One received at nine in the evening lets the slot be reallocated the next morning.
- Route and leave a record. If logging and the CRM connection are configured, the system can create a logistical enquiry for reception. Test failures and missed handovers as well as successful calls.
The value sits here: requests that dissolve into nothing become written contacts somebody can work on.
Whether those contacts can also reach a CRM or the practice diary depends on the systems and permissions in use. Our guide to connecting AI, CRM and practice management software sets out the checks and the human hand-off.
What it must never do
This list matters more than the previous one, and it admits no exceptions "just for the simple cases".
No clinical triage. An automated system does not judge how serious a symptom is, does not decide whether a patient should be seen today or in a fortnight, and does not set clinical priorities. Triage is a professional act.
No medical advice. Nothing on medicines, doses, stopping a treatment, or interpreting symptoms or test results. Not even the "general" version, which is still advice.
No handling of emergencies. The system has to recognise signs of urgency and react in exactly one way: point immediately to the local emergency number and the correct channels. This is the first behaviour to test before it goes live, not the last.
Do not solicit clinical detail. Ask for the minimum information needed to route an enquiry. A caller may still volunteer health information, and an appointment category can reveal it too. Define what is transmitted, recorded and retained, and how reception handles those cases; a prompt alone does not prevent sensitive input.
No pretending. State clearly at the first contact that the person is interacting with an AI assistant. Article 50 requires disclosure for systems intended to interact directly with people, unless the AI interaction is obvious in context, with information no later than the first interaction. These transparency obligations apply from 2 August 2026. This disclosure is distinct from the lawful basis for processing personal data.
No total replacement of the front desk. There has to be a fast route to a person at all times, asked for by the patient or triggered when the conversation leaves the expected path. A system that cannot hand over is a wall.
Our Claudia AI service focuses on missed-call recovery, written logistical enquiries and a route to reception on channels agreed after analysis. A live voice agent or calendar connection is a separate capability to scope, configure and verify. It is not commercial caution, it is the condition under which a tool like this belongs in a practice at all.
Privacy and compliance: what to check
Map what each supplier does with the data. When it processes solely on the practice's instructions, a processor agreement under Article 28 is required; other purposes may create different roles. Check the actual arrangement rather than assigning a role from the product name. Before signing, these are the questions to ask.
- Where is the data processed and stored? Servers inside the European Union is the answer that makes life simpler. Where there are transfers outside the EU, the safeguards relied on have to be identified and documented.
- Are calls recorded? If so, the caller has to be told at the start, a legal basis defined and a retention period set. A structured record may reduce what is retained, but it still contains personal data. Confirm whether recordings or transcripts can actually be disabled or deleted in the selected service.
- Does the data feed the vendor's model training? The acceptable answer is no, and it belongs in the contract.
- Who can access the conversations, and what happens if the service goes down. Roles and access logs on one side; a fallback route on the other, because calls must land on a real number, not in a void.
The privacy notice and the record of processing activities have to be updated accordingly. Where the platform is hosted outside Europe, the questions to put to the vendor are covered in the article on GoHighLevel and GDPR in a European medical practice.
How to introduce it without causing damage
Switching the system on for every call from day one creates a rollout risk. A sensible rollout is gradual: out of hours only as one possible controlled pilot, after routing, privacy, human escalation and emergency instructions have passed their tests; then overflow, so the system answers only when the line is busy or after a set number of rings; then a selective widening, for instance logistical information at peak times.
Before each step, test by hand: call in and try the ordinary request, the confused one, the angry one and, above all, the urgent one. If the simulated emergency does not produce an immediate referral to the emergency number, the system does not go live.
Then decide what happens afterwards: who reviews the requests, within what time they are called back, where the contacts end up. A system that gathers twenty requests nobody returns produces twenty more disappointed patients than before. Collected requests belong in the same flow as every other channel, described in the article on patient communication across email, SMS and WhatsApp.
What it costs, and when it makes sense
Pricing is usually a subscription plus a usage component on minutes, with a setup cost on top. Figures vary widely and change constantly, so ask for them on the same parameters from at least two vendors: monthly fee, cost per minute, minutes included, what happens above the threshold, setup, contract term.
The sensible comparison is not "AI versus receptionist", which is a false choice, but the cost of the system against the value of the calls that currently go unanswered — a number to measure first, as described in the article on what a missed call really costs a medical practice. No serious vendor can promise how many extra patients will arrive.
Frequently asked questions
Can a virtual receptionist replace the receptionist?
No, and that is not the right goal. It covers the calls nobody picks up today and gives time back to the person for the work that needs judgement and presence.
Can it tell a patient whether a symptom is urgent?
No. Triage is a professional act and stays outside the scope. The system has to recognise signals of urgency and refer immediately to the emergency number, without assessing anything.
How do we know whether our practice needs one?
Start from real numbers: calls received, calls missed, and when they are lost. If you would like us to look at them with you, request an assessment with no commitment. If you would rather get a general picture first, there is the free guide to medical marketing.