You test a project by chatting with it in a test panel. The panel runs the real flow, with its LLMs and integrations, so you can see what a customer would see before you publish. See Flows.
Opening a test
| Where you open it | What it tests | Where the conversation starts |
|---|---|---|
| Test Conversation on the designer's right rail | The draft | In an intent's action flow: that action flow. Anywhere else, including an AI Agent tool flow: Main. |
| The chat icon on the project card | The published version | Main |
Test Conversation is available only while the open flow is valid. If it is greyed out, fix the nodes marked invalid first. See Designing a Flow.
A test always reads the latest saved draft, so an edit shows up in your next test without publishing. A test session does not consume licence or credit.
For example, to check a weather question end to end:
- Open the Main flow and select Test Conversation.
- On the Test tab, type
What's the weather like in Istanbul today?and send it. - Open the Log tab to see each node that ran, in order.
- To start again from the beginning, select the refresh icon in the panel header.
⚠️ Warning: A test calls your real services. An HTTP node that creates a ticket or takes a payment does so during a test too. To test without calling the service, turn on Mock HTTP Response on that HTTP node. The node then returns your mock body instead of calling, and does this only in tests.
The test panel
The panel header has a refresh icon, which ends the current session and starts a new one, and a close icon. The panel has three tabs: Test, Log and Settings.
The test runs on its own test channel. Where a node has responses for specific channels, the test is treated as WebChat.
Test
Type a message and send it. You can also attach a file of up to 10 MB. Common image, document, audio and video types are accepted.
There is no language picker. The reply language comes from the flow, through the ResponseLanguage variable. See Variables and Context.
Talking instead of typing
Talk to an Agent switches the test to a voice call. It ends the current session and starts a new one. It is offered only when the project has both a Speech Recognition and a Text-to-Speech service:
- for a test from the designer, on the draft
- for a test from the project card, on the published version
Your browser must allow the microphone. When you test an intent's action flow, the microphone button for voice messages is hidden. To add the services, see Service Integrations.
Log
The Log tab shows the node trace of the current conversation: every node that ran, in order. To see it, your role needs the Elastic Search permission.
Test settings
All settings are off by default. They are remembered in your browser for each project and user, so a colleague who opens the same project starts with their own settings.
| Group | Setting | What it does |
|---|---|---|
| Monitoring | Show responder AI Agent name | Shows which AI agent wrote each reply. |
| Show AI Agent tool call details | Shows each tool call and its result. | |
| Show guardrail details | Shows guardrail evaluations. | |
| Show HTTP call details | Shows each HTTP node's request and response. | |
| Show AI Agent Invoke Failure | Shows it when an AI agent fails to run. | |
| UI Interaction | Disable previous buttons after a new message | Stops the customer clicking buttons from earlier messages. |
| Audio Response | Enable audio responses | Reads replies aloud. Needs a valid Text-to-Speech service in the project. |
Without the Agentic AI feature, Monitoring offers only Show HTTP call details.
Voice Activity Detection
These settings appear only when voice is available. They control how the voice test decides when you have started and stopped speaking.
| Setting | Default | Range |
|---|---|---|
| Enable interruption while talking | Off | |
| Pre-Speech Buffer Length (ms) | 300 | 0-1000 |
| Post-Speech Buffer Length (ms) | 250 | 0-1000 |
| Sensitivity | 6 | 0-10 (higher is more sensitive) |
| Max Speech Duration (ms) | -1 (unlimited) | Up to 60000 |
| Silence Trigger Duration (ms) | 700 | 100-3000 |
Test Call in outbound projects
In an outbound project with the Outbound feature, Test Call places a real test call:
- Enter the Destination phone number.
- Under Parameters, enter values for the flow's variables.
- Select Test. The outcome appears under Call Result.
Limits
| Item | Limit |
|---|---|
| Attachment size | 10 MB |
| Mock HTTP response body | 5,000 characters; anything longer is cut |