Stillpoint field notes

Build Your FAQ From the Questions Clients Actually Ask

Most practice FAQ pages are written from guesses. Here is how to collect the questions clients really ask, answer them in plain words, and keep the page useful as your practice changes.

Stillpoint Team6 min read

From the team behind Stillpoint, practice software for wellness practitioners. See Practice Website in Stillpoint

A useful FAQ page starts with a list of real questions, not a blank page and a guess.

Most practice FAQ pages were written on the same afternoon as the rest of the website. You sat down, imagined what a new client might wonder, and wrote eight tidy questions about your training, your approach and your philosophy of care. Then the real questions started arriving by email and text, and almost none of them were on the page.

Clients rarely ask about your philosophy. They ask whether there is parking, whether they should eat first, what to wear, whether you send receipts their insurer will accept, and what happens if they are ten minutes late. Those small questions decide whether someone books, and whether they arrive relaxed or flustered.

A good FAQ is not something you write from scratch. It is something you collect. This guide walks through a simple way to gather the questions people actually ask, turn them into short answers, and keep the page honest as your practice changes.

Collect for two weeks before you write anything

Start with a plain list. A note on your phone works, or a page at the front of your planner. For two weeks, every time someone asks you a practical question, write it down in their words, not yours. Add a tally mark when the same question comes up again.

Look in all the places questions arrive:

  • New enquiries by email or through your contact form
  • Texts and messages between visits
  • Phone calls and voicemails
  • The first few minutes of a first appointment
  • The walk to the door at the end of a session

The first email from a potential client is often the richest source, because it shows you what someone needed to know before they felt safe booking. If you have a habit of answering those well, you already have half your FAQ written. There is more on that in answering the first email from a potential client.

Two weeks is usually enough to see a pattern. Most practices find that five or six questions make up the bulk of what they hear.

Sort what you collected into three moments

Once you have the list, group the questions by when a client needs the answer:

  • Before booking: which service to choose, how long a visit takes, what it costs, whether you work with their insurer or benefits plan, whether you see their kind of concern.
  • Before arriving: where to park, which door to use, whether there are forms to finish, how early to come, what to wear or bring.
  • After a visit: whether soreness is normal, how often to come back, how to get a receipt, how to reschedule.

This tells you where each answer should live. Before-booking questions belong on your FAQ page and near your services. Before-arriving answers belong on the FAQ and in your confirmation email. If arrival questions dominate your list, your instructions may need work first, and writing arrival instructions clients can actually follow is a good place to start.

You will also find a few questions that do not belong on a public page at all. "Is this pain something I should worry about?" is a clinical question for a conversation, not a paragraph on a website. Leave those off and keep answering them one person at a time.

Use the client's wording for the question

The question on the page should sound like the person who asked it. "Do I need to undress?" is clearer than "Draping and comfort protocols." "Can I bring my kid?" beats "Accompanying persons policy." People scan an FAQ for their own words, and if they cannot find them they give up and send you an email instead.

Then lead the answer with the answer. If the question is "Is there parking?", the first word should be "Yes" or "No", followed by the detail. Keep most answers to two to four sentences. When an answer genuinely needs more, write the short version and link to the page that holds the long one.

A quick test: read each answer aloud as if you were saying it to a client at the door. If it sounds like a policy document, rewrite it the way you would actually say it.

Put the money questions near the top

Questions about cost and payment are the ones people feel most awkward asking, so they are the ones most likely to stop a booking quietly. Put them high on the page, and be plain:

  • What a first visit costs and how long it is
  • When payment is taken and what you accept
  • Whether you provide receipts for insurance or benefits claims
  • What happens if they need to cancel or arrive late

Clear payment answers save you from awkward conversations later. If you have not settled exactly when and how clients pay, telling clients when payment happens before they book walks through it. Your cancellation answer should match your actual policy word for word, so a client never reads two different versions.

Know what an FAQ should not try to do

An FAQ is for practical reassurance. It is not the place for clinical promises, long biographies or every policy you have ever written.

Be careful with questions like "Can you help with my migraines?" You can say what kinds of concerns you often see and invite people to book a consultation or get in touch, without promising a result. That keeps you within your scope and is more honest for the person reading.

The FAQ also does not replace your intake form. If you find yourself writing "please tell us about any injuries before your visit," that belongs in intake, where the answer reaches you privately.

Use the same answers everywhere

Once your answers are written, they become more than a web page. The parking answer can go word for word into your confirmation email. The receipts answer can become a saved reply you paste into messages. If you work with a team, everyone answering the phone or the inbox can use the same wording, so clients hear one consistent version of your practice.

This is where an FAQ quietly saves time. A question you have answered well once should not need to be written fresh every week.

Keep the list going and review it each season

Do not stop collecting once the page is live. Keep the running list, and every few months look at it again.

Pay attention to one signal in particular. If a question keeps arriving even though it is already on your FAQ, the answer is either hard to find or not clear enough. Move it higher, rewrite it in the client's words, or put it in the confirmation email as well.

Also remove what is no longer true. A page that still mentions last year's prices or a door code you changed in spring does more harm than having no FAQ at all. A seasonal review takes fifteen minutes and keeps the page trustworthy.

Which question did you answer most often this week, and could a client have found that answer without asking you?

How Stillpoint helps

If your website is built in Stillpoint, open Website, choose Add page and pick the FAQ starter, or add an FAQ section to your Services page with Add section. Each of your collected questions goes in with Add question, the preview updates as you type, and nothing goes live until you choose Publish. If an edit does not work out, History lets you preview and restore an earlier version. See the website builder.

For the answers you send again and again, open the More menu in Messages, choose Templates, and save each one as a reply template. Practice templates are shared with everyone who messages clients, and you can pin up to six so they appear as quick reply pills above the message box. A template can include your booking link, so a parking or pricing answer can end with the next step. See messaging.

Ready when you are

Answer the usual questions before anyone has to ask.

Stillpoint's website builder has a ready-made FAQ page you fill in one question at a time, next to your services and booking link. Start free with no card required.