How to handle customer returns and refund requests

How to handle customer returns in chat and email: a clear policy, a first reply that gets every detail, approval limits, reply examples and a checklist.

13 min read
How to handle customer returns and refund requests

Here is how to handle customer returns without losing money or goodwill: publish a policy short enough to quote in one message, ask for everything you need in your first reply, sort each request into one of five types, give every type a clear owner and approval limit, and send the decision in writing with a date. Then log the reason, since a pattern in return reasons usually points to a fix on a product page or in your packaging.

This guide is for small stores where two to ten people answer customers on live chat and email. Every step below works with a spreadsheet and a shared inbox; none of it needs a returns app.

Step 1: Write a return policy you can quote in one message

Most return arguments start with a policy that was written by a lawyer, a template site or nobody. If an agent cannot paste the relevant line into a chat and have it settle the question, the policy is too long or too vague.

A workable policy answers six questions:

  • How long does the customer have? Count from delivery, not from the order date, so a slow courier does not eat the window.
  • What condition must the item be in? "Unworn with tags" is clear. "Like new" invites a debate.
  • Who pays return shipping, and in which cases? A common split: the customer pays for change of mind, you pay when you made the mistake.
  • What do they get back: a refund to the original payment method, store credit, or an exchange?
  • How fast do you refund once the item arrives, and how long does the bank or card take after that?
  • What can never be returned, such as personalised items, perishables or opened hygiene products?

Check the legal floor where your customers live. In the EU, shoppers can cancel most online purchases within 14 days of delivery without giving a reason, with exceptions for made-to-order, perishable and unsealed goods (Your Europe). Under the Consumer Rights Directive the seller must refund within 14 days of being told, and may hold the refund until the goods come back or the customer shows proof of sending. In the US there is no general federal duty to accept returns, but the FTC's mail order rule requires a refund within seven working days (or one billing cycle on credit) when you cancel an order you cannot ship (FTC business guide). Your published policy can be more generous than the law, never less.

Step 2: Sort every request into one of five types

Return requests look endless, but nearly all of them fall into five types. Naming the type in the first minute tells the agent what to ask for and what the default outcome is.

Five sorted crates on a shelf, standing for the five types of return request
TypeExampleWhat to ask forDefault outcome
Change of mind"The colour looks different in person."Order number, item, conditionRefund after the item comes back, customer pays postage
Exchange"Can I swap the medium for a large?"Order number, the size or variant they wantReserve the new item, ship once the old one is in transit
Damaged or faulty"The handle snapped off the first time I used it."Photos of the item, the box and the shipping labelReplacement or refund, you pay any return
Wrong item sent"I ordered the blue one and got green."A photo of what arrivedSend the right item now, prepaid label for the wrong one
Never arrived"Tracking says delivered but I have nothing."Delivery address, a check with neighbours and the safe placeCarrier claim, then a reship or refund

"Never arrived" is an order-status question that has turned into a refund request. Check tracking and the carrier first; most of these resolve without a refund once the parcel turns up at a neighbour's or a pickup point.

Step 3: Ask for everything in the first reply

The slowest returns are the ones that take four messages to collect an order number, a reason and a photo. Ask for all of it at once, and say why you need it.

A first reply should request:

  1. The order number, or the email address the order was placed with.
  2. Which item, if the order had more than one.
  3. What went wrong, in their words.
  4. Photos, for anything damaged, faulty or wrong.
  5. What they would like: refund, exchange or replacement.

On live chat, keep it short and ask while they are still there:

Sorry about that. So I can sort it in this chat, could you send your order number and a photo of the damage? If you would prefer a replacement over a refund, tell me that too.

On email, the customer may not reply for a day, so ask for everything and set expectations in the same message:

Thanks for letting us know, and sorry the lamp arrived cracked. To arrange a replacement or refund, please reply with (1) your order number, (2) a photo of the lamp and (3) a photo of the box and shipping label. Once we have those, we will confirm the next step within one working day.

Save both versions as saved replies. Our free canned response examples include more return and refund wording you can adapt.

Step 4: Decide who can approve a refund or exchange

When nobody knows who can say yes, two things happen: agents promise refunds they cannot authorise, or every request waits for the owner. Write approval limits down and put them where agents can see them.

