Knowledge Base

A knowledge base is a central, searchable library of information - answers, procedures, policies and troubleshooting steps - that contact centre agents, customers or AI tools use to find accurate, consistent answers quickly.

What is a knowledge base?

A knowledge base is a structured collection of the information people need to answer customer questions and handle requests correctly. In a contact centre it typically includes:

  • Answers to common questions, written clearly and briefly.
  • Procedures, such as how to process a refund, log a fault or set up a payment plan.
  • Policies and rules, including eligibility, exceptions and approval limits.
  • Product and service details, such as plans, pricing and terms.
  • Troubleshooting guides, often as step-by-step decision trees.
  • Escalation paths, saying who to contact for what and when.

There are two main types. An internal knowledge base is for agents and staff, and can include sensitive detail. An external knowledge base is customer-facing, such as a help centre or FAQ pages, and supports customer self-service. Increasingly, both are maintained from one source.

Why it matters

Contact centre work is full of detail that changes. Agents can’t remember everything, and they shouldn’t have to. A good knowledge base:

  • Improves accuracy and consistency, because every agent gives the same, correct answer.
  • Supports first contact resolution, because agents can solve more issues without transferring or calling back.
  • Reduces handle time, because finding the answer is quick.
  • Speeds up training, because new agents can rely on the system rather than memorising everything before they start.
  • Supports quality and compliance, because the approved process is written down and can be checked against.
  • Feeds AI. AI agent assist, chatbots and voice assistants draw on the knowledge base to answer questions and suggest next steps.

What makes a good contact centre knowledge base

  1. Easy to search. Agents search mid-conversation, often using the customer’s own words. Search should handle that, not just exact titles.
  2. Short and scannable. Lead with the answer, then the detail. Use steps and bullets.
  3. Linked to the workflow. The best knowledge bases surface the right article automatically, linked to the call script or the reason for contact.
  4. Owned and dated. Every article has an owner and a review date, so stale content gets checked.
  5. Fed by the front line. Agents should be able to flag gaps and errors quickly.

Common mistakes

  • Letting content go stale. Out-of-date articles are worse than none, because agents trust them.
  • Duplicating information. Two articles saying slightly different things create confusion. One topic, one article.
  • Writing for experts. Articles written in internal jargon slow down new agents.
  • Treating AI as a fix for poor content. Generative AI tools can summarise and search a knowledge base well, but they can’t correct what’s wrong in it. Grounding AI in approved content is a key guardrail, and it only works if that content is right.

A knowledge base is never finished. The contact centres that get the most from theirs treat it as a living tool, updated every time a product, policy or process changes.

How Telnet Helps

Where Telnet comes in

The knowledge base is built into ContactSuite, Telnet’s own contact centre platform, so the right information is on the agent’s screen alongside the customer’s history and the right script.

  • Natural-language search. Agents find the accurate answer however the customer phrased the question, so nobody relies on memory.
  • Consistent across channels. Phone, email and webchat agents answer from the same source, so customers get the same answer whichever way they get in touch.
  • Faster onboarding. Putting the expertise in the system is a big reason our agents can be competent on a new client in days rather than weeks. For Z Energy, training time fell from 5 weeks to 3 days.

For agents to give the right answer, the knowledge base has to reflect your products, policies and processes, so we work with you on its content and keep it current as those change.

FAQ

Knowledge Base FAQs

What's the difference between a knowledge base and a call script?

A script guides how a conversation should go; a knowledge base holds the facts and procedures behind it. A call script sets out the steps, questions and wording for a type of call. The knowledge base answers the questions that come up along the way, such as policy details, product information or troubleshooting steps. Many platforms link the two, so the script points the agent to the right article.

Should customers and agents use the same knowledge base?

Usually they should share a single source, with different views. Agents need internal detail such as procedures, escalation rules and exceptions; customers need plain-language answers. Keeping both drawn from one maintained source avoids the common problem of the website saying one thing and the contact centre another.

How does a knowledge base support AI in the contact centre?

AI tools such as chatbots, voice assistants and agent assist rely on a knowledge base for accurate answers. If the content is out of date or contradictory, the AI will repeat those errors. Grounding AI responses in an approved knowledge base is one of the main guardrails against made-up answers.

Ready to scale?

Outsourced contact centre
for New Zealand & Australia.

30+ years. 100% onshore. The leading provider to the energy & utilities industry.

Get in Touch