Embeddable widget
The embeddable widget puts an Ask agent on a partner website, for customer self-service, citizen-facing assistants, and similar outward-facing use cases. End users see a chat bubble; the full conversation lives in Ask.
Prerequisites
-
You are an admin or developer integrating Ask into a host website.
-
Your Ask organization has the widget enabled.
-
For end users, no setup at all: you only need to open the host site.
What end users see
On the host website, a chat bubble in the corner. Click it and a panel slides out with a chat input. From here it behaves like a focused Ask conversation:
-
Send a message, get a streamed reply.
-
Open citations to the underlying knowledge.
-
Start a fresh thread by clicking New session (or refreshing the page on the host site, where applicable).
How sessions work
The widget uses session tokens issued by the host site so each visitor gets a fresh conversation. It supports new session behavior via those tokens, and history stays in the standalone Ask app.
In practice: a visitor's conversation lives inside the widget for the session, but the full conversation history (and any downstream analytics) lives in the standalone Ask app, not on the host site.
When to use the widget
- You want a focused, branded chat experience on a website you do not control end-to-end (for example a customer portal or partner CMS).
- You want stateless visits, where each session is a fresh start.
- You want answers grounded in your Ask knowledge bases, with citations.
When the standalone app is a better fit
- The user already has an Ask account and you want continuity across conversations.
- You need multi-agent workflows, advanced tools, or admin features.
- You want the full sidebar, history, and Knowledge views.
Tips & gotchas
The widget is intentionally minimal. If you need richer chrome (agent picker, history, knowledge browsing), link out to the standalone Ask web app instead of trying to recreate it inside the widget.
In some on-prem deployments the widget is the primary channel, paired with backend speech-to-text. Configuration in those cases is tightly coupled to the deployment, so your widget setup may differ.