AI Receptionist for GP Surgeries in the UK: What It Can Safely Do in 2026

Why GP Practices Are Asking About AI Receptionists

Anyone who has tried to ring a GP surgery at 8am knows why practices are asking about an AI receptionist: the lines open, a large number of patients dial at once, most hear an engaged tone or sit in a queue, and by the time some get through the same-day slots are gone. Reception teams spend the first hour of every day absorbing that pressure. This is not a criticism of reception staff — it is a structural problem: demand arrives in a spike, and a handful of human lines cannot flatten it. NHS England has been pushing practices towards modern general practice access — cloud-based telephony, online consultation tools and care navigation so patients reach the right service first time — and many practices have now moved to cloud telephony as part of that programme, which is what makes an AI receptionist technically possible.

An AI receptionist, in this context, is a voice agent that sits on the practice phone line, answers every call immediately, deals with routine requests itself and hands the rest to a human with the details already captured. This guide covers what it can safely do, what it must never do, the governance to confirm, what drives the cost of a build, and how to run a low-risk pilot.

What an AI Receptionist Can Safely Do in a GP Practice

The safe scope for a GP surgery is narrower than for a private clinic or dental practice, because a general practice handles undifferentiated demand from a whole population. Within that scope, the following tasks are realistic today.

Answering and queueing calls. Every call is picked up on the first ring; callers who need a human are queued with an honest wait estimate and the option of a callback.

Appointment booking, rescheduling and cancellation. Where an integration with the clinical system exists, the agent can offer appointment types the practice has pre-approved for self-booking — nurse appointments, blood tests, vaccinations, long-term condition reviews — and book, move or cancel them. Cancellations alone are worth having: many wasted slots are ones the patient meant to cancel but could not get through to do so.

Repeat prescription requests. The agent captures the patient's identifiers and the medication requested, reads it back for confirmation, and passes the request into the practice workflow for approval. It issues nothing itself.

Test result notifications. With the practice's approval, the agent can tell a patient a result is back and normal, or that they should book a follow-up, using exactly the wording the practice specifies. It never interprets results.

Signposting per protocol. Community pharmacy, NHS 111 out of hours, the urgent treatment centre, or self-referral physiotherapy — following the practice's own care navigation rules rather than inventing its own.

Callbacks and messages. Where a request needs a human, the agent records the reason, a preferred number and a good time, and creates a task in the right queue so calls are returned in order.

What It Must Never Do

Two lines must not be crossed.

• •It must never triage clinical urgency using its own judgement. If a caller mentions chest pain, breathing difficulty, a very unwell child, or any red-flag phrase the practice defines, the agent follows the practice's protocol — usually advising a 999 call or transferring immediately to a human — and does not attempt to assess the situation.
• •It must never give medical advice: not whether a symptom is serious, whether a medication can be doubled, or whether an appointment is needed. It books, records, signposts and hands over.

Safety and Governance: What to Confirm Before You Start

Work through this with your practice manager, ICB and supplier. It is not legal advice, and expectations differ between ICBs. Two structural changes are worth knowing before you start. NHS England published the implementation detail for integrated care board mergers and boundary changes taking effect from 1 April 2026, with further changes due in April 2027, so confirm which ICB your practice now sits under before you ask anyone to approve anything. And under the NHS Modernisation Bill set out in the 2026 King's Speech, NHS England is to be abolished and its functions moved into the Department of Health and Social Care by March 2027, so check where a given piece of guidance sits at the time you read it rather than assuming the publisher is unchanged.

Care navigation protocols. The agent's behaviour should directly express the practice's existing care navigation protocol. If it is not written down, writing it down is the first job — it becomes the specification the AI follows.

Clinical safety (DCB0129 and DCB0160). Health IT deployed in the NHS is expected to be covered by a clinical safety case. DCB0129 is the standard the supplier follows when building the product; DCB0160 is the standard the practice or its ICB follows when deploying it. Both involve a named clinical safety officer, a hazard log and mitigations for each risk. NHS England has a national review of both standards under way, and its supporting information for that review says the revised standards need to reflect advances including artificial intelligence supporting clinical decisions and complex interconnected systems sharing data across organisations — which is precisely the category an AI receptionist falls into. Ask any supplier whether they hold a current DCB0129 safety case against the standard as it stands on the day you ask, and expect to work with your ICB on DCB0160.

DTAC and DSPT. The Digital Technology Assessment Criteria is the NHS baseline for digital health tools, covering clinical safety, data protection, security, interoperability and usability. NHS England published a refreshed DTAC form and guidance on 24 February 2026, shortening the form, de-duplicating it against the Data Security and Protection Toolkit and the pre-acquisition questionnaire, and confirming its scope as software-based digital health technologies aligned with NICE. The previous form was retired from 6 April 2026, so a supplier presenting a DTAC completed on the old form is presenting something that should no longer be in use — ask which version they submitted and when.

Suppliers handling NHS patient data are also expected to hold a current Data Security and Protection Toolkit submission. The toolkit has been moving onto the National Cyber Security Centre's Cyber Assessment Framework: NHS England Digital's guidance records the CAF-aligned toolkit reaching trusts, integrated care boards and commissioning support units in September 2024 and independent providers designated as operators of essential services in September 2025, with the 2025-26 toolkit published as version 8 aligned to CAF version 3.4 and a mandatory submission deadline of 30 June 2026. General practice has its own assertion and evidence set within the toolkit, so ask a supplier which organisation type they submitted as, at what level, and for which year. Many ICBs check DTAC and DSPT together before approving procurement.

