Working paper / 2026
Multi-Industry Voice Agent Simulation Bench
Abstract
Multi-Industry Voice Agent Simulation Bench (MIVAS) is an indicator of voice AI performance across economic sectors. MIVAS is comprised of tasks and verifiers with granular rewards executed in production-grade multi-agent RL environments across industries where voice AI is being adopted the fastest. Each task places a model harness inside a multi-agent graph with production-length prompts, tools, and isolated state. Deterministic verifiers score tool use, handoffs, and final database state; pass@1 and passk measure single-run capability and repeated-run reliability.
Clone the repository, pair a model harness with an industry task suite, and reproduce the evaluation environment.
Customer Support / T1-M2
What this task measures
The caller is on the line with Kestrel Electronics for one locked request: Cancel an unshipped speaker. They keep repeating that ask through a callback offer, a different ticket, or an unrequested fix. We included it as a medium orders and delivery case because order-bound delivery facts only exist after verification, and the 48-hour change fee is a representative retail trap. The agent succeeds only if it stays on that request, reaches the outcome by following the verification then orders path, and leaves the record exactly as this case requires: the right row written or cleared, and nothing extra.
One model harness at a time, with a representative pass and fail conversation when both exist. OpenAI Realtime 2.1 is the default view.
Recording
Conversation cost $0.198
0:00 / 2:21 · audio · trace 813213 · click a span to play, drag to scrub, scroll to pan
Audio
Speech Audio
Agent Audio
Handoffs
Tool Calls
Errors
Transcript
How a conversation passes
Combined pass is the logical and of three deterministic gates. Tools, handoff path, and final database state must all pass on the same conversation. One miss fails the call.
Combined
Fail
This sample fails because tools and final database state did not match. Combined cannot pass unless every gate does.
Expected versus actual tool calls on this conversation.
Expected
Actual
Parameters
+ from: reception
+ to: verification
Output
None recorded.
None recorded.
Parameters
+ full_name: Selena Cortez
+ order_number: KE4498870
+ phone: 5415550171
Output
+ ok: true
Parameters
card_last4: 1156
card_last4: 1156
postal_code: 97035
postal_code: 97035
Output
+ ok: true
Parameters
None recorded.
None recorded.
Output
+ ok: true
Parameters
+ from: verification
+ to: orders
Output
None recorded.
None recorded.
Parameters
+ order_number: KE4498870
Output
+ ok: true
Parameters
- order_number: KE-4498870
+ order_number: KE4498870
Output
+ ok: true
Parameters
+ reason: caller_done
Output
None recorded.
None recorded.
Open a row for parameters and outputs. Required tools must appear. Extra industry tools are allowed. Parameter miss: cancel_order. Extra: get_order, end_call.
Full industry architecture, same graph as the industry page. The left diagram marks the expected specialist path in green. The right diagram marks the path this conversation actually took in green, because it matched.
Expected path
transfer_to_verification → transfer_to_orders
Actual path
transfer_to_verification → transfer_to_orders
Rows that differ between the expected hangup and the actual hangup.
extra · order_cancellations · 1
Expected
Actual
+ id: 1
+ order_number: KE-4498870
+ status: cancelled
orders · KE-4498870
Expected
Actual
- status: processing
+ status: cancelled
Locked caller script. This is the technical definition. Copy it as written.
Open with exactly: "Please cancel my Corva Mini speaker order. It should not have shipped yet." Give identity when asked. Order KE-4498870. You want it cancelled on this call. Do not start a return. Do not ask for a confirmation text. Hang up once they confirm the cancellation and the refund back to the card. Once they have finished what you asked and confirmed it, say exactly: "Thank you, that's all I needed." and end the call. Do not start a second request.
