Chat Widget
A support assistant you train on your own content. Embed it on any site and it answers your visitors with your material, and stays honest when it does not know.
Why teams use it
Answers from your own content
Train it on your pages, your documents and your folders. It replies with your material instead of inventing an answer, and says when it does not know.
Embed once, works everywhere
One script tag. It renders in an isolated shadow DOM so your site CSS cannot break it, and it cannot break your site.
Grounded and refuse-capable
If a question falls outside what you trained it on, it declines rather than guessing. Visitors get accuracy, not confident nonsense.
Yours, visually
Logo, colours, launcher position and widget tier are all configurable, and the branding is delivered at request time so changes apply without redeploying your site.
Manageable training sources
Add or remove sources from a dashboard, run ingestion, and preview exactly which chunks a question will match before you go live.
A real SDK, typed
The chat widget SDK is framework-agnostic with a typed API surface, so you can drive it from your own code, not just the embed.
Use cases
Where a trained assistant beats a static FAQ page.
Customer support deflection
Answer the repetitive "how do I…", "what does it cost", "do you support…" questions on your site before they become tickets.
Product documentation assistant
Point it at your docs and let users ask questions in plain language instead of hunting through pages.
Internal knowledge base
Train it on your handbooks and process docs so staff get consistent answers instead of asking whoever is online.
Onboarding companion
Give new users an assistant that answers with your onboarding material, available the moment they land.
Pre-sales qualification
Answer buying questions accurately from your real product information, and hand off to a human when it cannot.
Multi-page site coverage
Train across many pages at once so the assistant understands the whole site, not one corner of it.
Embed it in a minute
Add the snippet, point it at your widget, and train it. Full details in the SDK documentation.
<!-- Drop this where your site's scripts go -->
<script>
window.ThinkFlyFlow = {
widgetId: 'YOUR_WIDGET_ID',
publicKey: 'pk_...',
}
</script>
<script async src="https://cdn.thinkflyflow.com/widget.js"></script>Read the documentation
Embedding, configuration, theming, events and the typed API surface.