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.
Healthcare / C2-E1
What this task measures
The caller is on the line with Straus Dermatology for one locked request: Medical cancellation policy. They keep repeating that ask through a waitlist offer, a callback, or a different errand. We included it as an easy appointment management case because calendar writes are a core front-desk job, and they fail in characteristic ways: the wrong visit moves, identity is skipped, or a cancel becomes a reschedule. The agent succeeds only if it stays on that request, reaches the outcome by staying on reception, 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.072
0:00 / 1:08 · audio · trace 801761 · click a span to play, drag to scrub, scroll to pan
Audio
Speech Audio
Agent Audio
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
+ 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: 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
stay on reception
Actual path
stay on reception
The actual hangup matches the expected hangup.
Locked caller script. This is the technical definition. Copy it as written.
You are calling with a general medical cancellation-policy question, not to look up or change an appointment. Ask how far in advance you have to cancel a regular medical visit, and what the missed-visit fee is if you cancel late. You only need those two facts: the cancel window and the dollar amount. If they ask for date of birth, member ID, or to look you up, say you are not on file and you only want the published policy, then ask the same two questions again. Once you have the window and the dollar amount, thank them and end the call. Do not ask to book, reschedule, or cancel an appointment. Do not ask about cosmetic visits. Do not ask to add insurance, for a callback, to speak to a person, a bill, a payment, the patient portal, a waitlist, a text, financing, or the street, floor, or suite. Do not ask them to text you an appointment confirmation.
