How to Write a Website FAQ Page That Reduces Phone Calls, Not Just Fills Space
The FAQ pages that actually work share one thing in common: someone sat down with a highlighter and went through a few weeks of real enquiries first. 💖 Most FAQ pages, by contrast, get written in a single sitting by someone imagining what people "probably" ask — and they end up full of softball questions nobody actually has ("What makes you different?") while missing the genuinely repetitive ones that are clogging the phone line ("Do you come to me or do I come to you?", "What happens if I need to cancel?"). The gap between those two approaches is the entire difference between a page that deflects calls and a page that just exists.
What most businesses get wrong
Most FAQ pages are written to sound reassuring rather than to actually answer anything. They hedge ("it depends," "every situation is different") where a specific, direct answer would have worked, and they're often buried at the bottom of the site in a spot nobody scrolls to before reaching for the phone. The honest purpose of an FAQ page isn't to look thorough — it's to let someone resolve their question themselves, right now, without waiting for a callback. If your FAQ answers are vaguer than what your receptionist or you yourself would say on the phone, the page isn't doing its job, and people will keep calling instead of reading.
The real-questions FAQ method — copy this:
- Collect two weeks of real enquiries. Every phone call, email, DM and in-person question someone asks before becoming a customer. Don't rely on memory — jot them down as they come in, or ask whoever answers the phone to do the same.
- Group them into themes and count frequency. You'll usually find 8-12 questions cover 80% of what comes in — pricing, timing, logistics, cancellations, "do you do X" edge cases. Those are your FAQ page, in order of how often they're asked.
- Write each answer the way you'd actually say it out loud — specific numbers, specific timeframes, no corporate hedging. "Yes, we can usually fit same-week bookings in" beats "availability varies."
- Add one honest limit to any answer that has one. If something only applies in some cases, say which ones — a reader who later finds out the real answer was more complicated will trust you less than one who got the nuance up front.
- Link each answer to the next logical step — a booking page, a contact form, a pricing page — so someone whose question is answered can act immediately instead of having to go hunting for what to do next.
How to actually set this up
Put the FAQ page somewhere people will genuinely find it — linked from the main navigation, and also embedded directly on the pages where the relevant questions actually arise (pricing questions near pricing, booking questions near the booking button), not just as one isolated page nobody stumbles across. Use real, specific headings as questions (not "Pricing" but "How much does this cost?") since people scan for their exact question rather than reading a page top to bottom. Keep answers short — two to four sentences is usually enough; if an answer needs a full paragraph, it's probably a sign that question deserves its own dedicated page, with the FAQ entry linking through to it. Revisit the page every few months against your actual current enquiries, because new repetitive questions appear as your offer changes, and old ones fade.
Mistakes to avoid
- Writing questions from imagination instead of real enquiries: a guessed FAQ page misses the actual repetitive questions and answers ones nobody was asking.
- Hedging instead of answering directly: vague answers just generate a follow-up call anyway, defeating the entire purpose of the page.
- Burying the FAQ page where nobody looks before calling: it needs to be in the nav and ideally embedded near the relevant decision point, not just a forgotten footer link.
- Making every answer sound identically upbeat: an honest "this doesn't apply if…" note builds more trust than relentless positivity, and it heads off the follow-up question before it's asked.
- Never updating it: a stale FAQ that doesn't reflect current pricing, policies or offerings will generate more calls, not fewer, once someone spots the mismatch.
Frequently asked questions
How many questions should an FAQ page have?
Fewer than you'd think — most effective FAQ pages run 8-15 questions, covering the genuine high-frequency ones. A 40-question page is harder to scan and usually means low-frequency or invented questions have crept in alongside the real ones, which dilutes the page's usefulness.
Should FAQ pages be written for SEO or for reducing calls — can they do both?
Often both, but reducing calls should come first. A question phrased the way a real customer would ask it tends to match real search queries too, so optimising for genuine clarity usually helps search visibility as a side effect. Chasing search volume first, at the expense of how a real caller would phrase the question, tends to produce a page that ranks reasonably but still doesn't stop the phone ringing.
Will an FAQ page actually reduce phone calls, or do people call anyway?
It reduces them for genuinely repetitive, resolvable questions — it won't eliminate calls from people who prefer talking to a person, have an unusual situation, or simply didn't look at the page first. The honest expectation is fewer calls about the same handful of standard questions, not zero calls overall.
Where should the FAQ page sit in the site structure?
In the main navigation at minimum, plus relevant individual questions repeated or linked near the page they relate to — a cancellation question near the booking flow, a pricing question near the pricing table. A single standalone FAQ page that isn't linked from anywhere else tends to get far less traffic than one woven into the places people are already looking.
Keep reading 🤍
I help Gold Coast and Brisbane businesses grow with branding, websites and marketing that actually works.
Work with me ✦