Testing & Publishing
Validate your flow with test calls and publish it for live use.
Test mode
Before publishing a flow, switch it to TESTING status to make test calls directly from the editor.
Test calls behave identically to live calls — same AI models, same voice, same latency. The only difference is that test calls are not billed and are clearly marked in your call logs.
Running a test call
- Set the flow status to TESTING
- Click Test Call in the editor toolbar
- Enter a phone number to receive the test call
- The flow executes as it would in production
- Review the call transcript and node execution trace in the test results panel
Validation requirements
A flow must pass validation before it can be published. All of the following are required:
| Requirement | Description |
|---|---|
| Main Agent | The flow must have exactly one Main Agent node |
| LLM provider | At least one LLM provider node must be connected |
| TTS provider | At least one TTS provider node must be connected |
| STT provider | At least one STT provider node must be connected |
If validation fails, the editor highlights which requirements are unmet.
Publishing
Publishing locks the flow and makes it available for assignment to phone numbers.
Status transitions
DRAFT → TESTING → PUBLISHED → ARCHIVED| Transition | What happens |
|---|---|
| DRAFT → TESTING | Enables test calls. Flow remains editable. |
| TESTING → PUBLISHED | Validation runs. If it passes, the flow is published as an immutable snapshot. |
| PUBLISHED → ARCHIVED | Retires the flow. Unassigns all phone numbers. Cannot be undone. |
Immutability
A published flow is a snapshot — it cannot be edited. This guarantees that the flow running on your phone numbers is exactly the version you tested and approved.
To make changes to a published flow:
- Open the published version
- Click Create New Version
- A new draft is created with the same configuration
- Edit, test, and publish the new version
- Reassign phone numbers to the new version