Help Desk Knowledge Base: What It Is and How to Build One

A help desk knowledge base lets customers, employees, and agents solve common problems from searchable articles. See what to include, how to build one, and which tools fit.

Help Desk Knowledge Base: What It Is and How to Build One
Created by
Do not index
Created time
Sep 19, 2023 04:43 AM
A help desk knowledge base is a searchable library of articles that lets customers, employees, and agents solve common problems without opening a ticket, and it helps agents close the tickets that do arrive faster.
TL;DR
  • A help desk knowledge base holds how-to guides, troubleshooting steps, and known fixes inside or next to the ticketing tool.
  • Self-service often fails on content. In a Gartner survey of 5,728 customers, only 14% of issues were fully resolved in self-service, and the most common failure was not finding relevant content.
  • Build it from your ticket data. Write the top ticket reasons first, use one template, and have agents create and fix articles while they resolve tickets.
  • Use the knowledge base your help desk already includes. Zendesk and Help Scout suit customer teams. Freshservice and Jira Service Management suit IT teams.
  • SiteGPT is not a help desk. It is the AI answer layer that reads your articles and answers questions in chat, from $39 a month billed yearly.

Key takeaways

Type
Who reads it
Typical articles
Tool that fits
Customer help center
Customers
How-to guides, billing questions, account steps
Zendesk, Help Scout
IT help desk knowledge base
Employees and IT agents
Password resets, VPN fixes, software requests
Freshservice, Jira Service Management
Internal agent knowledge base
Agents only
Escalation rules, known errors, internal procedures
Any of the above, with restricted articles
AI answer layer
Anyone who prefers to ask
No new articles. It answers from the ones you have
Summary graphic of a help desk knowledge base in four parts: the right articles, one simple template, articles written inside the ticket, and an owner with a review date
Summary graphic of a help desk knowledge base in four parts: the right articles, one simple template, articles written inside the ticket, and an owner with a review date

What is a help desk knowledge base?

A help desk knowledge base is the set of articles a help desk team keeps so that common questions get one correct, reusable answer. It usually lives inside the help desk software, so agents can search it from a ticket and customers or employees can search it from a portal.
The difference from general knowledge base software is the link to tickets. Tickets show which articles to write, and each article exists to prevent or shorten a ticket. For software that holds company knowledge more broadly, see the guide to knowledge base systems.

Help desk knowledge base vs FAQ page vs knowledge base software

Option
What it is
Connected to tickets?
Use it when
FAQ page
One page of short answers
No
You have under about 20 simple questions
Help desk knowledge base
Searchable articles inside the help desk
Yes
You handle tickets and want fewer of them
Standalone knowledge base software
A separate tool for documentation or company wikis
Only through an integration
Your docs serve more teams than the help desk

Why does a help desk need a knowledge base?

A help desk needs a knowledge base because people try self-service first, and most of them do not finish there. Gartner surveyed 5,728 customers in December 2023 and found that 73% use self-service at some point in their journey. Only 14% of issues were fully resolved in self-service.
Stat grid of Gartner survey results: 73 percent of customers use self-service at some point, 14 percent of issues are fully resolved there, and in 43 percent of failed cases customers could not find relevant content
Stat grid of Gartner survey results: 73 percent of customers use self-service at some point, 14 percent of issues are fully resolved there, and in 43 percent of failed cases customers could not find relevant content
Even issues that customers called "very simple" were fully resolved in self-service only 36% of the time. The most common reason for failure was content: in 43% of cases, customers could not find anything relevant to their issue.
Those numbers point to the job of a knowledge base. It has to contain the answer, in the words people search for, and it has to stay current. A good knowledge base gives a team three results:
  • Fewer repeat tickets. One article can answer the same question for every person who asks it.
  • Faster resolution. Agents search for a known fix before they work the problem from scratch.
  • Consistent answers. Every agent gives the same steps, and new agents can learn from the same articles.

What are the types of help desk knowledge base?

The three types of help desk knowledge base are the customer help center, the IT help desk knowledge base, and the internal agent knowledge base. Many teams run two of them in one tool and control who sees each article.

Customer help center

A customer help center is a public site where customers search for answers about a product or service. It should use the customer's words and avoid internal terms. Teams that also offer chat can compare the options in the guide to help desk chat.

IT help desk knowledge base

An IT help desk knowledge base is an employee-facing library for internal technology problems. It usually sits behind single sign-on in a service portal. These articles belong in most IT help desk knowledge bases:
  • Password resets and account lockouts
  • Multi-factor authentication setup and new-phone steps
  • VPN connection errors
  • Wi-Fi, printer, and meeting room setup
  • New laptop and new starter setup
  • Software access requests and approved software lists
  • Known errors with a workaround and a status
