Bots — an assistant that answers from your content and nothing else
Open Bots →A bot is a chat widget for your own website, and the thing that makes it trustworthy is what it will not do: it answers from the knowledge you gave it, and when it cannot find an answer it says so rather than inventing one. Every question it could not answer is filed in a review queue, so the gaps in your documentation come back to you as a to-do list.
Before you start: Bots live in a workspace, so the first screen asks you to make one. A workspace holds your assistants, your team and the pooled credits the answers are billed against.
What Bots makes
- A deployable widget — a public key and a one-line script tag you paste before the closing body tag of your site.
- An indexed knowledge base built from pages you crawl, files you upload and text you paste.
- A conversation log of what real visitors asked and what the bot said.
- An unanswered-questions queue — the questions it could not answer, counted by how often they were asked.
Walkthrough: from nothing to a live widget
Create a workspace, then an assistant
Give the workspace a name, then press Create assistant and name the bot. A new bot opens on the Knowledge tab, because with no knowledge it has nothing to say.
Add knowledge, three ways
Paste text for a policy you can copy. Crawl a site to follow links within one site — it obeys robots.txt, and large sites keep indexing in the background so you can leave the page. Upload files for the documents that were never web pages.
Watch the sources index
Each source shows its state and how many pages and passages it produced. Indexing is not instant; the list refreshes itself while anything is still queued.
Interrogate it in the Playground
Ask the questions a real visitor would ask. Playground answers are not saved to your conversation logs and its failures are not added to the review queue — it is a rehearsal room, not a live channel.
Customise and deploy
Set the persona, the welcome line, the accent colour, the position and the theme. Then the important field: Allowed domains, one per line. The key in the snippet is public, and this list is what actually authorises requests.
Copy the snippet onto your site
One script tag, pasted before the closing body tag on every page. Until a domain is saved the widget answers nobody — including on your own site — and the bot wears a Draft badge to say so.
Come back to the Review tab
It shows how many conversations were handled without the bot saying it did not know, how many visitors asked for a human, and the queue of unanswered questions. Answering one files it as knowledge straight away.
Options
- Knowledge kinds — crawled pages, uploaded files, pasted text, and answers you write from the review queue.
- Re-crawl — manually, every day or every week.
- Position — bottom right or bottom left; Theme — match the visitor's system, light or dark; plus an accent colour.
- Privacy — mask emails, phone numbers and card numbers in saved transcripts. It applies to what is stored, not to the live reply.
- Talk to a human — an email address, a webhook, or both. Set neither and the offer is never shown.
- Roles — owner, admin, member, viewer. A viewer cannot change a bot; only owners and admins can delete one or change what is deployed.
Limits
- 50 bots per workspace, 50 members per workspace, 20 allowed domains per bot.
- 20 MB per uploaded file. PDF, DOCX, TXT, MD, CSV and HTML are accepted; anything else is refused with a message naming the list.
- 200,000 characters for one pasted text, and for one answer written from the review queue.
- A crawl defaults to 200 pages and can be raised to 1,000. A re-crawl always starts again from the defaults.
- 4,000 characters of persona, 300 of welcome text, up to 6 conversation starters.
- The live widget accepts 30 messages a minute per visitor before it asks them to slow down.
What it costs
Bots is a Max app. Inside it, building costs nothing and answering costs credits:
- Free — workspaces, bots, crawling, uploading, pasting, indexing, settings, the snippet, and every number on the Review tab.
- Costs credits — an answer, whether a visitor asked or you did in the Playground.
Answers are billed against the workspace's pooled quota rather than one person's balance, which is what makes a shared bot workable. When the quota is gone the answer is refused before any model is called, so a busy month cannot overspend.
Frequently asked questions
Will it make things up?
It answers from that bot's indexed knowledge and cites what it used. When nothing matches, it says it does not know and the question goes to your review queue — which is more useful than a confident wrong answer and is the whole design.
The widget is on my site but it answers nobody.
Check Allowed domains. The key in the snippet is public, so the domain list is what actually authorises requests; a bot with no domains saved wears a Draft badge and answers no one.
Does the Playground count as real traffic?
No. Playground answers are not saved to your conversation logs and its failures do not enter the review queue. They do cost credits, because they run the same pipeline as the live widget.
Who pays for the answers?
The workspace, out of its pooled quota, not the individual who happened to build the bot. When the quota runs out answers stop before any model call.
Can I export the conversations?
Not today — there is no download or share link for a transcript. You read them on the Review tab.
How do I keep a crawled site up to date?
Set the source to re-crawl daily or weekly, or press Re-crawl yourself. A re-crawl re-reads the site from the default depth rather than continuing the old one.