Boson AI logo
More articles

IHBench: What Voice Agents Say After You Interrupt

Ahmad Salimi, Wentao Ma, Yuzhi Tang, Dongming Shen, Mu Li, Alex SmolaJune 29, 2026
IHBench is a benchmark for post-interruption recovery: it measures whether the agent resumes the workflow correctly after an interruption, rather than whether it stops talking when you cut in. It defines six interruption types, scores recovery on two axes — task fulfillment and recovery quality — across closed- and open-weight audio-language models, and shows recovery quality is a largely distinct capability axis that general audio benchmarks don’t already capture.
428
interruption samples
6
interruption types
10
enterprise domains
What is IHBench?

When voice agents lose the thread

When a user interrupts a voice agent mid-sentence, two different things have to go right. The model has to stop talking at the right moment, and then it has to say the right thing next. A growing set of full-duplex benchmarks measure the first one: barge-in detection, yield latency, telling a real interruption from a backchannel.
IHBench measures the second one. Given a workflow-driven conversation where the user cuts in to correct a detail, express impatience, switch topics, or push back, does the model resume at the correct step, address the interjection, and avoid re-delivering content the user already heard? That is post-interruption recovery, a capability existing speech benchmarks leave unmeasured.

Six interruption types

Human interruptions fall into six natural groups. We inject them into the conversation at a controlled point mid-utterance, each with its own recovery criteria generated alongside the conversation. Here are the groups:
Normalcooperative
A cooperative cut-in that volunteers a new detail or asks a quick clarification. Address the interjection, then resume the workflow with a fresh start.
Impatientdirective
The user wants to speed up or skip an explanation. Skip the interrupted content and advance without re-explaining what was asked to skip.
Correctiondirective
The user corrects something they said in a prior turn. Accept it without pushback, integrate the corrected value, and continue.
Topic switchredirective
The user raises an unrelated request. Address the new topic, then steer back to the original workflow without blending the two.
Fillercooperative
A brief backchannel (“mm-hm,” “yeah,” “right”) that changes nothing. Continue the interrupted utterance from exactly where it was cut off, without repeating or restarting.
Pushbackadversarial
The user challenges or resists the assistant’s request. De-escalate empathetically and offer alternatives without losing the workflow.

What good and bad recovery look like

Two real IHBench cases. The em dash () marks where the user cut in mid-utterance. The difference is rarely about understanding the words; it is about whether the model keeps its place in the workflow.
Filler interruption (backchannel)
Assistant…and there is elevator access from the garage. Back
User interrupts“mm-hm”
✗ Bad“Before we continue, I just want to …”
Starts over after a simple backchannel, and jumps to a different workflow stage.
✓ Good“to your registration, we still need to schedule your first appointment. Is now a good time?”
Continues exactly from where it was cut off.
Correction interruption
AssistantGot it, I'll use john.smith@example-company.com. Reading that back
User interrupts“Oh wait, sorry, no hyphen. It should be examplecompany as one word.”
✗ Bad“Sure, it's john.smith@examplecompany.com. I'll use that for the email.”
Accepts the correction but drops the workflow (was about to send the summary).
✓ Good“Got it, I'll use john.smith@examplecompany.com. I'm sending the brief summary now with Jane Doe's direct contact and scheduling link.”
Integrates the correction and resumes the workflow.
Scoring

Two axes: task fulfillment and recovery quality

At each interruption the model generates the next response, which is scored on two independent axes:
Task fulfillmentcomparative
Does the response advance the workflow? An LLM judge compares it against a baseline (GPT-4o Audio) given the same context and picks the better one. We report the win rate: the fraction of interruptions where the model is preferred. 0.50 is parity with the baseline.
Recovery qualityabsolute
Did the recovery itself go right? The judge checks the response against 2–4 type-specific criteria written for that interruption (e.g. for filler: continue without restarting). We report the pass rate: the fraction where every criterion is met.
Results

What we found

