Making Voice Automation Work for People

Reviewed and updated 22 October 2026. Original publication date retained.

Design around the caller's task

A caller may want to find information, change an arrangement or reach the right team. Start with that task and the information needed to complete it. Keep the service's purpose clear and avoid asking the caller to follow an internal process they cannot see. The conversation should help them understand what can happen next.

Expect interruptions and missing information

People change their minds, speak in different ways and may not have every detail ready. Include these situations in the design and test cases. Agree how the service asks for clarification, confirms important details and handles an answer it cannot confidently interpret. The aim is a usable service, rather than a script that works only under ideal conditions.

Make handover part of the journey

Define when the call should move to a person and what context can be passed safely. Consider opening hours, unavailable teams and the information a colleague needs to continue. The caller should not be left guessing whether an action has completed. Verification and permissions should reflect the task and information involved.

Review the whole service

Voice quality is one part of the experience. Telephony, response time, integration behaviour, accessibility and support arrangements also affect whether the service works. Test common journeys and exceptions with representative callers or approved scenarios. Review results, feedback and supplier changes once the service is in use.

Start with a focused conversation

Choose a manageable task and a useful outcome for a first trial. Agree the checks and measures before extending the scope. Our voice and telephony, integration and software and ongoing oversight pages explain how design connects to operation.