The Zendesk Help Center, Built to Deflect
A help centre nobody reads is a content project. A help centre that removes tickets is a support strategy. The difference is mostly structure and measurement.
How Guide is organised
Zendesk Guide gives you three levels and most teams misuse the middle one.
You also get user segments and permission groups, which is how you publish internal-only runbooks in the same place as public articles without them leaking.
What to publish first
Do not start with a content plan. Start with your queue.
Export last month of tickets, group by subject, and take the ten questions you answered most. That list is your first ten articles, and it will beat any brainstormed content calendar because it is evidence rather than opinion.
Write each one to be findable rather than complete: the customer question as the title, the answer in the first two sentences, the detail underneath. Nobody scrolls a help article to find out whether it is the right article.
Getting the help centre in front of people
Publishing is the easy half. The second half is placement.
Measuring whether it works
Article views are a vanity metric. Two numbers matter.
Search with no results. Guide reports what people searched for and found nothing. That list is your next set of articles, written by your customers.
Ticket volume for the topic you documented. Pick a topic, write the article, place it properly, then watch that topic ticket count over the next month. If it does not move, the article is wrong, unfindable, or the problem is in the product rather than the documentation.
The deflection your help centre cannot do
No article prevents the customer who emailed you an hour ago and has now filled in the web form because nothing came back yet.
That contact is not an information gap, it is an impatience gap, and it produces a duplicate ticket rather than a new question. Documentation cannot touch it. Merging can.
Frequently asked questions
What is the difference between Zendesk Guide and Help Center?+
Guide is the product, the Help Center is what your customers see. In practice people use the terms interchangeably.
Can I restrict some articles to logged-in users?+
Yes. Articles can be public, restricted to signed-in users, restricted to specific organizations, or internal only, which is how teams keep runbooks alongside public content.
How many articles do we need?+
Ten good ones covering your top questions beat two hundred that nobody maintains. Add articles from the failed-search report rather than from a content calendar.
The tickets no article prevents
Duplicates arrive because someone got impatient, not because they lacked information. Ticket Merger removes those before an agent replies twice.
Start free trial14-day free trial. No credit card required.