Skip to main content
A widget gives visitors an agent interface inside your website. You can review its saved configuration now; a production installation also needs a released embed asset and a working conversation runtime.
A supported production script URL and end-to-end widget session are not established by the current release. The dashboard preview is not an installation contract. Do not copy a development script or expose a workspace API key in page code.

​
Prepare the configuration

1

Choose the agent and audience

Record the workspace, agent, intended branch, and pages where the interface should appear. Review authentication, including public access and allowed origins, before planning an anonymous visitor experience.
2

Review the saved appearance

Inspect platform_settings.widget in the saved agent configuration. It includes placement, colors, avatar, labels, transcript visibility, and feedback options. Check text contrast and use labels that describe the action clearly.A saved option describes the desired interface. Verify that the released widget implements it before relying on it in your site.
3

Choose an installation location

Reserve space for the expanded interface and a fallback contact link. On sites with client-side navigation, plan one widget instance and cleanup when its owner unmounts. For builders, use the no-code guides.
The separate Get agent widget configuration route requires a valid, unexpired conversation_signature; a workspace API key alone does not authorize that read. Signature issuance remains tied to the gated session path, so this route is not a general configuration-read shortcut.

​
Before a public launch

Browser microphone access requires a secure context and user permission. Embedded contexts also need the correct permission policy; a rendered iframe alone does not prove microphone access. See the browser microphone reference.

​
Frequently asked questions

The route requires a valid conversation_signature. An API key does not replace that signature, and the read does not return a production embed script.
No. A text interface still needs a supported session and message transport. A saved text-mode setting does not create that transport.