Foldwren

Writing an FAQ page that actually answers questions

How to collect the questions customers really ask, answer each one directly, group them sensibly and keep your FAQ page up to date.

A good FAQ page is built from questions customers have really asked, answered in the first sentence. A bad one is a list of things the business wishes people would ask, followed by answers that never quite arrive.

You can tell which kind you are reading within seconds. "Why choose us?" is not a frequently asked question. "Do you charge a call-out fee?" is.

Collect real questions

Start by gathering evidence, not by brainstorming. Real questions live in:

  • Your inbox and enquiry form submissions
  • Text and social media messages
  • The phone. Ask whoever answers it to keep a tally for a fortnight.
  • Quotes and consultations, where people ask the things they were too shy to email
  • Reviews, especially the ones that say "I wish I'd known"

Write the questions down in the customer's words, not yours. A customer asks "How long will I be without a kitchen?" and a builder rewrites it as "What is the typical project duration?" Keep the first version. It is the phrase people search for and the one they will recognise on the page.

If you end up with more than about twenty, pick the ones asked most often.

Answer in the first sentence

The single most useful rule for FAQ writing is to put the answer first. Then add the explanation, the conditions and the detail.

Here is the question "Do you work weekends?" answered badly:

"We understand that our customers lead busy lives, and we always try to be as flexible as possible to accommodate individual scheduling needs."

And answered well:

"Yes, we work Saturdays from 8am to 1pm. We don't work Sundays or public holidays, except for emergencies, which cost extra."

The second answer starts with "Yes". If a question can be answered with yes, no, a number or a timeframe, start with that word.

Some more guidelines:

  • Be specific. "Usually three to five business days" beats "as soon as possible".
  • Be honest about the awkward ones. If you don't offer refunds on custom orders, or you can't service a certain suburb, say so plainly and briefly explain why.
  • Keep answers short. Two to four sentences. If an answer needs three paragraphs, it deserves its own page, and the FAQ can summarise and point to it.
  • Don't answer a question with a sales pitch. "How much does it cost?" should be answered with a price, a range or an explanation of what affects the price.

Take care with answers about refunds, warranties and guarantees. Customers have rights under Australian consumer law regardless of what your FAQ says, so make sure your wording doesn't contradict them. If in doubt, check the ACCC's guidance or ask an adviser.

Group them so people can find theirs

Twenty questions in one long list is hard work. Sort them under a few plain headings so a visitor can jump to the right area. For a house cleaning business, that might be:

  • Booking and prices: how to book, what it costs, how to pay, cancellation
  • The clean itself: what is included, how long it takes, products used
  • Access and pets: keys, alarms, dogs, whether you need to be home
  • If something goes wrong: breakages, complaints, re-cleans

Within each group, put the most asked question first.

Some questions belong elsewhere

Here is an opinion you may not expect from a web studio: the FAQ page should be a backup, not the main place for important information.

If nearly every customer asks whether you charge a call-out fee, the answer belongs on your pricing or services page, where they are already looking. If everyone asks about parking, put it on the contact page beside the map. The FAQ page can repeat the answer, but people shouldn't have to go hunting for it there.

A useful habit is to place two or three relevant questions at the bottom of each service page. Someone reading about your roof restoration service gets the roof questions right there.

And treat frequent questions as feedback. If people keep asking something your website supposedly covers, the page that covers it is unclear. Fix that page.

Keep it current

An FAQ with wrong answers is worse than no FAQ, because people act on it. The things that go stale fastest are prices, opening hours, turnaround times, service areas and anything that mentions a specific staff member or supplier.

Build a small routine:

  1. Put a reminder in your calendar every three months to read the whole page.
  2. Ask your front-line staff what new questions have come up, and add the common ones.
  3. Remove questions nobody asks any more.
  4. Check every answer after any change to your prices, policies or hours.

A quick audit of the page you have

If you already have an FAQ, run it through these questions:

  • Has a real customer asked each of these in the last year?
  • Does every answer begin with the answer?
  • Is each question written the way a customer would say it?
  • Could a new staff member use this page to answer the phone correctly?
  • Is there anything here that should really be on a service or contact page?

That fourth question is a handy test. A well written FAQ doubles as training material for new staff. If it wouldn't help someone in their first week, it probably isn't helping customers much either.

Your order