A widget is one Delivery of an Agent: the chat bubble you paste onto a site. It holds the appearance, the visitor-facing text, the publication state, and the domains allowed to embed it. The Agent behind it is unchanged — one Agent can carry a widget per domain.
- 1
Open the widget builder
From the Agent, on an Agent that faces the public.
- 2
Configure appearance and language
Brand treatment, greeting, labels, and the languages visitors get.
- 3
Add allowed domains
Every production and preview host that may embed it.
- 4
Publish and install
Publish, copy the snippet, and place it on the approved site.
Draft until you publish
Changes stay in draft. The site keeps serving the last published configuration, which gives you room to review appearance and text without touching what visitors see.
Chat features
Under Chat features in the builder you choose what this widget adds to the Agent's answers: feedback on answers (a rating, a rating with a comment, or off), suggested follow-up questions beneath an answer, and whether visitors may attach a file. They are set per widget, so two widgets of one Agent can differ, and like everything else they reach visitors when you publish. The Agent answers in Copilot, over the API and in chat without any of them.
Allowed domains are the envelope
The browser's origin has to match a domain on the list. Add production and preview hosts deliberately and exactly; a broad wildcard turns a controlled installation into an embed you no longer know the shape of.
Losing the snippet does not lose the widget
The snippet loads the published configuration and mounts it. If it goes missing, take the current installation instructions from the Agent again.
Test as a visitor
Open the real page in a clean browser session, so an internal login cannot hide a public-access problem. Ask a normal question, an out-of-scope one, and one that fishes for internal material. Check the narrowest width your site supports.
Launch and troubleshooting checklist
Confirm the widget is published, the production host is listed exactly as the browser sends it, and the loader appears once on the page.
If nothing appears, check the origin and the installation code before you touch the Agent. If it appears but answers badly, open the conversation and read its citations. A missing public Source is a Knowledge problem; a refused internal Standard is the boundary working as designed — a visitor reaches Knowledge and never a governing rule.