Zoho Desk Knowledge Base: Set Up a Help Center by Edition

A Zoho Desk knowledge base costs nothing to start, but customers can only read it from Standard. Free and Express keep articles agent-only. Standard is the first edition with a public knowledge base, community forums and the ASAP widget, at $20 per agent per month billed monthly or $14 per agent per month billed annually ^[1]. Professional adds CSS, articles in over 40 languages, 301 redirects and Google Analytics; Enterprise adds HTML control, multi-brand help centers and auto-translation. Our verdict: start on Standard if one brand and one language cover your customers.

Which edition puts articles in front of customers

The gate that matters is public visibility. On Free, the knowledge base is a private, agent-only library with article versioning. Express keeps that private model, lets agents save a ticket resolution as an article, and adds custom domain mapping. Standard opens the doors to customers. Every agent needs a seat on the same edition, so the bill grows with headcount; our pricing breakdown has the full math. The table shows where each self-service layer starts.

If customers must read your articles, Free and Express are out. If you need two languages or your own styling, budget for Professional at $35 per agent per month billed monthly or $23 billed annually. For five agents billed annually, Standard comes to $70 a month and Professional to $115 a month, so styling and languages cost $45 a month more, or $540 a year, by our arithmetic. That gap is the real decision for most small teams, and it is worth paying only if a second language or a branded look is already on your roadmap.

Build the structure before the first article

Articles sit in a tree: category, sections, then sub-sections, with at most three levels under a category and up to 700 sections per category, root included ^[2]. Each new department creates a default category. A category belongs to one primary department, and only that department's agents create, edit and delete its articles. Visibility is set per category: None, Groups, Public, Agents or Custom IP. Agents-only categories never reach the help center, so internal runbooks belong there, and child sections inherit the category's visibility.

Each article then takes its own permission of Agents, All users or Registered users. User groups, not on Free, narrow access further: up to 200 groups per help center and 2,000 end users per group. Inside the team, permissions run from View up to Admin Access, which covers every department. Light agents can get View permission to read articles; they are an add-on from Standard at $6 per light agent per month, and Enterprise includes 50. Pick the permalink format too: title, article number, or both. Article numbers cannot be edited once assigned. Decide this first.

Write, review and retire articles

The editor handles accordions, tabs, tables, code blocks and a table of contents built from Heading 1 to Heading 3. Article templates, from Standard, fix the format so ten writers produce one style. Drafts save automatically. Each saved draft counts as a minor version and each publish as a major one, and restoring an older version creates a new latest version instead of erasing history. Owners and admins can compare any two versions side by side before deciding which one stays live.

Review is set per category, never per article. Turn it on and only reviewers can publish. A category takes up to 50 reviewers from its primary department, and a submitted article goes to all of them at once. Review cannot be enabled on a category associated with another department, so plan departments and categories together. Put an expiry date on anything tied to a price or a policy: owners get emails seven days and one day before, and an expired article leaves the help center until someone republishes it.

Tickets are the cheapest source of new articles. From Express, agents can save a resolution as an article, and Zia's article generation starts there too, but Express and Standard run it only with your own OpenAI key, billed by OpenAI. Zia's own model starts on Professional and runs only in the US, IN, AU, EU, JP and CA data centers. Zia's generated content works on English text only. Our AI playbook compares the engines and their data-center limits in detail.

Make the help center findable and on-brand

Every article has an SEO section for title, meta description, keywords and tags, and each help-center page takes its own meta fields plus NoIndex and NoFollow switches. The optional XML sitemap updates every five days and exists only for domain-mapped help centers. It leaves out agent-only, registered-user, draft and expired articles. Permalinks break quietly. Edit one without a redirect and external links return a 404. 301 redirects start on Professional, with a maximum of three per article ^[3].

The help center has seven page types you arrange with drag-and-drop widgets such as Popular Articles and Announcements. CSS customization starts on Professional, imported as a .css or .txt file up to 1 MB ^[4]. HTML customization is Enterprise only and does not work in the Flat theme; custom JavaScript is Enterprise too, enabled on request. Google Analytics 4 connects from Professional, and its data can take up to 72 hours to sync accurately, so judge traffic only after the first few days.

Sign-in, brands and languages

An open help center lets anyone search articles and submit tickets, while customers log in to track ticket status; you can instead make registration mandatory. Users join by invite, self-signup, moderated self-signup, or an automatic invite after their first ticket. From Standard, sign-in can run through SAML, JWT, OpenID Connect or federated login with Google, Facebook, LinkedIn or Zoho accounts. Help-center MFA, also from Standard, uses codes from an authenticator app. Enterprise adds SMS one-time passwords, which work only with Indian mobile numbers.

Multi-brand is Enterprise territory. Each brand is a department with its own help center, logo, colors and permissions, served from a common user base with one login or a unique user base per brand. Switching to unique cannot be rolled back by admins. Enterprise costs $50 per agent per month billed monthly or $40 billed annually. For five agents billed annually, that is $200 a month against $115 on Professional, or $1,020 a year more, by our arithmetic. It rarely pays for one brand.

A multilingual knowledge base starts on Professional, where translation is manual. Enterprise adds automatic translation through Google Translate or Unbabel with your own API key, or through Zia. Auto-translated articles land as drafts you publish yourself, and categories and sections are never auto-translated. The help center does not pick its language from the visitor's browser. Change the default language and any article not translated into it stops showing, so translate before you switch.

Community, the widget and the Answer Bot

Community forums arrive with Standard, with topics typed as Discussion, Announcement, Question, Idea or Problem, up to 50 moderators per category, and best-answer marking. Categories cannot be deleted, only renamed. Professional adds Gamescope points and badges. The ASAP widget puts the knowledge base, community and ticket form inside your site or app, with SDKs for Android, iOS, Flutter and React Native. Guests can read and submit tickets; JWT-authenticated users can also track tickets and post. The Answer Bot or live chat inside ASAP needs Enterprise.

The knowledge base dashboard is your editorial to-do list. It splits search keywords into popular and failed, the second being searches that returned no article, and counts how often agents reference each article in tickets. Readers leave written feedback only through Dislike, and that feedback can become a ticket automatically. The Answer Bot, from Standard, answers customers from your articles. Zoho recommends at least 30 articles per department, though it can work with one trained article. It is not offered in the China data center.

The bottom line

For most small teams the answer is Standard: a public knowledge base, forums, the ASAP widget and single sign-on for $14 per agent per month billed annually. Move to Professional when you need a second language, your own CSS, or 301 redirects for permalinks you expect to change. Move to Enterprise only for multi-brand help centers, auto-translation or HTML control. Whatever you pick, settle the category tree, the review rules and the permalink format before the first article, because those three are the hardest to unwind once customers and search engines depend on them.