← Back to the journal

Words & pictures

An FAQ Page That Answers Questions and Saves Calls

A good FAQ page answers the questions you get on the phone all day, so customers help themselves and you get fewer interruptions.

July 28, 20264 min read

Every time your phone rings with the same question — "Do you take card?", "Are you open Sundays?", "Do you come out to my area?" — that's a call you could have skipped. A well-built FAQ page answers those questions once, in writing, so customers find the answer themselves and you get on with your work. Done right, it also quietly builds trust: people can see you've thought about their worries before they even ask.

Here's how to build one that actually earns its place, not a dusty list nobody reads.

Start with the questions you already get

Don't invent questions. Write down the ones you hear every week. The best source is your own phone and inbox. For a few days, jot down every question a customer asks before they book or buy.

A two-van electrician might collect things like:

  • "Do you charge a call-out fee?"
  • "How soon can you come for an emergency?"
  • "Which areas do you cover?"
  • "Are you insured and registered?"

A bakery might hear:

  • "Can you make a cake without nuts?"
  • "How much notice do you need for a custom order?"
  • "Do you deliver, or is it collection only?"

Ask the people who answer your phone too — your partner, an apprentice, whoever picks up. They often remember the annoying repeat questions better than you do. Aim for a first list of ten to fifteen real questions. That's plenty to start.

Write answers the way you'd say them out loud

The mistake most people make is writing stiff, half-answers that raise more questions than they settle. Write like you're talking to a customer standing in front of you. Be specific and commit to a real answer.

Compare these two:

"Delivery may be available depending on circumstances."

versus

"We deliver free within town for orders over a small minimum. For villages nearby, there's a small delivery charge — call us and we'll tell you before you order."

The second one actually answers the question and heads off the follow-up call. A few tips:

  • Put the answer first. Don't make people read a paragraph to find the yes or no.
  • Keep each answer short — two or three sentences is usually enough.
  • Say what to do next. If the honest answer is "it depends," tell them how to get a firm answer: "send us a photo," "call between 9 and 5," "fill in the booking form."

Avoid promising exact prices or timings you can't guarantee. Instead of a figure that goes out of date, say how it's decided: "We quote per job after seeing the space," or "Call-outs are booked same-day where we can."

Group and order questions so people find things fast

Ten questions can sit in one list. Once you have more, group them under small headings so a customer can scan straight to what they need. A restaurant might use headings like Booking, Dietary needs, Parking and access, and Payment.

Order matters too. Put the most common questions at the top, not buried at the bottom. If everyone asks about opening hours, that goes first. Think of it as answering questions in the order a customer thinks of them: can you help me, when, where, how much, how do I book.

Keep the whole thing on one page if you can. People are used to scrolling and pressing Ctrl+F (or using their phone's "find on page") to jump to a word. Splitting FAQs across ten separate pages just hides the answers.

Keep it honest and keep it current

An FAQ page only saves calls if it's right. A wrong answer costs you more than no answer — the customer turns up expecting something you didn't mean. Set a reminder to reread it every few months, and update it the moment something changes: new opening hours, a new service, a policy you've tightened.

When a new question keeps coming up on the phone, that's your cue to add it. Your FAQ should grow with your business. A club that suddenly gets lots of "can non-members come to the summer event?" questions should add that answer the same week.

For anything with legal weight — refunds, cancellations, guarantees, your obligations — give the plain-English version of your policy and be clear it's your policy, not legal advice. If you're unsure where you stand, check with a professional before you publish a promise you can't keep.

One last thing: link to your FAQ from the places people look — your contact page, your booking form, the automatic reply on your email. That's how it actually catches questions before they become phone calls. If you build your site with something like Foliovo, an FAQ section is one of the easier pages to add and keep tidy — but the value is in the answers, not the tool.

More posts

Rather have it built for you?

Tell us about your business and see a real, finished website in seconds.

Create free preview