Skip to main content
The website channel lets visitors meet your published agent through a chat bubble or an embedded experience. First build and test the agent, including its knowledge and any connected actions. Then configure and test the website where visitors will use it.

Choose where the agent may appear

Open the agent’s Share & embed page and select its website channel. Under Allowed websites, list the hostnames where the embed should load. Use the actual hostnames for your intended destinations, including a staging site if you need to test there. The editor supports a wildcard such as *.example.com for subdomains. An empty list allows any website to add the agent. Restrict the list when you want the embed limited to your own sites, then save and publish the setting. The agent’s share link works separately; the allowed-websites list controls embeds and does not make that link private. Treat the link and the information the agent can disclose accordingly.

Install the code

  1. Publish the agent. An unpublished agent cannot load on a visitor’s site.
  2. In Share & embed, find Put it on your site and copy the generated embed code. The page includes installation directions for common site platforms and a general HTML option.
  3. Add the code using your site’s supported custom-code mechanism. For a plain HTML site, the provided instructions place the launcher code before the closing body tag, or in a shared footer or layout.
  4. Save and publish or deploy the host site according to its own workflow. Check the page that visitors actually use, not just the site’s editor preview.
A site builder may restrict custom scripts. Check its current plan and settings if you cannot add the code; an inline or direct share link may be a better fit for a destination that does not support the launcher.

Verify and troubleshoot

Open the published host page in a separate browser session. Confirm the bubble appears, opens, and answers a representative question. Test a smaller viewport and the intended handoff. Review any form or consent prompts that apply to the published agent. The install section reports sites where the agent has been seen. If a site is marked blocked, check its hostname against Allowed websites, save the correction, and publish it. If nothing has been seen, check that the code is present on the published page and that the host permits the required script and iframe resources. A restrictive content security policy or a site editor that strips scripts can prevent loading; inspect the host page’s browser errors before changing its settings. The installation status is a useful signal that a page loaded the agent; it does not replace testing a conversation and any connected actions. Remember that test actions can run for real.