Voicely

Barge-in: letting callers interrupt a voice agent

Updated

Barge-in is a caller talking over the agent and the agent stopping to listen, the way a person would. Without it, callers have to sit through every sentence, which is the thing everybody hated about phone menus. Getting it wrong in the other direction is worse: an agent that cuts itself off whenever a door slams.

Barge-in
The ability of a caller to interrupt a voice agent while it is speaking and have the agent stop and listen, rather than finishing its sentence first. Named after the same setting in older telephony systems.
Barge-in and the terms around itBarge-in, related to End-of-turn detection, Response time, Voice AI agentEnd-of-turn detectionResponse timeVoice AI agentBarge-in
Barge-in and the terms around it

What it is

Barge-in is the caller talking over the agent, and the agent stopping to listen. The name comes from older telephony systems, where a bargein property on a prompt decided whether callers were allowed to cut it short. In VoiceXML it was a setting you turned on per prompt. In a modern voice agent it should be on all the time, because that is how people talk.

Not the same as call barging

Contact-centre software uses the same word for something else. There, a barge call or call barging is a supervisor listening to a live call between an agent and a customer and joining it, sometimes after whispering guidance to the agent first. That is a management feature for a human team. The barge-in on this page runs the other way: it is your customer breaking into what a voice agent is saying, and the agent giving way. If you are evaluating voice AI, this is the one to ask about.

Why it matters

Callers who already know what they want do not wait. They say the account number over the greeting. An agent that has to finish its sentence turns every one of those callers into somebody repeating themselves, and it is the single most recognisable trait of a system that was built without listening to real calls.

The two ways it goes wrong

Deaf at the end of the answer. This is the common one and it is hard to spot in a short demo. Many systems arm interruption when they start producing audio and disarm it when they have finished handing that audio over, which happens seconds before the caller has finished hearing it. The result is an agent that can be interrupted during the first half of a sentence and not the second. The fix is to keep listening until the audio the caller is hearing has finished playing, which is a different clock from the one the speech vendor reports.

Too easily startled. The opposite failure. A door slams, a bus passes, somebody in the room says something to somebody else, and the agent stops mid-word. On an Indian mobile call there is nearly always background noise, so a system tuned for a quiet room will cut itself off constantly. Distinguishing speech aimed at the agent from noise is the harder half of this problem, and it is where the difference between vendors shows.

How to check it

In any demo, do these two things. Interrupt the agent in the last two seconds of a long answer. Then, while it is talking, make a loud noise that is not speech. The mirror image, an agent that cuts the caller off, is a different setting going wrong, and it is worked through in why a voice AI agent interrupts callers. A system that handles both is one that has been on a real phone line. A system that handles neither is one that has been tested in a browser tab, which is a different product from the one you are buying. Our own version of that lesson is in what four phone calls taught us, and the full list of ways an agent fails once it meets a real line is in why voice AI agents fail on real phone calls.

Questions this raises

Is barge-in the same as call barging?

No. Call barging, or a barge call, is a contact-centre supervisor feature: a manager listens to a live call between an agent and a customer and joins it, turning it into a three-way call. Barge-in on this page is the caller interrupting a voice agent mid-sentence and being heard. Same word, opposite direction, and only the second one is about how your customers experience the agent.

How do I test barge-in in a demo?

Two tests. First, interrupt near the end of a long answer, not at the start: many systems stop listening once the audio has been handed over, so the last few seconds of every reply are deaf. Second, make a noise that is not speech while the agent is talking, such as a door or a cough. It should keep going.

Why does it matter more on a phone than in an app?

Because there is nothing else to look at. In an app you can see that the system is responding. On a call, talking over it is the only control the caller has, and taking that away is what made phone menus so disliked.

Sources

  1. W3C Voice Extensible Markup Language (VoiceXML) 2.0 — the bargein property, where the term comes from · checked 2026-09-02
  2. Voicely internal: elixir-app/docs/12 — interruption stays available for as long as the caller is still hearing the reply, measured against playback rather than against delivery · checked 2026-09-02
  3. NICE glossary: contact-centre barge-in, the supervisor feature that turns a live agent call into a three-way call (the other meaning of the term) · checked 2026-09-15