How does a knowledge base work?
- Start from the questions already sitting in your inbox, ranked by how often each one arrives.
- Write one article per question, answer in the first two sentences, steps and screenshots below it.
- Title articles in the customer's words rather than your internal product name, so site search finds them.
- Link articles from saved replies and chat greetings, so every answer teaches people where to look next time.
- Put a review date on each article and rewrite anything that draws a follow-up question.
A worked example
A three-location dance studio kept fielding the same parent questions: make-up classes, costume deadlines, sibling discounts and the winter recital schedule. The assistant wrote eight articles, each under 300 words, and put the link in the enrollment email and the chat greeting. Front desk calls about costumes fell sharply in the first month, and when the costume policy changed the studio edited one article instead of briefing four staff. The internal version holds the refund rules nobody is allowed to improvise.
Where does a knowledge base show up in your tools?
Zendesk Guide, Freshdesk Solutions, Help Scout Docs, Intercom Articles and HubSpot all publish customer-facing articles and report which searches returned nothing. Internal procedures more often live in Notion or a Google Workspace shared drive, where permissions are easier to keep tight.
Common mistakes
- Writing articles from the org chart instead of from real questions, so the useful answers never get written.
- Publishing once and never updating, which teaches customers the whole library is out of date.
- Burying the search box below the contact form, so people open a ticket rather than hunt for the answer.
Why does a knowledge base matter?
Every question answered by an article is a question nobody has to answer twice, which is the cheapest capacity a small team can buy. A good library also speeds up training, because a new assistant reads exactly what your customers read. Search engines and AI assistants quote these pages too, so they earn visits while they deflect tickets.
How does AssistBPO handle a knowledge base?
AssistBPO assistants write and maintain your articles as part of the work, starting with whatever they answer most in the first month. Drafts come to you for approval, then go live and get linked from saved replies and chat greetings. At the weekly review the team lead brings the search terms that returned nothing and proposes the next few articles.
Tickets resolved by agents who learn your productGet a staffing plan