A well written, maintained, and accessible knowledge base should be the cornerstone of any customer service team’s self-service strategy; more than 6 out of 10 U.S. consumers prefer a self-service tool for simple inquiries.
In this article, we will explain what a knowledge base is and show you how to plan, create, and deliver effective knowledge base content that will truly create better customer experiences.
A knowledge base is an organized, curated collection of information about a particular subject area — a way of making that information more accessible and usable.
The term “knowledge base” typically refers to the information stored in the system, but it can also refer to the software used to author and present that information. In this article, we will use “knowledge base” to refer to the content contained within your knowledge base software.
A knowledge base can encompass many forms of content, including:
Knowledge bases are the end product of collecting and organizing all of that information into a useful form, through a process called “knowledge management”. So typically you would apply knowledge management processes to collect information, then use knowledge base software to create, manage and deliver that information, as a knowledge base, to your readers.
Some types of knowledge bases are intended purely for machines to learn from. Other types — the types we’re referring to in this article — are built for people to use and learn from.
Knowledge bases can be aimed at external audiences or internal audiences, and can serve many different purposes. For example, an appliance company may maintain FAQs and maintenance instructions in a customer-facing knowledge base, and also have an internal knowledge base for their employees to understand company policies and learn work related tools.
In some cases, companies maintain knowledge bases that are relevant not just to their own customers, but to anyone interested in their particular field. Consider for example Blue Nile’s diamond buying guide, an educational knowledge base filled with information useful for anyone in the market for a diamond.
Your knowledge base isn’t just helpful for customers, it’s also useful for your staff. A well-structured, clearly written, and cleanly designed knowledge base helps customers help themselves, acts as a learning tool for new staff, and can even be a source for machine learning.
Much of customer service is basic information transfer — the customer has a gap in their knowledge that is preventing them from achieving some goal, and the customer service team steps in to fill that gap.
Questions like these can be addressed through multiple means, such as improving your product or service design, better labeling, and upfront training. But there will always be people who need more help.
A knowledge base is a cost-effective way to reduce the time and effort the customer has to spend in order to get an answer and move on with their current task. A well-stocked knowledge base creates a better customer experience in several ways:
Recent research shows that a majority of people prefer to find their own answer first before they will reach out for help. A knowledge base is where they will look!
A single knowledge base can present information as text, annotated images, video, audio or any other media format. It can give customers the best chance of receiving the information they need in a way they can best absorb.
Even if you have customers on the other side of the world from your customer service team, a knowledge base can be there with them. Plus, your knowledge base will never ask for time off to go to Bonnaroo.
Customers don’t need to start from page one and read through your whole knowledge base. With the right knowledge base software, you can deliver the right piece of information at just the right moment.
If you select a knowledge base tool with reporting capabilities, those reports will show you what people are looking for and are finding, the terms they use to search, any gaps you have in your knowledge base, and more. You can use that information to improve your knowledge base content — and also your product or service.
Convinced yet? The next step is to get all of that useful information into a format and structure that can be turned into a knowledge base.
Humans have created many, many tools for information storage and access. You probably won’t choose stone tablets as your knowledge transfer tool of choice, but there are plenty of other options.
Some common points for collecting information into a knowledge base include:
It may be a local file server with MS Word or PDF documents, a Dropbox shared folder, a Google Drive, but shared document storage is a common solution for making information accessible to many people. This method can sometimes create challenges with duplication, file format and accessibility to other systems.
Making information easily editable and findable by many people is the key benefit of a wiki tool. Intranet tools (whether or not they are technical wikis) are often used for capturing internal knowledge and making it accessible to staff.
Knowledge base software are specialized tools for creating, maintaining and delivering information. Help Scout’s Docs is an example of knowledge base software, built to deliver better self-service and to integrate tightly with our customer service help desk.
We’ve got more help for getting started with a knowledge base in seven tips for creating a knowledge base. If you’d like to browse some great examples for inspiration, check out 10 knowledge base examples that get it right.
A knowledge base is a long-term project, the Sagrada Família of the software world. Building out that set of content is no small task, so is it worth spending the effort? Yes! An effective knowledge base can vastly improve your customer service.
And in good news, your knowledge base will start being useful long before you have completed all (or even most) of the possible content it will contain.
Follow these five tips to create effective knowledge base content.
Anyone on your team who regularly talks to customers will be able to share the most commonly asked questions, and that’s a great place to begin. Once you document those items, move on to the next tier of common misunderstandings, challenges, and queries.
Consider using a tag or custom field in your help desk software that allows anyone answering a customer query to flag that query for documenting in your knowledge base. That way you’ll have a continual flow of genuine customer questions to address.
You probably already have content you can add to your knowledge base. Look for FAQs, release documentation, and internal materials that contain information customers could also use. Your customer service tool likely contains plenty of well-worded, reusable explanations to draw from.
Copy all of that information into one place so you can see what you have, what you still need, and where you might have inconsistencies or duplication.
Clearly structuring and arranging all of that information is key to a successful knowledge base. Try to group together information according to how customers are likely to need it (as opposed to matching your internal structure or even your product’s navigation).
Go deeper into knowledge organization with these useful guides:
Writing (or recording) knowledge base content takes significant effort, so it’s important to create content people will really find and use. Earlier in this process you have likely identified gaps in your current set of knowledge.
Perhaps your support team find themselves having to write longer answers because the information isn’t already covered in your knowledge base. Those answers can form a perfect base for new content.
When your have prioritized the list of questions you want to cover, you can begin to create new knowledge base content. If you aren’t the subject matter expert yourself, collect the answer from the best informed team members, and use that to outline your document.
Then you can build on that outline, applying a consistent voice and tone, always keeping in mind the task, question or mindset that your end reader is likely to have.
Continue learning how to develop effective knowledge base content with these articles:
A knowledge base should not be a stone tablet, written once and fixed in place. Especially in the software world, information becomes outdated or incomplete constantly, so you will need to revisit it regularly.
Nominate a person or a team to own the knowledge base (or some portion of it), and be sure they have the time and capacity to work on it. Additionally, consider using knowledge base article ratings to allow readers to flag content that might need work.
Over time, your team can extend your knowledge base, updating existing content and adding new content (or new formats for existing content), building an information resource that will save plenty of time for your customers and your team.
Of course, that assumes your customers are finding your knowledge base and are able to comprehend and apply the information in it. That’s where the next step comes in.
A knowledge base isn’t useful if people can’t first find the right information, understand it, and apply it to their questions. Some simple guidelines can greatly increase the usability of your knowledge base.
Help your readers understand your content and make use of it by applying simple knowledge base design tips like contrast and white space.
You might use your own marketing terms or internal jargon to describe features or elements of your service, but customers may never search for those terms or understand them. Review support conversations and chat transcripts to understand how customers talk about your offerings and include those terms.
Rather than wait for readers to arrive at the front door of your knowledge base, make the information visible right where they need it, inside your application or on specific pages. Tools like Beacon can let you easily show the most appropriate content for the customer’s current goal.
One reason customers reach out for your help is that they just don’t know your knowledge base is there. Link to your knowledge base prominently from the places people can trigger a support question, and help them help themselves.
Knowledge base software can help greatly in creating and delivering useful information to customers. Picking the right tool for your specific situation will make everything easier.
Which knowledge base software is best? It depends on the software environment you are in, the capabilities you need (or want), and the resources you have available. Here are some key questions to help you narrow down the options:
When you have a shortlist you are considering, be sure to spend some time using the company’s own knowledge base (and contacting their support team). They should be the best example of their own capabilities!
Planning, designing, creating, and maintaining a knowledge base can feel daunting. However, every article you write might represent hundreds or thousands of future customer questions answered without needing your help.
A great knowledge base can also be an incredible tool for training new staff and an excellent SEO resource that draws in new potential customers. Time spent well on building your knowledge base will pay off for years to come.
Want to learn more? Check out our collection of knowledge base content below. We’ve only just scratched the surface in this article, so read on for even more helpful advice and examples!
A knowledge base can be your customer’s self service guide through your product, but not if your help content is mediocre.
Expertly curated emails that’ll help you deliver an exceptional customer experience.