Last reviewed: 2026-03-18 Owner: Web + support engineering Source of truth:

https://dawnhq.ai/docs/channels/web-widget
https://dawnhq.ai/docs/channels
Internal deployment configuration (private; not for visitor disclosure) Applies to: support responses for website widget behavior Refresh cadence: on every widget config change

Facts

Production widget is configured through a dedicated Web channel binding.
The widget binding must be attached to the intended active agent profile.
Visitor-facing support should provide setup and troubleshooting steps only, not environment values.
Do not expose concrete config values (keys, host mappings, origin lists, internal deployment notes).
Allowed origins must be explicitly configured and validated during rollout.
Widget should be embedded at the site layout/template level for consistent availability.

FAQ snippets

Where should the snippet go? In website layout/template before closing </body>.
Why does widget open but not send? Most often origin policy mismatch, wrong API base, or channel binding/profile mismatch.
What details can I share with visitors? Only public setup guidance from docs; no environment or key values.
What should I check first on a custom site? Exact allowed origin, active Web binding, and that the binding points at the intended agent.