About
The interesting question is what it does when it cannot answer
Every product in this category can answer an easy question. What a business is actually deciding is what happens on the one it cannot — whether it guesses, goes quiet, or says so and finds somebody. That decision is the reason this product is built the way it is.
What it does
Three behaviours, not a feature list
Features are easy to match. These are the behaviours the rest of the product is arranged around.
It answers from your material
Your site, your documents, your own written answers — retrieved by meaning rather than by keyword, and cited, so you can check what it used. It is not answering from a model's general knowledge of your industry.
It says when it does not know
Retrieval either found enough to answer or it did not, and that judgement is recorded per message rather than inferred from how confident the reply sounded. A gap becomes something you can go and write, not a wrong answer somebody acts on.
It acts only where you allowed it
Every connected action has one of four settings: run it, ask the customer, wait for your team, or off. A read-only lookup and a refund are not the same kind of thing and are not configured as though they were.
How we build it
Six decisions you can go and check
Anybody can say they care about trust. These are the places it cost something — each one is a choice in the running product, not a sentence written for this page.
Escalation is decided from signals, not from the reply
Whether a conversation reaches a person is worked out from what the visitor did — asked for somebody, complained, went unanswered twice — never from what the model wrote. A customer who asks for a human gets one even when the reply worded the offer badly, or refused outright.
The classifier never sees retrieved knowledge
Working out what a visitor wants happens before retrieval and without it. It decides whether to capture a lead or escalate, so letting a document influence it would hand injected text a lever on the platform rather than on one reply.
Contact details come from the message, never the model
An email address or a phone number is taken from what the visitor actually typed, by pattern match. The model is never asked for them, so it cannot produce an address nobody gave.
A feature is not announced until it has carried real traffic
Every capability named on the home page carries a status label, and those are set by checking rather than by memory. The WhatsApp adapter is written and passes its tests, and it still does not say available, because no live message has gone through it.
One workspace cannot see another
Every query is scoped to a single workspace, and that isolation is covered by tests written specifically to try to break it. Credentials for connected systems are encrypted before they are stored and never shown again.
Nothing here is called finished
The product is in early access and the site says so, including in the footer of this page. Where something is not built, it is listed as not built rather than left off the page to make the list look longer.
Point it at your own material and see what it does
The free plan covers one agent with enough messages to judge it on your own content. No card, and nothing here is charged before you have seen it work.