Embed a support widget as a launcher, page, or pane

A Heliune widget is a workspace object, not a second inbox. You draft it in the widget builder or from the builder agent in the rail. Install copies a snippet. Visitor messages open a widget-channel thread in the same inbox the team already works.

The live frame at /widget/{id} is noindexed on purpose. Search should find this note, not the chat iframe. The public boot script is /widget/{id}.js.

Three embed placements

• Floating: a script before </body> mounts a launcher. The open window is a corner panel, a centered popup, or an edge sidebar.
• Page: an iframe for a dedicated support or help URL. Give the host a height; the chat fills it. The snippet uses a 640px minimum.
• Pane: the same iframe pattern for a product sidebar, help drawer, or in-app inbox. The snippet uses a 480px minimum.

What the visitor sees before they type

Pre-chat can be empty, the greeting, greeting plus starter chips, or the first message step of the attached chat flow. An optional bubble sits outside the launcher with a hint and FAQ chips. Appearance is a token theme plus optional CSS on stable heliune-widget-* hooks — not the workspace chrome.

How a message reaches the inbox

Each visitor keeps a thread keyed by widget id and visitor id. The first message opens an inbox conversation. If a live flow is attached, the graph can reply as the widget and record a flow run on that conversation.

Toggle Enabled before you expect the public frame to answer. Copying the Install snippet is the workspace onboarding signal that the embed left the builder. The rail’s create_widget and update_widget tools write the same config the manual builder edits. Free workspaces show the Heliune mark on the widget; paid plans do not.