PolyAI platform describes the creation of voice agents and dialogue verification through separate scripts and test sets.

Do not limit yourself to one call
After changing a phone agent's workflow, test common calls and unexpected follow-up questions. PolyAI documents simulations, scenario sets, and comparisons of agent behavior, so you can replay conversations after a settings change. Define the expected outcome for each case. For a simple information request, an accurate answer is enough. A transfer needs a verifiable handoff to the correct queue.
A sample at a fictional workshop
One caller asks for opening hours. Another interrupts the answer and asks for the address. A third asks to speak to a person. Use the same reference information and run these cases through a test channel. Listen for whether the agent continues its previous reply after the change. Check whether it transfers the call without asking the same question again. If the queue is closed, check what the caller hears and how the call ends.
How to accept change
Repeat the check after changing the tips, knowledge or connection rules. Compare old and new versions on the same input lines. Separately evaluate the answers to the wording, which were not in the examples. If the simulation goes through, make a few calls to the test number with live speech. Talking on the phone is different pace, pauses and noise. The available means of verification and connection depend on the selected part of the platform. Confirm them before moving the script to the work channel. It is useful to write down the method of verification for each key transition and the condition for its acceptance.
Suitable tasks
- Make a set of tests for the telephone agent.
- Verify interrupt and call translation.
Strengths
- It documents simulations and repeatable test scenarios.
- The platform takes into account the routing of calls and transmission to the operator.
Limitations
- Simulation does not cover all the features of living speech.
- Connecting telephony and queues requires a separate configuration.
Selection and conditions
- Free access
- Not confirmed
- Trial period
- Not confirmed
- No sign-up required
- Not confirmed
- Russian interface
- Not confirmed
- Local installation
- Not confirmed
- API
- Not confirmed
“Not confirmed” means there is not enough information. The feature may still be available; check the developer’s terms.
- Input formats
- Text, Audio
- Result
- Audio, Text
Terms
Repeat key scenarios on the dedicated test number.From task to first result
Practical example
- Task
- Make a set of tests for the telephone agent.
- What to prepare
- Training number and agreed certificate of a fictional workshop.
Task brief or prompt
Set up an agent to respond about work hours and address. In the test call, interrupt the answer with a question about the address, then ask to transfer the call to an employee.
Expected result
Test conversation with a verifiable answer and transition to an employee.
How to check the result
- Check the opening hours and address with a certificate.
- Repeat the translation when the employee is unavailable.
An editorial teaching example of a task brief, not the result of hands-on testing of the service. Check that the required mode is available, that you have rights to the source material and that the intended use of the result is permitted.
Check details
Official sources
This description is based on the developer’s material. Features, prices and availability may change; check the primary source before use.




