Documentation
How to actually get this working.
None of it is written yet. Everything below is listed in the order it will be, so you can see what is coming instead of finding out by clicking. Until then, the widget on this page answers from the product itself, and anything it cannot answer reaches us.
Written first
What people need in the first hour, so these are the ones being written now.
Coming
Getting started
Signing up, the crawl, reviewing what it proposed, and getting the widget onto your site.
Coming
The WordPress plugin
Installing, connecting, the four placement rules, and reading cases inside wp-admin.
Coming
Embedding the widget
The script tag, the two embed modes, and verifying the domain the widget answers on.
Coming
Entries and bulk import
Writing an entry, typed attributes, importing a file, and undoing an import that went wrong.
Coming
Sources and syncing
Adding a sitemap or feed, the review step for changes, and what happens when a sync fails.
Coming
Routing and webhooks
Sending cases to an inbox, to email per state, or to a signed webhook.
After those
Written next, in roughly this order.
- Coming Widget theming - The token and slot reference. Public, because the widget is open source.
- Coming Identity hints - Telling the bot who it is talking to, and what the inline embed mode refuses.
- Coming Connected APIs - Pointing the bot at a read-only endpoint of yours for the things that change hourly.
- Coming MCP access - Reaching your workspace's content from your own AI tooling.
- Coming API reference - The public conversation API, and the endpoints a connected site uses.
The fastest way to ask a documentation question
This site carries the Ask widget, running against these docs. It is the same thing you would install, answering from the same kind of material, and when it cannot answer, the question lands in our inbox as a case - which is how these pages get written.