We found that task fulfillment and recovery quality do not necessarily improve across model generations and that there’s a significant difference between model families, in particular how they handle fillers. This suggests that models so far haven’t really been trained to do particularly well on the type of situations that we believe matter for human-machine interactions. Here’s what we find:
Task fulfillment and Recovery Quality
Task fulfillment and recovery quality rank models differently. GPT Realtime 2 leads task fulfillment (0.73 win rate against the GPT-4o Audio baseline), while Gemini 2.5 Flash with thinking leads recovery quality (0.70 pass rate) on a lower task-fulfillment score. Since a model can advance the task well and recover differently, both axes are worth reporting. The full per-model table is in the Leaderboard tab.
Filler separates model families the most
The fillertype, continuing an utterance after a backchannel like “mm-hm,” is where recovery quality splits most cleanly along model families. Each bar below spans the range of filler pass rates within a family; the dot marks the family mean.
0%20%40%60%80%Gemini 2.5Gemini 3.xGPT familyfiller RQ pass rate
Filler recovery-quality pass rate by model family. Each bar spans the minimum to maximum per-model rate within the family; the dot marks the mean.
Recovery shifts with conversation depth
Task fulfillment varies with how deep into the conversation the interruption lands. A per-model logistic regression of the win/lose outcome on depth gives a mean slope of −0.030 (t(25) = −7.04). The decline is far steeper for open-weight models: their mean slope (−0.053) is about 3.3× that of the closed-weight models (−0.016), a gap that is itself significant (Welch t = 7.74). Depth is therefore a useful axis for telling robust multi-turn behavior apart from shallow turn-taking.
swipe to see all models →
Closed-weightOpen-weight0.000.170.340.510.680.85TF Win RateGPT Realtime 2 †GPT Realtime 2 (xhigh) †GPT Realtime 1.5GPT AudioGemini 3 Flash †Gemini 3 FlashGPT RealtimeGemini 2.5 Flash †Gemini 3.1 Pro †Gemini 2.5 Pro †Gemini 2.5 FlashGPT Audio MiniGemini 3.1 Flash LiveGPT Realtime MiniGemini 3.1 Flash Live †GPT-4o Mini AudioGemma 4 12B Instruct †Gemma 4 12B InstructMiMo-Audio-7B †MiMo-Audio-7BVoxtral-Small-24BQwen3-Omni-30BKimi-Audio-7BQwen2.5-Omni-7BPhi-4-MultimodalQwen2-Audio-7B
0–45–910–1415–19Logistic fit
Task-fulfillment win rate by conversation-depth bin for each of the 26 configurations (closed-weight first, then open-weight, each block ordered by overall TF), with a per-model logistic fit (dashed). Open-weight models slope down about 3.3× more steeply than closed-weight ones.
Text-only input is never worse than audio
For the 15 configurations that accept both modalities (six Gemini, nine open-weight), we re-run the benchmark on the text transcript alone, holding everything else fixed. A TOST equivalence test shows the Gemini models are statistically indistinguishable across modalities (within ±0.02 on every metric), while text input is strictly better for the open-weight configurations (by ~8 points on task fulfillment and ~6 on recovery quality). Audio input never outperforms text, so there is no audio-versus-text modality gap on what IHBench measures.
swipe to see all models →
GeminiOpen-weight0.000.200.400.600.80TF Win RateGemini 3 Flash †Gemini 3 FlashGemini 2.5 Flash †Gemini 3.1 Pro †Gemini 2.5 Pro †Gemini 2.5 FlashGemma 4 12B Instruct †Gemma 4 12B InstructMiMo-Audio-7B †MiMo-Audio-7BVoxtral-Small-24BQwen3-Omni-30BQwen2.5-Omni-7BPhi-4-MultimodalQwen2-Audio-7B
AudioText-only
Audio vs. text-only task-fulfillment win rate across the 15 dual-modality configurations (Gemini block, then open-weight). Text input is never worse than audio.
Pipeline

How the data is built

