Bluejay / Labs
Open navigation

Working paper / 2026

MIVAS

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.

GitHub repository ↗

Clone the repository, pair a model harness with an industry task suite, and reproduce the evaluation environment.

Healthcare / C2-M2

C2-M2: Cancel a September follow-up

mediumAppointment management· Alice Romano

What this task measures

The caller is on the line with Straus Dermatology for one locked request: Cancel a September follow-up. They keep repeating that ask through a waitlist offer, a callback, or a different errand. We included it as a medium 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 following the identity then scheduling path, and leaves the record exactly as this case requires: the right row written or cleared, and nothing extra.

Performance

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.362

0:00 / 3:42 · audio · trace 801806 · click a span to play, drag to scrub, scroll to pan

Audio

Speech Audio

Agent Audio

Handoffs

Tool Calls

Errors

0:000:100:200:300:400:501:001:101:201:301:401:502:002:102:202:302:402:503:003:103:203:303:40
0:00

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.

All three gates matched, so the conversation counts as a pass.

1. Tools

Expected versus actual tool calls on this conversation.

Expected

Actual

  • transfer_to_identitynext_intent=schedulingtransfer_to_identityto=identity · from=receptionhit

    Parameters

     
    + from: reception
    - next_intent: scheduling
     
     
    + to: identity

    Output

    None recorded.

    None recorded.

  • identify_patientdob=1995-09-08 · zip=34786 · last_name=Romanoextra

    Parameters

     
    + dob: 1995-09-08
     
    + first_name: Alice
     
    + last_name: Romano
     
    + zip: 34786

    Output

     
    + ok: true
  • get_patient_summaryextra

    Parameters

    None recorded.

    None recorded.

    Output

     
    + ok: true
  • transfer_to_schedulingtransfer_to_schedulingto=scheduling · from=identityhit

    Parameters

     
    + from: identity
     
    + to: scheduling

    Output

    None recorded.

    None recorded.

  • verify_identitydob=1995-09-08 · full_name=Alice Romanoverify_identitydob=1995-09-08 · full_name=Alice Romano · second_factor=34786hit

    Parameters

      dob: 1995-09-08
      dob: 1995-09-08
      full_name: Alice Romano
      full_name: Alice Romano
     
    + second_factor: 34786

    Output

    - data: {"verified":true}
     
      ok: true
      ok: true
  • cancel_appointmentappointment_id=3 · cancellation_reason_code=patient_requestcancel_appointmentappointment_id=3 · cancellation_reason_code=patient_request · fee_disclosed_and_accepted=falsehit

    Parameters

      appointment_id: 3
      appointment_id: 3
      cancellation_reason_code: patient_request
      cancellation_reason_code: patient_request
     
    + fee_disclosed_and_accepted: false

    Output

    - data: {"status":"cancelled","fee_charged_cents":0}
     
      ok: true
      ok: true
  • end_callreason=caller_doneextra

    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: identify_patient, get_patient_summary, end_call.

2. Handoff path

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_identity → transfer_to_scheduling

Actual path

transfer_to_identity → transfer_to_scheduling

3. Final database state

The actual hangup matches the expected hangup.

Scores across model harnesses

Model harnesspass@1pass5Runs

Task definition

Locked caller script. This is the technical definition. Copy it as written.

You are an existing Straus patient. You have a follow-up in the middle of September at the Windermere office in Florida and you want it cancelled. Answer their identity questions once, confirm the readback, then stay on the cancel. Ask whether cancelling this far out costs anything. If they offer to rebook or put you on a waitlist, refuse. Once it is cancelled, thank them and end the call. Do not ask to book or reschedule. Do not ask to add insurance, for a callback, to speak to a person, a bill, a payment, the patient portal, a text, financing, or the street, floor, or suite. Do not ask them to text you an appointment confirmation.

Caller traits

patient_status
existing
full_name
Alice Romano
carrier
Oscar Health
preferred_office
Windermere
date_of_birth
1995-09-08
zip
34786
mobile
407-555-0155