A hypothetical example for a store with three agents and one owner:

SituationWho decides
Inside the policy, any amountAny agent, no approval needed
Damaged or wrong item under $50Any agent; replace without asking for the item back
Up to 14 days past the windowSupport lead; store credit by default
More than 14 days late, or over $200Owner
Third return from the same customer this yearOwner, after reviewing the history

Your numbers will differ. Agents should know, mid-chat, whether they can answer "yes" or must say "let me check with my lead, I will reply by 3 pm". If your tool has assignment, hand the case to the approver with a two-line summary so they do not have to read the whole thread.

Step 5: Handle out-of-window and no-receipt cases

These are where tone matters most, because the answer is often "not the full refund" and the customer usually knows it.

Work down a short ladder instead of choosing between yes and no:

  1. Exchange for another size or item.
  2. Store credit for the full amount.
  3. A partial refund, if the item can be resold.
  4. A polite no, with the policy line quoted and a reason.

For no-receipt cases, look the order up by email address, phone number or shipping address. If you cannot find any record, the item may have come from another retailer or a gift; offer store credit at the current price if you sell the item, and say no if you do not.

Say what you can do before what you cannot:

Your order was delivered on 2 March, so it is outside our 30-day return window. I can't refund it to your card, but I can give you store credit for the full $64 or swap it for a different size. Would either of those help?

Step 6: Damaged and wrong items: evidence and speed

When the mistake is yours or the courier's, speed is worth more than investigation. A replacement that ships the same day turns a bad delivery into a small inconvenience; a customer left waiting two weeks for a carrier claim to settle is the one who writes the review.

  • Ask for photos of the item, the outer box and the shipping label in one message. The label photo is what the carrier claim needs.
  • Set a keep-it threshold. Below a certain value (say $25), paying for return shipping costs more than the item is worth; refund or replace and tell them to keep or donate it.
  • Ship the replacement before the return arrives for anything below your approval limit.
  • File the carrier claim yourself. Do not make the customer chase the courier.
  • Tag the case with the product and the damage type, so you can see if one product or one warehouse keeps showing up.

Step 7: Keep chat and email in one thread of record

Returns cross channels more than most support topics. A customer starts in live chat, gets told to email photos, then replies to the shipping notification from their phone. If those three messages land in three places, the second agent asks for the order number again and the customer loses patience.

One length of twine tying letters and a parcel together, like chat and email kept in one record

Three habits fix most of it:

  • One case per return. Keep the chat, the emails and the photos in the same conversation or ticket, with a status such as "waiting for item" or "refund sent".
  • An internal note with the decision. Something like: "Approved refund $48, item back 12 May, refunded to card 13 May." The next person reads one line, not twenty messages.
  • One owner. Whoever took the case keeps it until it closes, unless it goes to an approver.

A shared inbox makes this the default. In Sellio, website chat and email arrive in the same inbox, and a ticket keeps a multi-day return open without cluttering the conversation list. If your team works from a single Gmail account, a shared label and a pinned spreadsheet can stand in for a while. If you are choosing a help desk for this, we compared two common picks for a five-person team in Freshdesk vs Help Scout.

Step 8: Send the decision in writing, with a date

Every return should end with a message that says what happens, when, and what the customer has to do. "We've processed your refund" invites a follow-up a week later. This does not:

Your return arrived today, and we have refunded $48.00 to the card you paid with. Card refunds usually show within a few business days, depending on your bank. If you don't see it by 24 May, reply here and we'll trace it.

Use the refund times your payment provider actually publishes, and put a date in the message rather than "5 to 10 days". A date the customer can check stops most "where is my refund?" emails before they are written.

Reply examples for each case

Adapt the details, keep the structure: acknowledge, decide, give the next step and a date.

Change of mind, approved

No problem. You're inside the 30-day window, so you can send the sweater back for a full refund. Pack it unworn with the tags on and use the return form at the link below. Return postage is on you for change-of-mind returns. We refund within two working days of it arriving.

Exchange

Happy to swap it. I've put a large aside for you. Send the medium back using the prepaid label attached, and we'll ship the large as soon as the courier scans your parcel.