Teams that want employees to ask these questions in chat can compare the AI chatbots for IT support.

Internal agent knowledge base

An internal agent knowledge base holds what only agents should see. That includes escalation rules, refund limits, diagnostic steps, and notes on known defects. Keep these articles restricted, because a chatbot or portal that can read them can also repeat them.

How do you build a help desk knowledge base?

You build a help desk knowledge base by starting from ticket data, writing the most common issues first, and making article work part of ticket work. These seven steps cover the order.
  1. Export 90 days of tickets. Group them by reason and sort by volume. The top 20 reasons are your first 20 articles.
  1. Pick one reader for each article. A customer article and an agent article on the same issue need different words and different detail.
  1. Agree on one template. Use the same fields in every article. The next section gives a simple one.
  1. Write titles in the reader's words. Copy the phrasing from ticket subject lines. A title such as "VPN says authentication failed" beats "VPN credential troubleshooting".
  1. Put search where tickets start. Show article suggestions on the request form, in the portal, and in the agent's ticket view.
  1. Assign an owner and a review date. Every article gets one named person. Review high-traffic articles every 90 days and archive what no one uses.
  1. Make articles part of closing a ticket. Gartner advises enabling reps to create knowledge as part of resolving an issue, and not as a separate process. Agents search first, then link, fix, or create an article.

The KCS article template

Knowledge-Centered Service (KCS) is a method from the Consortium for Service Innovation for creating and reusing knowledge while solving issues. KCS captures articles during the interaction, not after the fact. Its article structure works well as a help desk template.
Field
What goes in it
Example: IT help desk
Issue
The problem in the requester's words
VPN says authentication failed after a password change
Environment
What is true for this person's setup
Company Windows laptop, VPN client, password changed today
Resolution
The answer or the steps
Sign out of the VPN client, remove the saved password, and sign in with the new one
Cause
Why it happened, if known. This field is optional
The client still holds the old saved password
KCS also treats a knowledge base as work that never finishes. Its Solve Loop covers capturing and improving articles during tickets. Its Evolve Loop covers content health and reviewing the system as a whole.

How much time can a help desk knowledge base save?

A help desk knowledge base saves time in proportion to the tickets it prevents. This worked example uses a hypothetical IT help desk, and every number in it is illustrative. Replace the inputs with your own ticket data.
Input
Value
Tickets a month
1,500
Tickets from the top 20 reasons
600 (40%)
Share of those tickets solved by an article
20%
Tickets avoided a month
120
Agent time per ticket
15 minutes
Agent time saved
30 hours a month, or 360 hours a year
Use your own measured rate. Gartner's 14% figure is a reminder that self-service results can be low, so a small estimate is safer than a large one.

Which metrics show a help desk knowledge base is working?

Five metrics show whether a help desk knowledge base is working. Review them every month.
Metric
What it tells you
What to do when it looks bad
Searches with no result
Which content is missing
Write the article or add the missing term to a title
Tickets on documented topics
Whether people find the article
Improve the title, or show the article on the request form
Tickets closed with a linked article
Whether agents use the knowledge base
Add article search to the ticket workflow
Article flags and low ratings
Which articles are wrong or unclear
Let customers and agents flag content, then fix it
Articles past their review date
How much content may be stale
Review it, update it, or archive it

5 tools for a help desk knowledge base

These tools were selected for one job: running a knowledge base next to a ticket queue, or answering from one. Four criteria decided the order:
  • Knowledge base on the plan. The article tools are included, with a clear entry plan.
  • Link to tickets. Agents and requesters reach articles from the place tickets start.
  • Fit for the main reader. Customer teams and IT teams need different tools.
  • Published price. A team can estimate the cost without a sales call.
Zendesk ranks first for customer teams, and Freshservice ranks second for IT teams. SiteGPT ranks third because it is not a help desk. It adds an AI answer layer to the knowledge base you already run.

1. Zendesk: best for a customer help center inside a full help desk

Zendesk home page describing AI-powered customer service software with a 14-day free trial
Zendesk home page describing AI-powered customer service software with a 14-day free trial
Zendesk is customer service software whose Suite plans combine ticketing, messaging, live chat, a help center, and voice. The knowledge base starts on Suite Team, and it sits in the same system as tickets. Teams that want an AI chatbot on top can compare the AI chatbots for Zendesk.
Key features
  • Knowledge base, AI agents, and action builder on Suite Team
  • Help center as part of every Suite plan
  • Omnichannel routing, messaging, live chat, and telephony
  • AI writing tools on Suite Professional
