Handle a refund request calmly: a response policy for small sellers in India
A refund request is a moment that decides whether a customer buys again. A written rule, a short reply within a day and a record of what you did turn a painful chat into a fair one.
By Madhur Tyagi
· 10 min read

Quick answer
How should a small seller handle a refund request calmly? Sort the request into one of four kinds, check it against a written rule, reply within a day with the decision and the next step, and record the outcome in one line. Keep the tone warm and specific, and never argue the customer's feelings in writing.
In short, for busy readers and AI answers
- Who is it for?
- Small sellers in India who take orders on WhatsApp, Instagram or a marketplace and receive refund or return requests.
- What do you get?
- A four kind sort, a written rule template, three reply scripts, an illustrative example, mistakes and a short FAQ.
- How long?
- About 10 minutes to read, then about 30 minutes to write your rule.
- Next step?
- Write your refund rule this week and paste it where your team can see it.
Key takeaways
- Sort each request into one of four kinds before you reply.
- Check the request against a written rule.
- Reply within a day, with the decision and the next step.
- Record the outcome in one line.
- Never argue the customer's feelings in writing.
The short version
A refund request is one of the hardest messages a small seller gets. The customer is upset, the seller is worried about cash, and both sides are typing fast. The reply often decides whether the customer comes back, and whether they tell a friend. A written rule, a short reply within a day and a clear record make the reply easier to send and easier to defend.
The method has four parts. Sort the request, check it against your rule, reply with the decision and the next step, and record what happened.
Why refund chats go wrong
Most refund chats go wrong for the same reasons. The seller replies late, so the customer escalates. The seller replies with a long defence, which reads as a refusal even when the answer is yes. Or the seller agrees to something in one chat that the team cannot deliver, so a promise is broken a week later. None of these needs a bad person. They need a rule and a habit.
Step 1: sort the request into one of four kinds
Read the message twice and name the kind. A damaged item means the product arrived broken or leaking. A wrong item means the product is not the one ordered. A changed mind means the customer no longer wants it and the item is not faulty. A delivery problem means the parcel was lost, late or refused at the door.
Each kind has a different default. Damaged and wrong items usually get a replacement or a refund, depending on your rule. Changed minds depend on your return window. Delivery problems depend on the courier's report, which you should check before you reply.
Step 2: write one rule and check the request against it
Write your rule in one page, and keep it where the team can read it. The rule says the return window, which kinds get a full refund, which get a replacement, what the customer must send as proof, and who decides the edge cases. A simple rule might say: damaged or wrong items are replaced or refunded within seven days of delivery with a photo, and changed minds are accepted within three days if the item is unused.
Check the request against the rule before you reply. If the request fits, reply with the yes. If it does not fit, reply with the no and the reason, in the same words your rule uses. Do not invent a new answer each time.

Step 3: reply within a day, with the decision and the next step
Reply within a day, even if the full answer takes longer. A reply that says we have received this and will reply by tomorrow evening is better than silence. When you do decide, give the decision, the next step and the date the customer will see the result.
Keep each reply under sixty words. Long replies read as arguments, even when they are polite.
Step 4: record the outcome in one line
After the decision, write one line in your record: the order number, the kind, the rule you used, the decision and the date. A record stops the same request being handled two ways, and it shows you which kinds of request come back most. A month of records is the strongest evidence you will have for changing the rule.
A worked example, illustrative
This example is illustrative and uses a made up seller. A small home decor seller sends a ceramic vase by courier. The customer writes on WhatsApp that the vase arrived cracked and asks for a refund. The seller sorts the request as damaged, checks the rule, and asks for one photo of the box and the vase. She replies within three hours, thanks the customer and confirms a replacement will ship the next morning.
The customer sends the photo the same evening. The replacement arrives in two days. The seller records the order, the kind, the rule and the decision in one line. A week later, a second customer asks for a refund on a different item that is past the window. The seller uses the same structure: thank you, the rule, the reason, and an offer to check any fault.
Mistakes that turn a refund into a fight
- Replying late. Silence turns a small issue into a public complaint.
- Making a new rule each time. Customers talk to each other. Inconsistency costs more than a generous answer.
- Arguing the feeling. Do not tell the customer they are wrong to be upset. Acknowledge the problem and move to the next step.
- Promising what the team cannot deliver. If the courier cannot pick up until Monday, do not write that it will be done today.
- No record. Without one, the same case gets handled twice.
- Refunding everything without a rule. Generosity without a rule becomes a pattern that the next customer expects.
When the rule needs a judgment call
Some requests do not fit the rule neatly. A customer who has used the item for a week and then finds a small crack, or a parcel that arrives two days after the window because of a courier strike, are real cases. Decide these with one person, and write the decision in the record with the reason. Do not let each team member decide differently in the chat.
Set a simple escalation line: the person who answers the chat can approve a replacement up to a set value, and anything above that goes to the owner the same day. A clear line protects the seller and speeds the reply, because the person in the chat knows what they can say.
Keep the tone steady
Refund messages often arrive late at night, in capital letters and with a deadline. Reply the next morning, in the same calm tone as your rule. A short line that names the problem, the decision and the next step is enough. Avoid emojis in a refund reply, and avoid jokes. The customer wants to feel heard and to know what happens next.
Tick off the steps
Tick each box as you go.
Frequently asked questions
How long should my return window be?
That is your decision. Pick a window you can check, such as three or seven days, and write it on every order confirmation. Consistency matters more than the number.
Should I ask for a photo?
For damaged or wrong items, yes. Ask for one clear photo of the item and the outer box. Do not ask for a video unless the case needs it.
What if the customer threatens a bad review?
Reply once, calmly, with the rule and the next step. Do not match the tone. A calm reply in public is the strongest answer to a threat.
Can I offer store credit instead of a refund?
Yes, if you offer it as an option in your rule, and the customer can choose. Do not push credit on a customer who asked for money back.
How do I handle a marketplace refund?
Follow the marketplace's own process, and use your rule for the reply in the chat. Keep the marketplace record and your own record in step.
Can you help me write the rule?
Yes. Tell me what you sell, your return window and your courier, and I will draft the one page rule with you.
Your next step
Write your refund rule this week on one page, with the four kinds and the window for each. Paste it where the team can see it, and use the three reply scripts for the next request. Then write the one line record for each case, and review the rule at the end of the month.
Your refund log
One line per request. The record is what makes the next decision easier.
| Order number | |
|---|---|
| Customer and the date of the message | |
| Kind: one of the four kinds | |
| The rule I checked the request against | |
| Reply sent on (within a day) | |
| Decision and next step, in one line |
Self-check
Answer in your head, then tap a question to see the answer.
What is step one with a refund message?
Read the message twice and name its kind. A damaged item means the product arrived broken or leaking.
Why reply within a day?
Silence turns a small issue into a public complaint.
What goes in your record?
One line: the order number, the kind, the rule you used and the outcome.
Why keep one written rule?
So the decision comes from a rule everyone can read, not from a new rule each time.
Written by Madhur Tyagi, founder of The Human Algorithm. 8+ years, 25+ brands, since 2017.
Scope note: Examples are illustrative, not client results. Numbers are marked with their source or as unverified. Nothing on this page is sent unless you press the WhatsApp button.
Festive
Replies
Pricing