An assistant that actually knows your site.
Embed a chat assistant on any website, web app, store or docs site. It answers from your own content rather than guessing, cites what it used, and tells you what people were really asking.
Works anywhere. Deeper on the platforms it connects to.
How do I add the chat to my site?
Copy the script tag from Install and paste it before </body>. It loads after your page does, so it never slows the first paint.
docs/install.mdIllustration. Every figure and answer here is invented.
Any site with questions, not just a storefront.
Websites
Marketing sites, landing pages, portfolios. It reads what you publish and stops the same three questions reaching your inbox.
Web apps
In-product support that knows your plans, limits and settings — so 'where do I change this' is answered where they already are.
Online stores
Pre-purchase questions answered on the product page itself — sizing, materials, delivery and returns, from what you already published.
Documentation
Docs and knowledge bases, where the answer exists but nobody can find it. Cited, so they can go and read the source.
Answers from your content, not from its imagination.
Analytics that answer questions
What people actually asked, clustered by topic — and what it could not answer, which is a training to-do list rather than a vanity metric.
Trained on your content
Pages, files, pasted text, and exact question-and-answer pairs it may never paraphrase.
Safe by construction
Sensitive fields never enter the context, so no prompt can talk them out of it.
Fits where you put it
Bubble, panel, or inline on the page. One setting, not a fork.
Test what it says
Test the answers themselves, with deterministic assignment and a metric chosen up front.
Integrations, not a rewrite
The product is complete before any of these. A connector adds what a platform knows — a catalogue, a ticket history, a CMS — and removing it leaves everything else working.
Complete on its own. Deeper where it connects.
Any site
The base product, and it stands on its own:
- Custom training — files, pasted text, FAQ pairs
- The widget, its branding and its placement
- Conversations, analytics and A/B testing
With a connector+
Everything above, plus what only that platform can tell it:
- Content read from the source, not from the rendered page
- Kept fresh on its own, rather than re-crawled
- Actions inside that platform, off until you turn them on
- Shopify is first. Help desks, CRMs and CMSs follow.
Four steps, and the last is the interesting one.
- 01
Create a workspace
Sign in and name the site, app or store you are putting it on. One workspace per surface.
- 02
Give it something to know
Upload files, paste text, write FAQ pairs. Connect an integration and pick exactly which of its content it may use.
- 03
Try it, then ship it
Talk to it in the playground until it is right, style it to match, then drop in the embed.
- 04
Watch and improve
Read the questions, fill the gaps it could not answer, and test changes before they go live.
Not built yet, and here is what is coming.
Human handoffSoon
When it cannot resolve something, hand the conversation to a person with the transcript attached.
More connectorsSoon
Help desks, CRMs, CMSs and commerce platforms — each adding its own knowledge and its own actions.
MultilingualSoon
Answer in the language the visitor asked in, from a catalogue written in one.
The ones people ask first
Put it in front of the questions you keep answering.
Create a workspace, give it your content, and see what people actually ask.
Get started