Every change fixes one thing and can quietly break another. Without tests you find out from customer conversations. With tests: before publishing.
Switch versions to see how a scenario catches a bug after an instruction change and how Copilot suggests a fix in the draft.
A scenario is a conversation (scripted customer messages or a simulated customer with a goal and facts) and a list of checks. Each check is a separate result, so you see straight away what broke.
No. Tools that write (lead, booking, ticket) are simulated in tests. Read-only tools can use real data if you set the scenario that way.
Tests use AI credits like regular conversations. A chat scenario usually costs a fraction of a cent; voice is noticeably more expensive. Each scenario can have its own cost limit.
You run tests in the panel, from Copilot or via MCP, usually on the draft before publishing. There is no nightly schedule today.
No. A voice scenario checks the agent's behaviour in the voice channel (the same conversation engine) but in text mode. Check audio and phone quality with test calls.
Search tests check whether the right documents are in the results and how relevant they are. Conversation scenarios check the answer itself (content checks and the judge).
Up to 200 scenarios, conversations of up to 20 turns, up to 10 judging criteria per scenario. A custom tool has up to 20 test cases.
Copilot reads the failed checks, the conversation and tool errors, judges whether the problem is in the agent, the test, the tool or the environment, and suggests a specific fix. Changes go to the draft, tests run again and the published agent doesn't change.