Pros
  • Tickets, help center, and channels live in one product
  • Very large review base: 7,120 reviews on G2
  • 14-day free trial with no credit card
Cons
  • The knowledge base is not on Support Team, the $19 plan
  • Costs rise quickly per agent
  • AI agents are billed on automated resolutions, so usage adds to the seat price
Pricing
Plan
Per agent a month, billed yearly
Knowledge base
Support Team
$19
Not listed
Suite Team
$55
Yes
Suite Professional
$115
Yes
Suite Enterprise
Contact sales
Yes
Rating: 4.3 out of 5 from 7,120 reviews on G2.
Best for: customer service teams that want tickets and the help center in one system.

2. Freshservice: best for an IT help desk knowledge base

Freshservice home page describing one AI-powered platform for service, operations, and assets
Freshservice home page describing one AI-powered platform for service, operations, and assets
Freshservice is the IT service management product from Freshworks. Knowledge management and a support portal are listed on its entry plan, Starter, so an IT team gets articles and tickets from the first tier. Teams leaving a customer-focused tool can also read the Freshdesk alternatives or Zoho Desk alternatives guides.
Key features
  • Incident management, knowledge management, and a support portal on Starter
  • Service catalog and SLA management on Growth
  • Problem and change management on Pro
  • Freddy AI Copilot as a paid add-on, and Freddy AI Agent on Enterprise
Pros
  • Built for IT teams and ITIL-style processes
  • The knowledge base is on the entry plan
  • 14-day free trial with access to all features
Cons
  • Change and problem management start at Pro
  • Freddy AI Agent is listed only on Enterprise, which has a custom price
  • The pricing page shows local currency by visitor location, so check it for your region
Pricing
Plan
Billing
Knowledge base
Starter
Per agent a month, monthly or yearly
Yes
Growth
Per agent a month, monthly or yearly
Yes
Pro
Per agent a month, monthly or yearly
Yes
Enterprise
Custom
Yes
Rating: 4.6 out of 5 from 1,376 reviews on G2.
Best for: mid-size IT teams that want a full service desk with the knowledge base included.

3. SiteGPT: best AI answer layer on top of a help desk knowledge base

SiteGPT home page with a chat widget offering plan, setup, and security questions
SiteGPT home page with a chat widget offering plan, setup, and security questions
SiteGPT is an AI chatbot that trains on your existing content and answers questions in a chat widget. It does not replace a help desk or a knowledge base. It reads the articles you have and answers people who would rather ask than search.
Key features
  • Trains on website URLs and sitemaps, so it can read a public help center
  • Trains on files and text, plus Notion, Google Drive, Dropbox, OneDrive, Box, and GitHub
  • Fallback message when the content has no answer
  • Escalation to a person
  • Weekly digest with the questions the chatbot could not answer (Growth and above)
  • Auto refresh monthly on Growth and weekly on Scale
  • Slack, Google Chat, Crisp, and Freshdesk Messaging from Growth, and Zendesk AI Agent from Scale
Pros
  • No migration: it works with the articles you already publish
  • Unanswered questions show which article to write next
  • 95+ languages
Cons
  • No ticket queue, article editor, or published help center
  • Search works by meaning, so exact error codes and part numbers can match less reliably
  • No free plan, and the 7-day trial requires a credit card
  • Starter has 1 member and manual refresh only
  • No Intercom or HubSpot integration
Pricing
Plan
Billed monthly
Billed yearly
Messages a month
Pages
$59 a month
$39 a month ($468 a year)
4,000 GPT-4.1-mini or 400 GPT-4.1
1,000
$129 a month
$79 a month ($948 a year)
10,000 GPT-4.1-mini or 1,000 GPT-4.1
10,000
$429 a month
$259 a month ($3,108 a year)
40,000 GPT-4.1-mini or 4,000 GPT-4.1
50,000
Custom
Custom
Custom
Custom
Rating: 4.9 out of 5 from 12 reviews on G2.
Best for: teams with a working knowledge base whose customers or employees still open tickets for documented answers.

4. Jira Service Management: best free start for a small IT team

Jira Service Management home page with a headline about high-velocity service management
Jira Service Management home page with a headline about high-velocity service management
Jira Service Management is Atlassian's service desk, now sold through its Service Collection pricing. The Free plan covers 3 agents and includes an embedded knowledge base that can recommend articles to requesters. This makes it the lowest-cost way for a small IT team to start.
Key features
  • Embedded knowledge base on every plan, including Free
  • Requests by portal, email, chat, Microsoft Teams, Slack, or an embedded widget
  • Custom-branded help center from Standard
  • Asset and configuration management from Standard
  • Virtual service agent on Premium
