Zendesk FAQ Pages That Deflect

Guide has no FAQ object. A Zendesk FAQ is just articles arranged well, and the arrangement decides whether anybody finds them.

Start free trial All guides

There's no Zendesk FAQ feature, and that's fine

People go looking for an FAQ setting in Guide and come back confused. There isn't one. What you get is categories, sections and articles, plus search and permissions on top.

So an FAQ is a decision about shape, not a feature you switch on. You have two options and they behave very differently once real customers arrive.

One article, many questions. A single page with a question as each H2, plus a table of contents. Reads like a classic FAQ. Easy to skim.

One section, many articles. Each question is its own article, titled as the question. Slightly more admin. Much better in search.

Why one question per article usually wins

Three reasons, and all three show up in your numbers.

Search results are article-level. If ten questions share one page, Guide can only offer you the page, and the customer lands at the top of a wall of text and has to hunt. Individually titled articles land the customer on the answer.

Article metrics are article-level too. A single FAQ page tells you nothing about which of its twenty questions people came for. Twenty articles tell you exactly, and that list is the most useful piece of product feedback support produces.

And the AI features that read your help centre work on articles. A page that answers twenty unrelated questions is a poor retrieval target, whatever the model.

The exception is genuinely short answers, five or six of them, on a topic nobody searches for in isolation. Shipping details, opening hours, that kind of thing. Put those on one page and move on.

Structuring the section

Name the section the way customers describe the problem, not the way your org chart describes it. "Billing and payments" beats "Revenue Operations". Obvious, and violated constantly.

Title each article as the question, in the customer's words. "Why was I charged twice?" outperforms "Duplicate charge policy" because it matches what people type.

Answer in the first two lines. Preview text and AI snippets both take the opening. Context after, answer first.

Use manual ordering where the order carries meaning, otherwise let recency sort it. Guide lets you set article position within a section.

Promote the handful that matter. Promoted articles surface on the section or category page, which is your only real merchandising lever.

Add labels. They feed search and related-article suggestions, and they cost nothing to maintain.

Writing answers people accept

A deflecting answer does one thing an unhelpful one doesn't: it ends the task.

That means the next action is in the article. A link to the cancellation page, the actual refund window in days, the exact place in the app where the setting lives. "Contact us for more information" at the bottom of an FAQ is an instruction to raise a ticket, and customers follow it.

Keep the register plain. Nobody is reading an FAQ for pleasure and hedged legal phrasing reads as evasion, which sends people to the contact form faster than no answer at all.

If the honest answer is no, write no. A clear no deflects. A vague maybe does not.

Finding out which ones work

Guide reports article views, and views on their own are close to meaningless. Pair them with two other things.

Search terms with no results, from your Guide search reporting, tell you which FAQ you have not written yet. That report is the single highest-value thing in Guide analytics and most teams never open it.

Ticket volume by topic tells you which FAQ isn't working. High views plus high tickets on the same subject means the article is found and rejected, which is a rewrite, not a promotion.

Review both quarterly. An FAQ set that nobody prunes turns into a graveyard of answers about features you removed, and stale answers are worse than missing ones because customers act on them.

The repeat-question tell

One pattern is worth naming. When a question is missing from your FAQ, you don't get one ticket about it. You get the same ticket over and over, sometimes from the same person twice, once through email and once through the form because they weren't sure the first one went through.

Sudden clusters of near-identical tickets are usually a documentation gap wearing a costume.

FAQ

Frequently asked questions

How do you build an FAQ section in Zendesk?

As a section of articles, one question each. A Zendesk help center FAQ isn't a feature, so an FAQ section Zendesk customers actually use is just a well-named section pinned to the home page.

Does Zendesk Guide have a built-in FAQ page type?

No. You build FAQs from ordinary articles and sections. The structure you choose is the whole design decision.

One long FAQ page or separate articles?

Separate articles in almost every case. They rank better in Guide search, produce per-question metrics, and work better with AI answers. One page is fine for five trivial questions.

How many FAQ articles should we have?

Start with the twenty questions that generate the most tickets. Write those properly rather than writing eighty thin ones nobody maintains.

Where do I see what people searched for?

Guide search reporting shows search terms, including searches that returned nothing. Check the current Zendesk docs for where it sits in your plan, since the reporting has moved between Guide and Explore.

Should FAQ articles be visible to everyone?

Usually yes. If some answers are only for signed-in customers, control it with user segments rather than by hiding the whole section.