Collect genuine buying questions, identify the decision each affects and place essential information where it is needed. Use an FAQ for supporting answers, with an owner and source for each policy.
A useful pre-purchase FAQ answers the uncertainties that stop someone making an informed decision. Build it from genuine sales and support questions, answer directly, and put essential costs or eligibility conditions beside the offer. An FAQ supports the buying journey; it should not hide information needed to understand it.
The central task is editorial, not decorative. A polished accordion cannot compensate for vague answers or invented questions. This guide covers which answers to write and where they belong. The separate interaction guide covers how an expandable FAQ behaves.
Collect questions before inventing headings
Review recent enquiries, sales-call notes and customer-service conversations that you are permitted to use. Remove personal information before sharing examples more widely. Write down the customer’s wording and the point in the journey where the question arose. Do not translate everything immediately into internal product terminology.
Distinguish frequency from importance. A rare but consequential exclusion may deserve prominent treatment even if someone asks about it only once. A repeated question about delivery may indicate that the primary page needs correction rather than that the FAQ needs another entry.
GOV.UK’s user-needs guidance grounds content decisions in evidence from users. Treat proposed questions from your team as hypotheses until customer conversations or observed journeys support them. Keep a source note so later editors can understand why a particular answer exists.
Find the decision behind the wording
“Can I use my existing domain?” may mean “Will I lose my business email?” rather than a request for a technical definition. “How long does it take?” might refer to delivery, setup or the time the customer must contribute. Establish the actual uncertainty before answering confidently.
| Customer uncertainty | Useful answer | Placement |
|---|---|---|
| Is this suitable? | Eligibility and significant exclusions | Near the offer |
| What will I pay? | Full commitment and variable costs | Near the amount |
| What happens next? | Process and realistic expectations | Beside the action |
| What about my unusual situation? | Specific exception or contact route | Supporting FAQ |
Avoid headings such as “Why are we the best?” that invite promotional copy. “Does the package include rewriting my existing pages?” establishes a concrete boundary. It helps the customer and gives the business a statement it can verify against its actual scope.
Make the first sentence the answer
Begin with yes, no, a qualified answer or the relevant condition. Then provide the explanation and next step. Avoid a long introduction that makes the reader hunt for a decision. If the answer depends on the selected package or delivery destination, name that dependency.
For a fictional content review, “You receive recommendations; rewriting is a separate service” is clearer than “Our flexible solutions can meet your content needs.” The second phrase may sound positive, but it does not establish whether the advertised package includes rewriting.
W3C’s writing guidance supports meaningful headings, descriptive links and clear instructions. Use the customer’s vocabulary, explain unfamiliar terms and describe supporting destinations instead of repeating “click here” beside every answer. A short answer with a specific link can be more useful than an exhaustive policy pasted into the panel.
A worked example for a fictional service
Imagine an independent website review. Customers ask whether the reviewer will change their website directly. The answer could be: “This package includes a review document and a discussion of priorities. Editing the website is not included.” A separate implementation option can be linked when it actually exists.
Another question concerns page limits. Explain how pages are selected, whether different page types count differently, and when a revised scope is required. Do not promise to “accommodate anything” if extra work needs a separate agreement. A customer should be able to identify which route applies before sending a request.
A third asks whether account access is needed. If the review uses public pages, say so. If an optional private section needs assessment, explain the separate access arrangement without inviting passwords through a general form. These answers resolve different concerns and should match the team’s real operating process.
Move essential terms into the main journey
Read the offer without opening an FAQ. Can someone understand the deliverable, significant exclusions, financial commitment and next action? If not, move that information into the primary page. A supporting answer can add examples; it should not be the first place revealing a material limitation.
Do not make a delivery FAQ the only way to discover that the store cannot ship to a region. Similarly, a required subscription belongs beside the product that depends on it. Place information at the point where it changes the decision, even if that means removing the same question from the FAQ.
GOV.UK’s guidance on understandable questions emphasises clear wording and relevant help. The commercial adaptation here is editorial judgment: each answer should help this reader make this decision, rather than satisfy an arbitrary target number of FAQ entries.
Maintain one answer to each policy question
Give each answer an owner in pricing, operations, product or customer service. Record the maintained source of the underlying rule. If the rule appears in several places, use a shared source or a documented update checklist so the FAQ, checkout and confirmation cannot quietly drift apart.
Set review triggers as well as dates. A changed package, delivery area or refund process should prompt a review of affected answers. Keep a short change note. Retire old product-launch questions that no longer help current visitors, and leave a clear contact route for cases the published answer cannot cover.
Check contact outcomes too. An answer that tells a visitor to request an assessment is incomplete if the form offers no relevant option or the team no longer handles that request. Content and operational capability need to remain aligned.
Review comprehension on a real phone
Ask a prospective customer to find an answer without telling them which heading to open. Then ask them to explain the relevant condition. Record findability and understanding separately. An opened panel does not prove that the reader interpreted its content correctly.
Review long answers, lists and links at narrow widths. Check that the current policy destination opens and interactive controls work with a keyboard. Do not judge content solely by the balance of desktop columns. Shorter paragraphs and precise headings make the same factual answer easier to navigate.
After publication, review repeated questions and inaccurate expectations alongside enquiry totals. Fewer questions may mean better information, but they may also mean fewer visitors or a broken contact route. Interpret the evidence in context and improve the answer without claiming an unsupported conversion gain.
Continue with the relevant checks
Choose clear disclosure behaviour for supporting answers. Read visit and enquiry evidence in context. Identify the language of your published answers.
Sources and verification
Editorial review 2026-10-18. Source check dates are recorded separately. Notes describe what each source supports and its limits.
View sources
- GOV.UK: user needsChecked Content decisions grounded in user evidence.
Limits: Does not prescribe commercial FAQ counts or conversion outcomes. - W3C: writing for accessibilityChecked Meaningful headings, links and instructions.
Limits: General tips, not proof of accessibility conformance. - GOV.UK: designing good questionsChecked Understandable wording and relevant help.
Limits: Form-question guidance adapted editorially to customer questions.