You wrote a thorough FAQ page. Delivery, returns, sizing, payment, it is all there. And yet the emails keep coming: "How long does delivery take?" "Can I return this?" The answers are on a page nobody seems to read.
This is one of the most common frustrations for store owners. Here are some myths about why an ecommerce FAQ page is not working, and what actually helps.
Myth 1: customers are lazy
Reality: customers are busy, and they have a question at a specific moment. They are on a product page or in the basket, and the FAQ is somewhere else. Leaving to hunt through a list feels like more effort than typing a quick message. That is not laziness; it is how people use websites.
Myth 2: a longer FAQ answers more questions
Reality: longer FAQs are harder to scan. The answer to one specific question gets buried among thirty others. Many stores find that trimming their FAQ to the most common questions, with clear headings, works better than adding more.
Myth 3: the FAQ page is where answers belong
Reality: answers belong where questions arise. Delivery times belong next to the price. Returns belong in the basket. Sizing belongs on the product page. The FAQ is a backup, not the main source.
Myth 4: customers read answers fully
Reality: they skim. An answer that starts "Our comprehensive returns policy covers a wide range of situations" loses them. Lead with the fact: "You have 30 days to return unused items."
Want a 24/7 AI Employee for Your Website?
See how SpideyChat can answer customer questions, capture leads and handle enquiries while your team is offline.
Myth 5: an FAQ can cover every situation
Reality: customers ask about combinations your FAQ never anticipated. "If I order two sizes and return one, do I pay return postage?" needs an answer that pulls from several parts of your policy.
What actually reduces repeat emails
Put answers on the pages that trigger questions. Delivery and returns near the price, fit notes on product pages, payment options in the basket.
Write FAQ answers that lead with the fact. One or two sentences, then detail if needed. The free FAQ generator can draft a starting set from your website.
Let customers ask in plain language. SpideyChat for ecommerce stores answers from your FAQ, policies and product pages the moment a customer asks, including combination questions that no single FAQ entry covers. It works at any hour.
Reviewing what customers still ask
Even with good pages, some questions remain. Look at what customers ask each month and ask why the answer did not reach them. Often the fix is moving an answer to where the question starts. Promotion terms are a common example, as shown in discount code questions that stall a checkout.
The time you get back
For solo owners, repeat emails are one of the biggest drains on time, described in running a one-person store without living in your inbox. Software founders feel the same pressure, covered in founder-led support and when it stops working. Reducing repeat questions without making support harder to reach is the balance explored in reducing support costs without reducing support quality.
A quick test
Pick five questions you get every week. For each, check whether the answer appears on the page where the question usually starts, not just on the FAQ. Move the ones that do not. Then try an assistant on your store and ask the same five questions, or look at what else it handles.