Chat channels
Set up the website widget
A chat bubble on your own site or intranet — one script tag, no third-party platform, no account, no cost: the widget talks straight to this deployment and makes no other request. Visitors are always guests: they read only the guest access groups you choose for this channel, and there's no way to link a visitor to an account.
Before you start
- Nothing outside the product — no developer account, no platform review, no credential to create. You only need to know the origins of the pages that will carry it.
- Chat channels → Website chat widget: enter the Allowed origins, one per line — scheme + domain, https://intranet.example.com, no path, no trailing slash. Under “Who may use it” pick the guest access groups (and whether guests may also read documents shared with everyone). Optionally a Title, Welcome message and Accent colour. Create, then Test — “Widget ready for N origin(s).”
- The checklist step “Put the widget on your pages” shows the embed tag — copy it.
- Paste the tag into the pages that should show the widget, just before the closing body tag.
The tag looks like this — one script, nothing else, and it is the same on every page:
<script src="https://your-assistant/channels/widget/<channel-id>/embed.js" async></script>| Title | The heading visitors see when the chat bubble opens. Blank uses the assistant's own name. |
|---|---|
| Welcome message | The first message in the chat window before the visitor types anything — a good place to say what the widget can help with. Blank shows a sensible default greeting. |
| Accent colour | The widget's header and button colour, so it matches your site — any CSS colour: a hex code like #0f766e or a name like darkslategray. Blank uses the default. |
Access
The widget answers only from the guest access groups chosen for this channel — with none chosen it tells visitors the assistant isn't open to visitors yet, and the checklist flags “Choose what visitors may read”. There is no member tier: every visitor is a guest, by design, so put only documents meant for that audience in those groups. Each answer ends with a Sources line naming what it cited. The widget's own wording (title, placeholder, buttons) uses the deployment's language; the assistant answers in the language the visitor writes.
The widget also answers only on the origins you list — www.example.com and example.com are different origins, list both if both serve the site; a page anywhere else that copies the embed tag gets nothing. Test refuses an empty list and any entry that isn't an origin (“scheme + host only, no path”). Questions are cut at 4,000 characters and replies at 8,000. One visitor is answered at most 12 times a minute and one network address at most 60 — enough for people, not for scripts. Changes to the title, welcome message or colour reach pages within five minutes.
Last updated 20 Sep 2026