Playbook, fashion retailer
When a return stops being a policy lookup and becomes a decision
The facts in these conversations are not missing. Everybody can see that the return is four days late or that the tag is off. What is missing is somebody with the authority to say yes anyway, which shops do far more often than their policies admit. An assistant that reads the policy strictly at this moment does not fail to answer, it answers wrongly, and it does so in the shop's voice.
Why this is not the general answer
The handling pattern for asking for a person holds across every trade. What follows is the part that does not.
- The shape here is a decision rather than a lookup: nothing needs to be found, somebody needs the authority to allow it.
- Shops routinely accept returns they could refuse, so an assistant applying the published terms strictly says no on behalf of a business that would have said yes.
- A garment that failed in wear has moved out of the returns policy entirely, and in many markets rights over goods that are not of satisfactory quality are separate from a shop's own window and outlive it.
- These arrive already tense, because the visitor has usually read the policy and is making contact precisely because it does not cover them.
How it arrives
- i am two days past the returns window
- i took the tag off before i tried it on
- it split the first time i wore it
- the colour ran in the wash
- you refused my return and i want to appeal
- can i speak to a manager about a return
What has to be indexed for this to work
| That discretion exists, without where the line is | A short internal note saying the team can and does make exceptions on late returns and condition. The point is not to let the assistant decide, it is to stop it announcing that nothing can be done. |
|---|---|
| The faulty goods route in customer language | Split seams, shrinkage, colour loss, hardware failure, described the way customers describe them, with the statutory position for your market stated separately from your own policy. |
| What evidence helps a decision | Photographs of the fault, the order number, when it was bought, how many times it was worn and how it was washed. Collecting these at handover turns three exchanges into one decision. |
| Who decides, and what they have committed to | Which team handles contested returns and their published response time. Somebody escalating wants to know a person will actually look, and a named route reassures more than a promise about the outcome. |
The reply
That is past our published window, and whether we can still take it is a decision for the team rather than something I should answer, because they do make exceptions and I have no way of knowing when. If the garment has split, shrunk or lost colour rather than simply not suiting you, that is a different route altogether and it is not limited by the returns window. Leave your name, the email on the order and a couple of photographs of the fault and somebody will come back to you.
It declines to refuse, which is the important move, because a strict reading would close a case the shop might have opened. It separates the two routes in the customer's own vocabulary rather than in legal language, so a real defect does not get filed as a late change of mind. Asking for photographs in the same reply means the person picking it up can decide rather than write back for evidence.
Where it stops
The trigger. The visitor falls outside the published terms in any direction, or is contesting a decision the shop has already made.
This needs somebody who can make a decision, which is not me. Leave your name, the email on the order and what happened, with photographs if there is something to see, and it goes to the team who handle returns.
It stops answering before it guesses, says who will pick it up, and asks for the one thing that makes a reply possible. Nothing about it reads as a dead end.
Never say this here
Out of bounds
- Never refuse a return or say that nothing can be done.
- Never describe a decision the team has already made as final.
- Never treat a garment that failed in wear as a change of mind.
- Never promise that an exception will be granted.
Questions
- Why should it not just quote the policy?
- Because the policy is the shop's opening position and not its practice. A customer told no by an assistant does not appeal, they leave and tell people. A customer told a person will decide waits, and the shop keeps the option of saying yes.
- How does it know a fault from a change of mind?
- From the customer's own words, which is why the faulty goods material should be written in those words rather than in policy language. Split, shrunk, ran, came apart. Material phrased around the satisfactory quality standard will not match anything a real person types.
- Does asking for photographs put people off?
- Not when it is framed as speeding up a decision rather than as a test. The alternative is a reply asking for them, which adds a day and reads as reluctance. Photographs arriving with the first message are also what let a manager say yes without a second look.
Keep reading
- Everything for a fashion retailerFit is both the most asked pre-purchase question and the biggest cause of returns. Here is what a clothing retailer can safely automate.
- Handling asking for a person in generalThe design question at the centre of a support assistant. Offer early, offer once, collect what a reply needs, promise a time you can keep.
- One order, several lines, and they did not all leave togetherClothing orders split by line and by drop. A despatch email covers one garment, and a line can leave an order after the money was taken.
- The date in their head belongs to somebody elseThe deadline is an event, not a preference. Cut-offs, pre-order windows and a collection counter that closes before the shop does.
- Two histories end with the same mark on a sleeveA security tag left on, a pulled thread, a dropped hem. Transit damage and a garment fault look identical and take different routes.
Try it on your own material
Upload a document or point it at your site, paste one line of HTML, then ask it something only your business could answer.