Knowledge Base in helpdesk -
how to reduce repetitive tickets?

A significant portion of helpdesk tickets are repeat questions: how to change a password, where to find files, how to log in to a system. The employee waits for an answer, the technician explains the same thing once again. A well-built Knowledge Base changes the pattern - employees find the answer quickly on their own and technicians can focus on harder cases. In this article I break down how to build a Knowledge Base, tag articles, integrate it with ticketing and use an AI bot to answer FAQs.

Knowledge Base structure - categories, tags and search

A Knowledge Base without structure is exactly like a wardrobe with no drawers - everyone throws something in, nobody finds anything.

Main categories: 5-10 top-level categories:

• Accounts & Access: password, VPN, SSO, MFA, PIN reset
• Email & Communication: Outlook, Teams, Slack, email client setup
• Collaboration: SharePoint, OneDrive, Teams, Google Drive
• IT systems: SAP, ERP, CRM, Jira, Azure
• Hardware & devices: laptop, monitor, printer, VoIP phone
• Security: antivirus, firewall, secure VPN, phishing
• Procedures: first-time login, how to work remotely
• Troubleshooting: internet down, app frozen, slow PC

Tags (multiple tags per article): #password, #reset, #mfa, #office365, #teams, #vpn. Tags let an article be reached from multiple angles.

How to write Knowledge Base articles - practical format

KB article template:

1. Title (short, in question form): "How to change your Active Directory password?"
2. Summary (1-2 sentences): "This article explains how to change your company account password directly or through the self-service portal."
3. Steps (numbered, clear): Step 1. Click the user icon in the top corner. Step 2. Choose "Change password". Step 3. Enter the old password, then the new password (min. 12 characters, 1 uppercase letter).
4. Screenshot or video: Show the procedure visually - people learn faster.
5. Troubleshooting (if something went wrong): "If you get the error 'Password does not match complexity', the password does not meet the requirements. Try xxx."
6. Related articles: Links to related items (for example "How to change a password - on macOS" or "How to reset a forgotten password").
7. Publication date and version: "Last updated: May 2026, applies to Office 365 vXXX"

KB integration with ticketing - ManageEngine SDP

The magic connection: when a technician handles a ticket, the system suggests a KB article that could resolve the issue.

• Setup: Admin → Knowledge Base → Enable article suggestions when creating a ticket
• How it works: The technician opens a ticket (category = "Password Reset"). The system automatically searches KB articles with the same tag (#password). It shows 3 suggestions: "How to change a password", "Password reset - forgot password", "Password complexity requirements".
• Benefit: The technician can send a link to the article instead of writing instructions from scratch. The employee reads the KB article instead of waiting for a reply.

Self-service portal - where employees look for answers

A Knowledge Base without visibility is a Knowledge Base nobody reads. You have to make it easy to access.

• Self-service portal: ManageEngine SDP has a built-in portal. The employee logs in, sees the KB categories (Accounts, Email and so on), clicks a category, sees a list of articles, reads, solves the problem. The portal must have a search bar (type "VPN" - return 5 articles about VPN).
• Chatbot on the portal: A more advanced option - a chatbot that asks "What is the issue? Password reset? No internet? Printer offline?" - and suggests a KB article based on the answer.
• Link in the ticket: When an employee submits a ticket, the email confirmation includes a link to KB articles on that topic.

AI FAQ bot - let AI handle simple questions

The next level: instead of a technician, a bot answers the question based on the KB. If the bot does not know, it escalates to a technician.

• How it works: The employee asks the bot: "How do I change my password?" The bot searches the KB, finds the article, summarizes the answer and sends it. The employee does not have to wait 4 hours.
• Tech: ManageEngine Zia (AI in SDP) can do this. Or, more advanced - integration with OpenAI GPT + Knowledge Base (the bot has access to the KB and answers like ChatGPT but based on your articles).
• Benefit: The bot picks up part of the simple, repetitive questions so technicians can focus on complex problems. Response time for typical questions drops from hours to minutes.

Knowledge Base metrics - what to measure and optimize

KPI #1: Article views per month - how often people read the KB. Target: rising trend (if the KB is good, people read it).

KPI #2: Self-service resolution rate - percentage of tickets resolved through the KB without contacting a technician. This is a key effectiveness metric for the knowledge base - set your own target and watch the trend over time.

KPI #3: Ticket volume trend - is the number of repetitive tickets dropping as you add and improve KB articles? Watch the direction of change rather than expecting a fixed percentage.

KPI #4: Article quality score - are the articles useful? ManageEngine lets employees rate articles (thumbs up/down). A high share of positive ratings means the content is actually helping.