Handling Returns and Refunds in Chat

The return request is the moment a customer decides whether to buy from you again. Handled badly — a form nobody can find, three days of silence, a refund that lands whenever — it costs you the customer and the review. Handled in the same thread where they bought, it often costs far less than the order value: a good share of returns end as an exchange or store credit rather than money going out.

That is the argument for keeping returns inside WhatsApp instead of pushing people to a portal with a password they never set. The conversation already holds the order, the address, and the product. If you are still building the flow that comes before this one, our in-depth guide to selling and taking orders on WhatsApp covers the whole path from catalog to payment.

What the AI should handle

Most return conversations are made of four questions: can I return this, how long do I have, how do I send it back, and where is my money. All four have exact answers that do not change, which makes them ideal work for an assistant. It reads the order, checks the purchase date against your window, issues the label, and says what happens next — at ten on a Sunday evening, in the customer's language.

• Eligibility: is this item inside the window, and is its category returnable at all.
• Labels: generate the return label and send it into the thread as a PDF.
• Status: "your parcel arrived yesterday, the refund goes out today".
• Reasons: ask one question about why the item is going back, and store the answer on the order.

What a human should own

Anything containing judgement belongs to a person. A customer arguing the product was described wrongly, a damaged item outside the window, a third return on the same account, a request for goodwill beyond policy — those are decisions about your money and your relationships, not lookups. Route them to a named colleague in the shared inbox with the full thread attached.

Write the escalation rule down instead of hoping the assistant behaves. Quality complaints, any mention of a lawyer or consumer authority, and any second attempt at the same return go to a human inside the hour. Then give that human a goodwill budget — a fixed amount they can refund on their own. A team that escalates a twelve-euro decision to a manager burns more in salary than the refund costs.

EU withdrawal rights, in plain language

Selling to consumers in the EU means distance-selling rules apply. The buyer has fourteen days from the day the goods arrive to withdraw, with no reason required, and another fourteen days to send them back. You refund within fourteen days of being told — including the standard delivery charge you originally took — though you may wait until the goods arrive or the customer shows proof of postage. Custom-made items, perishables, and opened hygiene products are among the exceptions.

Two practical consequences. If your written policy is stingier than the law, the law wins, so the assistant should quote your published terms and never improvise a number. And say it in normal words: "you have 14 days after delivery to change your mind, no reason needed" is a sentence a customer understands and trusts. Clauses full of paragraph symbols are what people forward to a consumer advice centre.

“

Nobody remembers the return that went smoothly. Everybody remembers the one that did not.

— be digital ai team

Refund timing: promise the boring truth

Almost all anger about refunds is about uncertainty, not speed. Give the sequence and the range up front: we process within 24 hours of the parcel arriving, your bank needs another three to five working days to show it. Card refunds through Stripe go back to the original method automatically, so the two moments worth announcing — parcel received, refund sent — can be pushed into the chat without anyone opening a dashboard. The same proactive rhythm you use for order confirmations, tracking, and delivery updates simply runs in reverse.

Where money moves slowly, offer the faster alternative honestly. Store credit issued in seconds beats a transfer that takes a week, and many customers take it — as long as it is a choice, not something they discover after the parcel is gone.

Read the reasons, then fix the page

Every return carries a reason, and reasons cluster. If a third of one dress's returns say "too small", the size chart is wrong, not the customer. If "not as pictured" keeps appearing on the same lamp, the photo is lying about the colour. Reviewing those tags monthly turns support work into product work, and the fixes land where people are choosing: in setting up a WhatsApp product catalog customers actually browse, one corrected measurement can quietly remove a dozen returns a month.

Start with three sentences

You do not need a returns project. Write your window, your exceptions, and your refund timing in three plain sentences, teach them to the assistant, and set one escalation rule for complaints. Everything after that — labels, status updates, reason tags — is configuration you can add in the weeks when it starts to hurt.