Customer Experience

    Knowledge Base

    Term #257

    A central information repository (articles, guides, FAQs) accessible to customers and/or agents. Reduces service load, raises FCR, and enables 24/7 self-service. Zendesk Guide, HelpScout Docs, Gorgias Help Center.

    In practice

    A knowledge base is the 'always-available assistant.' A customer searching 'how to return a product' on Google can find your help center before ever contacting support. 40% of customers prefer self-service before reaching out to an agent. A knowledge base saves money and improves UX.

    Common misconception

    'Knowledge bases are only for big companies.' Gorgias and Tidio include a help center in their basic plan. 10 articles on common topics (shipping, returns, policy, cancellation) means 20% fewer inquiries. 3 hours of writing = immediate ROI.

    How to fix it

    Knowledge base underused? (1) Check the deflection rate — what percentage of help-center visitors didn't contact support (target: 70%+), (2) search analytics — what are people searching for and not finding? → add articles, (3) visibility — link the help center in the header, email signature, and chatbot, (4) update articles with every policy change.

    Example

    Pet store: 300 inquiries/month. 45% were 'how long is shipping?' + 'how do I return this?' Built a knowledge base: 5 detailed articles + a header link. A month later: inquiries fell to 210/month (-30%). Agents freed up time for complex inquiries.

    Priority

    A knowledge base is a one-time investment with compounding ROI. Build it before growing your service team. First 10 articles: (1) shipping policy, (2) return policy, (3) order cancellation, (4) updating details, (5) payments and subscriptions — then follow inquiry volume.

    Jimmy tracks your Knowledge Base, automatically

    WhatsApp alerts when something important changes. No dashboards, no hassle.