Most of a support inbox is routine: stock checks, courier questions, sizing. Then a message starts with "I want a refund," and the stakes of the thread change. Money plus emotion is where sellers lose customers they could have kept. Three replies decide how the conversation ends: the answer to the request itself, the answer when you cannot refund in full, and the answer to "should I wait for restock or take my money back." Write them before you need them.
Ground Rules Before Any Script
- Scripts decide wording, not outcomes. Whoever replies needs the authority numbers in advance: what a full refund covers, what partial means, who approves which amount.
- Every figure comes from the order record and the payment provider, not from memory.
- In automated setups, a refund request should wake a human. A setup guide for auto-reply in chat-based customer service lists refunds and complaints among the scenarios that should trigger an alert to the owner rather than an automated verdict.
- When you do not yet know the answer, stall honestly: "Let me verify this and come back to you with a firm answer." A checked reply beats a fast wrong one.
Reply One: Yes — Agree Without Friction
When the request is clearly valid, confirm the decision in the first sentence: "You're covered — I've started the refund for the 【item】." Then state the amount, that it returns to the original payment method, and the processing window your payment provider actually quotes. Add one request only if you need something ("Keep the box until the carrier collects it"). Skip the interrogation: five questions after a valid claim reads like punishment, and the story gets retold in the review that follows.
Counter-example: "We're sorry you feel this way. Please note that refunds are subject to our policy..." Policy recitation before the yes converts a tidy exit into a grudge.
Reply Two: Partial Refund or a Decline
This is the reply that decides whether the customer returns. Structure it in four moves:
- Acknowledge the specific problem by name ("the seam split on the second wear")
- State the offer with the amount as a slot: "I can offer 【amount】 as compensation, or a full refund once the item is back with us"
- Give the reason in one plain sentence, no legalese
- Name the next step if neither option works: "Tell me and I'll escalate it myself"
After-sales lines in template collections written so that refund amounts stay as variables for a human to confirm follow this pattern deliberately: the acknowledgment can be templated, the number cannot. An over-promised figure becomes a liability the store then has to honor, and customer service staff who improvise one create that liability for everyone behind them.
Reply Three: Wait for Restock or Take the Refund
Frame it as a real choice with dates, not a plea: "The restock is expected around 【date】 — I can hold your order and ship it the day it arrives, or refund you in full now. Which do you prefer?" Say how firm the date is: "supplier confirmed" and "supplier estimate" are different sentences, and customers can tell when you are blurring them. If they choose to wait, set your own reminder and tell them you will message proactively about any slip. Silence after "please wait" is what turns a restock into a lost customer — the follow-up message is part of the script, not an extra.
Close the Loop and Log It
Tag every refund thread with a reason code so next month's counts mean something, then spot-check a few closed threads each week: did the reply match the authority numbers, did promised follow-ups actually happen, did any draft go out with a figure nobody confirmed? The three replies above are wording. The habit around them — check the facts, confirm the number, follow up on the promise — is what actually decides everything.
Top comments (0)