UK GDPR and confidentiality. The practice remains the data controller. Confirm where call audio and transcripts are stored, whether the data stays in the UK, the retention period, how a patient can request deletion, and whether a data processing agreement and a DPIA are in place before go-live. Any language model providers the supplier relies on should be named as sub-processors.

Human override. At every point in every call a patient must be able to say "I want to speak to a person" and be transferred or queued for a callback, and reception staff need a simple way to switch the agent off. Callers with limited English, hearing or speech impairments, or anxiety need that human route offered early rather than buried.

Integration Notes: EMIS, SystmOne and Cloud Telephony

EMIS Web and SystmOne dominate English general practice, and both sit behind controlled interfaces. Booking and cancellation integration is normally achieved through the NHS IM1 Patient API rather than a direct database connection, reached by the supplier completing NHS England's IM1 information governance process. Ask a supplier plainly: is your booking integration with our clinical system live in another practice today, or a roadmap item? If not live, start with call handling, callbacks and prescription capture, and add booking once the integration is assured.

For cloud telephony, most practices on a hosted platform can use call forwarding, SIP trunks or a routing API, with the AI agent answering first and forwarding to the existing queue where a human is needed, keeping the practice's numbers, call recording and reporting intact. Confirm overflow and transfer rules can be changed without a support ticket.

What Drives the Cost of an AI Receptionist for a GP Practice

There is no single figure for a GP build, and any supplier who quotes one before understanding your practice is guessing. GP work sits at the higher end of voice agent pricing generally because of the governance work, clinical safety documentation and integrations involved, not the underlying technology.

What sits inside the setup work. Protocol capture and script design, the red-flag escalation flow, telephony and (where assured) clinical system integration, clinical safety documentation support, testing with the reception team, and go-live. The ongoing plan covers hosting, monitoring and call quality reviews, and call minutes are billed on usage — ask any supplier for a worked estimate against your own call numbers before comparing proposals.

NHS funding routes to ask about. Do not assume dedicated AI telephony funding is currently open. The ring-fenced digital telephony funding tied to the Primary Care Access Recovery Plan closed to new sign-ups in 2023 and ended in March 2025, and the 2026/27 GP contract has repurposed the old PCN-level Capacity and Access Payment towards funding additional GP sessions rather than telephony. Some ICBs still run their own local digital transformation or IT allocations, which change every financial year, so ask your ICB's digital or primary care team what is currently open before assuming a build will be subsidised. We cannot promise eligibility and neither should any supplier.

For a broader view of voice agent pricing outside healthcare, see /blog/ai-voice-agent-cost-uk.

Worked Example: Receptionist Hours Freed

Treat this as an estimate with stated assumptions, and substitute your own numbers. Take a single-site practice receiving roughly 3,000 inbound calls a month, of which roughly 40 per cent are routine — cancellations, prescription requests, result queries, signposting — and within the agent's approved scope, with the rest still reaching a human but with the reason for the call already captured. At an average of four minutes of receptionist time per routine call, that is roughly 80 hours of receptionist time a month freed up — close to half a full-time receptionist's hours, redirected to face-to-face patients, care navigation and the more involved calls.

The important measure is not what any individual role costs but hours moved from the phone queue to work that needs a person — most practices keep their team. Our guide at /blog/ai-phone-answering-vs-receptionist-cost-uk-2025 works through the wider comparison.

How to Run a 4-Week Pilot

A pilot lets the practice learn how the agent behaves with real patients while keeping risk contained.

Week 1: Protocol and scope. Agree the approved task list, red-flag phrases and escalation route, and confirm the data processing agreement, DPIA and clinical safety paperwork with the ICB.

Week 2: Build and internal testing. The reception team and a GP call the agent repeatedly, try to confuse it, and review the transcripts before anything goes live.

Week 3: Limited live traffic. Route overflow calls only, or a single line such as prescription requests, and review every transcript daily.

Week 4: Widen and measure. Extend to the 8am rush if the team is confident, compare call abandonment and queue times against the previous month, and decide whether to continue, adjust or stop.

How BigBerri Approaches AI Receptionists for GP Surgeries

We build voice agents for UK businesses and healthcare providers, and approach GP work with more caution than any other sector.

• •Protocol first. We begin with the practice's care navigation rules and build the agent to follow them, not the other way round.
• •Fixed-price build. A written scope and a single price covering design, integrations, safety documentation support, testing and go-live.
• •Human handoff by design. Every flow has an early, obvious route to a person, and reception can switch the agent off at any time.
• •UK data handling. Storage, retention and deletion agreed up front, in line with UK GDPR and practice policy.

We also build for private clinics and dental practices — see /industries/clinics, /industries/dental-practices and /services/ai-voice-agents.

Next Step

If your practice or PCN is weighing up an AI receptionist, book a free discovery call at /contact. We will talk through your call volumes, telephony and clinical systems, and give you a fixed quote and an honest view on whether a pilot is worth running.