Skip to main content

Duplicate, export, and delete agents

Duplication is useful for controlled variants. Deletion is destructive and should not be used as an archive substitute.

Duplicate an agent​

Select Duplicate from the agent menu. Wirevox:

  • checks the active workspace's agent limit;
  • creates the copy in the same workspace;
  • copies the current draft when one exists, otherwise the base/published configuration;
  • copies channel, direction, prompt, model, voice, avatar, knowledge-base selection, tools, and attached reusable functions;
  • creates a new working draft;
  • resets the phone-number assignment;
  • sets the new agent to Paused;
  • names it (Copy), (Copy 2), and so on.

The copy is a new agent with its own ID and no published version history. It must be reviewed, tested, published, and connected to delivery separately. Shared knowledge bases, functions, and integrations are referenced rather than cloned into new workspace resources.

Export to JSON​

Export to JSON downloads the agent object currently returned to the Agents page. Treat it as a diagnostic or review artifact, not a complete portable backup or a guaranteed import format.

The export does not package external credentials, knowledge documents, provider resources, full version history, conversation records, or every related table. Wirevox currently exposes no matching general agent-import action in the interface.

Delete an agent​

Delete Agent permanently removes the agent after confirmation. The backend first unassigns any Wirevox phone-number record, deletes agent tools, calls, and leads, then deletes the agent. Cascading relationships remove agent versions, function attachments, chat deployments and sessions, playground share links, and other agent-owned records.

Deletion does not release the phone number from the workspace, delete shared knowledge bases or reusable functions, disconnect workspace integrations, or guarantee cancellation of an external provider-side transaction.

Safe deletion sequence​

  1. Pause the agent.
  2. Disable Website Chat deployments or unassign the phone number.
  3. Wait for active calls and generations to finish.
  4. Retain any required logs, contacts, or audit data through an approved process.
  5. Review shared resources to determine whether they are still used elsewhere.
  6. Delete only after accepting that agent-owned history is removed.

There is no general Agent archive control in the current interface. Use Paused when the agent must remain available for later review or reactivation.