# Zendesk Help Center: Setup, Plan Limits and Self-Service Guide

> Zendesk help center guide: knowledge base, community and portal, what each Suite plan unlocks, limits, AI search, SEO and the 2027 theme deadline.

_Source: https://professionalstoolkit.com/articles/zendesk-help-center — The Professional's Toolkit · updated November 2026_

---

A Zendesk help center is a branded support site that holds three things: a knowledge base of articles, an optional community forum, and a customer portal where people submit and follow their requests. It comes with every Zendesk Suite plan, not with Support Team, which is email ticketing only and gets the help center as a separately sold product. Zendesk's pricing page lists Suite Team at $55 per agent per month billed annually ($69 billed monthly), with one help center in one language[1]. Suite Professional, at $115 per agent per month billed annually or $149 billed monthly, unlocks up to five help centers, 40+ languages, community and portal ticket management. Every agent seat is paid, so read [our Zendesk pricing breakdown](/articles/zendesk-pricing) before sizing a team.


**40,000** — Articles a single Zendesk help center can hold (archived articles and translations excluded)



- **1 vs 5** — Help centers on Suite Team vs Suite Professional
- **100,000** — Generative searches a month included in Suite and Knowledge plans
- **Jul 31, 2027** — Deadline to move custom help center themes to templating API v4


## What each plan unlocks in the help center

The plan decides more than the article count. Suite Team gets a working knowledge base with article comments and the standard Copenhagen theme, but several pieces that self-service teams expect only start one plan higher. **The second language is the most common upgrade trigger**, because Suite Team stays at one default language. Custom code, labels, user segments and the automatic XML sitemap are also missing there. Suite Enterprise, which is quote-only, adds the editorial controls a larger documentation team needs: review workflows, scheduled publishing, reusable content blocks and nested sections.

| Help center feature | Suite Team | Suite Professional | Suite Enterprise |
|---|---|---|---|
| Help centers per account | 1 | Up to 5 | Up to 5 |
| Languages | 1 default | 40+ | 40+ |
| Community forums (Gather) | No | Yes | Yes |
| Ticket management in the customer portal | No | Yes | Yes |
| Theme code editing, custom and Marketplace themes | No | Yes | Yes |
| Labels, user segments, XML sitemap | No | Yes | Yes |
| Team Publishing, content blocks, nested sections | No | No | Yes |

Upgrading changes the bill for every seat, not for the help center alone. The gap between the two listed Suite plans is $60 per agent per month billed annually, or $720 per agent a year by our arithmetic; billed monthly the gap is $80 per agent per month ($149 vs $69). For a three-agent team that wants a Spanish version of its articles, that is $2,160 a year; at twenty agents it is $14,400. Price the language need against the whole team.

## From setup mode to launch

A new help center starts in **setup mode**. Customers cannot see it; only agents and admins can. Only the account owner can enable the help center, and activating it needs a Zendesk Support administrator, so a Knowledge admin alone cannot flip the switch. Plan for that hand-off if your documentation lead is not an account admin.

Branding needs no code on any plan. You change the logo, colors and fonts in the settings, and you can map a custom subdomain such as help.yourcompany.com through host mapping. The structure has three levels a reader sees: categories, sections and articles (Suite Enterprise adds nested sections). A trial help center ships with an Agents only section, which shows the pattern for an internal knowledge base: restrict a section and agents search it alongside the public articles at no extra cost.

Decide early who may read what. Article viewing can be set to everyone, signed-in users, agents and admins, or up to 10 custom user segments per article, but user segments are not on Suite Team. Admins can also require sign-in for the whole help center and its request form. One side effect matters: a help center that requires sign-in gets no automatic sitemap, because search crawlers cannot reach it.


> 💡 **Build the internal section first:** Restrict a section to agents and you get an internal knowledge base that agents search alongside public articles at no extra cost. It also lets you test structure while the help center is still in setup mode.


Anonymous requests changed in 2026. A request from someone who is not signed in now lands as a suspended ticket and triggers a verification email; it stays suspended until the person clicks the link or an agent recovers it. Triggers do not fire until then. Admins can turn verification off, but Zendesk warns that doing so opens the account to email spam.

## Building the knowledge base

The ceilings are generous for a small team. A help center holds 40,000 articles, 5,000 per section, 100 categories and 100 sections per category[2]. Each article can reach 1 MB per translation, and uploads top out at 20 MB per file. The limit that shapes writing is search: native search reads only the first 10,000 characters of an article. **Put the answer near the top.** Titles carry the most weight in search, labels less, the body least, so a title phrased the way customers ask beats a clever one.

Renaming or moving an article keeps its ID, so old links keep working. Archiving is different: an archived article disappears and links to it stop working until you restore it. If you plan to use AI agents, Zendesk recommends at least 10 published articles on common questions before you start.

AI can draft the first set. Zendesk says Knowledge builder analyzes historical tickets and drafts a knowledge base structure and articles that admins review and publish. Knowledge copilot, an early access program open to Suite Professional and above, adds a health report on coverage, freshness and AI readability, plus an article builder that drafts from ticket data or prompts. Its procedure builder needs the Copilot add-on.

Editorial control scales with the plan. On Suite Professional, edit and publish permissions are granted together. On Enterprise they split, and Team Publishing adds Author, Approver and Publisher roles, review assignments, verification reminders and content blocks that update one passage across many articles. The Knowledge dashboard tracks search activity, including searches with no result or no click and tickets created afterwards, which shows where articles are missing.

## Community forums and the customer portal

The community is Zendesk Gather, available on Suite Professional and above, and it needs a help center first. Adding a community to a live help center does not switch it on; you activate it deliberately. Limits are wide: 750 topics, unlimited posts and 1,000 comments per post. Agents can turn a community post or an article comment into a ticket, which keeps public questions inside the queue.

