There is a particular kind of support email that makes a website owner sigh: “How long does delivery take?” The answer is on the site. It is in the shipping page, beneath the FAQ, inside a menu labeled “More,” which also contains the privacy policy and an announcement from last spring.
The buyer is not failing a scavenger hunt. They have a decision to make, and the answer is not where they need it. Before adding a chatbot or rewriting the entire FAQ, find the question that matters at the point of choice and place its answer there.
Begin with what buyers actually ask
Gather recent pre-sale questions from email, chat, calls, sales notes, and customer-support tags. Keep the original wording and mark how often each question appeared during a defined period. Separate questions that block a decision from general curiosity. “Can you serve our area?” may determine whether someone contacts a service provider; “Do you have a newsletter?” probably does not.
A small-business owner described repeatedly answering questions that were already addressed on the company website. One forum post cannot tell us how common this is, but it captures the practical gap: information can exist and still fail to help a customer. Read the discussion.
Find the moment when the question becomes important
For each repeated question, trace the customer’s task. A shopper may need delivery timing while deciding whether to buy. A prospective client may need to understand the first call before submitting a form. A hotel guest may need cancellation terms before entering payment details. Put the answer close to that decision, rather than assuming everyone will navigate to the same general information page.
Ask a few customers or prospects to complete the task while thinking aloud. Notice where they pause, search, backtrack, or ask for help. You can also observe support conversations and analytics, but do not infer a precise cause from a click map alone. A person may leave a page for reasons unrelated to its content.
GOV.UK guidance on interface writing emphasizes clear labels and language that people recognize. The underlying principle applies broadly: call an answer “Delivery and returns” if that is what buyers look for, rather than a clever brand phrase that requires decoding. Writing for user interfaces.
Move the answer, then make it complete
For each high-priority question, write a short answer that resolves the concern and states any important condition. Put it near the action it affects. A product page might show the delivery estimate beside the add-to-cart control and link to full regional details. A service page might say what happens after the inquiry form and how quickly the team usually responds—but only if that response time is operationally reliable.
Avoid replacing a specific answer with vague reassurance. “We care about your order” does not tell a shopper when it will arrive. “Flexible cancellation” is not useful without the actual deadline and terms. “We make it easy” does not explain whether an initial consultation is paid. State verifiable facts in plain language; link to the full policy where necessary.
An answer beside a button should not overwhelm the button. Use one or two lines for the essential point, and provide a clear path to detail. If many conditions apply, summarize the practical rule and link to the complete policy. Keep that policy consistent with what the team and systems actually do.
Decide what belongs beside which action
Map questions to actions rather than making a long universal checklist:
- Before a contact request: who the service is for, service area, likely response, and what information to prepare.
- Before a booking: availability, duration, cancellation, who will provide the service, and what is included.
- Before payment: total price or how it is calculated, delivery, returns, payment methods, and material restrictions.
- Before a signup: what the person will receive, when, and how often; do not imply a launch date that is uncertain.
These are prompts, not requirements for every page. The relevant information depends on the product, audience, legal obligations, and operational model. Include the answer that removes a real unknown for the specific next decision.
Check whether the moved answer helps
After moving it, watch for both behavior and new questions. Did more people complete the action? Did support contacts about that topic change? Did users interpret the answer correctly? A page can produce more form submissions but lower-quality inquiries; a store can reduce questions while still losing shoppers because the price or product is wrong.
Define the observation before editing. For example: “Prospects ask whether the discovery call includes a recommendation; we will state the call’s purpose and duration beside the booking link, then review inquiry notes for four weeks.” That is a learning plan, not a guaranteed conversion increase. If the traffic is too low for a meaningful comparison, conduct more task-based sessions and report the evidence as qualitative.
Do not move an answer based on a single unusual request without checking whether it matters to other buyers. On the other hand, repeated questions are not the only signal. A buyer may silently abandon because the answer is missing. Usability sessions and a review of decision paths can uncover questions customers have not thought to ask support.
When the FAQ still has a job
An FAQ can be useful for questions that do not fit naturally elsewhere, edge cases, or details people want to explore after understanding the basic offer. It is a poor substitute for explaining the offer itself. If the top navigation, product page, and form all require a buyer to leave their task and search a catchall list, the content hierarchy is asking the customer to do the organizing.
Outside the discussion, a clinic redesign case from The Pixel reports a 52% increase in online appointment requests and a 29% decrease in calls about basic scheduling questions after the pages were organized around patient questions and a shorter path. These figures are the studio’s reported before-and-after results, not controlled proof that placement alone caused the change. They are useful as an example of the questions-first approach, not a forecast for another business. Clinic case study.
Keep the answer near the decision it supports
Choose one recurring, consequential question. Find where a buyer first needs its answer, place a concise and accurate response there, and verify the path with a person who was not involved in writing it. Then monitor the action and the questions that follow.
The goal is not to eliminate every conversation. Some questions deserve a human answer, and many people prefer to talk before buying. The useful change is simpler: make customers ask because their situation is unique, not because the website hid an ordinary fact one page away.