Skip to main content

Operate securely and respond to incidents

Secure operation requires periodic review and a prepared containment path. Do not wait for an incident to identify owners or provider contacts.

Deployment checklist​

  • Review workspace and agency memberships.
  • Remove secrets from prompts, variables, knowledge, and test data.
  • Minimize provider scopes and attached functions.
  • Add caller disclosure and a refusal or human alternative.
  • Test prompt injection, unknown facts, tool failures, duplicate requests, and cancellation.
  • Disable tools on shared tests unless explicitly required.
  • Verify production number routing and the published version.
  • Define log access, review cadence, retention decision, and deletion owner.
  • Confirm provider agreements for the data category.
  • Record known platform limitations and accepted risk.

Suspected account or membership compromise​

  1. Remove the unauthorized membership or revoke the pending invitation.
  2. Reset the affected identity through the authentication provider.
  3. Review other workspaces and agency subaccounts reachable by that identity.
  4. Inspect recent agent, integration, Vox approval, call, knowledge, and billing changes.
  5. Rotate connected provider credentials where exposure is possible.

Suspected integration-secret exposure​

Revoke or rotate the credential at the provider first. Then disconnect and reconnect it in Wirevox, inspect provider audit history and Wirevox tool events, and remove exposed values from messages, files, repositories, and tickets.

Unsafe agent or function behavior​

Pause the agent or disable delivery, revoke shared test links, disconnect the affected integration when necessary, preserve the relevant call and action IDs, and compare the draft with the published version. Fix and test the narrowest configuration change before republishing.

Revoke the shared test link. For Beta Website Chat, disable or delete the deployment and rotate it by creating a new deployment/public key if required. Review stored sessions and external tool side effects.

Data sent to the wrong place​

Stop the responsible function or integration, identify the exact destination and affected records, preserve evidence, contact the destination owner, and follow the organization's incident and notification procedure. Deleting the Wirevox record does not retract data already delivered externally.

Evidence to preserve​

Keep workspace and agent IDs, version, call/chat/Vox action ID, timestamps and timezone, provider, function name, status, affected data categories, access changes, and remediation steps. Redact secrets and unnecessary personal information.

Escalation​

Use the official support and privacy contacts published by Wirevox. For a suspected breach or legal request, involve the organization's security and legal owners. Do not use Vox chat to transmit credentials or unrestricted sensitive evidence.