Featured
Start here: what to train an assistant on
Source selection is the highest leverage decision and the one most often made without thought in the first ten minutes.
Resources
Everything written down, sorted by what you are trying to decide.
Creobot opens to teams in order, so this is documentation and writing rather than a product tour. It is grouped by the question you arrived with: how these systems work, whether this one fits, what happens to your data, and where the product actually is.
- Private launchOnboarding selected teams now
- Answers from your pages onlyIt refuses when your content does not cover it
Start here
Featured
The 72 term glossary
Every term that changes a decision when building, buying or running a website assistant, each with why it matters rather than just a definition.
Featured
Pricing, with the full comparison table
Four plans priced per conversation rather than per seat, and a 22 row table so you can see what each one actually includes.
Learn
Read these if you are trying to understand how these systems actually behave before choosing one.
- Blog, 32 articles
Retrieval, routing, handoff, analytics and the decisions behind each.
- Glossary, 72 terms
Searchable, filtered by category and A to Z, with cross references.
- Retrieval explained
What RAG is, in plain terms, and where quality is actually won.
- What visitor questions reveal
Reading chat logs as a content map rather than a support cost.
Decide
Read these if you have shortlisted tools and need to know which fits your situation, including when ours does not.
- Comparisons
Including where we lose, and where another tool is better.
- Use cases
Eight places teams put an assistant first, with the limits of each.
- Features
How the six capabilities work and which are still planned.
- Questions to ask any vendor
Including the ones that make us uncomfortable.
Trust
Read these if you are the person who has to sign off on where customer data goes.
- Security and data boundaries
Design positions, and what is not settled yet.
- Privacy
What is stored, for how long, and what we do not claim.
- Subprocessors
Every party in the processing chain.
- Data boundaries, plainly
What a data boundary is and how to read one.
Launch
Read these if you want to know whether you can use this yet, and what it will cost when you can.
- Pricing
Pricing. Not final, no checkout.
- Ask a question
Answered by the people building it, not a queue.
- Support
What help looks like during private launch.
Questions
With choosing what to train it on. Nearly every complaint about answer quality traces back to an index that was too broad, and that decision is made before anything else.
No. Creobot opens to teams in order, through the waitlist rather than open signup. Everything here is reading material and product documentation rather than a product you can switch on.
The retrieval explainer if you want to understand how these systems work, or what visitor questions reveal if you want the commercial argument.
Yes, deliberately. Every comparison page names a case where the other product is the better choice, and every feature page separates what is built from what is planned.
No. It describes how website assistants work in general. Where Creobot makes a particular choice, the feature pages say so rather than the glossary.
It is written alongside the product, so it changes as the product does. Anything describing a capability that is not built says planned, and that wording is checked before every release.
Ask on the contact page. A person replies. There is no drip sequence, because there is no product to onboard you into yet.
Launch
Cannot find what you were looking for?
Ask directly. Creobot is not open to general signup, so questions are answered by the people building it rather than a support queue.