Pros
  • Free for 3 agents
  • Published prices, with lower per-agent rates at higher team sizes
  • Fits teams that already use Jira
Cons
  • The Free plan has community help only
  • The virtual service agent needs Premium
  • The per-agent price depends on team size, so use the pricing calculator
Pricing
Plan
10 agents, billed monthly
10 agents, billed yearly
Free
$0 for 3 agents
$0 for 3 agents
Standard
$26.90 per agent a month
$2,700 a year
Premium
$61.60 per agent a month
$6,200 a year
Enterprise
Contact sales
Contact sales
Rating: 4.3 out of 5 from 991 reviews on G2.
Best for: IT teams of up to 3 agents, and larger teams already on Jira.

5. Help Scout: best for a small customer team

Help Scout is a shared inbox for customer service with Docs, its knowledge base product, built in. The Free plan includes 1 inbox and 1 Docs site, and Standard adds multiple knowledge bases. Its AI assistant, Envoy, costs $0.75 per resolution. For a wider comparison, see the guide to knowledge base software.
Key features
  • Docs knowledge base, with multiple knowledge bases on Standard
  • Shared inboxes, live chat, and SMS on Standard
  • Secure customer portal on Plus
  • AI Answers through Envoy at $0.75 per resolution
Pros
  • A free plan with one Docs site
  • Simple to learn
  • 15-day free trial of Standard or Plus with no credit card
Cons
  • Built for customer teams, with no IT service management features
  • Extra Docs sites cost $20 a month billed yearly, or $24 billed monthly
  • SSO is on Pro
Pricing
Plan
Per user a month, billed monthly
Per user a month, billed yearly
Free
$0
$0
Standard
$30
$25
Plus
$54
$45
Pro
$90
$75
Rating: 4.4 out of 5 from 431 reviews on G2.
Best for: small customer service teams that want a simple inbox and help center.

How much does a help desk knowledge base cost?

A help desk knowledge base costs $0 on a free plan, and about $2,700 to $13,800 a year for 10 agents on the paid plans below. Most of that price pays for the help desk, not only the knowledge base.
Bar chart of yearly list price for 10 agents billed yearly: Jira Standard 2,700 dollars, Help Scout Standard 3,000, Help Scout Plus 5,400, Jira Premium 6,200, Zendesk Suite Team 6,600, and Zendesk Suite Professional 13,800
Bar chart of yearly list price for 10 agents billed yearly: Jira Standard 2,700 dollars, Help Scout Standard 3,000, Help Scout Plus 5,400, Jira Premium 6,200, Zendesk Suite Team 6,600, and Zendesk Suite Professional 13,800
Plan
Yearly cost for 10 agents, billed yearly
Note
Jira Service Management Free
$0
Covers 3 agents only
Jira Service Management Standard
$2,700
Saves $528 a year against monthly billing, or 16%
Help Scout Standard
$3,000
Saves $600 a year against monthly billing, or 17%
Jira Service Management Premium
$6,200
Adds the virtual service agent
Zendesk Suite Team
$6,600
$55 × 10 agents × 12 months
Zendesk Suite Professional
$13,800
$115 × 10 agents × 12 months
An AI answer layer is an extra cost. SiteGPT Growth adds $948 a year billed yearly, which covers the whole team and not one seat. Pay-per-resolution tools charge by use instead. At $0.75 per resolution, 100 resolutions a month cost $900 a year. For more options on that layer, see the comparison of chatbots for an existing knowledge base.

The stack: which tool does which job

A help desk knowledge base and a chatbot do different jobs. Most teams need the first before the second, because a chatbot can only answer from content that exists.
Layer
Job
Tool
Ticketing
Track, route, and resolve requests
Zendesk, Freshservice, Jira Service Management, Help Scout
Knowledge base
Hold the correct answer in articles
The one built into your help desk
AI answer layer
Answer in chat from those articles
SiteGPT, or the help desk's own AI
People
Handle exceptions and write new articles
Your agents
Gartner recommends a single digital concierge, such as a GenAI chatbot, as the most prominent entry point on a website. A chatbot helps when people ask in their own words and do not know which article to open. It stays accurate only if the articles are accurate, so fix content first. The guide to stopping chatbot hallucinations covers the remaining safeguards.

How to choose a help desk knowledge base

