Voice agents: a consistent voice still needs a reliable human handover

Retrospective · week of 12 October 2026

A pleasant voice makes a good first impression. It does not resolve a misunderstood request or a failed transfer. For a small business, the welcome and routing process matter as much as the sound: callers should understand who they are speaking to, what the assistant can do and how to reach a person when necessary.

The announcement puts journey design back in focus

On 16 October, OpenAI announced voices generated from descriptions and new voices, including two French options. Source: official changelog.

Our recommendation is to treat voice as one part of the experience, not as proof of its quality. A consistent sound can support a brand, but evaluation should cover the complete journey. It should not depend on imitating a real person without their authorization. The operational design must still work when the conversation becomes less predictable.

Start with a clear introduction

The greeting should identify the assistant and explain its role in a few words. For example, it might help clarify a request before passing it to the team. Avoid wording that implies a human adviser has already taken ownership when that has not happened.

Also decide what information is necessary at this stage. Asking for a customer's entire history before discovering that the assistant cannot help creates avoidable friction. A short opening question followed by a targeted clarification is preferable to a long questionnaire delivered regardless of the answer.

Illustrative example: preparing a useful handover

Imagine a fictional call about changing an appointment. The demonstration scenario has the assistant identify the request, check only the necessary details and ask whether the caller wants to speak to the team. It does not announce an available slot without checking or claim a change has been made without confirmation from the relevant system.

The summary for the adviser contains the reason for calling, confirmed information, remaining uncertainty and actions actually completed. It distinguishes “change requested” from “appointment changed”. That difference prevents the adviser or customer from assuming an operation occurred when it was merely discussed.

This example describes a journey to test, not an already deployed service or a promise about SWM response times. Its purpose is to make the boundary between conversation and completed action visible.

Plan for transfers when nobody can answer

A transfer button or spoken phrase is not enough. Define the destination, actual opening hours and expected behaviour when no one is available. A callback offer must correspond to a real process with an assigned owner, not a promise improvised by the assistant.

The caller should know whether their request has merely been recorded or accepted by a person. If the transfer fails, the scenario should explain that plainly and offer an authorized next step. The conversation should not loop indefinitely through the same questions, leaving the caller unsure whether anything has happened.

Test difficult moments, with consent

Prepare a consented demonstration that includes background noise, an interruption, a corrected name, an unfinished sentence and an immediate request to speak to a person. Check that the assistant accepts corrections, stops an explanation that is no longer useful and acknowledges what it has not understood.

Before real use, define appropriate rules for disclosure, any recording, retention and access, and have applicable obligations checked. Prefer fictional data during acceptance testing. Measure successful transfers, repeated questions and information the adviser has to ask for again. These measures reveal whether the design actually helps the next person in the conversation.

The WhatsApp, Instagram and voice agents offering can therefore start from a concrete goal: a clear welcome and a prepared human handover, rather than a sound demonstration alone.

Let's build a voice welcome scenario that fits your customers and your team.