Publish and share

Publish a Viber agent and share or embed its Webchat.

Publishing promotes the current working version to the version used by live channels. It does not create a separate agent.

Working and published state

SurfaceVersion it runs
PreviewThe current working version, including unpublished changes.
Hosted WebchatThe published version.
Connected channelsThe published version.

After an agent is published, later edits remain in the working version until you publish again.

Publish changes

  1. Select Publish changes.
  2. Review the enabled channels and change summary.
  3. Inspect the detailed channel or change list when needed.
  4. Publish the working version.

The only user-facing publish prerequisite is at least one enabled channel. New agents start with Webchat enabled.

Readiness guidance is advisory and does not block publishing.

Share the hosted Webchat

Open Deploy > Channels > Webchat, then select Share your agent. Copy the Shareable link to give someone access to the published agent in a browser.

Embed Webchat on a website

In Share your agent, copy the provided embed snippet and paste it immediately before the closing </body> tag on your site.

The snippet contains the correct Webchat loader and the agent’s current configuration file. Copy it from Viber rather than writing it by hand.

The Acme Support Webchat embed snippet and website preview

Choose a deployment mode

Under the Webchat deployment settings, choose one of these interfaces:

ModeBehavior
ToggleOpens from the default chat bubble or a custom launcher element.
EmbeddedRenders inside a page element. The default element ID is bp-embedded-webchat.

Toggle can use the standard chat bubble, a custom launcher element, and an optional launcher image. Embedded mode uses the configured container element ID.

Webchat controls and plans

Some Webchat controls depend on your workspace plan. Viber identifies plan requirements in the Webchat editor.

Diagnose a publishing problem

If Publish changes is disabled, open Deploy > Channels and enable at least one channel.

If a publish request fails even though a channel is enabled:

  1. Keep the exact error message.
  2. Confirm that the channel is still enabled and configured.
  3. Retry the publish once.
  4. Contact support if the error persists.