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, set their test values in the Test Inputs panel first, so placeholders resolve the same way they would on a real call.
3

Run the test

Click Run Test and allow microphone access, then talk to your agent. Click again to end the call.

​
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

Transfers aren’t supported in a web call test. To test a call transfer, DTMF navigation, or real carrier audio, use phone call testing. For automated pass or fail across many scenarios at once, use simulation testing and batch testing.
After a test call, ask Conductor to review it and suggest fixes.

​
Next steps