Skip to main content

Manage versions and restore safely

Wirevox keeps published and archived versions in Version History. Drafts are working state and do not appear there.

Read version history​

Open the agent's more menu and select Version History. Each entry can show:

  • optional version name;
  • version number;
  • Live status for the current published version;
  • publication date and time; and
  • optional version note.

A published version contains the prompt, model, voice, full configuration, and function/tool snapshots captured at publication.

Use names that identify the intended outcome and notes that state the change, reason, risk, and verification reference. Avoid names such as Final or New version.

Restore an older version​

For an archived entry, select Restore, then Confirm.

Restore overwrites the current draft with a copy of that historical version and reconciles its function/tool snapshots into the working configuration. It does not immediately change production.

After restoring:

  1. Review the complete draft and current shared-resource availability.
  2. Test critical scenarios.
  3. Review integrations and cost.
  4. Publish it as a new version with a note referencing the incident or rollback reason.
  5. Start a new production interaction and verify it.

The new publication receives a new version number. History remains chronological rather than moving the live pointer backward silently.

Discard the current draft​

When unpublished changes exist above a published version, select Discard Draft and confirm. This replaces the draft with the current live published version and permanently removes the unpublished edits, including working attachment differences.

Use discard when the draft itself is unwanted. Use restore when a specific older published configuration should become the basis of a new release.

Emergency rollback expectations​

If the live agent presents immediate risk, pause or disable its delivery first when operationally appropriate. Then restore, test the minimum critical paths, republish, and verify. Restoration alone is not an emergency stop and not a completed rollback.