The widget, explained
The widget is a launcher button that sits in the corner of your site. Clicking it opens a panel with everything a visitor might need.
What's inside the panel
Search — the default view. A visitor types a question and gets an AI answer with numbered citations, plus the matching articles underneath. Answers are drawn only from your content.
Browse — your collections and articles, for visitors who'd rather look around than search.
Chat — a conversation rather than a one-shot question. The agent remembers the thread, can run additional searches mid-conversation, and cites as it goes.
Contact — how to reach a human. Email, phone, or your live chat provider, depending on what you've configured. See Contact options.
Announcements — if you've published any, visitors see an indicator. See Announcements.
How it loads
The widget is a single async script that renders into its own container at the top of the page stack. It doesn't block page load, doesn't need a build step, and doesn't require any framework.
Configuration is fetched at runtime, so changes you make in the dashboard appear on your site without re-deploying anything and without changing the snippet.
Context it collects
To make support conversations more useful, the widget collects a small amount of session diagnostics and sends them with chat messages:
- The current page URL and route
- Recent failed network requests (URL, method, status code)
- Console errors
- Form validation errors
This is what lets a visitor say "it's broken" and get a useful reply. It's diagnostic data about your own app, not tracking — the widget doesn't set advertising cookies or follow visitors across sites.
If you identify logged-in users, their details are attached too.
Making it yours
- Customizing the widget — colours, position, logos, text
- Widget behavior — auto-open, mobile, AI toggles
- Page rules — different behaviour on different pages