Plan requirement
| Subscription | Suite Professional or higher |
| Access | Admin |
Yes, through Explore. The standard dashboard covers most of it; one report you build yourself covers the part that matters.
What comes as standard
- Views per article, and how they change.
- What people searched for, including searches that returned nothing.
- Votes and comments.
- Which articles agents link into tickets.
That is enough for the everyday questions: what is read, what is not, and what people cannot find.
The report worth building
Ticket volume by subject, over time, against when you published articles on that subject. That is the only report that shows whether the knowledge base is doing its job, and it is the one nobody builds.
It takes an afternoon and it is what makes the case for the next afternoon.
Compare, do not count
A number on its own says nothing. Twelve thousand views is good or bad depending on last month. Set every measure against the period before it and the noise falls away.
What the numbers will not tell you
Whether the reader got their answer. Views and votes are proxies, and a heavily-read article with poor votes might be badly written or might simply be about something frustrating.
Reading a few tickets on the same subject settles that faster than any dashboard.
Share it on a schedule
A report nobody opens changes nothing. Send it monthly to the people who decide where effort goes.
Comments
0 comments
Article is closed for comments.