What Is Zendesk Guide (Now Zendesk Knowledge)? Plans, Structure and AI in 2026

Zendesk Guide is Zendesk's knowledge base product, now renamed Zendesk Knowledge: the place where you write, organize, publish and search help content, included in every Zendesk Suite plan from Suite Team up. The Help Center is the customer-facing website that Guide powers: the public page with the search bar and the category tiles your customers actually visit. One is the back office; the other is the storefront. (We go deep on the storefront in Zendesk Help Center explained, and untangle all three terms in knowledge base vs. Help Center vs. Guide.)

Zendesk's own plan documentation now uses "Knowledge" for the current plans and keeps "Guide" for the legacy ones, while plenty of admin screens, docs and sales decks still say Guide. We use both names below, and they mean the same product. Here is how the plans map, checked on 24 September 2026:

Knowledge Professional and Knowledge Enterprise can also be bought as add-ons to any Support plan.

What is the difference between Zendesk Guide and the Help Center?

This trips up almost everyone, so it's worth nailing before anything else.

• Zendesk Guide is the product: the knowledge management system inside Zendesk. When you're logged in as an agent or admin and you write an article, arrange categories, set publishing permissions, or turn on AI search, you're working in Guide.
• The Help Center is the output: the branded, public-facing site (e.g. support.yourcompany.com) that Guide generates and serves to your customers. It's where end users land, search, read articles, and, if you've enabled it, submit tickets or post in the community.

A clean analogy: Guide is to your Help Center what a CMS like WordPress is to your published blog. You author and manage in one; customers experience the other. A single Guide instance can power a knowledge base, a self-service portal where customers track their tickets, and a community forum, all under the same Help Center roof.

How is Zendesk Guide content structured?

Every Zendesk knowledge base uses the same three-level content hierarchy: Categories, then Sections, then Articles. Get this model right and navigation, permissions and search fall into place.

1. Categories are the top-level containers. Think of them as the big buckets on your Help Center home page: Getting Started, Billing, Troubleshooting. Categories hold sections.
2. Sections live inside categories and group related articles. For a software company, a Billing category might contain Invoices, Refunds, and Plan changes sections. Sections can also be nested inside other sections, up to five levels deep with up to 200 sections per section, so larger libraries can build real sub-topic trees.
3. Articles are the actual help content (the how-tos, FAQs, and policies), and they live inside sections.

A few details that catch new admins off guard, straight from Zendesk's hierarchy docs:

• If your Help Center has only one category, that category is hidden from end users; they see only its sections. So a single-category KB looks "flatter" than you might expect.
• Visibility permissions are set at the article level, not the section level. That's how you publish some articles to everyone, restrict others to signed-in customers, and keep internal-only articles visible to agents alone, all within the same section. A section whose articles are all internal is hidden from end users.
• Only users with the Knowledge admin role can add, edit, or delete categories and sections. Regular agents can draft and (with permission) publish articles, but the structure itself is admin-controlled.

The practical takeaway: resist the urge to over-structure. A handful of broad categories with clear sections beats fifty hyper-specific buckets that confuse both authors and customers.

What can Zendesk Guide do?

Guide is more than a folder tree of articles. These are the features that make it a real knowledge management system.

Search

Search is the heart of any knowledge base. Most customers never browse categories; they type a question. Guide's Help Center search indexes your articles (and, on higher plans, community posts and federated external content) and ranks results. Good search depends entirely on good content: clear titles, real keywords, and articles that match how customers actually phrase things.

Generative search (AI answers)

On top of classic keyword search, Zendesk offers generative search: the "Quick answer" box that appears at the top of search results and writes a direct answer from your top-matching articles instead of just listing links. Zendesk's documentation now lists it on all Suite and Knowledge plans, Team through Enterprise Plus, with up to 100,000 eligible searches per month and a Generative Search Extender add-on beyond that (details here). Your theme needs the generative_answers helper: standard themes released after March 26, 2025 include it, and older customized themes need a manual update. The important caveat: a generated answer is only as good as the article behind it. Thin or contradictory content produces thin or contradictory answers.

Team Publishing (drafting, review, approval)

