Start with the decisions customers are trying to make
Before someone contacts a small organization, they are often deciding whether it can help them, what the process involves and whether taking the next step feels worthwhile. The questions behind those decisions may be more specific than “What do you do?” A prospective client might want to know whether a service is suitable for a small project, what they need to prepare or what happens after they submit a form.
Make a short list of the steps a person takes before getting in touch: recognizing a need, comparing options, checking practical details and deciding to act. Then write down the questions you would expect at each step. Treat this as a starting guess, not as evidence. The aim is to give yourself a framework for spotting real questions in the places your customers already speak to you.
Collect questions from everyday conversations
Start with the people who answer emails, take calls, handle enquiries or meet customers. Ask each person: “What do people ask just before they decide to contact us or book?” and “What do they misunderstand?” Invite them to share the wording customers use, rather than polished versions of the questions. “Can you help if I only have three pages?” may be a more useful content prompt than the broad label “service scope.”
Review a small, manageable sample of recent enquiries and note repeated questions. Look for queries that come before a sale as well as those that arrive after an initial conversation; the latter may reveal information people wanted but could not find earlier. Remove names and other personal details from your notes. If several colleagues collect questions, a shared document with columns for the question, where it came from and the date is enough to begin.
For example, a community workshop might hear “Do I need to bring my own tools?” by phone, while its email inbox contains “Is the beginner session really for someone with no experience?” Those are distinct concerns. One is about preparation; the other is about confidence. Keeping them separate helps you answer each one clearly.
Look for clues on your website
Your website may show where people are looking for answers, though it cannot tell you exactly what every visitor is thinking. If your site has an internal search function, review the terms people enter. If you have basic page and navigation reports, look for heavily visited service, pricing, process or contact pages. Frequent visits to a page do not prove it is confusing, but they can suggest where to check whether important details are easy to find.
Try completing a visitor’s task yourself. Starting from the home page, find out whether a service is available in a particular area, what it includes and how to enquire. Note any points where you have to guess. Ask a colleague unfamiliar with the page to do the same without prompting them. Add the questions they raise to your list, marking them as observations to verify rather than assuming all customers share them.
You can also inspect the labels on your forms. If an enquiry form asks people to select a service before explaining the differences between services, some visitors may hesitate. A short explanation beside the choice, or a link to a comparison page, may answer the question at the moment it matters.
Choose questions worth answering first
After a week or two of collecting, group similar questions in plain language. Separate practical questions, such as opening hours or preparation, from decision-making questions, such as suitability and what is included. Keep a note of the original wording so your eventual answer sounds relevant to the person asking.
Prioritize questions that come up repeatedly, prevent people from taking a useful next step or require staff to explain the same thing each time. A question does not need a high count to matter: if misunderstanding a requirement could lead someone to book the wrong service, a clear answer deserves attention. Choose three to five questions for a first pass rather than trying to build a complete FAQ at once.
Publish answers where people need them, then keep listening
Match each answer to the customer’s task. Put a short answer about what to bring on the relevant booking page. Give a nuanced question about who a service suits its own section on the service page. If an answer needs examples or several steps, a dedicated article may work better. Write the direct answer first, then add useful conditions and a clear next step. Avoid hiding essential details behind a generic “contact us to learn more” message.
Once the answers are live, tell staff where to find them so they can share the right page during conversations. Keep collecting questions and check whether the same uncertainty still appears in enquiries. If it does, the answer may be hard to find, too vague or missing an important exception. Update the page rather than automatically writing something new. Over time, this small cycle of listening, answering and revising can make your website more helpful before anyone has to ask.
