Voice AI technology

Barge-In: How Voice AI Handles Caller Interruptions

What barge-in is, why interruption handling is hard on phone lines, and how to write replies, set options and test calls so a voice agent feels natural.

Call editorial team · Published · 6 min read

In ordinary conversation, people interrupt each other constantly: to correct a detail, to say "yes, that one", or simply because they have already understood. A phone system that insists on finishing its sentence feels stiff, and callers soon start to talk over it, or give up. Barge-in is the feature that lets a voice agent handle this properly.

A person speaking into a phone headset during a call
Illustrative image

This article explains what barge-in is, why it is harder than it sounds, how to design replies and settings that work with it, and how to test it. It is part of a group of guides on voice AI; for the wider picture see How Voice AI Works and Turn-Taking in Voice Agents.

What barge-in means

A voice agent normally works in a loop: listen, understand, reply, speak. Without barge-in, the agent stops listening while it speaks, so anything the caller says during the reply is lost. With barge-in, the system keeps listening during its own speech. When it detects that the caller has begun to talk, it stops the audio, discards the rest of its planned reply, and treats the interruption as the next turn.

What happens when a caller interrupts

  1. Agent is speakingThe reply is playing while the system keeps listening.
  2. Speech detectedThe system decides that the sound on the line is a person talking.
  3. Playback stopsThe agent falls silent quickly so the two voices do not overlap for long.
  4. Interruption capturedWhat the caller says is transcribed as a new turn.
  5. New replyThe agent answers the interruption, not the sentence it was in the middle of.

Why it matters on the phone

Interruptions are not just rudeness. They carry information. A caller who cuts in with "no, Tuesday" is correcting an error. One who says "yes, yes" wants you to hurry. One who says nothing but sighs is probably losing patience. A system that ignores these signals produces calls that run long and end badly.

Common reasons callers interrupt

  • To correctThe agent got a date, name or number wrong.
  • To answer earlyThe caller knows the question and replies before it ends.
  • To skipThe agent is repeating something they already know.
  • To redirectThe caller wants something else entirely.
  • To confirmA quick yes or no that does not need the whole sentence.

Allowing interruptions also lets you write shorter replies, because you need not worry that a long answer will trap the caller. That fits well with how people listen on the phone.

Why it is harder than it sounds

The idea is simple, but a phone line is a noisy, imperfect channel. Several problems have to be solved at once.

These problems pull in opposite directions. A very sensitive detector reacts fast but triggers false interruptions. A cautious one is calm but feels unresponsive. Good systems combine acoustic detection with checks on how long the sound lasts and what it contains. Voice Activity Detection and Telephony Audio Quality explain two of the building blocks.

Designing replies that work with interruptions

Settings alone will not make a conversation feel natural. The writing of the agent's replies matters at least as much.

Writing for interruption

Hard to interrupt wellEasy to interrupt well
LengthLong paragraphs with several pointsOne or two short sentences
OrderBackground first, answer lastThe answer first, details after
OptionsReads a long listOffers two or three, then asks which
ConfirmationsRepeats everything at the endConfirms the key detail as soon as it is given
ToneFormal and elaboratePlain and conversational

When the agent confirms information, make it interruptible by design. For example, "Your appointment is on Tuesday at ten. Is that right?" invites a quick yes even before the question ends. Avoid sentences where the crucial word comes last.

Settings and trade-offs

Most voice systems offer a setting that allows or disallows interruptions, and some offer more fine-grained controls over how sensitive detection is. Turning interruptions off can make sense in narrow cases, such as a legally required statement that must be heard in full. Elsewhere, leaving them on is usually better for callers.

A related setting is how long a silence lasts before the call ends. Too short, and a caller looking for a document is cut off. Too long, and a dropped call ties up a line. Match it to what your callers do: someone checking an order number needs longer than someone saying yes.

SituationSuggested approach
Required disclosure or scriptAllow no interruption for that part only, and keep it short
Quick yes or no questionsAllow interruptions and accept the answer early
Callers on noisy mobile linesTest carefully for false triggers; keep replies short
Elderly or slower speakersAllow generous pauses before the system decides the turn is over
Outbound callsTest for the agent's own echo and answering machines

Elderly callers and people with speech differences deserve special attention. They may pause longer, speak more slowly or repeat themselves. If the system jumps in too soon, it will talk over them. See AI Receptionist: Elderly Callers for ideas.

Testing barge-in

Test with real calls, not only clean recordings. Make a set of scenarios and run them after every change to settings or prompts.

Barge-in test cases

  • Interrupt in the first second of a reply and check that the start of your words is captured
  • Interrupt near the end and make sure it does not repeat the finished sentence
  • Say a quiet "mm-hm" during a long reply and see whether the agent keeps going
  • Cough, tap the phone or let a dog bark and see whether the agent stops
  • Call from a car, a street and a speakerphone
  • Remain silent and check how long the call waits
  • Correct a detail mid-sentence, such as a date, and check the correction is used

Record how quickly the agent stops and whether any words are lost. For a wider test method see Voice AI Testing, and for the delay between a caller's last word and the agent's reply, Voice AI Latency.

Barge-in in Call

In Call, the voice settings for an agent include a switch labelled Allow interruptions, which lets callers speak over the agent. It is on by default. Next to it is a setting for how many seconds of silence end the call, and there are limits for simultaneous calls and the longest call. These sit on the Agent voice page, together with the voice and the prompt.

On outbound AI calls, background noise is filtered and the agent stops speaking only when the person really says something; the agent's own voice returning on the line is not taken as the person speaking. The replies themselves follow a rule of one or two short spoken sentences, which suits interruption. Try the agent with the test call on your own phone, and then read call details for how much each side talked and how often both spoke at once.

Frequently asked questions

What is barge-in in a voice agent?

It is the ability for a caller to interrupt the agent while it speaks. The agent stops, listens and responds to what the caller said.

Why does my voice agent sometimes stop for no reason?

Background noise, an echo of its own voice or a cough can be mistaken for speech. Shorter replies, better audio and careful sensitivity settings reduce this.

Should I switch interruptions off?

Rarely. They are useful for natural calls. Turning them off may suit a short required statement that has to be heard in full.

What is a backchannel?

A small sound like "mm-hm" or "right" that shows a listener is following. A good agent does not treat it as a request to stop.

How can I make replies easier to interrupt?

Keep them short, put the answer first and ask quick confirmations. Avoid long lists and placing the key word at the end.

How do I test barge-in properly?

Make real calls from different places, interrupt at different moments, add noise and silence, and check whether words were lost. Repeat after each change.

Tune interruption settings in Call

In the demo console you can try incoming calls in a simulation.

Related guides