Learn

What is a help center?

A help center is a searchable place where customers or employees find instructions, policies and answers without contacting a support person. It combines articles and troubleshooting guidance with a route to individual help. Customer-facing help centers explain a product or service; internal ones help staff use company systems. This guide focuses on customer support.

Updated

What can customers do in a help center?

Customers use a help center to find an answer, follow instructions and decide what to do next. Search and browsing provide different routes to the same information, and a contact option covers questions the articles cannot resolve.

Imagine a fictional home coffee-machine retailer. A customer wants to know how to clean a removable filter, whether a replacement part fits their model or what to include in a return parcel. Those questions need different articles, but customers should be able to find each without knowing the retailer's internal departments.

Zendesk's end-user guide describes searching and browsing categories, sections and articles. That structure is a useful example of a help center's navigation; a customer should be able to begin from either a specific search or a broad topic.

How does a help center differ from an FAQ or customer portal?

A help center contains an organised collection of answers; an FAQ is usually a shorter set of common questions. A customer portal can include personalised account information and actions beyond documentation.

Place Main purpose Coffee-machine retailer example
FAQ page Answer a small set of recurring questions Whether the shop ships internationally
Help center Explain tasks, policies and troubleshooting Finding the correct replacement filter
Customer portal Show or change a customer's own information Viewing a particular order
Help desk Manage a request that needs investigation Investigating a missing parcel
Internal wiki Guide employees doing the work Supplier escalation instructions

These can share links without sharing an audience. A public explanation of returns should not expose internal supplier contacts or employee notes. A help article can explain how to reach an account page without displaying anyone's account details.

Which articles should you write first?

Write articles for the questions that repeatedly stop customers from completing an ordinary task. Start from actual requests and product instructions rather than a list of features the business wants to promote.

For the coffee-machine retailer, a first collection might cover identifying a model, finding compatible parts, delivery, returns and routine care. Each article needs a defined scope. A compatibility guide should say which models it covers and where the customer can find the model label.

Use the language in support requests as evidence for titles and search terms. "Which filter fits my machine?" is a better starting point than an internal stock-category name. Zendesk's content-planning guide recommends organising content with the audience's needs in mind.

Do not publish a universal troubleshooting answer when model differences matter. Link to the relevant manufacturer's instructions when those are the authority, and tell customers when they need individual support.

What makes an individual help article useful?

A useful help article answers one recognisable question and gives a clear next step. The opening should tell the reader whether the article applies before asking them to follow a long procedure.

A practical article pattern is:

  1. State the answer or expected outcome.
  2. Identify the models, account types or situations covered.
  3. List anything the customer needs before starting.
  4. Give numbered steps in the order they happen.
  5. Explain what success looks like.
  6. Show how to contact support if the steps fail.

For example, a replacement-part guide can show where to find the model number, how to compare it with the compatibility list and what information to send if no match appears. A picture can help someone recognise a label, but the essential instruction should also be written in text.

Avoid asking customers to send passwords or unnecessary personal information. A contact instruction should request only the details needed to investigate the problem.

How should you organise and publish a help center?

Organise a help center around customer goals, then review the content and its audience before publishing. A small number of clear categories is easier to navigate than a deep copy of the company's organisation chart.

Getting started, Using your product, Parts and Orders are plausible categories for the retailer. Add subtopics when the article count makes them useful. Zendesk's category and section documentation distinguishes top-level categories from sections that group related articles.

Before publication, check that links work, the instructions fit a phone screen and an unfamiliar reader can follow them. Give policy pages an owner. When a rule changes, update the public article and the support team's guidance together so customers receive a consistent answer.

Publishing is a separate decision from saving an edit. A draft can contain unfinished instructions or private notes. A publication review should check both accuracy and whether the information belongs outside the business.

How do you measure whether a help center works?

A help center works when customers can solve the problem they came with. Article views show attention, but they do not prove that the answer is useful or complete.

Look for searches with no relevant result, articles followed by repeat contacts and requests that quote confusing instructions. A heavily viewed returns article might be excellent, or it might be the page customers repeatedly reopen because the next step is missing.

Compare similar periods and topics. Fewer support requests can also reflect fewer orders, so volume alone is weak evidence. Pair available analytics with direct checks: ask someone unfamiliar with the product to find a compatible part and explain what they would do next.

AI support also depends on the quality of the published answers. A clear article gives an assistant a specific source; an undocumented exception still needs a person rather than a confident guess.

How does Mojobase provide a help center?

Mojobase publishes a Handbook collection as a searchable help center on a company address or an own domain. Only approved pages are included, and a person presses Publish; saving an AI edit does not immediately change the public site.

The support AI in Customers answers from published Handbook pages. For topics set to Auto it can reply directly; otherwise it drafts for a person to send, and uncertainty goes to a person. Replies appear in Activity. The connection keeps the public guidance and the support answers based on the same reviewed information. See the support-answer workflow and Zendesk alternatives for a comparison with dedicated support tools.

For other support approaches, compare Tidio alternatives and Zoho Desk alternatives.

Further reading

  1. Zendesk: Help center guide for end users (checked 7 Nov 2026)
  2. Zendesk: Planning your self-service content structure (checked 7 Nov 2026)
  3. Zendesk: Organising content in categories and sections (checked 7 Nov 2026)

Questions people ask

Is a help center the same as a knowledge base?

A knowledge base is the collection of written answers. A help center is the place customers visit to search or browse those answers and find a route to support. People often use the terms interchangeably.

What is the difference between a help center and a help desk?

A help center publishes information customers can use themselves. A help desk manages individual requests and the people resolving them. The two work together when an article cannot answer a customer's specific question.

Does a help center have to be public?

A help center can be public or restricted to signed-in customers. Public information suits common product questions; restricted documentation may suit account-specific services. Private account details should not appear in public articles.

How many help center articles should I write first?

Start with the recurring questions that block customers from using the product or service. There is no universal minimum. A small set of complete, accurate answers is more useful than many pages that leave the next step unclear.

Can a help center replace customer support?

A help center handles repeatable information, but individual problems still need a route to a person. Account access problems, unusual failures and exceptions to published rules often require investigation beyond an article.

Stop being the only one who knows how it all fits together.

The first 10 companies pay $29 a month for the first person and $19 for each after, for life. We open in small groups, and the waitlist goes first.