Resources & guides

Vetiu editorial · 3 min read

One support knowledge base for learning, searching and staying up to date

Why shared source articles matter more than putting every document in the same folder, and how to avoid competing versions of the truth.

Illustration of a shared, organised knowledge collection

Centralised is not always unified

A folder containing every document is centralised, but it may still hold three versions of the same policy. A training deck, a team wiki and a saved customer reply can disagree even when all three are easy to find. The challenge is deciding which source should be trusted and keeping the places that use it aligned.

A unified support knowledge base gives each rule a clear home and connects learning and search to that source. It is a content discipline as well as a tool choice: duplicate pages and vague ownership can undermine any platform.

Write once, use in context

Keep the operational rule in one article. A course can teach it in sequence, an agent can search it during a ticket and a quiz question can link to it as the explanation. Those are different uses of the same knowledge, not reasons to create separate policy copies.

Vetiu course chapters link to Knowledge Base articles, so updating the source changes the article wherever it is used in courses. Questions can also link to their source. However, changing an article does not automatically rewrite the wording or correct answer of an existing quiz question; review related questions when a policy changes.

Give agents a structure they can recognise

Agree on a small, consistent topic vocabulary. If the same subject is tagged as Refund, Returns and Refund policy without a deliberate distinction, search and reporting become harder to interpret.

  • Use folders for a stable home: product, billing, delivery, account access or escalations.
  • Use subject tags to connect related articles and questions across folders.
  • Name articles after the situation an agent is trying to resolve, not an internal project name.
  • Put the rule and next action first, followed by conditions, exceptions and examples.

Treat a policy change as a short review cycle

When a policy changes, update the source article, review the course context and check linked quiz questions. Tell the affected team what changed. A source update keeps the material current, but it does not prove every agent has noticed or understood the new rule.

For important changes, follow up with a focused quiz assignment or coaching. Keep a clear responsibility for approving the content; AI writing can help prepare a draft, but it should not invent policy limits or publish unreviewed instructions.

Start with the material people use most

You do not need to migrate every historical document before the knowledge base becomes useful. Start with frequent tickets, risky decisions and the articles your next onboarding cohort needs. Merge conflicting copies and confirm the approved rule with the responsible person.

As the team uses the material, review search issues and quiz results for signals that an explanation is missing or unclear. Add what is needed and remove duplication. The aim is not the biggest library; it is a reliable set of answers that the team can use and maintain.

Put your support knowledge to work

Related reading