Skip to content
English
  • There are no suggestions because the search field is empty.

HubSpot Knowledge Base vs Happy Center Kit

Why we use two approaches

We set up knowledge and resource hubs in two main ways in HubSpot: the built‑in Knowledge Base (part of Service Hub) and the Happy Center Kit (a HubDB‑based hub on your website). We choose between them based on whether the focus is support deflection or a broader learning/resources experience.

 

HubSpot Knowledge Base

We use HubSpot’s native Knowledge Base when the priority is customer support and self‑service help.

When we use it:

  • The main goal is to reduce support tickets and give customers clear answers quickly.

  • The support team already works in HubSpot tickets, chat and the customer portal.

  • You want out‑of‑the‑box analytics such as article views, helpful/not helpful feedback, and search terms that return no results.

What this gives you:

  • A fast way to launch a support centre using HubSpot’s default structure (categories → articles).

  • A simple editor that support and success teams can maintain themselves.

  • Tight integration with Service Hub features like tickets, chatbots and the customer portal.

 

Happy Center Kit (HubDB‑based)

We use the Happy Center Kit when the priority is a flexible, on‑brand resources or learning hub on your website.

When we use it:

  • You want a “Resources”, “Help & Resources” or “Academy” area with mixed content (documentation, tutorials, guides, downloads).

  • You need filters (categories and tags) so users can slice content easily.

  • You are on CMS Hub Pro/Enterprise and are happy to manage content in HubDB once the framework is in place.

What this gives you:

  • A hub that looks and feels like the rest of your site, using CLEAN‑compatible templates and modules.

  • Flexible structure using HubDB.

  • Standard HubSpot page analytics, with the option to add custom tracking as needed.

 

How we typically apply them

In practice, we usually follow this pattern:

  • For support‑led, ticket‑driven teams, we set up the built‑in Knowledge Base first as the primary support centre.

  • For broader “Resources” or “Academy” areas, we use the Happy Center Kit to create a flexible, on‑brand hub on the website that can grow over time.

You may see both in use together: the built‑in Knowledge Base focusing on troubleshooting and FAQs, and the Happy Center Kit hosting broader guides, tutorials and learning content.