Skip to main content
A web call test lets you talk to your agent in the browser, so you hear how it sounds and handles a live voice conversation before you put it on the phone. Where simulation testing runs on text, a web call exercises real audio: latency, turn-taking, and interruptions. It needs no phone number, and you can test a draft agent without publishing it first.

​
Start a web call test

1

Open Test Audio

In the agent editor, open the Test panel on the right and select Test Audio.
2

Set test inputs (optional)

If your agent uses dynamic variables or functions you’d rather not fire for real, open the Test Inputs dropdown next to the tabs, fill in the Dynamic Variables and Custom Function Mocks tabs, and click Save. The same values apply to Test LLM runs.
3

Pick a starting point (optional)

For a multi-prompt or Conversation Flow agent, choose a starting state or node to begin partway through the conversation instead of at the beginning. This is the quickest way to hear one branch without talking your way to it.
4

Run the test

Click Run Test and allow microphone access, then talk to your agent. Click End the Call to hang up.

Run a test web call from the agent detail page.

​
What a web call test is good for

Use it for the checks a text simulation can’t make:
  • Latency and turn-taking: how quickly the agent responds and whether it waits for you to finish.
  • Interruptions: whether the agent stops and listens when you talk over it.
  • How the voice actually sounds: pacing, pronunciation, and filler.
For example, after reworking your greeting and opening question, run a web call to hear the turn-taking, interrupt the agent mid-sentence, and confirm it yields before you ship the change.

​
Limitations

Some telephony behavior can’t happen in a browser call:
  • Transfers to a phone number fail, whether cold, warm, or agentic warm. The dashboard warns you when your agent has a transfer, and the call returns a transfer failure if the agent tries. Transfer to another agent does work, and the test panel follows the swap.
  • Sending an SMS fails, since there’s no phone number on the call.
  • Voicemail and IVR detection don’t run, so you can’t check a voicemail drop or a phone-tree branch.
Use phone call testing for any of those, or for real carrier audio. For automated pass or fail across many scenarios at once, use simulation testing and batch testing. A web call test is a real call for billing and limits: it bills per minute, takes one of your concurrent call slots, and won’t start if your account has a payment problem.
After a test call, ask Conductor to review it and suggest fixes.

​
Next steps