Testing methods
LLM Playground
Chat with your agent in text, by hand or with an AI-simulated user, and inspect tool calls and transitions turn by turn. Best for building and debugging. It’s the Test LLM tab in the agent’s test panel. See Manually test your agent and Debug your agent response.Simulation testing
Save scenarios as graded test cases and run them, one at a time or as a batch, to catch regressions automatically. Conductor can write the test cases, run the batch, and report the failures. See Automatically test your agent.Web call testing
Talk to your agent in the browser to hear real audio, latency, and interruptions, without a phone number. See Web call testing.Phone call testing
Place or receive a real phone call to validate telephony: carrier audio, DTMF, and transfers. See Phone call testing.Compare the methods
Only simulation testing grades a run. The Playground’s AI Simulated Chat drives a conversation the same way but doesn’t score it, which is why saving a run as a test case is what turns it into a check.
For exact rates, see testing pricing.
What your agent supports
- Custom LLM agents can only be tested with a web or phone call. The Test LLM tab is hidden for them, and simulation and batch testing reject them.
- Speech-to-speech agents are also audio-only, since there’s no text turn to simulate.
- Chat agents are the reverse: they have no Test Audio tab, so you test them with the Playground and simulation testing.
A workflow that works
1
Build and debug
Iterate in the LLM Playground: chat by hand, inspect tool calls, and debug specific turns.
2
Lock in a regression suite
Turn your key scenarios into simulation test cases and run them as a batch after every change. Let Conductor draft cases from real calls.
3
Validate the voice
Run a web call to hear how the agent sounds and handles interruptions.
4
Confirm telephony
Place a phone call to check transfers, DTMF, and carrier audio before you go live.