Team Publishing is Guide's editorial workflow, available on Knowledge Professional and Enterprise. It lets agents draft articles, assign reviewers, and route content through an approval step before it goes live, so a stray edit doesn't ship to customers unreviewed. You can verify articles on a schedule, flag content that's gone stale, and keep a clear owner on every page. For any team with more than one or two authors, this is what keeps a KB trustworthy instead of drifting out of date.

Content blocks

Content blocks are reusable snippets of content stored independently from any single article: a disclaimer, a set of troubleshooting steps, a support hours notice. Drop the block into ten articles, and when the underlying info changes you edit it once and every article updates. On a large KB this is what keeps repeated facts consistent; we cover the mechanics and gotchas in Zendesk content blocks explained.

Themes

The look of your Help Center is controlled by themes. Zendesk ships a default theme (Copenhagen) that's responsive and customizable out of the box, and you can edit colors, layout, and copy with no code, or go further with custom HTML/CSS/JavaScript and the templating language for a fully branded experience. How far you take it, and the trade-offs of customizing, are covered in Zendesk Help Center themes.

A note on Content Cues

You may still see references to Content Cues, an older feature that surfaced AI-suggested topics your KB was missing based on ticket trends. Zendesk removed Content Cues effective May 1, 2025. Its job, spotting content gaps from real ticket data, now falls to other AI tooling and to analyzing your own ticket history. If a guide tells you to "turn on Content Cues," it's out of date.

Community and the customer portal

Guide also powers two adjacent experiences under your Help Center. The customer portal lets signed-in users see and track their own tickets, the self-service layer beyond articles, which we cover in the Zendesk self-service portal. And Gather adds community forums where customers help each other and your team curates the best answers (community is available on Suite Professional and above). Together with the knowledge base, these are the three pillars of self-service that Guide brings together.

How much does Zendesk Guide cost?

Guide isn't a separate purchase for most customers anymore. It's bundled into the Zendesk Suite, and the tier you're on determines which knowledge features you get (official plan breakdown):

• Knowledge: included with Suite Team. The knowledge base and Help Center. Zendesk describes it as the equivalent of the old Guide Lite plan.
• Knowledge Professional: included with Suite Growth and Suite Professional, and available as a paid add-on on any Support plan. Adds multilingual content, Team Publishing and content blocks, among other features.
• Knowledge Enterprise: included with Suite Enterprise and Enterprise Plus, also a paid add-on on any Support plan. The full set of publishing controls and knowledge features.

A bit of history for anyone on an older contract: Zendesk used to sell standalone Guide plans. Guide Lite Legacy was discontinued on February 1, 2021, and accounts on Team, Professional or Enterprise plans from before May 2, 2017 may sit on a Guide Legacy tier, which has to move to the Enterprise tier to get newer Enterprise features. New customers buy knowledge as part of the Suite. If you're unsure what you've got, check Admin Center → Subscription in your own account rather than trusting any blog (including this one), because Zendesk adjusts packaging periodically.

Why does a knowledge base matter?

It's easy to treat the KB as a "nice to have" you'll get to eventually. The economics say otherwise.

• Deflection. Every customer who finds their answer in an article is a ticket your team never has to touch. At any real volume, that's the single biggest lever on support cost.
• 24/7 self-service. Your knowledge base answers instantly, across time zones and at 2 a.m. when no agent is online.
• Consistency. A published article gives every customer the same correct answer, instead of ten agents improvising ten slightly different ones.
• Faster agents. Agents link to articles in replies, which cuts handle time and helps new hires get up to speed.

The honest counterpoint: a knowledge base only delivers any of this if it's maintained. A stale, half-finished KB deflects nothing and erodes trust. The work is in keeping it current, which is exactly why Guide's publishing workflows and reusable content blocks exist.

How does a knowledge base power AI agents?

Your KB used to be read by humans. Now it's also read by AI, and that raises the stakes on getting it right.

Generative search (above) is one example: it turns your articles into direct answers inside the Help Center. The bigger shift is AI agents that resolve tickets. When a customer emails or chats in, an AI agent can read your knowledge base, find the relevant article, and either answer directly or draft a reply for a human to approve. The same content does the work at the front line instead of waiting to be searched. We walk through that wiring in connecting a knowledge base to an AI agent.

