Answer Cloud adds its embed settings and script to published hosted pages. Keep the generated integration and configure the site's widget through the supported platform controls. Adding another manual embed to Astro source can create conflicting settings or duplicate collection.
Inspect the current site#
Ask your connected agent to list organizations and sites, then inspect the exact site slug. Review its current widget state and stored configuration before changing it. A familiar display name does not establish that it is the intended production site.
The supported configure_widget operation controls whether the site's generated chat is enabled and can store its supported labels, greeting, and custom stylesheet. Chat availability also depends on the site's plan; a configuration value cannot grant a feature that is unavailable to the site.
Change the label and greeting#
This example shows the argument shape. Replace the target and text with the real site values:
{
"organization_id": 123,
"site_slug": "example",
"enabled": true,
"config": {
"chat": {
"button_text": "Ask Example",
"intro_text": "What can we help you find?",
"button_text_color": "#1a1b1c"
},
"css_path": "https://example.answer.cloud/assets/chat-theme.css"
}
}
The stylesheet must already be publicly available at its absolute HTTPS URL. Build and deploy that asset before configuring the URL.
Supplying config replaces the stored widget configuration. Preserve the existing stylesheet and other intended settings when changing one field. Passing an empty object resets custom settings. Omit config when you only want to toggle enabled without discarding the theme.
Keep settings within their supported scope#
The generated hosted integration includes organization/site routing, chat configuration, analytics availability, and supported stylesheet settings. It does not pass every possible external window.aeoSettings option through from config.
For example, do not assume adding site_search or arbitrary analytics consent options to the widget config enables those features on hosted pages. Use the supported configuration path for the specific feature and ask support when an integration needs controls beyond that path.
Verify the live result#
Open a published page after configuration. Confirm the launcher text, greeting, and readable color. If you changed a theme, inspect both the launcher in the host page and the conversation inside its iframe. Check desktop and mobile, focus visibility, a completed exchange, and whether the composer stays reachable with a long answer.
Local Astro preview does not include platform injection. A successful configuration response or CSS request alone cannot verify the actual widget. If a live page has no launcher, inspect its publication and generated settings before editing Astro to add another script.
See appearance and accessibility, answer checks, and widget tool reference.