You cannot write the page you do not know is missing. Amvio hits the gap every day, works the answer out from the product, and keeps the list ranked by what each one costs you.
gaps a content team can see until somebody complains
undocumented field is enough to cost a customer a night of work
question it cannot answer becomes an entry on the list
Every page is read and structured, so it knows precisely where coverage ends.
Discovery walked the product itself. When the product does something the help centre does not mention, that difference is the gap.
The gap becomes visible the moment a customer asks about it, which is months before anybody files a content ticket.
The reasoning it had to do is the first draft of the page. You are editing, not starting.
A gap asked four times that cost an account is above one asked ninety times that cost thirty seconds.
Drafts the answer it already gave
With the reasoning and the sources it used. You are editing, not starting.
Reopens an entry when the asks return
A page that did not solve it comes back onto the list with the new phrasings.
Which gap costs the most
Ranked by accounts affected and consequence, not by frequency.
What your users call the thing
The vocabulary mismatch between your help centre and your customers, listed.
Publishing to your help centre
It never writes to your site. A human decides what your help centre says.
Inventing coverage
If neither your material nor the product supports an answer, it says so and logs it.
Six ways the gap becomes visible, none of which require anybody to file a ticket.
A required field nobody wrote down.
A seller lost 340 listings the night before a sale. It was asked, answered, and logged the first time it happened.
Two pages, neither of which finishes the thought.
The reasoning it had to do to answer is the page that should exist.
They search for a word your help centre does not use.
It answers anyway, then reports the vocabulary mismatch as a finding.
The product changed and the page did not.
Discovery re-walks each release and reports where the page and the product now disagree.
They found their own way round it and said nothing.
It is in the transcript, which is the only place that kind of gap ever appears.
You wrote it, and the asks kept coming.
The entry reopens with the new phrasings attached, so you can see what the page missed.
Know which documentation is missing.
The gap list, ranked by cost, updated the day a customer hits it.
Write from real user language.
Every entry carries the transcripts, in the words they used.
Keep the help centre current with the product.
Discovery re-walks each release and reports the disagreements.
Prioritise against limited writing time.
Ranked by accounts affected, so a rare expensive gap outranks a common one.
Prove documentation had an effect.
Asks against a closed gap fall to zero, and the fall is in the record.
You cannot write the page you do not know is missing. This is the list of the ones you do not know about.
Nothing is broken and no ticket exists. The only thing happening is that people keep asking, in places nobody is counting.
a guess at the question
the transcripts
by intuition
by accounts affected
none
asks fall to zero
340 listings were lost overnight to one undocumented field. The gap had been asked about for weeks.
It does not publish anything to your help centre. It writes the list, drafts the answer, and shows the evidence — a human still decides what your documentation says.
The first gaps appear.
Usually three or four, and usually surprising.
They get ranked by cost.
One of them is expensive and nobody had noticed.
You are shipping against evidence.
With a draft answer attached to each entry.
Coverage is measurable.
Gaps closed, asks eliminated, in the same view.
content tickets needed for a gap to appear on the list
draft attached to every entry, from the answer it gave
entry ranked by accounts affected, not by volume
asks once the page actually solves it
It drafts, from the answer it already gave and the sources it used. Publishing is yours — it never writes to your site.
From the people who bothered to file one. This is from everybody who hit the gap, including the ones who worked around it silently.
Then the list will be short, and the few entries on it will be the expensive ones. That is a useful result either way.
By accounts affected and consequence, not by frequency — so a rare gap that cost someone 340 records outranks a common trivial one.
The entry reopens when the asks come back, with the new phrasings attached. That is the only real test of a page.
There is nothing to configure. The gap list is the difference between what your help centre says and what your product does, and it starts filling on day one.
<script src="https://cdn.amvio.ai/a.js" data-key="acme_live_8f2c"></script>Point it at your help centre
Every page is read and structured, so it knows exactly where coverage ends.
Walk it through the product once
The difference between the product and the pages is the first version of the list.
Read the list on Monday
Ranked by cost, with a draft and the transcripts attached to each entry.
Not eight products with eight logins. One specialist with one memory, which is the only reason the renewal conversation knows about the onboarding one.
Forty accounts known properly, and the nine that need a person handed back.
An implementation call for the eighty percent who got a welcome email.
The three people who know the whole product, available to six thousand at once.
Tier one resolved in the product, escalated with the transcript attached.
The technical answer at 2am, during the trial, not next Tuesday.
Everyone who was confused, at the moment they were confused.
The gap list, ranked by what each missing page actually costs.
Decided seven months before the date, with time left to fix it.
Your users are already having the conversation. Right now it is with nobody.