The dependency runs one direction: the AI is only as good as the KB behind it. A clean, well-structured, current knowledge base is the fuel. A messy one produces confident, wrong answers, which is worse than no answer at all.

Where Macha fits (a quick aside). Macha is an AI agent layer that runs on top of Zendesk; it's not a help desk and not a replacement for Zendesk or Guide. It reads your existing Guide knowledge base (plus past tickets and other sources) to draft replies, triage, and resolve routine tickets, leaving anything it can't handle as a normal ticket for a human. It bills per ticket: one conversation, charged once, covering every automated step in it (summarize, tag, route, look up data, draft, or resolve). It never bills per resolution, so the bill never hangs on an outcome definition you don't control. Plans start at $299 a month for up to 750 tickets, with setup and monitoring by the Macha team included. The relevant point for this article: a good Guide KB is what makes any AI layer, Macha included, actually useful. You can try it free with $50 of free usage, no credit card required.

What are the best practices and common mistakes?

A few habits separate a knowledge base that pulls its weight from one that gathers dust.

Do:

• Start with a few broad categories. Structure can always grow; over-structuring early just confuses people.
• Write titles the way customers search. "How do I get a refund?" beats "Refund policy v2."
• Use Team Publishing and a review cadence. Assign owners, set verification dates, and retire stale articles on a schedule.
• Reuse with content blocks. Anything that appears in more than one article (hours, disclaimers, steps) belongs in a block.
• Mine your tickets for gaps. The questions agents answer over and over are the articles you're missing.

Avoid:

• Treating launch as "done." A KB is a living product, not a one-time project.
• Deep nesting no one can navigate. Five levels are possible; that doesn't mean you should use them.
• Internal jargon in customer-facing articles. Write for the customer, not the org chart.
• Forgetting article-level permissions. Publishing an internal note to the public web is an easy, embarrassing mistake, so set visibility deliberately.
• Letting search results rot. If customers keep searching a term and finding nothing, that's a content brief, not a dead end.

Frequently asked questions

What is Zendesk Guide? Zendesk Guide is Zendesk's knowledge base product, now called Zendesk Knowledge in the plan documentation. It's the system where you create, organize, publish, and search help content, and it powers the customer-facing Help Center, where end users read articles and search for answers.

What's the difference between Zendesk Guide and the Help Center? Guide is the back-end product you manage; the Help Center is the public-facing website Guide generates for your customers. You author and organize content in Guide; customers experience it on the Help Center. See knowledge base vs. Help Center vs. Guide for a full breakdown.

How is a Zendesk knowledge base structured? Content uses a three-level hierarchy: Categories (top-level buckets) contain Sections (which can nest up to five levels deep), and Sections contain Articles (the actual content). Visibility permissions are set per article, and only Knowledge admins can manage categories and sections.

Is Zendesk Guide included in the Zendesk Suite? Yes. Knowledge comes with Suite Team, Knowledge Professional with Suite Growth and Professional, and Knowledge Enterprise with Suite Enterprise and Enterprise Plus. Older standalone "Guide Legacy" plans still exist on some pre-2017 accounts; check your subscription in Admin Center to confirm your tier.

Does Zendesk Guide have AI? Yes. The main native feature is generative search, which writes a "Quick answer" from your articles and is listed on all Suite and Knowledge plans, as long as your theme includes the generative answers helper. Beyond Zendesk's native AI, an AI agent layer can read your Guide knowledge base to draft and resolve tickets; the better your KB, the better any of these features perform.

How does the knowledge base help with AI ticket resolution? AI agents read your published articles to answer customer questions automatically, directly in the Help Center or inside tickets. The KB is the source of truth the AI draws from, so a clean, current knowledge base is what makes automated resolution accurate. See connecting a knowledge base to an AI agent.

Where should you go next?

Start broad, keep the KB current, and write titles the way customers search. Then go deeper on the pieces that matter most: the Help Center, the self-service portal, content blocks, and themes.

Plan names, generative search limits and the content hierarchy checked against Zendesk's official documentation on 24 September 2026. Zendesk updates its product and plans periodically, so confirm specifics in your own account before relying on them.