Your returns policy is probably one of the least read pages on your store. It is also, very likely, the subject of a large share of your customer emails. Those two facts are connected.
Nobody reads a returns policy for fun. They read it when they have a specific question, usually one of these: can I return this if it does not fit, who pays for the postage, how long do I have, and when will I get my money back. When the policy is long, legal and hard to scan on a phone, they give up and send you an email instead.
Returns questions come in two kinds
It helps to separate returns questions by timing, because they need different handling.
Before purchase, a returns question is a sales question. "Can I send it back if the colour looks different in person?" comes from someone deciding whether to buy. A fast, reassuring answer often closes the sale. A slow answer loses it, in the same way as the fit doubts described in sizing questions are killing your conversion rate.
After purchase, it is a support question. The customer has the item and wants to know what to do next. Most of these are routine. Some, like damaged goods, need a person.
Why the policy page does not stop the questions
There are a few reasons people email instead of reading.
The policy covers every situation, so the answer to one specific case is buried among exceptions. Phone screens make long pages hard to scan. Legal wording makes people unsure whether their case applies. And some customers want reassurance from something that feels like a person before they commit.
None of these are fixed by making the policy longer. They are fixed by answering the specific question, in the moment, in plain words.
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.
What good returns answers sound like
Specific and short, using only what your policy states:
Visitor: If I order two sizes, can I return the one that doesn't fit? Assistant: Yes. You have 30 days to return unworn items, and returns within the UK are free using the prepaid label in your parcel. Refunds go back to your original payment method within 5 working days of us receiving it.
That answer handles the exact situation, names the key conditions and removes doubt. If the policy does not cover something, the right answer is "I'll check with the team," with the customer's email captured.
Where a website assistant fits
SpideyChat for ecommerce stores reads your returns policy, shipping page and FAQs, then answers questions like the one above at any hour. Before purchase, that turns returns doubts into completed orders. After purchase, it explains the process for the customer's case and captures details for anything that needs a person.
It does not issue refunds or generate return labels. It explains, and it passes the customer's details to your team when action is needed. For most routine questions, explanation is all the customer wanted. Our guide on how ecommerce chatbots handle shipping and returns questions covers more examples.
Rewriting the policy so it answers questions
Look at the returns questions you received last month. Each recurring one is a sign the policy is unclear on that point. Then restructure the page around those questions:
- Lead with the time limit, in bold, near the top.
- Say clearly who pays return postage, and in which cases.
- Give the steps to start a return as a short numbered list.
- State when the refund arrives, counted from what event.
- Put exceptions, such as sale items or personalised products, in a clearly labelled section.
This makes the page more useful to humans and gives an assistant clearer material to answer from.
Counting the time returns questions cost
Here is a hypothetical. Say your store gets 60 returns questions a month and each takes five minutes to answer. That is five hours a month on one page's worth of information. Many of those questions came from shoppers who had not yet bought, so some sales were delayed or lost along the way. Our breakdown of what an unanswered product question costs a small store shows how those losses add up.
What to do next
Pull your last month of returns emails and write down the ten questions they contain. Rewrite your policy so each of those is answered in a sentence near the top.
Then check how those answers come across when a customer asks directly. You can build a free assistant from your store's address and ask it your ten returns questions. If it answers clearly from your policy, you have turned your least read page into one that answers people when they need it. You can also look at what else the assistant handles, such as capturing damaged item reports for your team.