What we do
Tools
Industries
Department
How we workLet's talk →
Home/Zendesk/Zendesk Help Center Setup, From Theme to Brands
Zendesk Guide

Setting Up a Zendesk Help Center That Stays Accurate After Launch

Launch day is easy to picture: a branded theme, tidy categories, a search box that answers the common questions. Six months on, a price has changed, the returns policy has moved, and three articles still say the old thing. Here's the setup in order, from structure to permissions to brands, then the part most Help Centers skip: tying each article to whatever system owns its facts.

Building the Help Center in the order that saves rework

  1. 1

    Sketch the structure before the theme

    Content sits in three levels: categories hold sections, and sections hold articles. Build the outline from your most common ticket reasons rather than your org chart, because that's how customers think about their problem.

  2. 2

    Pick and adjust a theme

    Start from Zendesk's standard Copenhagen theme and set colors, logo and fonts in its settings. Deeper changes mean editing the theme's templates, written in Zendesk's Curlybars language, and how much code access you get depends on your plan.

  3. 3

    Decide who can see and who can edit

    User segments group people by tags, organizations, groups or whether they're signed in, and control who can view a section or article. Management permissions control which agents can create, edit and publish. On Suite Growth and Professional plans, edit and publish rights go to one agent segment together. Enterprise plans let you give them to different segments.

  4. 4

    Add a Help Center per brand, if you run more than one

    In a multibrand account, each brand can have its own Help Center with its own theme, content and visibility. Agents still answer every brand's tickets from the same workspace.

  5. 5

    Translate, then turn on the request form

    Localized versions of an article sit alongside the original, so customers see their language where a translation exists. The request form gives anyone an article didn't help a way to open a ticket from the same page.

    Watch for: translations drift faster than the original, because nobody re-translates after an edit.

Who should see what

Content Visibility to set Watch for
Public how-to and policy articles Everyone, no sign-in needed Anything quoting prices, stock or dates needs an owner, or it's the first thing to go stale.
Account-specific or partner content A user segment built on organization or tag A tag-based segment is only as accurate as the tags on each user record.
Internal troubleshooting notes Agents and admins only The internal article is usually the true version. Customer articles copied from it fall behind.
A second brand's knowledge base Its own Help Center under that brand Articles copied between brands get updated in one and not the other.

Availability articles that used to lag behind the warehouse

Business publishing product availability in its Help Center

Before

Articles told customers which products were in stock or coming back. They were right on the day someone wrote them.

Once inventory moved, the articles stayed wrong until a customer complained or someone remembered to edit them.

After

n-frames built a sync on the Help Center API that updates those articles straight from the live inventory feed.

The articles change when the stock does, without anyone assigned to watch for it.

Before anything writes to your Help Center through the API

  • Which facts belong to a system, and which to a person?

    Only details that live somewhere else (stock, prices, specs, policy dates) should be written by a sync. Explanations and tone stay with your writers.

  • Does it write drafts or live articles?

    New articles generated from internal docs should land as drafts for review. A changed number inside an approved article can usually go straight through.

  • Which translations get updated?

    The API treats each language as its own translation of the article. A sync that only touches English leaves every other language behind.

  • Which account does it run under?

    Give it a dedicated agent account, so anyone looking at an article's edits can tell the sync's changes from a person's.

  • What happens when the source data is wrong?

    Have it skip and flag a value that looks off, such as a price of zero, rather than publish it to every customer.

Questions people ask

What's the difference between Zendesk Guide and the Help Center?

Guide is the Zendesk product you manage the knowledge base in. The Help Center is the customer-facing site it publishes. People use the two names almost interchangeably.

Can customers submit a ticket directly from the Help Center?

Yes. The request form, or the web widget, lets a customer open a ticket when an article doesn't answer the question, and it lands in the same Zendesk your agents already work in.

Is there an API for Zendesk Help Center articles?

Yes. The Help Center API can create, read and update categories, sections, articles and their translations. It's what makes it possible to update articles from another system, or to turn new internal docs into draft articles, instead of editing everything by hand.

Can I have more than one Help Center?

Yes, in a multibrand account. Each brand can run its own Help Center with separate branding, content and visibility settings.

Does the Zendesk Help Center support multiple languages?

Yes. You add localized versions of each article, and customers see their own language wherever a translation exists. Keep an eye on translations after edits, since they don't update themselves.

How should categories and sections in a Zendesk Help Center be organized?

Around what customers come to do: ordering, billing, returns, setup. Keep categories few and broad, put sections inside them for specific tasks, and let your ticket reasons decide which articles get written first.

Who builds a sync that keeps Help Center articles current?

We do, at n-frames: a job on the Help Center API that updates the facts in each article from the system that owns them, writes new articles as drafts from internal docs, and flags anything that looks wrong instead of publishing it.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.