
Knowledge base management: write it once, keep it current, make it findable
A knowledge base that was written in a burst two years ago is a knowledge base nobody trusts. In Cayzu, fixing an article is part of answering a ticket, so the articles stay right and search finds them.
What a current knowledge base does for customers and agents
A knowledge base you keep current means fewer tickets. An article that answers a question before it's asked can stop a ticket from arriving, and the ones that still arrive can be answered with a link. Agents get a second thing: a private library of procedures and workarounds in the same tool as the tickets, instead of a wiki three tabs away.
And the content stays right, because fixing it is part of answering a ticket rather than a project someone has to schedule.
Related features
- Knowledge baseCustomers search your articles in the portal and the widget on your site before they write in.
- Quick responsesSave the replies you keep sending, then turn the most-sent ones into articles customers can find themselves.
- Multiple languagesEach article can have a version per language, shown to the customer in theirs. On Pro and Enterprise.
Topics, articles, FAQs and news
Topics hold articles the way customers think: billing, getting started, troubleshooting. Articles are how-tos and explanations. FAQs are short question-and-answer pairs. News is dated, newest first, for outage notices and release notes.
Each article is public or private. Public ones appear on the portal and in the widget's search; private ones appear only to agents. The search indexes everything and returns results as people type, so the structure can stay simple.
Editing is in place. Change an article and the portal shows the new version at once. On Pro, an article can carry a version per language.
See it with your own tickets.
Every feature for 15 days. No credit card. No contract.
Setting up your knowledge base topics
- Make four or five topics. Resist making twelve.
- Turn your ten most-sent replies into articles, and the procedures your agents keep asking each other into private ones.
- Give one person the job of fixing any article a ticket proves wrong, the same day.
Knowledge base plans, and the import and brand limits
The knowledge base is on every plan. See the plans.
Articles are written in Cayzu's editor rather than imported from a wiki or a docs site, so moving an existing library is a copy-and-tidy job. And each brand has one knowledge base; separate libraries need separate brands.
Related: the knowledge base, 24/7 self-service, and the self-service portal.
Questions people ask
By topic, the way customers think, not the way your product is built: Getting started, Billing, Your account, Troubleshooting. Cayzu groups articles under topics, and the search cuts across all of them, so the structure is for browsing and the search is for finding.
Yes. Each article is public or private. Private articles are visible to agents inside Cayzu and never on the portal, so internal procedures and workarounds live in the same place as the public how-tos.
An article is a how-to or an explanation. An FAQ is a short question and answer. News is dated: an outage notice, a release note, a holiday hours post. All three are searchable; news is shown newest first.
Edit them in place; the change is live at once. The habit that works is to open the article every time a ticket proves it wrong, fix it then, and check the most-read ten once a quarter.
Every plan. The knowledge base is part of Standard; article versions in other languages need Pro.

Try it with your own tickets
Every feature for 15 days. No credit card. No contract.
