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.

Customer Support / T3-H4

T3-H4: Plans, coverage, book, then cancel

hardTechCrew service· Grace Okonkwo

What this task measures

The caller is on the line with Kestrel Electronics for one locked request: Plans, coverage, book, then cancel. They keep repeating that ask through a callback offer, a different ticket, or an unrequested fix. We included it as a hard techcrew service case because the service ladder and the safety refusals for recalled or hazmat devices are the support flows that look helpful when they go wrong. The agent succeeds only if it stays on that request, reaches the outcome by following the verification then service 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.412

0:00 / 3:51 · audio · trace 813319 · 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:50
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 final database state did not match. Combined cannot pass unless every gate does.

1. Tools

Expected versus actual tool calls on this conversation.

Expected

Actual

  • transfer_to_verificationtransfer_to_verificationto=verification · from=receptionhit

    Parameters

     
    + from: reception
     
    + to: verification

    Output

    None recorded.

    None recorded.

  • identify_customeridentify_customerphone=5415550112 · full_name=Grace Okonkwo · order_number=KE4471860hit

    Parameters

     
    + full_name: Grace Okonkwo
     
    + order_number: KE4471860
     
    + phone: 5415550112

    Output

     
    + ok: true
  • verify_identitypostal_code=97005 · card_last4=6628verify_identitycard_last4=6628 · postal_code=97005hit

    Parameters

      card_last4: 6628
      card_last4: 6628
      postal_code: 97005
      postal_code: 97005

    Output

     
    + ok: true
  • get_customer_summaryget_customer_summaryhit

    Parameters

    None recorded.

    None recorded.

    Output

     
    + ok: true
  • transfer_to_servicetransfer_to_serviceto=service · from=verificationhit

    Parameters

     
    + from: verification
     
    + to: service

    Output

    None recorded.

    None recorded.

  • get_orderorder_number=KE-4471860get_orderorder_number=KE-4471860hit

    Parameters

      order_number: KE-4471860
      order_number: KE-4471860

    Output

     
    + ok: true
  • get_protection_plansget_protection_planshit

    Parameters

    None recorded.

    None recorded.

    Output

     
    + ok: true
  • check_coverageorder_number=KE-4471860 · issue=will not chargecheck_coveragesku=SKU-CMP-9930 · issue=Aurora Pro will not charge · order_number=KE-4471860mismatch

    Parameters

    - issue: will not charge
    + issue: Aurora Pro will not charge
      order_number: KE-4471860
      order_number: KE-4471860
     
    + sku: SKU-CMP-9930

    Output

     
    + ok: true
  • check_coveragesku=SKU-CMP-9930 · issue=Aurora Pro will not charge · order_number=KE-4471860extra

    Parameters

     
    + issue: Aurora Pro will not charge
     
    + order_number: KE-4471860
     
    + sku: SKU-CMP-9930

    Output

     
    + ok: true
  • book_service_appointmentorder_number=KE-4471860 · service_type=bench · issue=will not chargebook_service_appointmentsku=SKU-CMP-9930 · date=first available · issue=Aurora Pro will not chargemismatch

    Parameters

     
    + date: first available
    - issue: will not charge
    + issue: Aurora Pro will not charge
      order_number: KE-4471860
      order_number: KE-4471860
      service_type: bench
      service_type: bench
     
    + sku: SKU-CMP-9930

    Output

     
    + error_code: INVALID_DATE
     
    + ok: false
  • book_service_appointmentsku=SKU-CMP-9930 · date=August 24 · issue=Aurora Pro will not chargeextra

    Parameters

     
    + date: August 24
     
    + issue: Aurora Pro will not charge
     
    + order_number: KE-4471860
     
    + service_type: bench
     
    + sku: SKU-CMP-9930

    Output

     
    + ok: true
  • cancel_service_appointmentcancel_service_appointmentappointment_id=1hit

    Parameters

     
    + appointment_id: 1

    Output

     
    + ok: true
  • end_callreason=caller finished; no further action neededextra

    Parameters

     
    + reason: caller finished; no further action needed

    Output

    None recorded.

    None recorded.

Open a row for parameters and outputs. Required tools must appear. Extra industry tools are allowed. Parameter miss: check_coverage, book_service_appointment. Extra: check_coverage, book_service_appointment, 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_verification → transfer_to_service

Actual path

transfer_to_verification → transfer_to_service

3. Final database state

Rows that differ between the expected hangup and the actual hangup.

extra · service_appointments · 1

Expected

Actual

 
+ customer_id: cust_grace
 
+ id: 1
 
+ status: cancelled

Scores across model harnesses

Model harnesspass@1pass5Runs

Task definition

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

Open with exactly: "Tell me what plans I have, confirm the Aurora Pro that will not charge is covered at zero, book the first bench slot, then cancel it because I cannot make it." Give identity when asked. Order KE-4471860. Do the four things in that order. Keep asking for the first available bench slot; do not choose a calendar date, including September, even if the agent insists that a specific month or day is required. Do not mention canceling again until the agent confirms a booked calendar day and time. If they say nothing was booked or the booking failed, tell them the request is not complete and ask them to book the first available slot. Hang up only after they confirm that the booked appointment was cancelled. Once they have finished what you asked and confirmed the cancellation, say exactly: "Thank you, that's all I needed." and end the call. Do not start a second request.

Caller traits

full_name
Grace Okonkwo
phone
541-555-0112
postal_code
97005
card_last4
6628
order_number
KE-4471860