How it works
- A simulation runs. For an inbound agent the Digital Human calls the agent. For an outbound agent the agent calls the Digital Human.
- They hold a spoken conversation over the connection you configured.
- Bluejay records the call and transcribes it in real time.
- When the call ends, Bluejay grades the run against your success criteria and custom metrics.
Connection types
A voice agent can be reached in several ways. Bluejay connects over whichever one you configure.
The provider agents are ElevenLabs, Retell, Vapi, Google CES, Google Dialogflow CX, Bland, Sierra and Amelia. For a plain phone agent you give it a phone number. For a provider agent you give its agent id, and the provider API key lives in your organization’s integrations rather than on the agent.
Create a voice agent
From the Agents view, click the + to add an agent. This opens the Connect Your Agent dialog. Fill it in:- Name the agent.
- Write its Agent Description / System Prompt.
- Set Agent type to Inbound or Outbound.
- Set Mode to Voice. It sits next to Email and Text as a top-level choice.
- Pick the connection type.
- Enter its details. This is a phone number for a phone agent, or a provider agent id for a provider agent.
- Click Create.
Connect a provider agent
For a provider agent, wire up the provider webhook and credentials first, then bind your Bluejay agent to the provider agent id. Each integration guide walks through the exact steps.Run a voice simulation
Build a simulation on the voice agent, add Digital Humans, and run it. Bluejay places or answers each call, drives the conversation, and grades the result. See Simulations Overview for how simulations are put together and scored.What Bluejay measures on a voice run
Alongside your goals and custom metrics, Bluejay reports voice quality signals from the call itself.
Your success criteria and custom metrics still decide whether a run passes. The voice signals sit alongside them so you can hear why a call felt off, not just that it failed.
Voice uptime monitors
An uptime monitor places the same call on a schedule against a live voice agent, so you catch a broken agent before your customers do. On each run it checks that the agent answers, does not malfunction, and stays within a latency threshold. See Uptime Monitoring for scheduling, alerting, and verdict rules.Set it up with the API or MCP
Voice agents and runs are fully scriptable.- Create the agent with add-agent:
mode="VOICE", theconnection_type, and its fields. This is a phone number for a phone agent, or a provider agent id and provider fields for a provider agent. Over MCP this is theadd_agenttool with the same fields. See Add Agent. - Queue a run with the standard simulation run endpoint, or the
queue_simulation_runMCP tool, passing thesimulation_id.