Damaged on arrival

Sorry, that should not have happened. Thanks for the photos. A replacement ships today and you'll get tracking by email this afternoon. No need to send the broken one back.

Wrong item sent

That one is on us. The blue jacket ships today by express at no cost to you. A prepaid label for the green one is attached; send it back whenever is convenient in the next 30 days.

Outside the window

The order arrived 41 days ago, past our 30-day window, so a card refund isn't possible. I can offer store credit for the full $36, valid for a year. Want me to set that up?

Turning refunds into repeat customers

A refund handled well is one of the few support moments a customer remembers in your favour. Thank them for telling you instead of just leaving. Mention the exchange or credit option once, without pushing. And if the problem was yours, fix it visibly: "We've added a size chart to the product page because of your message" is a reason to come back.

Do not send a discount code with every refund. It teaches regular customers that complaining pays, and it costs margin on people who would have bought again anyway. Save it for cases where you clearly let them down.

Track your return rate and reasons

You cannot fix a return problem you cannot see. Give every closed return a reason code and look at the totals once a month.

A notebook beside sorted seed packets, for tracking return reasons
  • Too small or too big
  • Looks different from the photos
  • Damaged in transit
  • Faulty
  • Wrong item sent
  • Changed mind or no longer needed
  • Arrived too late

Your return rate is returned orders divided by orders shipped in the same period. A hypothetical example: a store ships 800 orders in April and accepts 40 returns, a 5% return rate. If 18 of those 40 say "too small", the fix is a size chart or a fit note on the product page, not a better refund script.

Tags or ticket fields in your help desk make this a filter instead of a spreadsheet job. Pair it with satisfaction on returns cases, which our CSAT calculator can work out from your survey numbers, and you will know whether customers leave the process happy even when they send something back.

Common mistakes

  • Promising a refund in chat before checking the order.
  • Asking for the order number, then the photo, then the address, in three separate messages.
  • Making a customer return a broken $15 item at your cost.
  • Saying "refund processed" with no date, which guarantees a follow-up.
  • Letting each agent invent their own exceptions, so two customers in the same situation get different answers.
  • Closing the case when the refund is sent instead of when the customer confirms, for anything that was escalated.

Checklist: how to handle customer returns

  • Policy covers window, condition, shipping costs, refund method, timing and exclusions
  • Policy meets the legal minimum in each market you sell to
  • First-reply templates saved for chat and for email
  • Approval limits written down and visible to every agent
  • Keep-it threshold set for low-value damaged items
  • One case per return, with a status and a decision note
  • Decision message includes amount, method and a date
  • Reason code on every closed return, reviewed monthly

FAQ

How fast should we reply to a return request?

Answer live chat while the customer is still in the chat, and email within one working day. The first reply does not need a decision; it needs to collect what you need and say when the decision will come.

Should we refund before the item comes back?

For damaged or wrong items under your approval limit, yes: it is faster and builds trust. For change-of-mind returns, refund when the item arrives and passes inspection. In the EU you may hold the refund until you receive the goods or the customer shows proof of sending them.

Can an AI chatbot handle refund requests?

Let it answer policy questions such as "how long do I have to return this?" and collect the order number, then hand the case to a person for the decision. Refunds involve money and judgment, and a wrong automated yes is expensive. Our automation guide shows which parts of support are safe to automate.

What is a normal return rate for an online store?

It varies widely by category, so the useful benchmark is your own rate month on month. Track it by product and by reason; a single product with twice your average rate tells you more than any industry figure.

How do we stop serial returners?

Look at the customer's history before approving anything outside the policy, and route third or later returns in a year to the owner. Keep the decision consistent and polite; a clear policy applied the same way every time is your best defence.

Share

Share on XShare on LinkedInShare on FacebookShare on WhatsAppShare on TelegramShare on RedditShare on Threads

Article by

Khalid Nouri

Khalid Nouri is the founder of Sellio, a shared inbox and live chat platform for small customer support teams. He is a product designer and developer based in Marrakech, Morocco, and has spent years building digital products, designing interfaces and writing code. He started Sellio so businesses would not need five different tools just to talk to their customers.

Keep reading