Skip to main content
Open Chatbot → Channels to configure the website channel behind your Chatbot deployment. Channels define browser access, channel state, basic widget defaults, publishable-key lifecycle, and optional handoff delivery credentials.

​
Current channel type

The customer-facing production channel is the web widget. The dashboard therefore describes configured channels as web widgets. Other internal channel enums are not customer-facing availability promises.

​
Create a channel

A channel includes:
  • Channel name
  • Status: Active or Disabled
  • Allowed website origins
  • basic widget appearance
  • optional Turnstile site key
  • visitor attachment toggle
  • human-handoff toggle
  • optional handoff provider
When the channel is created, RAUM generates a browser publishable key.

​
Allowed origins

Enter one exact origin per line. Production origins must use HTTPS. Examples include https://www.example.com and https://support.example.com. Wildcards are not accepted. An origin includes the scheme, hostname, and port. Localhost HTTP is accepted only outside production.
Origin restriction is part of the widget security boundary. Do not replace the exact production list with an intentionally broad pattern just to make deployment easier.

​
Basic widget settings on the channel

The channel form includes:
  • welcome message;
  • primary color;
  • launcher position;
  • optional Cloudflare Turnstile site key;
  • allow customer attachments; and
  • enable human handoff.
The richer versioned configuration belongs under Chatbot → Widgets. Think of Channels as the browser/delivery boundary and Widgets as the full customer-experience configuration.

​
Human handoff provider

The channel can configure a delivery provider for handoff integrations.

​
Email

Provide the destination email address.

​
Signed webhook

Provide an HTTPS webhook URL and signing secret. The current UI requires a signing secret of at least 32 characters when the webhook credential is first configured. Use the signature to authenticate RAUM’s webhook delivery before trusting the payload.

​
Zendesk

Provide the Zendesk subdomain, optional ticket tags, Zendesk agent email, and Zendesk API token. Stored provider credentials are not returned to the normal editor after save. Leaving secret fields blank while editing keeps existing credentials.

​
Channel handoff versus Forms & Handoffs

These are related but not identical. Channels configure the external delivery integration, including signed webhooks. Forms & Handoffs configure what the visitor sees, when a form is offered, localized fields/copy, and whether the resulting request becomes a RAUM request, email, or Zendesk ticket. Forms & Handoffs →

​
Publishable key

A channel/widget uses a publishable browser key rather than an organization API token. The key is intentionally browser-visible, bound to the widget/origin security model, shown when created or rotated, and versioned. Copy it when RAUM displays it.

​
Rotate the key

Use Rotate key when you need to replace a publishable key. RAUM returns the new key, its key version, and the time until which previous keys remain valid. That overlap gives you time to update all allowed websites without creating an avoidable outage.

​
Disable versus remove credentials

Set a channel to Disabled when the channel should stop operating without destroying its configuration. Use the credential-removal control when you specifically want to remove stored handoff credentials. Removing those credentials also removes the associated handoff setup rather than leaving a configuration that claims to work with no secret behind it.

Widgets

Configure and publish the full visitor experience.

Installation

Install the public widget with the correct public ID, key, key version, origins, and CSP.