Choose a help desk knowledge base by its reader first and its price second. If your team already runs a help desk, start with the knowledge base it includes.
If you need...
Pick...
Why
A customer help center inside a full help desk
Zendesk Suite Team
Tickets, channels, and the knowledge base are in one plan
A knowledge base for an IT service desk
Freshservice
Knowledge management is on the entry plan
A free start for up to 3 IT agents
Jira Service Management Free
The embedded knowledge base is on the Free plan
A free help center for a small customer team
Help Scout Free
It includes 1 inbox and 1 Docs site
An IT team already using Jira
Jira Service Management
It fits the tools the team already uses
Answers in chat from existing articles
SiteGPT
It trains on your content with no migration
IT answers in a Slack channel
SiteGPT Growth
Slack is included from Growth
An AI agent that takes actions on tickets
Your help desk's own AI
SiteGPT answers questions and has no ticket queue
Decision tree for choosing a help desk knowledge base: who reads it, whether the team already runs a help desk, and whether people still open tickets for documented answers
Decision tree for choosing a help desk knowledge base: who reads it, whether the team already runs a help desk, and whether people still open tickets for documented answers

Common help desk knowledge base mistakes

The most common help desk knowledge base mistakes come from treating it as a writing project and not as part of ticket work.
  • Writing from memory. Teams guess at topics. Ticket data shows the real demand.
  • Using internal language. People search for "VPN won't connect", and they will not find "remote access remediation".
  • Having no owner. An article without an owner goes out of date without anyone noticing.
  • Hiding search. If search is not on the request form, people open a ticket first.
  • Adding a chatbot to bad content. A chatbot repeats outdated articles with confidence.
  • Measuring only article views. Views do not show whether the problem was solved.

Start with the articles you already have

Most teams already have the raw material for a knowledge base in their tickets. Export 90 days of tickets, write the top 20 answers, and add them to your help desk.
If people still open tickets for those answers, a chatbot can answer from the same articles. SiteGPT Starter costs $59 a month billed monthly, or $39 a month billed yearly. Every self-serve plan has a 7-day free trial that requires a credit card.

Frequently asked questions

Basics

What is a help desk knowledge base?

A help desk knowledge base is a searchable library of articles that helps customers, employees, and agents solve common problems. It usually lives inside the help desk software.

What should a help desk knowledge base include?

A help desk knowledge base should include how-to guides, troubleshooting steps, known errors with workarounds, and answers to the most common ticket reasons. Each article needs an issue, a resolution, an owner, and a review date.

What is the difference between a help desk and a knowledge base?

A help desk tracks and resolves individual requests. A knowledge base stores the reusable answers. Most help desk software includes both.

IT help desks

What is an IT help desk knowledge base?

An IT help desk knowledge base is a library of articles for internal technology problems, such as password resets, VPN errors, and software requests. Employees use it through a portal, and IT agents use it while they work tickets.

What is an IT support knowledge base used for?

An IT support knowledge base is used to give employees self-service answers and to give agents tested fixes. It reduces repeat tickets on common problems and gives new agents one place to learn the procedures.

What is the best knowledge base for an IT help desk?

Freshservice suits mid-size IT teams because knowledge management is on its entry plan. Jira Service Management suits small teams because its Free plan covers 3 agents and includes a knowledge base.

Building and maintaining

How many articles does a help desk knowledge base need?

A help desk knowledge base should start with about 20 articles that cover your top ticket reasons. Add more when search failures or new ticket reasons show a gap.

How often should a help desk knowledge base be updated?

Update an article whenever an agent finds it wrong, and review high-traffic articles every 90 days. Update affected articles as part of every product, policy, or system change.

What is Knowledge-Centered Service?

Knowledge-Centered Service (KCS) is a method from the Consortium for Service Innovation for creating and improving knowledge as part of solving issues. Articles are captured during the work and improved through reuse.

Cost and AI

How much does a help desk knowledge base cost?

A help desk knowledge base costs $0 on Jira Service Management Free or Help Scout Free. For 10 agents billed yearly, paid plans run from $2,700 to $13,800 a year in this guide.

Can a chatbot use a help desk knowledge base?

Yes, a chatbot can answer from a help desk knowledge base. SiteGPT can train on a public help center through its website URLs or sitemap. Private content can be added as files or through connected apps such as Notion and Google Drive.

Does a chatbot replace a help desk knowledge base?

No, a chatbot does not replace a help desk knowledge base. The chatbot needs articles to answer from, and the team needs one place to keep those answers correct.

Sources

Sources checked on October 30, 2026.

Give Your Customers The Experience That They Deserve

Create A Chatbot In Minutes, Today

Create Your Chatbot Now

Written by

Bhanu Teja P
Bhanu Teja P

Founder @ SiteGPT.ai & SourceSync.ai