The web chat (Web Widget)

It’s the chat embedded on your own site. Each Web Widget instance has its own snippet, with a different connection identifier per instance, so you can have several widgets — one for your main site and another for a different landing page, for example — each with its own agent and its own owners.

Requirements: administrator role to copy and configure the channel; access to your site’s code (or to whoever manages it) to paste the snippet.

1. On the Web Widget card you want to publish, copy the “Paste this snippet on your site” block with the Copy button.
2. Hand that snippet to whoever manages your site so they paste it into the code of the site that corresponds to THAT instance — one instance’s snippet only works for it, never for another.
3. To change the allowed domain or other connection parameters, use Connect / Configure on the card itself.

Result: the chat shows up on your site as a floating bubble (usually at the bottom right) that opens when tapped, with your agent’s greeting, quick-action buttons if you’ve configured them, and a field to write in.

The widget’s visual look (brand color, greeting, assistant name, avatar…) is adjusted separately, in Settings → Widget customization (Manual 26 · Settings) — it’s a setting shared across all your Web Widget instances, unlike the language, which is chosen per instance. Allowed domains (which sites it can load on) are configured on that same Settings screen. The detail of how it’s technically embedded in different content managers is in Manual 06 · Web widget.

6.1. Widget language

Every Web Widget card has its own “Widget’s default language” selector (Spanish / English / Italian). That instance’s snippet always emits that language as the value of its data-locale attribute, so choosing it here is enough — there’s no need to touch the snippet by hand. The selection saves instantly, with no separate “Save” button.

Note — Forcing a different language on a specific page

If your site is multilingual and you want the chat to speak a different language than the default on a particular page (for example, your site’s English version), edit the data-locale attribute of the snippet pasted on that page by hand — the rest of your site keeps using the default configured here. If the given language isn’t one of the three supported ones, the widget shows in English. The full technical detail is in Manual 06 · Web widget.

6.2. AI transparency and privacy, already built in

The widget complies by design with the AI Act (Art. 50) and with GDPR’s duty of information, with nothing for you to configure: the chat header always shows the subtitle “AI assistant · replies instantly”, and every AI-generated message carries the “AI” tag next to the assistant’s name (a human operator’s messages don’t carry it). The widget’s footer links to the privacy policy you’ve configured for that instance on its channel card — if you haven’t configured one yet, it shows an honest generic notice instead (“Your data is handled by {your business}”), never your provider’s policy as if it were yours.

For the footer’s link to point to your own agency’s policy (instead of the generic notice), configure the privacy policy URL on that Web Widget instance’s card.