A return is a moment, not just a transaction
When a customer asks to return something, the sale is already in question — but the relationship isn't over. How you handle the return decides whether they come back or write you off. A smooth, respectful return often earns more loyalty than the original purchase did, because it is remembered as the moment you were easy to deal with when it counted.
Know the policy cold, and state it plainly
Returns go wrong when the answer is vague or inconsistent. The customer needs to know clearly: can they return it, by when, in what condition, and how the refund or exchange works. Canned responses keep your policy answers exact and identical across agents, so nobody promises a window that doesn't exist and no two customers get different rules.
Offer the exchange before the refund
A refund ends the relationship; an exchange often saves it. If the issue is the wrong size or a defect, a friendly “want me to send the right one instead?” keeps the sale and the customer. Lead with the solution that keeps them a customer — but never at the cost of trapping someone who genuinely wants their money back, which only breeds resentment.
Ask why — the return is data
Every return is a note on where something fell short: a misleading photo, a sizing chart that lies, a quality issue. A gentle “mind if I ask what went wrong?” turns a loss into a lesson. If the same product keeps coming back for the same reason, the fix is upstream on the product page, not in the returns queue.
How MyLiveChat supports returns
MyLiveChat keeps canned responses for consistent policy answers, transcripts that document what was promised, and tagging so you can see which products drive returns and why. It handles the conversation cleanly while your fulfillment systems handle the logistics — and the reason data it surfaces is what stops the return from happening next time.
The returns conversation has a predictable shape
Almost every return chat moves through the same four beats: the customer states what they
bought, says what is wrong with it, asks whether they can send it back, and asks how long the
money takes. Agents who know that shape stop improvising and start moving — they can
gather all four facts in two messages instead of six.
The one thing that derails it is a customer who expects an argument. Retail has trained
people to brace for resistance, so many open with far more justification than they need. When
the first reply is a straightforward yes-or-here-is-what-we-can-do, the rest of the conversation
gets shorter and considerably warmer.
Get the facts in one pass
Ask for everything you need in a single message rather than dragging it out one question at
a time. A four-part request feels efficient; four separate questions feel like an interrogation.
- Order number or the email used to buy. Everything else depends on finding the order.
- Which item, if the order had several — assume nothing on a multi-line order.
- What is wrong — faulty, wrong item sent, wrong size, or simply not wanted. These four routes are usually different policies.
- Condition and packaging, if your policy depends on it. Ask plainly rather than discovering the problem after the label is issued.
For a faulty item, ask for a photo. It settles the question immediately, costs the customer
ten seconds, and it is far kinder than a description contest neither side can win.
Phrasing that keeps a return calm
- Sorry about that — let me get it sorted. What is your order number? Opens with resolution rather than policy.
- You are inside the window, so this is straightforward. Tells them the answer is yes before the mechanics.
- The refund lands back on your original card, and it usually takes three to five working days after we receive the item. Specific and honest about the whole timeline, including the part you do not control.
- I can send you a prepaid label right now, or arrange an exchange for the next size up — which would you prefer? Offers a real choice instead of assuming.
Retire the ones that read as suspicion. Do you still have the original packaging? as
the very first reply, unfortunately our policy states, and anything beginning
you should have all turn a routine return into a complaint.
When the answer has to be no
Some returns fall outside the policy, and pretending otherwise helps nobody. Say no once,
clearly, early, and with the reason. What makes a refusal land badly is rarely the decision
— it is discovering it after five minutes of hopeful back-and-forth.
Then offer whatever you actually can: a repair, a partial credit, a discount on a
replacement, or the manufacturer’s warranty route. Give agents a small, explicit
discretionary allowance and the authority to use it without asking. A goodwill decision made in
the chat costs less than the escalation, the second contact, and the public review that a rigid
no tends to produce.
What to measure
Track the split between exchanges and refunds among chats that reached an agent, and compare
it with your self-service return flow. A meaningfully higher exchange share is the clearest
evidence that the conversation is doing work — an exchange keeps the revenue and usually
keeps the customer.
Watch how often a return chat becomes a second contact. A customer who has to come back to
ask where the refund is means the first conversation left out the timeline. Keep the return
reasons as tagged data too: the same product appearing under wrong size week after week is a
sizing-chart problem, and fixing the page removes the return rather than processing it faster.