Key takeaways
- The Advanced Telephony Better Purchasing Framework was the first national route; NHS England said it would be replaced by the DCS Cloud Telephony Framework[1].
- The 2023/24 GP contract required practices in England to use the nationally set framework when buying digital telephony[1].
- Score suppliers on access features, reporting, integration, data protection and support, and weight what your patients need most.
- Treat the processor contract as part of the evaluation: UK GDPR Article 28 sets out what it must contain[2].
- If a supplier offers AI transcription or summaries, ask the same assurance questions you would ask of any clinical-adjacent tool.
What the framework is, and what replaced it
When NHS England set out its plan to end the 8am rush in 2023, it told practices that the 2023/24 GP contract required them to use the nationally set cloud telephony framework when procuring digital telephony. That framework lists suppliers who can provide the functions needed for good patient access[1]. A footnote in the same plan explains that the original Advanced Telephony Better Purchasing Framework would be replaced by the DCS Cloud Telephony Framework later that year[1].
Many practice managers still call it the Better Purchasing Framework, and suppliers still use the phrase in sales material. What matters in practice is simple: buy from the current national framework, and confirm with your ICB's digital primary care team which version and which lots apply before you start. Frameworks are refreshed, suppliers join and leave, and funding rules can change between years.
Before you contact any supplier
- Speak to your ICB digital lead. Some ICBs run a joint call-off for several practices or a whole PCN, which can save you most of the paperwork.
- Ask your PCN what neighbouring practices use. NHS England recommends PCNs use the same provider, and some ICBs prefer whole areas to standardise[1].
- Write down your current contract end date, notice period and any early termination charges. These often decide the timetable.
- Pull three months of call data from your current system, even if it is basic. You need it to size the new one.
- Agree who signs off: usually the practice manager and one partner, with the Data Protection Officer reviewing the data sections.
Procurement in seven steps
Write a one-page requirement
Describe your sites, number of users, peak call volume, clinical system, and must-have features. Mark each requirement as essential or desirable. Suppliers respond better to a short, specific brief than to a long generic one.
Shortlist three suppliers from the framework
Use the framework list, your ICB's advice and references from practices of similar size. Three is enough to compare properly without the process dragging on.
Run scripted demonstrations
Give every supplier the same script: change a queue message, set a bank holiday closure, show a live wallboard, export last week's call records and show what a receptionist sees when a registered patient rings.
Take references from live practices
Ask for two practices of your size using the same clinical system. Ask them what went wrong at go-live and how long support took to fix it.
Score against your weighted matrix
Each person scores independently first, then compare. Large differences usually mean one person saw something the others missed.
Review the contract and data terms
Check term, exit rights, number porting, data location, retention defaults and the processor clauses before you choose, not after.
Plan go-live and the first review
Agree a go-live date away from Mondays and bank holidays, and book a review meeting with the supplier two weeks later.
A scoring matrix you can adapt
| Criterion | Weight | What a top score looks like |
|---|---|---|
| Patient access features | 25% | Queue position, wait time, call-back that works near closing time, no engaged tone |
| Reporting and data | 20% | Live wallboard, raw call record export, abandoned calls by half hour |
| Ease of use for staff | 15% | Messages and closures editable by the practice in minutes |
| Clinical system integration | 15% | Caller identified and record opened from the call, live today on your system |
| Data protection and security | 15% | UK data location, clear retention controls, logged access, signed processor terms |
| Support and implementation | 10% | Named contact, tested porting plan, training included |
Example: a fictional 8,500-patient practice scored three framework suppliers. Supplier A had the best price and features list but could not export raw call data. Supplier B scored highest on reporting and ease of use. The practice chose B because its main problem was understanding its 8am demand, which made reporting worth more than an extra feature it would rarely use.
Questions to ask every supplier
- Show me the call-back setting. What happens to call-backs still waiting when we close?
- Can we edit queue and closure messages ourselves, and how quickly do changes go live?
- Which reports are included as standard, and can we export the underlying call records?
- Which clinical systems do you integrate with today, and what exactly does the integration do?
- Where is call and recording data stored, who can access it, and is that access logged?
- What is the default recording retention period, and can we set our own?
- How do you handle a request from a patient for a copy of their call recording?
- What happens to our data and our number if we leave at the end of the term?
Data protection is part of the evaluation
Calls to a GP practice routinely contain information about health, which is special category data under Article 9 of UK GDPR[3]. The practice stays the controller; the supplier is a processor. Article 28 requires the controller to use only processors that give sufficient guarantees, and sets out what the contract must cover, including acting only on documented instructions, confidentiality of staff, security, sub-processors, help with patients' rights, and deleting or returning data at the end[2].
The stakes are not abstract. Serious UK GDPR infringements can attract fines of up to £17.5 million or 4% of worldwide annual turnover, whichever is higher[4]. More practically, a data problem with your phone system becomes a complaint and a breach report that someone in the practice must handle. Health and care organisations in England also follow the eight Caldicott Principles on confidential information, which are worth reading against each supplier's answers[5].
If the system includes AI features
Some suppliers now offer call transcription, automatic summaries or AI-assisted routing. These can save time, but GPs are cautious about AI tools, and their worries map neatly on to procurement questions. In a 2025 Nuffield Trust and RCGP survey, GPs who did not use AI most often cited professional liability, lack of regulatory oversight and patient privacy[6].
- Liability: who is responsible if a summary misses something important, and does the supplier claim the tool is suitable for clinical decisions?
- Oversight: is the feature covered by your processor contract, and has the supplier assessed whether it counts as a medical device?
- Privacy: is call audio used to train the supplier's models, and can you switch that off in writing?
An AI Employee such as Ava is a separate layer that answers practice questions and passes patient matters to reception, so ask any supplier, including us, the same questions about data, retention and escalation before you connect it.
What to write into the order form
Framework terms cover the basics, but the order form or call-off contract is where your practice's specific needs are fixed. Anything a supplier promised in the demonstration and that matters to you should appear here in plain words, because sales notes are not binding.
- The exact features you are buying, with call-back, queue position and wallboard named individually rather than as a bundle.
- Your recording retention period and the date by which the supplier will have configured it.
- Number porting dates, with a named fallback if porting is delayed.
- Training sessions included, how many staff, and whether recorded training is provided for new starters.
- Support hours that cover your opening hours, including the 8am peak, and a response time for a full outage.
- A review point after the first three months where configuration changes are made without extra charge.
Keep a copy of the signed order form with your DPIA and your information asset register, so that whoever handles the next renewal can see exactly what was agreed and why.
Red flags during procurement
- The demonstration is a slideshow rather than a live system.
- Integration is described as coming soon, with no date and no live reference site.
- The supplier cannot say where recordings are stored or who can access them.
- Message changes need a support ticket and a wait of several days.
- Exit terms make it hard to take your number and call records with you.
For a plainer view of what the features do day to day, see what cloud-based telephony does and our guide to call-back settings.
Frequently asked questions
Is the Better Purchasing Framework still the right route?
NHS England said the original Advanced Telephony Better Purchasing Framework would be replaced by the DCS Cloud Telephony Framework. Ask your ICB digital team which national framework and which version currently applies before you start.
Can a PCN buy one system for all its practices?
Yes, and NHS England recommends PCNs use the same provider. Each practice is still a data controller, so make sure the contract and data sharing arrangements reflect that.
How long does procurement usually take?
Plan for a couple of months from requirement to go-live, longer if number porting or several sites are involved. Your current contract's notice period is often the real constraint.
Do we need a Data Protection Impact Assessment?
For a system that records and stores calls containing health information, a DPIA is the sensible default. Ask the supplier for their standard DPIA support pack to speed it up.
References
NHS England and DHSC (2023). Delivery plan for recovering access to primary care (opens in a new tab) ↑
legislation.gov.uk (The National Archives) (2016). UK GDPR Article 28: Processor (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) (2026). UK GDPR Article 83: General conditions for imposing administrative fines (opens in a new tab) ↑
GOV.UK (National Data Guardian) (2026). The Caldicott Principles (opens in a new tab) ↑
Nuffield Trust (2025). How are GPs using AI? Insights from the front line (opens in a new tab) ↑