Skip to content
All articles
Guides

What is a knowledge base? A guide

In short

A knowledge base is a self-service library of help articles - how-tos, FAQs and troubleshooting - that lets customers and agents find answers on their own. It’s the single highest-impact way to deflect repeat tickets and give people help around the clock.

Every support team answers the same handful of questions again and again. A knowledge base is where you answer them once, properly, so the next hundred people can help themselves - no wait, no ticket, no agent time. It’s the closest thing support has to a compounding asset.

The definition

A knowledge base is an organised, searchable collection of articles that document how your product or service works and how to solve common problems. It usually lives on a public help centre, and often plugs straight into your helpdesk so answers surface right where customers are about to raise a ticket. Its primary purpose in a support environment is simple: give customers and agents one accurate, up-to-date source of answers, so common problems are solved without a ticket and the ones that do arrive are answered consistently.

External vs internal

  • External (customer-facing). The public help centre customers search before contacting you. Deflects tickets and works 24/7.
  • Internal (agent-facing). Private documentation - policies, edge cases, escalation steps - that helps agents answer quickly and consistently.

Most teams benefit from both, and a good helpdesk lets you mark articles as public or internal from the same place.

What goes in a knowledge base

  • Getting-started guides - the first things a new customer needs.
  • How-to articles - one task, one clear answer.
  • Troubleshooting - symptoms, causes and fixes for common problems.
  • FAQs - short answers to the questions you get most.
  • Policies - billing, refunds, data and account questions.

Knowledge base vs FAQ

An FAQ is a list of short answers to the questions you get most. A knowledge base is the whole library: FAQs plus longer how-to guides, troubleshooting articles and policies, organised into categories and searchable. Start with an FAQ if you only have a handful of repeat questions; move to a full knowledge base once answers need steps, screenshots or more than a paragraph. In Raiseaticket you get both in the same place.

Why it matters

Four payoffs: ticket deflection (fewer tickets for the same questions), availability (answers at 2am without an agent awake), consistency (everyone gets the same correct answer), and onboarding (new hires learn from the same library your customers use). A knowledge base is rare in that it helps customers and your team at the same time.

How to start

  1. List your ten most-repeated questions - your ticket tags will tell you.
  2. Write a clear, skimmable article for each. One question, one page.
  3. Link the knowledge base everywhere questions happen - and show suggested articles on your ticket form.
  4. Review monthly: what’s still generating tickets that an article could answer?

Set up a knowledge base in Raiseaticket

The knowledge base lives under the Resources menu in your helpdesk portal, with two parts: Articles and FAQs. As an administrator:

  1. Plan your categories. Group articles the way customers think about them - Getting started, Billing, Troubleshooting - so related answers sit together.
  2. Add an article. Go to Resources › Articles, open the more options menu in the top-right corner and choose Add article. Give it a clear title, write the answer with rich text, images and attachments, and assign a category.
  3. Choose who can see it. Use the Visible to setting: Agents & Users for customer-facing help, or Agents Only for internal notes such as policies and escalation steps.
  4. Add FAQs. Under Resources › FAQs, add short answers to your most repeated questions and give each a category.
  5. Decide who can write. By default only administrators manage articles. To let an agent contribute, tick the Resources permission (add/edit, and delete if needed) on that agent’s profile.
  6. Point people to it. Customers find the knowledge base under the Resources menu of their portal, and agents can link articles in their ticket replies, which teaches customers where answers live.

For the detailed steps, see the help centre articles on setting up a knowledge base for customers and controlling article visibility.

No cost barrier: a knowledge base is included free on Raiseaticket, with article visibility control for public and internal docs - so you can start deflecting tickets today without a paid tier.

Start small and let it grow with your tickets. Within a few months a good knowledge base quietly becomes your most productive “agent” - one that never sleeps and never repeats itself.

Start free

Build a free knowledge base

Publish public and internal help articles and deflect repeat questions - included on the 100% free plan.