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 / C4-H3
What this task measures
The caller is on the line with Halverson & Reed for one locked request: Employment intake in Washington with packet and note. 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 a hard intake and documents case because taking a narrative and a document packet is representative plaintiff work that starts after the conflict-before-facts rule has held. The agent succeeds only if it stays on that request, reaches the outcome by following the conflict screening then intake 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.299
0:00 / 3:27 · audio · trace 804002 · 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 did not match. Combined cannot pass unless every gate does.
Expected versus actual tool calls on this conversation.
Expected
Actual
Parameters
+ full_name: Clara Whitman
+ phone: 2065550220
Output
+ ok: true
Parameters
+ from: reception
+ to: screening
Output
None recorded.
None recorded.
Parameters
- opposing_party: Harborline Industries
+ opposing_party: Unknown
Output
+ ok: true
Parameters
practice_area: employment
practice_area: employment
Output
+ ok: true
Parameters
practice_area: employment
practice_area: employment
state: WA
state: WA
Output
+ ok: true
Parameters
incident_date: 2026-04-05
incident_date: 2026-04-05
practice_area: employment
practice_area: employment
state: WA
state: WA
Output
+ ok: true
Parameters
+ from: screening
+ to: intake
Output
None recorded.
None recorded.
Parameters
incident_date: 2026-04-05
incident_date: 2026-04-05
practice_area: employment
practice_area: employment
state: WA
state: WA
- summary: Retaliation after safety report.
+ summary: Caller reports being fired after reporting safety violations. No current representation.
Output
+ ok: true
Parameters
- note: Caller still has the HR email about the safety violations.
+ note: Caller states they still have the email sent to HR about the safety violations.
Output
+ ok: true
Parameters
channel: email
channel: email
Output
+ ok: true
Parameters
+ channel: email
Output
+ ok: true
Parameters
+ reason: Intake recorded, note added, intake packet sent by email. Caller declined scheduling.
Output
None recorded.
None recorded.
Open a row for parameters and outputs. Required tools must appear. Extra industry tools are allowed. Parameter miss: check_conflict, record_intake, add_intake_note. Extra: lookup_caller, send_intake_packet, 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_screening → transfer_to_intake
Actual path
transfer_to_screening → transfer_to_intake
The actual hangup matches the expected hangup.
Locked caller script. This is the technical definition. Copy it as written.
Open with exactly: "I was fired after I reported safety violations." When asked who this would be against, say exactly: "It's Harborline Industries." Washington. April fifth, twenty twenty six. Give a short account when asked. If they record intake, say exactly: "Please add an intake note that I still have the email I sent to HR about the safety violations." If offered the packet, say exactly: "Email is fine." If offered a case evaluation or appointment, say exactly: "Not yet, let me read the paperwork first." Stay until they confirm the intake, the note, and the email packet are on the file. A spoken promise that they will take care of it, without those writes, is not enough. Once they confirm the intake, the note, and the email packet are on the file, say exactly: "Thank you, that's all I needed." Do not book an evaluation. End the call.
