Channels & deploy

Web widget, messaging, voice, and provider integrations.

Channels (Operate → Channels) and Deploy (/app/assistants/{id}/deploy) connect your assistant to users. Convoship supports an embeddable web widget plus provider-backed channels (WhatsApp, SMS, voice, helpdesk handoffs, and custom webhooks).

Deploy page

  • Lists active deployments with token prefix, allowed origins, last used.
  • Revoke — invalidates cdp_* token immediately.
  • Copy embed snippet — script tag + ConvoshipQueue init.
  • Theme JSON — primary color, launcher, header copy.

Web widget (embed)

  1. Click New deployment under Web widget.
  2. Set allowed origins — exact browser origins that may load the widget (e.g. http://localhost:5500).
  3. Copy the cdp_* token (shown once) and the embed snippet.
  4. Add the script to your site; the widget calls the public runtime API.
<script src="https://YOUR_HOST/embed/v1.js"></script>
<script>
  ConvoshipQueue.push(['init', {
    agentId: 'AGENT_UUID',
    token: 'cdp_...',
    channel: 'web',
    apiUrl: 'https://YOUR_API_HOST'
  }]);
</script>

Widget appearance

Configure launcher color, position, greeting, and avatar in the deployment config panel. Changes apply on next page load for embed visitors.

Provider channels

ChannelPurpose
WhatsApp (Twilio)Business messaging via Twilio-connected number.
SMS (Twilio)Text message conversations.
Voice (Twilio)Phone calls with Twilio voice number.
Voice gatewaySIP / streaming gateway for real-time audio.
Zendesk / Genesys / ServiceNowHelpdesk and CCaaS handoff integrations.
Custom webhookBring your own inbound/outbound HTTP bridge.

Channel connections vs deployments

  • Deployments — bearer tokens for the web embed (cdp_*).
  • Connections — persistent provider links with inbound secrets and credential keys stored in workspace secrets.

CORS & origins

If the widget shows a 403 on session start, the page origin must exactly match an allowed origin on the deployment — check for trailing slashes or http vs https mismatches.