# How to design turn taking and interruptions in voice AI > Design voice AI speaking states, interruption behavior, and task continuity. A practical test matrix covers pauses, barge-in, tool delays, and returning to a task. - Canonical page: https://humbleteam.com/blog/voice-ai-product-ux-turn-taking - Last updated: 2026-11-09 Skip to main content [All articles](https://humbleteam.com/blog) - Other Updated November 9, 2026 5 min read Voice AI must show when it is listening, speaking, waiting, or completing work. This guide tests interruptions and whether the user’s task survives them. Daniel Mercer AI product and design workflows Share [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fhumbleteam.com%2Fblog%2Fvoice-ai-product-ux-turn-taking) [X](https://twitter.com/intent/tweet?url=https%3A%2F%2Fhumbleteam.com%2Fblog%2Fvoice-ai-product-ux-turn-taking&text=How%20to%20design%20turn%20taking%20and%20interruptions%20in%20voice%20AI) [Email](mailto:?subject=How%20to%20design%20turn%20taking%20and%20interruptions%20in%20voice%20AI&body=https%3A%2F%2Fhumbleteam.com%2Fblog%2Fvoice-ai-product-ux-turn-taking) Copy link A voice assistant should make it clear when it is listening, speaking, waiting, or doing work, and what happens when the user interrupts. Turn taking is part of the product task, not simply a speech setting. A natural-sounding voice can still leave someone unsure whether a request was heard or whether an action continued after they spoke over it. ElevenLabs documents configurable [interruption behavior for its agents](https://elevenlabs.io/docs/eleven-agents/customization/tools/tool-configuration/tool-interruptions), including allowing interruption by default and restricting it around particular tool calls. This is a product example of an available control, not a Humbleteam project or a rule every voice product should copy. ## Which speaking states should a user recognize? Map the task before choosing an animation or audio cue. A user needs to distinguish at least listening, processing, speaking, paused, and unable to continue. The exact set depends on the product. A tool call that changes a record may need an additional state that says the operation is still running after the assistant stops talking. Use concise spoken acknowledgments when they prevent uncertainty, and a visible state for users who can look at the screen. “I’m checking the order” can be appropriate when a lookup takes time; repeating filler during every short pause is distracting. For screenless use, test whether a tone or brief phrase communicates the state without being mistaken for a completed answer. Keep the visible transcript aligned with what was actually heard and said. If the assistant is cut off halfway through an explanation, a transcript that shows the unspoken remainder as delivered can mislead the user. The product should distinguish generated text from speech already played where that difference matters. ## When should the user be able to interrupt? Ordinary conversation often needs barge-in: the user corrects a name, changes direction, or says they have enough information. An interruption should stop or duck speech quickly, acknowledge the new input, and retain the task context needed to proceed. It should not silently treat a background sound as approval for an action. Some operations cannot safely stop mid-call. ElevenLabs’ documentation describes modes that suppress interruption during a tool call or through the following agent turn. The product team must decide when that restriction is justified and make the wait understandable. A user who says “stop” while an external operation runs needs an accurate outcome, not a comforting claim that nothing happened. Separate stopping speech from canceling work. The assistant can stop reading a long answer while a lookup continues, or it can request cancellation of an action. Those are different commands with different possible results. If an operation may already have completed, check its status before offering a retry. ## How should a pause differ from an abandoned task? Silence may mean the user is thinking, searching for a number, or finished. Avoid treating every pause as a command to continue. ElevenLabs also documents a [skip-turn tool](https://elevenlabs.io/docs/eleven-agents/customization/tools/system-tools/skip-turn) that lets an agent wait after a request such as “Give me a second.” That illustrates one way a product can respect an explicit pause. Define what the assistant keeps during that wait: the current intent, confirmed details, and unresolved questions. Give the user a clear way to resume. If a session expires, explain what was saved and what must be repeated. Do not promise continuity across devices or sessions unless the product actually preserves it. In an illustrative support flow, a customer asks about an order and pauses to find the order number. The assistant should wait without inventing an answer. When the customer returns, it should connect the number to the same support task, while confirming any detail whose scope may have changed. ## What should happen after an interruption? Resume from the user’s current goal, not from the start of a memorized script. If the user corrects the destination address while the assistant is reading a delivery estimate, update the address-dependent part of the task and make any recalculation explicit. If the new utterance begins a different task, confirm that switch when abandoning the first task would lose work. For tasks with external effects, show or speak a concise action recap before execution. The [AI agent action-flow guide](https://humbleteam.com/blog/ai-agent-ux-approval-undo-human-handoff) covers approval, partial completion, and recovery in detail. Voice adds the need to confirm that the recap was actually heard, especially after an interruption. ## What should a turn-taking test matrix include? Test on the devices and in the environments the product actually targets. Use task completion and user understanding as the measures. The following proposed matrix is illustrative: Proposed voice turn-taking test matrix Condition Expected behavior to inspect User interrupts a long answer Speech stops and the correction enters the same task. User says they need a moment The assistant waits and can resume without a new request. Background speech overlaps No accidental confirmation or task switch occurs. A tool call is delayed The state and stop options reflect what can actually stop. Connection drops after a request The returning user can discover what completed. Screen and spoken answer differ The product marks what was shown and what was heard. After each scenario, ask the participant what the system is doing and what will happen next. Tune the speech timing and state cues against those answers. For a broader [AI product experience](https://humbleteam.com/ai), the test is whether the person can finish the original task after conversation inevitably becomes untidy. ## Read next - [Fintech Other November 6, 2026 Selecting a product design agency for Dubai fintech and enterprise](https://humbleteam.com/blog/dubai-product-design-agency-guide) - [Other September 5, 2026 How should AI agents handle approval, undo, and human handoff?](https://humbleteam.com/blog/ai-agent-ux-approval-undo-human-handoff) - [Other Fintech Healthtech August 11, 2026 How to go from 0 to 1 in product design — and when a startup should bring in an agency](https://humbleteam.com/blog/how-to-go-from-0-to-1-in-product-design-and-when-a-startup-should-bring-in-an-agency) - [Other November 8, 2026 How should an enterprise software startup prepare a VPAT before a buyer asks for one?](https://humbleteam.com/blog/enterprise-software-startup-vpat-accessibility-report)