A busy phone is not proof that a pharmacy needs more handsets. It may reveal a poor call route, repeated status enquiries, unclear service information, calls arriving at the wrong branch or work that could be completed safely through another channel.
A pharmacy phone system should be chosen around those real journeys. The technology then supports a defined operating model: which calls need a person, which need the pharmacist, which can use a recorded message or callback, how confidential conversations are protected, and how the pharmacy keeps essential contact available during an outage.
What should a pharmacy phone system do?
It should help callers reach the right response without creating unsafe delay or unnecessary interruption inside the pharmacy. That means clear call routing, usable queues and callbacks, dependable branch transfers, appropriate recording controls, useful reporting, secure administration and a tested plan for broadband, power or supplier failure.
Map the calls before the features
Start with a short call study rather than a product demonstration. For at least a representative week, record call reason, time, branch, destination, outcome and whether the caller had to try again. Do not capture clinical detail in a general spreadsheet. Broad categories are enough to expose the operating pattern.
A community pharmacy may receive calls about prescription readiness, stock availability, opening hours, NHS services, private appointments, deliveries, online orders, complaints, care homes, prescribers and requests to speak to the pharmacist. They do not all need the same path or response time.
- Routine information: opening times, location, service availability and booking links may be answered through a short recorded message or a maintained website.
- Transactional enquiries: appointment changes, order status and delivery queries may need a trained team member with access to the relevant system.
- Professional calls: prescribers, care settings and other healthcare professionals may require a separate route that does not sit behind a public marketing queue.
- Clinical conversations: the system should support an appropriate private handover, not encourage a caller to describe sensitive information to the first person who answers.
- Urgent or emergency needs: messages must not imply that a pharmacy line is an emergency service. Signposting should be accurate and locally reviewed.
Link the findings to the website and booking journey. If half the calls ask whether a service is available, the answer may be clearer public information rather than a larger queue. Our pharmacy booking-system guide explains how availability, confirmation and assisted support need to work together.
Design a pharmacy call flow
Draw the desired call flow on one page. Begin with opening hours and the phone numbers people already use. Then show the smallest number of choices that reliably separate different needs. A long menu can look sophisticated while making an anxious caller listen repeatedly or select the closest-sounding option.
Interactive voice response, usually shortened to IVR, lets a caller choose an option using their keypad or voice. Use it to make a useful distinction, not to hide the pharmacy. Test every menu with people who did not design it, including callers using a mobile in a noisy place and people who need more time to understand the options.
| Call-flow decision | Evidence to define it | Failure to test |
|---|---|---|
| Opening message | Top call reasons, current services and genuine out-of-hours route | Stale information sends callers to a service or branch that cannot help |
| Queue and callback | Peak volume, staffing pattern, average handling time and abandonment | A callback promise creates another unmanaged work queue |
| Branch routing | Number ownership, shared services, local capacity and overflow rules | Calls bounce between teams with no accountable destination |
| Private handover | Which roles can handle which information and where conversations occur | Sensitive information is repeated or overheard |
| Automation or AI | Approved scope, information source, escalation, monitoring and fallback | The system gives an unverified answer or blocks access to a person |
If a system offers transcription, automated summaries or an AI receptionist, treat that as a separate data and service decision. Define what the tool may answer, which source it uses, how uncertain requests reach a person, where recordings or transcripts are stored and how the team detects a wrong response. A fluent demonstration is not evidence that the tool is safe for every pharmacy call.
Keep the call route consistent with the pharmacy's wider communication model. The document ownership and access controls in our pharmacy intranet guide are relevant when branches need one approved source for opening information, scripts and escalation contacts.
Compare systems and suppliers
Give shortlisted suppliers the same call map and failure scenarios. Ask them to demonstrate the proposed configuration rather than a generic feature tour. The useful question is not whether the platform has queues, dashboards or artificial intelligence; it is whether those capabilities work with the pharmacy's numbers, people, broadband, systems and responsibilities.
- Number ownership and porting: establish who controls each number, what a transfer requires and how service is protected during a move.
- Commercial model: separate licences, handsets, call charges, installation, porting, support, storage, recording and optional AI costs.
- Administration: test how authorised users change hours, messages, routing, users and branches, and how those changes are logged.
- Integrations: verify booking, CRM or helpdesk connections using real scenarios and controlled test data. “Compatible” is not the same as implemented.
- Support: define service hours, severity levels, response targets, escalation and what the pharmacy can do while waiting.
- Exit: document number portability, recording export, configuration handover, data deletion and contractual notice.
Cloud telephony makes the internet connection, identity controls and supplier platform part of the phone service. Include the provider in the third-party review described in our pharmacy cybersecurity guide. Use named accounts, multi-factor authentication where available, limited administrator rights and prompt removal when staff or suppliers change.
Community Pharmacy England's IT supplier directory makes an important general point: inclusion is not endorsement. A supplier list can help discovery, but the pharmacy still needs its own assurance and selection evidence.
Protect privacy and recordings
Calls can contain names, contact details and information about health or medicines. The GPhC standards for registered pharmacies make pharmacy owners accountable for safe services and for keeping information secure. That responsibility still applies when a telecommunications or AI supplier processes the call.
Do not switch on recording simply because it is included. Define the purpose, lawful basis, access, retention, security, disclosure and deletion route. The ICO's guidance on monitoring telephone calls says routine recording of content is not usually proportionate in every case. It also explains the need to inform workers and callers about recording and its purpose.
Decide whether the purpose can be met with less data: call counts, time to answer, queue abandonment and selected quality reviews may answer an operational question without retaining every conversation. Where recording is justified, pause or exclude payment details and other material that should not enter the recording. Test subject-access, deletion and incident processes before live use.
Plan for digital-line failure
UK landlines are moving from the old public switched telephone network to digital services delivered over broadband. Ofcom's current digital-landline guidance says BT plans to retire the old Openreach network by 31 January 2027. It also notes that a digital line needs mains electricity and may not work in a power cut without backup.
A pharmacy should therefore test failure, not just normal calling. List the dependencies: router, local network, handset, power, supplier platform, number routing, mobile signal and staff access to the administration portal. Then agree what happens when each one is unavailable.
- Simulate loss of broadband during a busy period and confirm where new calls go.
- Turn off power to the local phone equipment in a controlled test and check the fallback route.
- Verify that the fallback device and mobile network work from the actual premises.
- Confirm who can change routing if the usual administrator is absent.
- Keep supplier support and emergency configuration instructions available outside the failed system.
- Record the test, defects, owner and retest date in the pharmacy's business-continuity process.
Do not assume a battery unit, mobile app or automatic diversion solves every case. Capacity, signal, device charging, login access and caller identification can all change during fallback. Connect material dependencies to the pharmacy's risk assessment.
Measure whether the system helps
Agree a small baseline before installation: calls offered, answered, abandoned, transferred and returned; peak periods; common reasons; and staff time spent resolving repeat enquiries. After launch, compare those measures with patient feedback, complaints, booking completion and the team's experience.
Do not chase the shortest call. A clinical or safeguarding conversation may appropriately take time. Look instead for calls reaching the right role, fewer avoidable transfers, reliable callbacks and less repeated work. Keep personal and clinical details out of a general analytics dashboard.
Review the data through the decision discipline in our pharmacy data analytics guide. If the queue improves but unanswered calls move into an unmanaged inbox, the system has moved the problem rather than solved it.
Pharmacy Mentor helps independent pharmacy owners connect patient journeys, websites, bookings, systems and operational change. Explore our pharmacy business strategy support or talk to the team about your digital operating model.
Saam Ali
Founder & CEO, Pharmacy Mentor · MRPharmSSaam Ali is a pharmacist, digital strategist and the founder of Pharmacy Mentor. He has worked across community pharmacy, healthcare marketing and digital product development since 2012, helping independent pharmacies build modern online services and reach more patients.