Knowledge is everything Amvio can answer from: what it learned by walking your product, and what you have already written — turned into answers rather than pages, and approved by you before any of it reaches a customer.
Where two of them disagree, it matters enormously which one said what. Flatten them together and you have thrown away the only thing that could settle it.
What Discovery recorded by being walked through the software. The only source that describes the product as it is today rather than as somebody described it once.
The things said out loud during a walk, or typed into Studio afterwards. Short, high-value, and the only source that carries intent — why a rule exists, not just that it does.
Crawled and kept. Excellent for the things it covers, and silent on everything it does not — which is most of what people actually get stuck on.
Notion, runbooks, the document your support team keeps for themselves. Usually the best-written knowledge in the company, and usually the only copy is in one team's head.
It proposes, you decide. There is no state in between where something it worked out quietly starts speaking to your customers.
What Discovery learned from walking your product, plus the material you have already written — a help centre, a Notion space, documents you upload. Where the two disagree, it knows which one it watched happen.
Not kept as pages. Separated into the things your product actually has — a concept, a rule, a workflow — so “what is a health score” and “how do I raise one” are two questions it can answer two ways.
Everything it writes waits for you, and nothing that is waiting can answer a customer. Somebody on your side reads it and approves or declines it. What you decline is kept so you can see what was proposed, and is never used.
Which is why searching your documentation so often returns the right page and leaves the reader to find the sentence. Amvio is looking for the sentence.
“How many rows can I put in one import file?”
Returns the Bulk import page. The person now reads six paragraphs looking for a number, on a screen they opened because they were already stuck.
“Five thousand rows per file — split anything larger and the second file imports on its own.” Then it can see whether theirs is larger.
Finding the right document is not the same job as answering the question, and your users have never wanted the first one.
This happens constantly, and it is the moment where most systems quietly pick the wrong one. Here it is not a tie to be broken — it is already ranked.
“Exports are limited to 1,000 rows per file.”
“A file may contain up to 5,000 rows.”
“It went to 5,000 in the spring, and the doc was never updated.”
A person explaining something outranks a screen, and a screen outranks a document. Not because documents are bad — because they are the only one of the three that cannot have changed since it was made.
Every system like this picks one of two ways to fail. It is worth knowing which one you are buying, because your customers meet it on their worst day.
The lookup finds nothing exact, so it returns the closest thing it has and writes around it. The user gets a confident paragraph about a neighbouring feature and acts on it — and neither of you finds out until something has gone wrong twice.
It says it has nothing on that, offers the nearest thing it is genuinely sure of, and the question goes on the list your team reads. Nobody is misled, and you find out the same week that people are asking.
The cost of that choice is real and worth stating: occasionally it will decline a question it could have half-answered. That is the trade being made on purpose.
Which is the reason most of them quietly become wrong. Three things keep this one from going the same way, and none of them is somebody's quarterly task.
Everything carries when it was last confirmed. Something nobody has checked in months does not get to answer with the same confidence as something confirmed this week.
When a fact changes, the old one is retired and points at what replaced it. Nothing quietly fades — you can see what it used to believe and when it stopped.
Every question that comes back empty is recorded. If your product moved and nobody re-walked it, that shows up as a list of questions rather than as silence.
A knowledge base is defined as much by its exclusions as by its contents, and these three are the ones that would quietly poison everything downstream.
The things Discovery could not establish are tracked as open questions and closed as they get answered — and they never quietly turn into answers. A gap must not become a claim.
Anything your team declined stays declined. It is kept so you can see what was proposed and what you decided, and it never reaches a customer by any route.
“The page has no export button” is not the same claim as “this product cannot export”, and the second one is never inferred from the first. Turning absence into a claim is the most confident kind of wrong.
That is the question a documentation search cannot pass and this is built to. It is also the fastest way to tell the two apart.
A map with nobody to ask. A conversation with nothing to draw on. A memory of a product it never learned. The system is the point.
A conversation inside the product, on the screen they are stuck on — spoken, and able to see what they are looking at.
read the page →Where it stops. It says it does not know, refuses the three subjects you never want answered, and promises nothing it cannot keep.
read the page →It walks your product screen by screen and writes down what it found, in a 22-section record per page — including what it could not establish.
read the page →Your maps and docs compiled into things it knows, held at two grains so a single fact inside a long document can still be found.
you are hereWhat it handled, what it learned, what it could not answer, and which accounts have gone quiet — for the people who own the product.
read the page →Where you set what it is, how it speaks, what it must never touch, and which pages it appears on. Settings that become instructions.
read the page →Your users are already having the conversation. Right now it is with nobody.