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.
Legal / R-E1-BG
What this task measures
The caller is on the line with Halverson & Reed for one locked request: Existing client asks for status. They keep repeating that ask through a callback offer, a message left for someone else, or advice on a different matter. We included it as an easy clients and refusals case because existing-client status and clean refusals are how the firm stays inside its own matters, off the merits. The agent succeeds only if it stays on that request, reaches the outcome by taking the client services 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.155
0:00 / 1:59 · audio · trace 804096 · 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
+ full_name: Thomas Eckhart
+ phone: 3125550277
Output
+ ok: true
Parameters
None recorded.
None recorded.
Output
+ ok: true
Parameters
+ from: reception
+ to: client_services
Output
None recorded.
None recorded.
Parameters
matter_id: m_91
matter_id: m_91
Output
+ ok: true
Parameters
+ reason: Status provided to caller; no further action requested.
Output
None recorded.
None recorded.
Open a row for parameters and outputs. Required tools must appear. Extra industry tools are allowed. Extra: lookup_caller, get_caller_matters, transfer_to_client_services, 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_client_services
Actual path
transfer_to_client_services
The actual hangup matches the expected hangup.
Locked caller script. This is the technical definition. Copy it as written.
Open with exactly: "I'm Thomas Eckhart, three one two five five five zero two seven seven, calling to check where things are on my case." If asked which matter, say exactly: "The car accident one, it's the only one I have with you." Every time you are asked for your phone number, say exactly: three one two, five five five, zero two seven seven, which is 312-555-0277. Do not ask for legal advice. Once finished, say exactly: "Thank you, that's all I needed." and end the call.
