Embedding on multiple sites

Your workspace has one chat widget. That widget can be embedded on any number of websites — your marketing site, your dashboard, a knowledge base on a different domain, a checkout flow — and every conversation lands in the same inbox.

How to do it

1. Copy the embed snippet from Chat → Settings → General.
2. Paste it before the </body> tag on each site where you want the bubble.
3. Add each host to Chat → Settings → Security → Allowed domains (one domain per line). If the list is empty, any origin is allowed — fine while you're trying things out, less fine in production.

That's it. Anyone clicking the bubble on acme.com, support.acme.com or acme-pro.io will start a new conversation that shows up in the same place.

Telling chats apart

Each conversation remembers the host the visitor was on when they opened the bubble. The inbox surfaces this two ways:

• A Site dropdown appears at the top of the inbox once you have chats from more than one host. Pick a site to filter; pick All sites to clear.
• Every row carries a small mono-spaced badge with the site host (acme.com, blog.acme.com), shown next to the status pill — so even without filtering you can scan a busy inbox and see who's writing from where.

The site is captured once, when the visitor first loads the widget. If they navigate to a different domain mid-chat, the badge keeps showing the original site so the conversation stays grouped correctly.

What multi-site does NOT do (yet)

The widget settings (color, header title, welcome message, bubble label, pre-chat form, business hours, GDPR consent, AI features) are per-workspace, not per-site. The widget on acme.com looks identical to the widget on acme-pro.io.

If you actually need different branding per site — a B2C consumer brand vs. a B2B enterprise brand with the same support team — the cleanest setup today is one workspace per brand. The same teammates can be invited into both. We have multi-widget per workspace on the roadmap but it's not built yet.

A few patterns this enables

• One brand, many sites. Marketing site + dashboard + help center, all linking back to the same support team.
• Beta vs. production. Same widget on acme.com and beta.acme.com; agents see both inbox flows and can tell beta tickets apart via the site filter.
• Documentation pages on a different domain. Use the bubble as the "Talk to a human" escape hatch from the docs without forcing the visitor over to your main site.

Snippet drift

You only ever update the snippet once, on your side, when we change the schema. The embed key in the snippet (data-site="NURA-XXXXXXXXX") never changes — it's the long-lived identifier of your workspace, the same on every site.