Every repeated question is a signal
A customer asks if your repair shop handles their appliance. Another wants to know if they should bring it in. A third asks the same thing through Instagram while you're helping someone at the counter.
You can keep answering each one from memory. Or you can use those questions to fix the information people see before they contact you.
The first step isn't writing a long FAQ about everything you do. It's finding one specific question that keeps coming back — and answering it where it matters.
Capture what people actually say
Look at a small set of recent inquiries from the channels you already use. Note the question and the situation. Keep names, contact details, and private info out of your working list.
'Do you fix this brand?' is different from 'Can I drop this off now?' The first is about whether you offer the service. The second depends on hours, space, or how you accept repairs.
Treat them separately when the answers lead to different actions. Group them only when they genuinely ask the same thing.
A simple tally is enough. Mark each time a question shows up during a period you choose. That tells you what recurs in your sample — not what every visitor is thinking.
Pick a question worth answering publicly
A good first candidate has three qualities: people ask it repeatedly, the answer helps them decide what to do, and you can give a reliable response.
For a cleaning business: 'Do I need to provide cleaning products?'
For a bike workshop: 'Can I bring the bike in without an appointment?'
For a photographer: 'What should I prepare before asking for a quote?'
Some questions need a personal conversation. A fixed public answer won't settle every unusual repair or individual requirement. Explain what you can say generally, and provide a contact route for the rest.
If you don't have a consistent policy yet, settle the business decision first. Publishing an uncertain answer just moves the confusion from your inbox to your page.
Write an answer people can act on
Use three parts: the direct answer, the important condition, and what the customer should do next.
Here's an example for a workshop that takes repairs by appointment:
Question: 'Can I drop my bike off without booking?'
Answer: 'Please arrange a drop-off before bringing your bike. We need to confirm workshop space and the type of repair first. Contact us with the bike type and the problem, and we'll tell you how to arrange a drop-off.'
That answer doesn't need a paragraph about your values. It gives the info the visitor came for, explains the condition, and points to a realistic next step.
Don't promise things you haven't checked. If price depends on inspection, say so instead of inventing a range. If availability changes during the day, send people to the current booking route rather than copying a slot that'll be stale by tomorrow.
Put the answer where the question lives
An answer can be correct and still hard to find. Match the location to the customer's situation:
- A service-area question belongs near your service description or inquiry route.
- A preparation question belongs near appointment info people read before visiting.
- A question about what affects a quote belongs near the request form — before someone starts filling it out.
- A parking or access question belongs with visit information.
- A question about what happens after submitting belongs beside the form or on its confirmation screen.
You might still want a short FAQ page for reference. But give the most important answers a place in the actual journey — don't rely on everyone visiting a separate FAQ first.
Use clear headings like 'What to bring to your repair appointment.' The W3C's accessibility guidance explains that headings communicate page structure and help people navigate, including with assistive technology.
Where your DiagBizCard fits
Your DiagBizCard gives people a consistent place to find your business and contact details. Use it to point toward the relevant service info, and check that connected destinations give answers that match your current policies.
You can start with clear text on an existing page and a consistent reply in the channels you already use. If you later add an automated answer service, give it approved information and a defined route for questions that need a person. Test its actual behaviour before relying on it with customers.
Keep answers current without creating another burden
Give each answer one named person responsible for checking it. Note where the answer appears — including saved replies — so a policy change doesn't leave several versions in circulation.
Match the review frequency to how often the info changes. A seasonal schedule needs attention before the season shifts. A stable explanation of what to bring might only need a check when the service changes. Also update when a customer question reveals your wording is incomplete or confusing.
If you find a wrong answer, fix the source and the places that repeat it. When someone is already acting on outdated info, use your normal customer-service process to address their situation.
The Answer Placement Sheet
Pick one repeated question. Copy these seven lines into your notes and fill them in. The complete worksheet is right here — no download or email needed.
1. Customer question — What do they ask, in their words?
2. Decision — What are they trying to decide?
3. Approved answer — The short answer and any important condition.
4. Source and owner — Where the answer comes from and who keeps it current.
5. Placement — Where the answer should appear.
6. Recheck — When to verify it's still accurate.
7. Exception — What happens when the answer doesn't fit this person.
Filled example for the appointment-only workshop:
Customer question: 'Can I drop my bike off without booking?'
Decision: whether to travel to the workshop now.
Approved answer: arrange a drop-off first so the workshop can confirm space and repair type.
Source and owner: the current intake policy, checked by the workshop manager.
Placement: visit info beside the workshop contact details; same wording in the saved reply.
Recheck: whenever the drop-off policy or intake hours change.
Exception: contact the workshop about unusual repairs before travelling.
What your answers tell you:
- No approved answer: settle the business policy before publishing.
- Clear answer, wrong location: move or repeat it where the customer makes the decision.
- Several conflicting versions: choose the current source and fix the rest.
- Answer depends on the person: give the general rule and the route to a human.
- Everything is clear: ask someone unfamiliar with your business to find the answer on their phone without hints.
Watch the next inquiries about this topic. If people still ask, check what they saw and what remained unclear. Their question might be showing you a placement problem, an ambiguous condition, or a genuine exception.
Common questions
Should I publish every question customers ask?
No. Publish questions whose answers help other customers and are safe to share. Keep personal situations, private info, and staff-only procedures out of public answers. You can generalise a recurring question without quoting anyone's message.
Do I need a chatbot to start?
No. One clear answer in the right place is a useful first step. Automation becomes worth considering when you know which questions recur, have dependable answers, and can handle exceptions. Test any service's actual behaviour before trusting it with customers.
How do I know if the answer helped?
First check that a new visitor can find and understand it. Then keep a short record of repeat inquiries and their context. Fewer questions can be useful evidence, but visitor volume and customer type may have also changed. Look for clearer conversations, not just lower counts.
Your next step: fill out the Answer Placement Sheet for one real question. Approve the answer, put it at the right decision point, and use the next customer inquiries to improve it.