Key takeaways
- Overflow is the calls your normal team cannot answer in time: peaks, sickness, training and short closures.
- Four broad options exist: flexing your own staff, a buddy practice or PCN hub, an answering bureau, and automated overflow.
- Phone access has been improving nationally, so long waits now stand out more to patients[1].
- Any outside handler processes health data for you, so you need a processor contract that meets UK GDPR Article 28[2][3].
- A sensible pattern is to combine two options: one for daily peaks and one for exceptional days.
What overflow means for a practice
Overflow is not the same as out-of-hours. It is the calls that arrive while the practice is open but cannot be answered quickly enough by the people on shift: the Monday 8am peak, the day two receptionists are off sick, the training afternoon, the hour after a clinical system outage. In a dental practice or private clinic, it is often the lunch hour or the moment the front desk gets busy with patients in the building.
Getting overflow right matters because patients' expectations have moved. In the GP Patient Survey, the share of patients who said it was easy to contact their practice by phone rose from 49.7% in 2024 to 52.9% in 2025 and 56.9% in 2026[1]. As the typical experience improves, the bad days stand out more.
Source: Ipsos (GP Patient Survey provider for NHS England), 2026[1]
Show the data
| Period | Value |
|---|---|
| 2024 | 49.7% |
| 2025 | 52.9% |
| 2026 | 56.9% |
Option 1: flex your own team
The first and often cheapest overflow is your own staff. Cloud phone systems let anyone with a log-in join the queue, so administrators, secretaries and the practice manager can take calls at the peak or when the queue passes a set length. Some practices let trained staff log in from home for the first hour.
- Strengths: staff know the practice, the patients and the clinical system; no new contract or data sharing.
- Weaknesses: it pulls people from other work, which then builds up; it does not help when the whole team is short.
- Cost: the time of people already employed. The National Careers Service puts typical receptionist pay at £21,000 to £25,000 a year[4], so an hour of a trained colleague's time is usually the least expensive cover available.
- Best for: daily peaks of predictable size.
Make the trigger automatic rather than a judgement call. For example, when more than eight callers are waiting, the phone system alerts the admin team, and two named people log in until the queue drops below four. Agree in advance which tasks can pause, such as scanning or coding, and which cannot, such as urgent referrals. Without a clear rule, flexing tends to rely on the same willing person every time.
Option 2: a buddy practice or PCN hub
Practices in the same PCN, especially if they share a phone platform, can answer each other's overflow calls. NHS England's access recovery plan describes Leeds practices on a shared cloud system supporting each other when one is under pressure or short-staffed[5]. Some PCNs go further and run a shared hub team for overflow and online requests.
- Strengths: staff with NHS primary care experience; often able to view the shared record or book into shared clinics.
- Weaknesses: needs a data sharing agreement, shared scripts and trust between practices; the buddy may be busy at exactly the same time.
- Best for: training afternoons, sickness and short closures, where one practice can help another at a quieter moment.
Option 3: a medical answering bureau
Answering bureaux take calls on the practice's behalf, usually following scripts the practice provides, and pass messages back. Some specialise in healthcare and offer staff trained in confidentiality and escalation.
- Strengths: scale; can absorb large peaks and cover whole closures; useful for dental and private clinics that cannot afford to miss new enquiries.
- Weaknesses: bureau staff do not know your patients; access to the clinical record is usually not appropriate; quality depends heavily on scripts and supervision.
- Data protection: the bureau is a processor of special category data, so the contract must meet Article 28[3].
- Best for: practices whose overflow is large, unpredictable or concentrated in times when no colleague can help.
Option 4: automated overflow
Automated overflow ranges from simple call-back, which holds the caller's place, to recorded information lines and AI tools that answer common questions. It does not replace people for patient matters, but it can stop routine questions from occupying the queue at the worst moments.
- Call-back: keeps the caller's place and reduces redialling. It shifts work later rather than removing it.
- Information options: opening times, how to order prescriptions or send forms, recorded once and kept current.
- AI Employee: an AI Employee such as Ava answers practice questions in approved wording, explains how to get help, signposts urgent care and passes anything about a patient to reception.
- Best for: peaks where many calls are routine questions, and quiet hours when a person is not always available.
Side-by-side comparison
| Factor | Own team | Buddy or hub | Bureau | Automated |
|---|---|---|---|---|
| Set-up time | Days | Weeks | Weeks | Days to weeks |
| Knows your patients | Yes | Partly | No | No |
| Record access | Yes | Sometimes | Rarely | No |
| Absorbs large peaks | Limited | Limited | Yes | Yes, for routine calls |
| Data protection paperwork | None new | Data sharing agreement | Processor contract | Processor contract |
| Main risk | Other work builds up | Both busy at once | Script gaps | Callers with complex needs |
Choosing in five steps
Measure the overflow
From your call reports, find when waits exceed your target and how many calls arrive in those periods. Separate daily peaks from exceptional days.
Decide what the overflow handler may do
Take messages only, answer practice information, book into specific slots, or triage? Write it down. The narrower the role, the simpler the contract.
Match options to the two kinds of overflow
Daily peaks usually suit your own team plus automated options. Exceptional days often need a buddy, hub or bureau.
Contract and script
Agree processor or data sharing terms, scripts, escalation rules and how messages come back, before the first call.
Test and review
Make test calls, listen to recordings in the first fortnight and review waits and complaints monthly.
Questions to ask any overflow provider
- How quickly do you answer overflow calls at 8am on a Monday, and can you show us last month's figures for a similar client?
- Who writes the scripts, how often are they reviewed, and how quickly can we change them on a busy day?
- What happens when a caller describes something urgent? Show us the escalation route and how you confirm the practice has received it.
- How do messages reach us, and how do we know none has been lost?
- Where are recordings and messages stored, for how long, and who can access them?
- Can we listen to a sample of our calls each month?
- What happens if your service is down? Do calls fall back to our own queue or to voicemail?
- How much notice do we need to give to change hours, add a closure or end the arrangement?
Ask the same questions of a buddy practice or PCN hub, adapted to an informal arrangement. The answers do not need a formal contract between practices in the same PCN, but they do need to be written down and agreed by both practice managers, so the arrangement survives staff changes.
Data protection essentials
Calls to any practice routinely include information about health, which UK GDPR treats as special category data[2]. Once an outside organisation answers your calls, it processes that data on your behalf. Article 28 requires a contract that, among other things, limits processing to your documented instructions, binds staff to confidentiality, requires appropriate security, controls sub-processors and requires data to be deleted or returned at the end[3].
- Ask where call recordings and messages are stored and for how long.
- Ask who can see patient details and whether access is logged.
- Check how messages reach you: secure email, the clinical system task list, or a portal. Avoid unencrypted email for health details.
- Read the Caldicott Principles against the proposed arrangement, particularly using the minimum necessary information[6].
- Update your privacy notice to say who may answer calls.
Example: combining two options
Example: a fictional mixed dental practice found that most of its missed calls fell between 12.30 and 14.00 and in the hour after opening. It moved to staggered lunches, added a call-back option and set up an AI-assisted information line for opening times and booking questions. For the two training afternoons each year, it agreed cover with a sister practice. Missed new patient enquiries fell, and the team stopped dreading Monday mornings.
For related decisions, see outsourced medical receptionists, covering lunchtime closures and out-of-hours messages. If staff are taking overflow from home, read remote reception working.
Frequently asked questions
Can an answering service book GP appointments?
Only if the practice gives it access to the appointment system and a clear protocol. Many practices limit outside services to taking messages and answering practice information, which keeps the contract and data flows simpler.
Do we need a DPIA for overflow answering?
For an outside service handling health information, a Data Protection Impact Assessment is the sensible default. It also helps you think through scripts, escalation and retention.
Will patients mind if someone else answers?
Tell patients in advance on the website and in the queue message. Most care far more about getting through and about their message reaching the practice than about who answered.
What should overflow handlers do with urgent calls?
Follow a written escalation rule: pass urgent calls straight to the practice's duty clinician, and direct emergencies to 999. Test the escalation route before go-live.
References
Ipsos (GP Patient Survey provider for NHS England) (2026). 2026 GP Patient Survey results released (opens in a new tab) ↑
legislation.gov.uk (The National Archives) (2026). UK GDPR Article 9: Processing of special categories of personal data (opens in a new tab) ↑
legislation.gov.uk (The National Archives) (2016). UK GDPR Article 28: Processor (opens in a new tab) ↑
National Careers Service (GOV.UK) (2026). Receptionist job profile (opens in a new tab) ↑
NHS England and DHSC (2023). Delivery plan for recovering access to primary care (opens in a new tab) ↑
GOV.UK (National Data Guardian) (2026). The Caldicott Principles (opens in a new tab) ↑