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 / T3-M4
What this task measures
The caller is on the line with Kestrel Electronics for one locked request: Protection plans on the phone account. They keep repeating that ask through a callback offer, a different ticket, or an unrequested fix. We included it as a medium techcrew service case because the service ladder and the safety refusals for recalled or hazmat devices are the support flows that look helpful when they go wrong. The agent succeeds only if it stays on that request, reaches the outcome by following the verification then service path, and leaves the record untouched: no appointment, ticket, or note the caller never asked for.
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.277
0:00 / 3:19 · audio · trace 813339 · 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
Pass
All three gates matched, so the conversation counts as a pass.
Expected versus actual tool calls on this conversation.
Expected
Actual
Parameters
+ from: reception
+ to: verification
Output
None recorded.
None recorded.
Parameters
+ full_name: Priya Raman
+ order_number: KE-4462884
Output
+ ok: true
Parameters
card_last4: 3361
card_last4: 3361
postal_code: 98104
postal_code: 98104
Output
+ ok: true
Parameters
None recorded.
None recorded.
Output
+ ok: true
Parameters
+ from: verification
+ to: service
Output
None recorded.
None recorded.
Parameters
+ order_number: KE-4462884
Output
+ ok: true
Parameters
None recorded.
None recorded.
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. 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_service
Actual path
transfer_to_verification → transfer_to_service
The actual hangup matches the expected hangup.
Locked caller script. This is the technical definition. Copy it as written.
Open with exactly: "What protection plans do I have on my Solstice phone?" Give identity when asked. Order KE-4462884. You only want the plans on file. Do not file a claim. 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.
