The best time to answer a returns question is before the customer pays, while they are still deciding. A shopper who asks "can I send it back if it doesn't fit?" on a product page is asking whether it is safe to buy, and a clear answer from your published policy settles that in one reply. Answered after the order, the same question is a complaint.
This guide covers the returns questions people ask before they buy, a reply pattern that reassures without overpromising, and the policy gaps that make those replies vague.
Why returns questions show up before checkout
Returns worries sit right next to the buy button. Someone choosing between two sizes, buying a gift or spending more than usual wants to know what happens if it goes wrong. If the answer takes a hunt through the footer, many will leave the tab open and never come back.
Our post on reducing refund requests with better pre-sale answers looks at the broad link between pre-sale questions and refunds. This one is narrower: the returns policy itself, and how to make it answer the question at the moment it is asked.
The five returns questions people ask before buying
Read a few weeks of pre-sale messages for most stores and the same five come up.
| What they type | What they need to hear |
|---|---|
| "Can I return it if it doesn't fit?" | Yes or no, and the condition (unworn, tags on) |
| "Who pays for the return?" | Free returns, a fixed fee, or the customer pays postage |
| "How long do I have?" | The window in days, and when it starts counting |
| "Can I swap it for a different size?" | Whether exchanges exist, or it is a refund and reorder |
| "Does that apply to sale items / gifts / opened items?" | The exceptions, stated plainly |
The last row is where most stores lose people. The headline policy is usually clear. The exceptions are buried, vague or missing altogether.
A reply pattern that reassures without overpromising
A good pre-sale returns answer has three parts: the rule, the condition, and what to do next. Here is how that looks for an imaginary clothing shop (a hypothetical example, not a real store):
Shopper: If the jeans don't fit can I send them back? Bot: Yes. You have 30 days from delivery to return unworn items with the tags on, and UK returns are free using the prepaid label in your parcel. If you'd rather swap sizes, start a return and place a new order for the other size, which gets it to you faster than an exchange.
That reply does not say "don't worry, returns are easy". It gives the window, the condition, the cost and the practical tip, all from the policy page. Reassurance comes from specifics.
Three habits keep these answers honest:
- State the condition every time. "Unworn with tags" or "unopened" belongs in the first sentence, not a follow-up.
- Say who pays. Postage is the detail people most often feel misled about later.
- Give the next step. Where to start a return, or how an exchange works, so the shopper can picture the process.
Be blunt about the exceptions
Some items can't come back: final-sale stock, earrings and other hygiene items, personalised or made-to-order products, opened cosmetics. Shoppers rarely object to the rule itself. They object to finding it out after delivery.
So write the bot's instructions to lead with the exception. In SpideyChat that goes in the "System prompt (persona & instructions)" field on your chatbot, for example:
When someone asks about returning a product, check whether it is final sale, personalised or a hygiene item before answering. If it is, say clearly that it can't be returned and why, before anything else. Never suggest an item can be returned unless the returns policy says so.
You will lose the occasional sale this way. That is a sale that would have come back as a return, a refund and probably a poor review.
Fill the gaps in your policy page
A chatbot that answers only from your content is only as specific as the page it reads. If the policy says "returns accepted within a reasonable time", the bot can't do better than that. Before launch, check your returns page answers each of these in a sentence or two:
- The return window in days, and whether it starts at order or delivery.
- The condition items must be in.
- Who pays return postage, per region if it differs.
- Whether exchanges exist, and how they work.
- Sale, clearance and final-sale items.
- Gifts: whether the recipient can return, and whether the refund goes to the buyer.
- Personalised, made-to-order, opened and hygiene items.
- International returns, if you ship abroad.
- How long refunds take once the return arrives.
The companion piece, a returns policy nobody reads is still your busiest page, explains why this one page carries so much weight.
Then make sure the chatbot has the current version. In SpideyChat you can crawl your site (Starter and above), upload the policy as a document, or add the trickiest rules as Q&A pairs, such as "Can I return earrings?" with the exact answer. Crawl again whenever the policy changes, so the bot never quotes last season's window.
Put the answer where the hesitation is
A returns answer is most useful on product pages and in the cart. Two settings help:
- Suggested prompts. Add "Can I return this?" as one of the prompts shown in the widget, so the question is one tap away.
- Proactive greeting on chosen pages. SpideyChat's greeting bubble can be limited to path prefixes such as your product pages, with a short line like "Questions about sizing or returns? Ask here."
After the order, the questions change. "I want to return this" needs a person or a ticket with the order number, not a policy recital. Our guide to handling where is my order questions without an order integration covers that hand-off and the fields to collect.
Check what shoppers actually ask
After a couple of weeks, read through the questions the bot couldn't answer. SpideyChat records these as knowledge gaps, including answers a visitor marked unhelpful. If "can I return a gift?" keeps appearing, that is a sentence missing from your policy page, and adding it fixes the answer for everyone who asks next. The ecommerce overview shows other store questions worth covering.
To see how your current returns page holds up, paste your website address into the free test and ask it the five questions above. If any answer is vague, the fix is usually one line in your policy.