Zendesk Guide Lite
Zendesk Guide Lite is the knowledge base that comes free with Support. More capable than people expect, and there are three specific moments when it stops being enough.
What Zendesk Guide Lite is
Guide Lite is the entry-level knowledge base included with Zendesk Support rather than sold separately. Turn it on and you get a working help centre: categories, sections, articles, search, and a theme you can brand.
The naming is a historical artefact and it confuses people. Zendesk now sells Suite plans, and Guide capability scales with whichever Suite tier you're on rather than being bought as a separate product with its own name. Guide Lite still appears in older documentation and in Support-only accounts. Check what your account actually includes in Admin Center, because a plan comparison page from three years ago will mislead you.
What matters isn't the label but the capability line. Roughly, there are three of them.
Guide capability by tier
Feature availability shifts between plan revisions. Verify against the current Zendesk plan comparison before you buy.
| Lite | Professional | Enterprise | |
|---|---|---|---|
| Public help centre | |||
| Categories, sections, articles | |||
| Theme branding and settings | |||
| Custom theme code | |||
| Multiple languages | |||
| Article labels | |||
| Community forums | |||
| Content blocks | |||
| Team publishing and approvals | |||
| Multiple help centres | |||
| Custom user segments for articles |
What Lite genuinely does well
Do not write it off. A single-brand, single-language company with a couple of hundred articles can run a perfectly good help centre on the entry tier, and plenty do.
You get search, structure, branding through the theme settings, article ordering and the request form. That's the whole core loop of self-service: customer searches, finds an article, doesn't raise a ticket.
The most common mistake is upgrading to fix a content problem. If your help centre is not deflecting tickets, the reason is almost never a missing feature. It's that the articles are thin, out of date, or written from the company point of view rather than the customer question. No plan tier fixes that.
A quick test before any upgrade conversation. Take your ten highest-volume ticket subjects from the last quarter and search your own help centre for each one, in the words the customer used. If fewer than eight return a genuinely useful article in the first three results, you have a content problem and Enterprise will not touch it.
The three triggers for upgrading
There are exactly three situations where a higher tier stops being a nice-to-have.
You need another language
Multilingual content is the cleanest upgrade case. Once you support customers in more than one language, translating the help centre isn't optional, and doing it outside Guide means maintaining parallel structures by hand. See Guide localization for what that involves.
More than a handful of people edit
Once five or more people can change articles, you want team publishing: drafts alongside published versions, review before publish, and the ability to let agents write without letting everyone publish. Below five people, a conversation does the same job.
You have real brands or real segments
Multiple help centres for multiple brands, or articles visible only to specific customer groups. If your content genuinely differs by audience and you are currently doing it with a naming convention and hope, the feature is cheaper than the mess.
Everything else, labels, content blocks, custom themes, is a productivity gain rather than a capability you lack. Nice, and not a reason on its own.
How to decide without guessing
Write down what you're trying to do, in one sentence, before looking at any pricing page. Then check whether the tier you are on can do it. Most upgrade conversations are really about a single blocked task, and naming it makes the decision obvious.
Two things worth checking before you commit. First, whether the feature you want is on Professional or genuinely only on Enterprise, since the gap between those is large and marketing pages compress it. Second, whether the upgrade applies to every agent seat, because Guide capability usually rides on your overall Suite tier and you pay for it across the whole team.
The plans and products guide covers how the pieces fit together, and the pricing comparison has the tier detail.
Frequently asked questions
What do the Guide plans actually differ on?
Zendesk Guide Lite vs Professional comes down to article approval, multiple brands and content blocks. Zendesk Guide Enterprise adds team publishing and richer permissions, and those are the only Zendesk knowledge base plans distinctions that matter.
Is Zendesk Guide Lite free?
It is included with Zendesk Support rather than sold separately, so there is no extra charge on top of your Support or Suite subscription. Confirm what your specific plan includes in Admin Center.
What does Guide Lite not include?
Broadly, custom theme code, multiple languages, labels, community, content blocks, team publishing and multiple help centres. The exact split moves between plan revisions, so check the current comparison.
Do I need Guide Professional for a multilingual help centre?
Multilingual content sits above the entry tier. It's the clearest reason to upgrade, since maintaining translated content outside Guide means running parallel structures by hand.
Is Guide Enterprise worth it?
It is worth it for team publishing, multiple help centres and article-level user segments. If none of those describe a problem you actually have, it is not.
The tier that pays for itself elsewhere
Whatever Guide plan you land on, roughly a tenth of your tickets are duplicates. Ticket Merger finds and merges them automatically.
Start free trial14-day free trial. No credit card required.