Testing and publishing
Wirevox separates editing, testing, publishing, and delivery so a change can be evaluated before it reaches callers.
This topic documents the stable inbound voice-agent workflow. Chat Agent preview and Website Chat delivery remain Beta and are referenced only where their version behavior differs.
The release path
| Stage | Configuration used | Production effect |
|---|---|---|
| Autosave | Working draft | None |
| Private browser test | Saved draft snapshot | None, but usage and tool side effects are real |
| Shared browser test | Snapshot captured when the link is created | None, but usage and allowed tool side effects are real |
| Publish | Saved draft | Creates a new immutable production version |
| Live verification call | Current published version at call start | Exercises real routing and carrier transport |
| Restore | Historical version copied into the draft | None until the restored draft is published |
In this topic
- Plan an agent test
- Run a private browser test
- Create and control shared test links
- Validate and publish a draft
- Manage versions and restore safely
- Verify and monitor production
- Troubleshoot testing and publishing
Core rules
- Wait for a successful save before testing or publishing.
- Treat browser tests as billed operational sessions, not disposable previews.
- Treat connected tools as real unless explicitly disabled.
- Give every important publication a useful name and note.
- Verify the production path with a new call after publishing.
- Never reuse an existing call or session to prove a new version.
- Restore into a draft, test it, and publish it as a new version.
For the underlying state model, see Agent lifecycle.