answer.cloud-hosted and companion pages receive the configured chat widget from the platform. Do not add a second embed to those pages. The instructions below apply to a website hosted elsewhere.
Install on an external website
Use your actual organization ID from answer.cloud. Place the settings before the embed script near the end of the page:
<script>
window.aeoSettings = {
organization_id: 123,
chat: {
enabled: true,
button_text: "Ask our AI",
button_text_color: "#1A1B1C",
intro_text: "What would you like to know?"
}
};
</script>
<script src="https://app.answer.cloud/embed.js"></script>
123 is an example, not a usable organization ID for your site. window.aeoSettings remains the supported API name. The working script is served from the application host; do not replace its hostname with the public www host.
Customize the chat
Chat labels belong inside chat. Set chat.enabled to true. Top-level button_text and intro_text are not the current chat contract, and button_color is not a supported color control in the current bundle.
For a custom theme, set a top-level css_path to a publicly accessible stylesheet URL. The stylesheet is loaded in both the host page and chat iframe, so scope selectors to the widget and retain its attribution. Set site_id when the supplied integration needs an explicit site target. See the configuration reference.
Platform integration
On Webflow, use the site’s supported footer custom-code area and publish the site. On WordPress, use a maintained custom-code integration or your theme’s supported mechanism rather than editing a parent theme file that an update could replace. Custom sites can include the snippet in their shared page layout.
Install one copy only. Check that the page loads normally, the launcher opens, and a short question returns an answer grounded in the intended organization’s content. If it fails, verify the organization/site configuration and contact support.