Knowledge base

Learn what a knowledge base typically includes, how it differs from a help centre, and how to use it effectively.

A knowledge base is a structured collection of articles, guides, FAQs, troubleshooting steps, and other educational content that helps users understand a product or service and solve common problems on their own. It is designed for self-service, so users can search or browse for answers without needing to contact support.

For financial and crypto platforms, a knowledge base is a core part of the support and education strategy. It reduces friction, speeds up problem resolution, and allows support teams to focus on more complex or sensitive cases.

What a knowledge base typically includes

While structure varies by company, most knowledge bases contain several common types of content.

Getting started guides

  • How to create an account.
  • How to complete identity verification (KYC).
  • How to secure your account (2FA, passwords, device management).
  • Overview of key features (wallet, trading, cards, staking, etc.).

These articles are aimed at new users and focus on essential first steps.

How-to articles and tutorials

  • How to deposit fiat or crypto.
  • How to withdraw funds to a bank account or external wallet.
  • How to buy, sell, or swap assets.
  • How to use budgeting tools, spending categories, or savings goals.
  • How to manage notification settings, limits, or security features.

These guides walk users through specific tasks step by step, often with screenshots or short videos.

Troubleshooting articles

  • What to do if a deposit or withdrawal is delayed.
  • How to resolve login issues (forgotten password, 2FA problems, device changes).
  • How to handle failed transactions or error messages.
  • What to do if you suspect fraud or unauthorised access.
  • How to update or reinstall the app if it is not working correctly.

These articles focus on diagnosing and solving common problems.

Security and compliance information

  • Explanation of verification levels and required documents.
  • Overview of security features (2FA, OTP, device recognition).
  • Guidance on recognising and avoiding phishing and scams.
  • Information on AML/KYC requirements and why they are needed.
  • Risk disclosures and regulatory information.

This content helps users understand their responsibilities and how the platform protects them.

Fees, limits, and product details

  • Fee schedules for deposits, withdrawals, trades, and other actions.
  • Transaction limits by verification level or product.
  • Details on supported assets, currencies, and networks.
  • Explanation of how interest, staking rewards, or other yields work (if applicable).
  • Policies on chargebacks, disputes, or refunds.

These articles provide transparency and help users plan their usage.

Account and settings help

  • How to update personal information (name, address, contact details).
  • How to change passwords, 2FA methods, or notification preferences.
  • How to close or delete an account.
  • How to download statements, transaction history, or tax reports.
  • How to manage linked devices and sessions.

Concept and glossary articles

  • Explanations of key terms (for example, “Bitcoin”, “Ethereum”, “Staking”, “AML”, “Volatility”).
  • Overviews of how certain technologies or features work (for example, “How blockchain works”, “What is proof of reserves”).
  • Definitions of common financial and crypto concepts.

These articles build user literacy and confidence in using the product.

Knowledge base vs help centre

The terms “knowledge base” and “help centre” are often used interchangeably, but there are subtle differences in how companies use them.

Knowledge base

  • Often more content-focused: a library of articles, guides, and documentation.
  • May be more technical or detailed, including deep dives, API docs, or developer guides.
  • Sometimes internal (used by support agents) as well as external (for users).
  • Emphasis on comprehensive coverage of topics.

Help centre

  • Often more user-facing and branded as the main support hub.
  • Typically combines:
    • Knowledge base articles.
    • FAQs.
    • Contact options (chat, ticket submission, phone).
    • Status pages and announcements.
  • Emphasis on easy navigation and quick answers for common issues.

In practice, many platforms use “Help Centre” as the public-facing name, with a knowledge base as the underlying content engine.

How users typically access a knowledge base

Knowledge bases are accessible in multiple ways.

Direct URL

  • A dedicated site or section, for example:
    • help.example.com
    • support.example.com
    • docs.example.com

In-app or website links

  • “Help”, “Support”, or “Resources” menus in the app or website.
  • Contextual help links inside specific features (for example, a “Learn more” link next to staking or withdrawals).
  • “Contact us” flows that first show relevant knowledge base articles.

Search engines

  • Users searching for a question (for example, “how to withdraw crypto”, “what is staking”) may land directly on a knowledge base article via a search engine.

Within support workflows

  • When users start a chat or open a ticket, they are often shown suggested articles from the knowledge base before or during the conversation.

How knowledge bases are organised

Good knowledge bases are structured to make finding information easy.

Categories and sections

Content is often grouped into high-level categories such as:

  • Getting started
  • Account and verification
  • Deposits and withdrawals
  • Trading and investing
  • Cards and spending
  • Security and privacy
  • Fees and limits
  • Troubleshooting
  • Concepts and glossary
  • Developer / API (if applicable)

Each category contains related articles and sub-guides.

Search and discovery

  • A prominent search bar with auto-suggestions.
  • Popular topics or “Most viewed articles” on the home page.
  • “Related articles” links at the bottom of each page.
  • Breadcrumbs to show where the user is within the hierarchy.

Language and localisation

  • Multi-language support for global user bases.
  • Region-specific articles (for example, local verification requirements, country-specific payment methods).
  • Clear indication of which content applies to which jurisdictions or products.

Benefits of a knowledge base

Knowledge bases help both users and the company.

For users

  • Fast answers – find solutions in seconds without waiting for support.
  • 24/7 availability – access content at any time, regardless of support hours or time zones.
  • Consistency – standardized articles ensure accurate, up-to-date information.
  • Empowerment – learn how the product works and become more confident using advanced features.

For the company

  • Scalability – handle many routine questions without proportional increases in support staff.
  • Lower support costs – deflect common queries to self-service.
  • Better support quality – agents can focus on complex or sensitive cases.
  • Insight – search analytics reveal gaps in content or product issues.

Good practices for users

To get the most from a knowledge base:

  • Start with a keyword search using simple terms (for example, “withdrawal delay”, “change email”, “enable 2FA”).
  • Use the category navigation if you are not sure what to search for.
  • Check the “Last updated” date on articles, especially for fast-changing topics like fees or supported assets.
  • Follow step-by-step instructions carefully and note any warnings or prerequisites.
  • If an article does not solve your problem, use the “Contact us” or “Still need help?” option to reach live support.

Good practices for companies

For platforms building or improving a knowledge base:

  • Write in clear, plain language and avoid unnecessary jargon.
  • Use step-by-step formats with screenshots or short videos where helpful.
  • Keep articles up to date and archive or flag outdated content.
  • Track search queries and article performance to identify gaps and improve content.
  • Provide easy paths from articles to live support when self-service is not enough.
  • Organise content around user tasks and questions, not just internal product structure.
Spend your
crypto.
Don’t sell it
Join the members who figured it out.