Agent lifecycle

Wirevox separates an agent's editable configuration from the version serving production traffic. Saving a draft does not change a published agent, and publishing does not automatically activate its delivery channel.

Create agent
    |
    v
Paused working agent + editable draft
    |
    +--> Browser/editor test uses draft
    |
    v
Publish draft --> Published version
    |
    v
Start agent + configure delivery --> Live traffic uses published version
    |
    +--> Edit again --> New draft --> Test --> Publish

The lifecycle has three independent dimensions:

• Agent status: Draft setup, Paused, Active, or legacy Archived state.
• Configuration state: Editable draft versus current published version.
• Delivery state: Assigned active phone number or enabled Website Chat deployment.

An agent is live only when the required conditions for its channel are satisfied.

In this topic

• Create an agent — choose channel and direction, use templates or Vox, understand defaults, limits, and workspace scope.
• Understand status and delivery — distinguish Draft, Paused, Active, publication, phone assignment, and Website Chat deployment.
• Edit and autosave drafts — understand draft initialization, 750 ms autosave, save failures, metadata, functions, and unpublished changes.
• Publish and manage versions — review validation, atomic snapshots, version history, restore, discard, and naming.
• Test draft and published behavior — see which configuration browser tests, chat previews, calls, and website sessions use.
• Duplicate, export, and delete agents — understand copied resources, reset delivery, JSON export, permanent records, and retained workspace resources.
• Test and troubleshoot the lifecycle — diagnose missing drafts, save failures, blocked publishing, stale live behavior, activation, restoration, and deletion.

Permissions and billing

Owner, Admin, and Member roles currently have agent-management permission; Viewer does not. Creation and duplication count against the active workspace's agent limit. Browser tests, live calls, and Website Chat usage consume workspace credits; saving and publishing configuration do not themselves create conversation usage.

Use Testing and publishing for the complete release procedure, guest test controls, evaluation evidence, production smoke tests, and rollback process.