Answering the Call: A Telephone Accessibility Audit for UK Service Teams

Telephone contact remains a vital service channel for many disabled customers, older people, people without reliable internet access and those who need to resolve an urgent issue quickly. Yet accessibility reviews often concentrate on websites, forms and apps while leaving the phone system untouched. In 2026, UK service teams should treat the telephone journey as part of the same public service experience, not as a separate operational matter.

At Enable UK, we see the phone channel as a practical inclusion issue. A customer may reach an organisation through a main switchboard, a department number, an out-of-hours line or a call-back request. Each of these entry points can either enable a confident conversation or create an avoidable barrier. The purpose of a telephone accessibility audit is to find those barriers before customers report them, and to turn the findings into clear service improvements.

Why the phone channel deserves a place in the audit plan

A telephone system is often the first human contact a disabled customer has with an organisation. An interactive voice response menu may be the first instruction they receive. A hold queue may be the first test of whether the organisation respects their time. A member of staff may be the first person who can confirm that an adjustment is available or explain what happens next.

Accessibility reviews that exclude the phone channel can therefore miss a significant part of the customer journey. The audit should consider customers who use relay services, textphones, hearing aids, captions, speech-to-text tools or British Sign Language interpreters. It should also consider customers who find long menus, fast speech, background music or repeated instructions difficult to follow. The aim is not to redesign the entire telephony estate at once, but to establish a repeatable method for checking whether the service works for the people who need it.

Map the journey before judging it

Begin by listing every public telephone number the organisation publishes. Include main numbers, department lines, out-of-hours numbers, voicemail routes, call-back options and numbers shown on campaign materials. Record who owns each number and where it is advertised. Inconsistency is common: a number may be current on one page and obsolete on another, or a specialist line may bypass the main accessibility route entirely.

Next, document the intended journey for a caller. What happens after the first greeting? Which options are offered? How long does the caller have to respond? Is there a route to a human being? What happens if the caller cannot speak or hear in the expected way? This map should be based on the actual system, not the process document. A short mystery-shopping exercise, carried out ethically and with the knowledge of the service manager, can reveal differences between the designed journey and the lived one.

IVR menus: clarity, time and escape routes

Interactive voice response menus are useful when they help callers reach the right team quickly. They become a barrier when they are deep, fast or inflexible. Check how many levels a caller must pass through before reaching a person. Listen to the pace of the recorded voice and confirm that essential information is not delivered only once. A repeat option and a clear route to an operator should be available without requiring the caller to guess.

Timing matters. If the system moves on before a caller has had time to process the options, the menu excludes people with cognitive fatigue, hearing difficulty or limited confidence with automated systems. Test the menu with a stopwatch and note where prompts feel rushed. Also check whether the same terminology is used consistently. A caller should not have to learn a new vocabulary at each level of the menu.

Hold, queues and call-back arrangements

Hold time is an accessibility issue when it is unpredictable or unexplained. Measure waiting times at peak and quieter periods, and note whether the system gives an expected wait. Where a call-back is offered, confirm that it works reliably and that it preserves the caller's place in the queue. A call-back that arrives without warning or from an unrecognised number may create a new barrier, so the organisation should explain what the caller should expect.

Background music, repeated messages and recorded apologies can add to the cognitive load of a call. Keep hold messaging calm, brief and informative. Where possible, offer alternatives such as a named contact, an email route or a scheduled call-back. The goal is not to remove all automation, but to ensure that automation does not become the only route.

Relay, text and alternative channels

UK organisations should confirm that staff know how to handle calls made through Relay UK, textphone or other assisted communication routes. Staff should allow extra time, avoid interrupting, and never assume that a silence means the caller has hung up. Published contact information should make alternative routes easy to find, including email, text-based contact and any British Sign Language video service the organisation provides.

It is not enough to publish a number. The number must work in practice, and the person who answers must understand the service being used. Include relay and text access in staff induction, refresher training and escalation guidance. A short reference sheet at the desk can be more useful than a policy that sits on an intranet page.

Scripts, staff confidence and escalation

Scripts should support clear conversation rather than force staff to rush. Review opening lines for jargon, check that staff can repeat information without sounding impatient, and confirm that they ask whether the caller needs any adjustment. Staff should know how to transfer a call without losing context, how to arrange a follow-up and how to reach a supervisor when a query cannot be resolved.

Escalation routes should be published and easy to explain. A disabled customer should not have to diagnose the organisation's phone system in order to complain about it. Capture accessibility feedback in the same way as other service feedback, and assign it to an owner. Where a recurring issue appears, such as repeated menu confusion or failed call-backs, treat it as a service design problem rather than a one-off customer error.

A short audit checklist

• List every public number, its owner and where it is published.
• Test the IVR menu with a timer and confirm repeat and operator escape routes.
• Measure hold times at peak and quiet periods, and check that call-back works.
• Confirm Relay UK, textphone and alternative contact routes are published and understood by staff.
• Review scripts for pace, jargon, repetition and adjustment questions.
• Test transfer and escalation to a human being, including out-of-hours arrangements.
• Ask disabled customers or trained testers to review the journey.
• Record actions, owners and dates for the next service review.

Turning findings into service review actions

A telephone accessibility audit should end with a small number of practical actions. Quick wins may include adding a repeat option to the menu, revising a script, publishing a relay contact route or training the front-line team. Medium-term work may involve changing call-back settings or reviewing queue messages. Longer-term decisions may affect procurement, so accessibility requirements should be written into contracts for telephony systems and contact-centre services.

Service teams should also agree how they will measure progress. Useful indicators include abandoned calls, successful call-backs, repeat calls about the same issue, accessibility complaints and feedback from disabled customers. Reviewing these measures alongside website and form accessibility data gives a more complete picture of the public service experience.

In 2026, inclusive service design should not stop at the screen. The phone system is part of the front door, and it deserves the same attention as any other channel. A focused audit, run before the next service review, can help UK organisations answer the call with confidence and clarity.