IHBench: Evaluating Post-Interruption Recovery in Voice Agents with Structured Workflows
This paper introduces IHBench, a new benchmark for evaluating how voice agents recover from interruptions in structured workflows, revealing that closed-weight models significantly outperform open-weight ones in task fulfillment and recovery quality across diverse enterprise domains.
Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer
Imagine you are talking to a very smart, automated voice assistant that is trying to help you fill out a complex form, like booking a doctor's appointment or filing an insurance claim. This isn't just a chat; it's a structured workflow, meaning the assistant has a specific script it must follow step-by-step to get the job done.
Now, imagine you are talking to this assistant, and you suddenly cut it off mid-sentence to say, "Wait, I meant my work address, not my home!" or just to say "Uh-huh" to show you're listening.
The Problem:
Most current tests for voice assistants only check if the robot knows how to stop talking when you interrupt. It's like testing if a driver knows to hit the brakes when a pedestrian steps out. But these tests don't check what happens after the brakes are hit. Does the driver know how to merge back into traffic? Do they accidentally drive the wrong way? Do they repeat the whole route from the beginning?
This paper introduces IHBench, a new "driving test" specifically designed to see how well voice agents recover after being interrupted.
The "IHBench" Test Drive
The researchers created a simulated environment with 10 different real-world scenarios (like banking, healthcare, or travel). They built a "traffic simulator" where a voice agent tries to guide a user through a task, but a "user simulator" constantly interrupts them in six specific ways:
- The "Filler" (Backchannel): You say "mm-hm" or "right" just to show you're listening. The agent should keep talking exactly where it left off.
- The "Correction": You fix a mistake you made earlier (e.g., "Actually, my email is one word, not two"). The agent needs to update its memory and keep going.
- The "Impatient" Skip: You say, "Just get to the point, skip the explanation." The agent needs to jump ahead without re-explaining.
- The "Topic Switch": You suddenly ask about something totally different (e.g., "By the way, what's the weather?"). The agent needs to answer briefly and then gently steer you back to the original task.
- The "Pushback": You refuse to give information. The agent needs to be polite and offer a different way to proceed.
- The "Normal" Request: You add a new detail. The agent needs to handle it and continue the plan.
How They Graded the Robots
Instead of just saying "Pass" or "Fail," they graded the robots on two separate scores:
- Task Fulfillment: Did the robot eventually finish the job (like booking the appointment) correctly?
- Recovery Quality: Did the robot handle the interruption gracefully? Did it avoid awkwardly repeating things you already heard? Did it remember where it was in the script?
The Big Findings
The researchers tested 27 different voice models (from big companies like OpenAI and Google, plus some open-source community models). Here is what they found:
1. The "Closed" vs. "Open" Gap
Think of the "Closed-weight" models (like GPT-4o or Gemini) as professional race car drivers who have trained on millions of miles of specific tracks. The "Open-weight" models are like talented amateur drivers who are great at general driving but haven't practiced this specific track as much.
- The professional drivers (Closed models) were much better at recovering from interruptions. They rarely lost their place in the script.
- The amateur drivers (Open models) got confused much more often. As the conversation got longer, they got worse and worse, often forgetting the original goal entirely.
2. The "Thinking" Trap
Some models have a "thinking" mode (like a driver taking a deep breath before merging). For the Google models, this "thinking" helped them finish the task better. However, it didn't necessarily help them recover gracefully from the interruption. Sometimes, over-thinking made them stumble more.
3. The "Audio" vs. "Text" Surprise
You might think listening to a voice is harder than reading text.
- For the professional drivers (Closed models), it didn't matter. They performed just as well with audio as they did with text.
- For the amateur drivers (Open models), audio was a disaster. They performed significantly worse when they had to listen to a voice compared to reading the words. They seemed to lose their place much faster when the input was sound.
4. The "Filler" Problem
One specific type of interruption was a major weak spot for many models: the "Filler" (saying "mm-hm").
- Many models treated a simple "mm-hm" as a signal to stop and restart the whole sentence, or they awkwardly said, "Glad you're following along!" when they should have just kept talking.
- The best models (like Gemini 2.5) handled this perfectly, continuing the sentence seamlessly. The newer models (Gemini 3.x) actually got worse at this than the older versions.
The Conclusion
The paper concludes that recovery quality is a unique skill. A model can be great at finishing a task (Task Fulfillment) but terrible at handling interruptions (Recovery Quality), and vice versa.
Current benchmarks mostly check if the robot stops talking when interrupted. This new test, IHBench, proves that the real challenge isn't stopping; it's knowing exactly how to start up again without losing the thread of the conversation. The best models today are the big, closed systems, while open models still have a lot of work to do to catch up in these real-world, interrupted scenarios.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.