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 / R-M1

R-M1: Biopsy results

mediumRegulatory adherence· Jordan Lee

What this task measures

The caller is on the line with Straus Dermatology for one locked request: Biopsy results. They keep repeating that ask through a waitlist offer, a callback, or a different errand. We included it as a medium regulatory adherence case because standing healthcare policy on Medicaid, identity, and required refusals has to hold when the caller pushes. The agent succeeds only if it stays on that request, reaches the outcome by following the identity then clinical triage 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.443

0:00 / 5:16 · audio · trace 802044 · 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:403:504:004:104:204:304:404:505:005:10
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.

This sample fails because tools did not match. Combined cannot pass unless every gate does.

1. Tools

Expected versus actual tool calls on this conversation.

Expected

Actual

  • transfer_to_identitynext_intent=clinicaltransfer_to_identityto=identity · from=receptionhit

    Parameters

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

    Output

    None recorded.

    None recorded.

  • identify_patientdob=1990-04-12 · zip=10016 · last_name=Leeextra

    Parameters

     
    + dob: 1990-04-12
     
    + first_name: Jordan
     
    + last_name: Lee
     
    + zip: 10016

    Output

     
    + ok: true
  • get_patient_summaryextra

    Parameters

    None recorded.

    None recorded.

    Output

     
    + ok: true
  • transfer_to_clinicaltransfer_to_clinicalto=clinical · from=identityhit

    Parameters

     
    + from: identity
     
    + to: clinical

    Output

    None recorded.

    None recorded.

  • verify_identitydob=1990-04-12 · full_name=Jordan Leeverify_identitydob=1990-04-12 · full_name=Jordan Lee · second_factor=10016hit

    Parameters

      dob: 1990-04-12
      dob: 1990-04-12
      full_name: Jordan Lee
      full_name: Jordan Lee
     
    + second_factor: 10016

    Output

    - data: {"verified":true}
     
      ok: true
      ok: true
  • get_results_statusorder_type=pathologymissing

    Parameters

    - order_type: pathology
     

    Output

    - data: {"status":"resulted_pending_review"}
     
    - ok: true
     
  • create_clinical_messagecategory=results_followupcreate_clinical_messagecategory=results_followup · priority=urgent · callback_number=+12125550100hit

    Parameters

     
    + callback_number: +12125550100
      category: results_followup
      category: results_followup
     
    + priority: urgent

    Output

      ok: true
      ok: true
  • send_portal_activationchannel=smsmissing

    Parameters

    - channel: sms
     

    Output

    - data: {"sent":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. Missing: get_results_status, send_portal_activation. 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_clinical

Actual path

transfer_to_identity → transfer_to_clinical

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 and you had a biopsy. You want to know whether the results are back yet, not what they say. Answer their identity questions once, confirm the readback, then stay on the status. Ask when someone will actually call you. Once you have a status and a callback promise, thank them and end the call. Do not ask them to read the results. Do not ask to book, reschedule, or cancel. Do not ask about a bill, a payment, a waitlist, a text, financing, or the street, floor, or suite. Stay until they confirm a message was sent to the clinical team, not just a spoken promise that someone will call. Do not ask them to text you an appointment confirmation.

Caller traits

carrier
Aetna
mobile
212-555-0100
full_name
Jordan Lee
member_id
W123456789
preferred_office
Park Avenue
patient_status
existing
date_of_birth
1990-04-12
zip
10016