Skip to main content
Publishing and distribution are separate steps. Publishing makes the tested staging configuration live for new conversations. Distribution makes the Agent reachable through a phone number, SIP connection, public profile, embed, or another supported channel.

​
Publish the tested configuration

Before publishing:
  1. Test the successful path and common failure or escalation paths.
  2. Verify every external action with safe data.
  3. Confirm the greeting, instructions, model, voice, functions, apps, and reporting fields are intentional.
  4. Save a named version when you may need a clear rollback point.
  5. Publish, then reopen the live Agent and verify the expected configuration.
Publishing does not automatically assign a phone number, approve SMS, connect SIP, or announce the Agent to customers.

​
Choose how customers reach it

  • Phone: Assign a Vida or bring-your-own number, or connect SIP, then run an inbound and outbound test.
  • SMS: Complete the required registration and test opt-in and opt-out behavior before promoting the number.
  • Public profile: Share the Agent’s public profile for supported web voice and chat.
  • Website: Follow the embed guide to place the interaction on your site.
Use the channels that match the workflow. A Computer Agent connected to an internal team channel usually should not be published as a customer-facing voice Agent.

​
Roll out deliberately

Start with a controlled audience or traffic source. Monitor conversations and reporting outcomes, correct problems in staging, and publish again only after testing the fix. When using a phone number in advertising, directories, or a website, update one source at a time and verify routing. Keep the previous route recoverable until the new Agent handles representative calls correctly. Use the production launch checklist when preparing a new workflow or material production change.