Accessible GP telephone reception should account for people who need more time to explain a request or understand the next step. Speed can be useful, but an interaction that ends quickly is not necessarily an interaction that worked. Review the person’s opportunity to speak, correct information and obtain help.
People may need more time for different reasons. Avoid assuming that age, a language preference or a particular condition tells you exactly how someone wants to communicate. Ask about the person’s needs through the practice’s established process and evaluate the service against the support actually required.
In an agreed fictional walkthrough, allow the caller to pause, ask for a question to be repeated or correct an administrative detail. Observe whether they can understand what is being asked and whether the eventual request reflects what they intended.
Do not turn this into a contest over a universal response-time threshold. A useful pace depends on the task and the person. Record what happened at the point of uncertainty and how the interaction recovered, rather than assigning a quality judgement from duration alone.
Ask the observer to describe the final next step in their own words. If they cannot tell whether an action happened or a request is awaiting staff attention, the closing explanation needs review.
The practice should be able to explain how a person asks for human help, where that request goes and what happens if the intended member of staff is unavailable. These arrangements need to reflect the actual service, including its operating hours.
Keep alternatives visible in the practice’s wider information. An online route may help some people while creating a barrier for others. Do not assume that directing everyone to a website resolves a difficult telephone interaction.
NHS England’s Accessible Information Standard addresses information and communication support for people with disabilities, impairments or sensory loss. Use the current official guidance and your local arrangements when reviewing those needs; a product demonstration is not a compliance assessment.
Keep observations from different tasks separate. One clear interaction cannot represent every person who may use the service. If a problem appears, identify the specific change and repeat that part of the walkthrough after it has been addressed.
EMMA supports 19 languages signed off through QuantumLoopAI’s Clinical Safety Officer process. This capability can be relevant to a practice’s language-access discussion, but it does not establish that all communication needs are met. The language-access article explores that wider context.
EMMA is the AI receptionist for NHS GP surgeries, operating during surgery hours. It does not provide medical advice or clinical triage. Current product information should be considered alongside the practice’s agreed human-help and communication-support arrangements.
Request an EMMA demonstration to explore an administrative task and the points where a caller may need more time or help. Use fictional information and avoid sharing a patient’s medical or identifying details in an initial enquiry.