Each conversation is an assistant-led state machine driving an ordered workflow (e.g. Authenticate → Verify Account → Process Request → Confirm) across one of 10 enterprise domains, grounded in concrete fictional values rather than placeholders. Interruptions are injected within stages, not at clean boundaries, so recovery is non-trivial: the model has to figure out where it left off inside a stage. A multi-agent pipeline generates and audits each conversation:
  • Prerequisites. For each (domain, goal) pair, generate a knowledge base, a system prompt, and user-intent profiles, each with a behavioral profile and an interruption probability distribution over the six types.
  • Round-by-round simulation. A round planner decides what happens each turn, whether an interruption occurs, its type, and where in the utterance the user cuts in. Separate assistant and user simulators write the utterances; the user simulator only reacts to the truncated portion the user actually heard, which prevents information leakage.
  • Rubric generation. Each interruption gets one task-fulfillment criterion and 2–4 type-specific recovery-quality criteria, written during synthesis so scoring is grounded in a rubric for that exact moment.
  • Verify and modify. A post-hoc verifier scans for naturalness violations, state-machine leakage, and references to undelivered content; a modifier applies minimal edits, and conversations that cannot be fixed are discarded.
Prerequisites
Domains
Goal Generator
Knowledge Base Builder
stages · guidelines · user info
Assistant Sys. Prompt
knowledge base in natural language
User Intent
reaction profile
description
interruption profile
attributes
Domains
Goal Generator
Knowledge Base Builder
stages · guidelines · user info
Assistant Sys. Prompt
knowledge base in natural language
User Intent
reaction profile
description
interruption profile
attributes
Domains
Goal Generator
Knowledge Base Builder
stages · guidelines · user info
Assistant Sys. Prompt
knowledge base in natural language
User Intent
reaction profile
description
interruption profile
attributes
Conversation Synthesis
Round Planner
assistant plan
user plan
interruption plan
termination signal
Assistant Simulator
interruption handling vs. normal
User Simulator
interrupting vs. normal
Rubric Generator
task fulfillment
recovery quality
↻ repeat
✂ interrupting?
Round Planner
assistant plan
user plan
interruption plan
termination signal
Assistant Simulator
interruption handling vs. normal
User Simulator
interrupting vs. normal
Rubric Generator
task fulfillment
recovery quality
repeat
interrupting?
Round Planner
assistant plan
user plan
interruption plan
termination signal
Assistant Simulator
interruption handling vs. normal
User Simulator
interrupting vs. normal
Rubric Generator
task fulfillment
recovery quality
Verification
Verifier
list of issues with fix procedure
information leakage
conversation naturalness
non-fixable signal
Modifier
list of modifications
up to N iterations
Verifier
list of issues with fix procedure
information leakage
conversation naturalness
non-fixable signal
Modifier
list of modifications
up to N iterations
Verifier
list of issues with fix procedure
information leakage
conversation naturalness
non-fixable signal
Modifier
list of modifications
Audio Synthesis
Text Normalization
TTS friendly user messages
Text-to-Speech
Text Normalization
TTS friendly user messages
Text-to-Speech
Text Normalization
TTS friendly user messages
Text-to-Speech
Evaluation Sample
system: You are a support agent…
[ instructions + state machine]
Perfect, I'll send it to john@gmail [interrupted]
Wait, actually, use my work email, john@company.com.
Model under evaluation
Got it, I'll send it to your work email, john@company…
Rubrics
LLM Judge
The IHBench synthesis and evaluation pipeline. A model under evaluation regenerates only at interruption points and is scored against the per-interruption rubric by an LLM judge. For audio evaluation, user turns are TTS-synthesized with ASR verification.

Citation

If you use IHBench in your research, please cite:
@misc{ihbench2026,  title         = {IHBench: Evaluating Post-Interruption Recovery in Voice Agents with Structured Workflows},  author        = {Salimi, Ahmad and Ma, Wentao and Tang, Yuzhi and Shen, Dongming and Li, Mu and Smola, Alex},  year          = {2026},  eprint        = {2606.19595},  archivePrefix = {arXiv},  primaryClass  = {cs.CL},}
#research
#benchmark
#voice-agents
#interruption
#evaluation