An agent opens a ticket: "VPN not connecting." They’ve seen this before — three times this week. The fix involves clearing a cached credential and restarting a service. But instead of remembering the steps or searching through old tickets, they type "VPN" into the knowledge base search, find the article, and walk the user through the resolution in two minutes.
That’s the promise of linking KB articles to tickets. GLPI supports this natively — and when configured well, it turns the knowledge base from a static library into an active tool embedded in the resolution workflow.
How KB linking works in GLPI
When an agent opens a ticket, they can search the knowledge base directly from the ticket interface. GLPI shows matching articles based on the ticket’s category and text content. The agent can:
- Apply a solution from a KB article — the article content becomes the ticket solution, linked back to the source article
- Link an article as reference — "This article was used to resolve this ticket" without copying the content
- Create a new KB article from a ticket — after resolving a novel issue, convert the solution into a reusable article directly
Category-based KB suggestions
The real power comes from associating KB articles with ticket categories. When you tag a KB article with the category "Network > VPN," any ticket created in that category will automatically suggest relevant articles to the agent.
This means:
- New agents don’t need to know the KB exists — it presents itself
- The most relevant articles surface first, not everything matching a keyword
- Agents see solutions before they start diagnosing, which speeds up first-call resolution
To set this up: edit each KB article and assign it to one or more ticket categories. GLPI uses this mapping to filter suggestions when a matching ticket is opened.
Measuring KB effectiveness
A knowledge base without metrics is a knowledge base you can’t improve. Track:
Article usage rate
How often is each article linked to a ticket solution? Articles with high usage are clearly valuable — keep them updated. Articles that exist but never get linked are either unfindable (bad title, wrong category) or irrelevant (outdated, too niche).
First-call resolution by category
Categories with good KB coverage should show higher first-call resolution rates. If they don’t, the articles might not be answering the right question — or agents aren’t using them.
Time to resolution with vs. without KB
Compare resolution times for tickets where a KB article was used versus tickets resolved without one. The difference quantifies the KB’s value in minutes saved per ticket.
Building the feedback loop
The knowledge base should grow from ticket resolutions, not from a documentation project. The workflow:
- Agent resolves a ticket with a novel solution
- Agent clicks "Create KB article from solution"
- Article is tagged with the relevant category and marked for review
- KB manager reviews, edits for clarity, and publishes
- Next time the same issue appears, the article surfaces automatically
This turns every resolved ticket into a potential KB article. Over time, the knowledge base reflects what agents actually deal with — not what someone thought they might deal with.