Knowledge
Give everyone the same trusted answer.
Articles, policies, procedures and pricing, each with an owner, a version and a date somebody last checked it — because an AI answering from unverified documentation is a confident wrong answer waiting to happen.
Verification is the whole point
Knowledge with no owner and no review date is where support answers go stale. The assistant answers only from verified material, so verification is a product mechanism rather than good intentions.
Gaps are found by counting
Eleven customers asked about VAT invoices this week and there is no article. That is a measurable gap, not an impression.
Usage tells you what is load-bearing
An article used in forty-two answers this month is critical infrastructure. One used twice a year probably needs deleting rather than updating.
In this area
6 pages under Knowledge.
Each one is its own surface in the product, and each one is here because it does something the others do not.
Articles
The answers themselves, written once and used everywhere.
ReadVerification
Who checked this, and when.
ReadOwnership
A named person responsible for each answer being true.
ReadKnowledge gaps
Questions customers ask that you have no answer for.
ReadUsage
Which answers are actually doing the work.
ReadWhere knowledge comes from
Your website, docs and policies, brought in rather than retyped.
ReadThe rest of Resolivo
This is one part of one loop.
Take better care of every customer.
Give your team the context, knowledge and AI they need to resolve problems properly — and know who needs attention before they ask.
Keep the mailbox you already use · The AI is never metered · [email protected]