The customer portal is where people submit tickets when the articles fail, and where they follow up. On Suite Team they can submit, but **ticket management in the portal is not available**: customers cannot review and manage their requests there. End users must sign in to comment anywhere in the help center, and spam tools cover every plan except word moderation.


> ⚠ **Suite Team portal is submit-only:** On Suite Team customers can submit requests through the help center, but ticket management in the customer portal starts on Suite Professional.


## Search, AI answers and SEO

Generative search is on by default. For queries of two or more words it writes an AI answer from the top results, and Suite and Knowledge plans include 100,000 generative searches a month; Zendesk sells a Generative Search Extender through Sales for more[3]. One cost hides here. When a conversation that starts in generative search is resolved by an AI agent, it consumes an automated resolution. Past the plan allowance (5 per agent per month on Suite Team, 10 on Suite Professional, up to 10,000 a year), each extra resolution costs $1.50 when bought ahead (committed) or $2.00 pay-as-you-go. Our [Zendesk AI playbook](/articles/zendesk-ai-playbook) covers that meter.

Federated search pulls outside content into results: other knowledge bases, blogs, course pages and website pages, through a no-code crawler or an API. You get 50 external sources, and external records stop at 10,000 on Team plans, 50,000 on Professional and 100,000 on Enterprise. External results show in help center search and in the knowledge section of the agent's context panel, but not in Instant Search. Themes created before September 25, 2019 might need changes before federated search works.

For search engines, the help center handles the basics itself. It uses canonical URL tags, hreflang tags on its main page types, and HTTPS everywhere. Articles and community posts get an automatic meta description from their first 140 characters, so write that opening for humans and search snippets at once. The XML sitemap is generated automatically and refreshed every two hours, but it skips community content and is not available on Suite Team.


> 💡 **Write the first 140 characters twice:** Zendesk turns the opening 140 characters of each article into its meta description, and search reads only the first 10,000 characters. Lead with the answer in plain customer wording.


## Themes: Copenhagen, custom code and the 2027 deadline

Copenhagen is the standard theme. Zendesk supports and auto-updates it, and you adjust it through branding settings, not code. Custom themes and Marketplace themes are off the table on Suite Team. From Suite Professional you can edit code, but a custom theme is no longer updated by Zendesk, because an update would overwrite your changes. An account can hold 10 themes and 100 custom pages.

**Custom themes face a hard date.** Zendesk is removing templating API versions 1 to 3, and themes must move to version 4 before July 31, 2027, when remaining legacy themes are force-upgraded[4]. A command-line upgrade tool arrives November 25, 2026 and an in-product tool on March 1, 2027. Check the api_version field in your theme's manifest now.

The next theme is already in early access. Lisbon powers a conversational help center where visitors ask questions in plain language and get quick answers that link to source articles. It is configured entirely through settings, with no code. It needs Quick answers on, AI agents configured, the Web Widget embedded in the help center and multi-conversations enabled; our [Web Widget guide](/articles/zendesk-web-widget) covers that last piece.


## FAQ

**Can I get a Zendesk help center on Support Team?**

Not as part of the plan. Support Team is email ticketing only; Zendesk sells the help center to Support plans as a separate product and includes it in every Suite plan.

**Does help center content carry over after a Zendesk trial?**

Yes, if you buy a plan: data, configuration, ticket history and help center articles carry over. Under Zendesk's Free Trial Terms, trial data is lost at the end of the trial unless you buy or export it.

**Can I connect Google Analytics to a Zendesk help center?**

Yes, Zendesk offers a built-in Google Analytics option for page views. Where cookie consent is required, analytics must be added through theme code, which Suite Team cannot edit.

**Is there an API for help center content?**

Yes. The Help Center API follows the Support API per-minute limits (200 a minute on Suite Team, 400 on Suite Professional) but is counted separately. Accounts created since July 28, 2026 cannot use API tokens at all, no account can create new tokens since October 27, 2026, and existing API tokens stop working on April 30, 2027, so integrations must use OAuth.


## The bottom line

Zendesk's help center is a complete self-service site, but the plan sets its shape. Suite Team covers one branded knowledge base in one language with a no-code theme, which suits a single-market team starting out. A second language, community forums, portal ticket management, custom code or the XML sitemap all mean Suite Professional for every agent seat, so price that upgrade across the team. Whoever owns a custom theme should schedule the version 4 upgrade before July 31, 2027.



## Sources

[1] Zendesk Pricing Plans - Starting from $19/month Skip to main content Try for free Platform Zendesk Resolution Platform Deliver faster, highe — https://www.zendesk.com/pricing/ (2026-11)
[2] Zendesk help: Knowledge product limits for your help center — https://support.zendesk.com/hc/en-us/articles/4408831783962-Knowledge-product-limits-for-your-help-center (2026-11)
[3] Zendesk help: About Zendesk product add-ons — https://support.zendesk.com/hc/en-us/articles/4408834152730-About-Zendesk-product-add-ons (2026-11)
[4] Zendesk help: Announcing the removal of help center templating APIs v1, v2, and v3 — https://support.zendesk.com/hc/en-us/articles/11058580642202-Announcing-the-removal-of-help-center-templating-APIs-v1-v2-and-v3 (2026-11)
[5] Zendesk help center — https://support.zendesk.com/hc/en-us
[6] Zendesk Customer Agreement — https://www.zendesk.com/company/agreements-and-terms/zendesk-customer-agreement/
[7] App Store (US), Zendesk Support listing — https://apps.apple.com/us/app/zendesk-support/id1174276185