An FAQ page that reduces support answers the real questions

Aug 29
3 min read

Updated: 3 days ago

Introduction

The FAQ page opens with a question asking what makes the company different, followed by one asking whether quality is important to them. Neither has been asked by a customer in the history of the business.

Meanwhile the same four genuine questions arrive by email every week, are answered individually every time, and appear nowhere on the site. A page built from what people actually ask reduces repetitive work and removes the obstacles stopping other people from buying.

1. An FAQ page that reduces support is built from evidence

Start with the record, not a brainstorm.

Go through the last few months of emails, messages and call notes and count what comes up. That list is the page, and it will differ substantially from what anybody in the business would have guessed if asked to write it from memory.

2. Write the questions in the customer's words

Phrasing determines whether it is found.

Use the language people actually use, including the terms the industry considers imprecise. A question phrased in your internal vocabulary will not match what somebody types into a search box or scans for on the page, however precise it is.

3. Answer directly and immediately

No preamble.

The first sentence should contain the answer, with any qualification following. Answers that open with context and reach the point three sentences later are abandoned before they get there.

4. Include the uncomfortable questions

The ones that matter most.

What happens if it goes wrong, why you cost more, what is not included, and what your cancellation terms are. Avoiding these does not prevent people from having the question; it only prevents them getting an answer, and a share of them resolve it by going elsewhere.

5. Group them so the page can be scanned

Structure over volume.

Sections by theme — pricing, timescales, process, aftercare — with clear headings. A single undivided list of forty questions is unusable, and everything below the first dozen is effectively invisible.

6. Keep each answer short and link to depth

The page is a routing layer.

Two or three sentences per answer, with a link to a fuller page where one already exists on the site. The reader who wants depth will follow it; the one who wanted a quick answer already has it. Long answers turn the page into an article and defeat the purpose of scanning it.

7. Put the answers where the question arises too

The page should not be the only location.

A question about delivery belongs on the delivery-relevant page as well. An FAQ page is a fallback for the people who go looking for one, and most people never do. Repeating the answer in context is what reaches everybody else.

8. Do not use it as a keyword exercise

A widespread misuse.

Pages of invented questions written to capture searches serve nobody and read as filler. The commercial benefit comes entirely from answering questions people genuinely have, which happens to also be what search engines reward. The two are not in tension and never were.

9. Update it from the inbox regularly

The page decays otherwise.

Every few months, check what is still arriving repeatedly and add it. If a question keeps being asked despite being answered on the page, the answer is unclear or in the wrong place.

Measure whether it is working by watching the questions that stop arriving. If the same four emails continue after publication, people are not finding the page, which is a navigation problem rather than a content one.

Conclusion

Build the page from your actual inbox rather than from imagination, because that is what makes it reduce work.

Phrase questions in the customer's words, put the answer in the first sentence, include the uncomfortable questions about cost and failure, group the entries so the page can be scanned, keep answers short and link to fuller pages, repeat the answers on the pages where the question naturally arises, avoid inventing questions for search purposes, refresh it from the inbox every few months, and judge success by which emails stop arriving.