Customer Service Email Templates for Ecommerce Returns, Delays, and Refunds
Use five customer service email templates for returns, delays, and refunds. Copy the replies, then check facts, approvals, and handoffs before sending.

Customer service email templates can save an agent from rewriting the same opening line all day. They cannot tell the agent whether a refund was actually issued or whether a parcel has left the warehouse. In ecommerce, the useful template is the one that makes those checks unavoidable before a message goes out.
The five examples below cover common return, shipping, and refund moments. Replace the bracketed fields with verified order details, use your own approved policy language, and keep the instructions beneath each example inside the support team.
Build every template around a verified decision
A useful response gives the customer the answer or current status early. It then says what happens next, who owns it, and when the customer will hear back. The subject should identify the issue without exposing more personal information than necessary. Digital.gov’s plain-language writing guide recommends active voice because it makes responsibility clear; that is useful when a message needs to say who will act next.
| Customer sees | Agent checks before sending |
|---|---|
| The order or case reference, the specific issue, and the current decision | Correct customer and order; full ticket history; correct store, product, and policy |
| The action already taken, separated from the action still pending | Whether the return, carrier inquiry, or payment action is actually recorded in the system |
| A clear next step and update date | Who owns that action, whether the date is realistic, and whether approval is required |
This is why a template library needs two layers: customer-facing copy and agent-only instructions. Keep the verified status in the message; keep the system checks, approval limits, and escalation route in the internal notes. A generic “we’re looking into it” email may sound polite while leaving both parties unsure whether anyone has checked the order. If the answer is not yet known, say what has been verified and give a time for the next update rather than inventing a resolution date.
Five customer service email templates you can adapt
These templates are starting points for a retailer’s approved macros, not automatic replies. The agent should remove any line that does not fit the case.
1. Return request received
Subject: We received your return request for order [order number]
Hi [first name],
I received your request to return [item]. I’m checking [the relevant eligibility detail] against your order and our return policy. I’ll email you by [day and time with time zone] with the next step. You do not need to submit another request in the meantime.
If the item arrived damaged or you received a different product, please reply with that detail so we can use the right process.
[Agent name], [company] Support
Agent check: Confirm the order, item, purchase channel, and reason for return. Do not send a return label or promise a refund while eligibility or the required approval is unresolved. If the issue is damage or a wrong item, follow that workflow rather than forcing it through a standard change-of-mind return.
2. Return approved with instructions
Subject: Your return steps for order [order number]
Hi [first name],
Your return of [item] has been approved under [policy or approved exception]. Please [packaging and drop-off instruction] by [verified deadline]. Your return reference is [RMA or case number]. [Label or collection instruction, including any applicable charge].
Once [the package is received / the item is inspected], we’ll [approved next action]. You can check the status at [verified link]. If anything in these instructions does not match the item you have, reply before sending it.
[Agent name], [company] Support
Agent check: Verify that the approval exists, the label belongs to the right item and address, and the policy supports the stated deadline and fees. Do not call a refund “issued” when the return has merely been approved.
3. Shipment delayed before dispatch
Subject: An update on shipment of order [order number]
Hi [first name],
We cannot ship your order by the [originally promised shipment date] shown at purchase. Our current expected shipment date is [revised date, if reasonably supported]. You may choose to wait, or cancel the unshipped order for a full refund through [no-cost cancellation method].
[Approved explanation of what happens if you do not respond, based on the revised date.] We will update you by [day and time] if the shipment status changes.
[Agent name], [company] Support
Agent check: Use the retailer’s legally approved delay notice, including the correct response and nonresponse terms. The FTC’s business guide says sellers that cannot ship within the promised time must offer a delay choice or cancellation with a prompt refund, and it permits notice by email. Confirm the order has not shipped; this notice is different from an in-transit carrier exception. Never invent a revised date.
4. In-transit delivery exception
Subject: What we know about the delivery of order [order number]
Hi [first name],
I checked the tracking for [item]. The latest carrier update at [verified time and time zone] is “[exact status].” [We opened case number X with the carrier / We are checking the status with our shipping team].
I’ll contact you again by [day and time], even if the investigation is still open. You can reply here if you have new information about the address or delivery.
[Agent name], [company] Support
Agent check: Distinguish the carrier’s actual scan from your own estimate. If no inquiry has been opened, do not claim one has. A “delivered” scan disputed by the customer, a high-value package, or a possible address change may need a different escalation path. Do not promise a replacement until the person with that authority approves it.
5. Refund issued
Subject: Refund issued for order [order number]
Hi [first name],
We issued a refund of [verified amount and currency] for [item] on [transaction date] to [verified payment method description]. Your reference is [refund reference, if available].
Your payment provider may need additional time to display the credit. If it does not appear by [provider’s verified guidance], reply here and we will investigate.
[Agent name], [company] Support
Agent check: Only send this version after the payment system confirms the refund transaction. Check the amount, currency, destination, and partial-refund calculation. When approval or processing is still pending, say so and give an update date; do not change the tense to make a pending action sound complete.
When a template should stop and a person should take over
The agent should leave the standard macro when the verified facts, authority, or safe path are missing. The customer still needs an owner and a next update; escalation is a handoff, not a resolution or a closed ticket.
| Stop condition | Next owner or action |
|---|---|
| Return requires a policy exception or an approval above the agent’s limit | Route to the authorized returns or refund approver; tell the customer when to expect a decision. |
| Payment status or refund amount does not match the order | Pause the refund claim and have the payments team reconcile the records. |
| Carrier says delivered but the customer disputes receipt | Preserve the tracking facts and use the retailer’s delivery-dispute process. |
| Customer reports injury, overheating, or a potentially unsafe product | Follow the product safety escalation path before ordinary return wording. |
| Customer asks to change sensitive account or payout details unexpectedly | Verify identity through the approved channel before making a change. |
The same rule applies to an AI-generated draft. Someone must still check whether it answered the customer’s actual issue. For more on the language of a service recovery message, see our guide to ecommerce apology mistakes.
Review the message, not just the grammar
An anonymized Canadian supermarket support team handled 42 customer emails on its first operating day on November 10, 2026. Forty passed the first internal review; two were completed after small edits. For an export-certificate request, the team first checked which regional store handled the order before giving instructions.
That example suggests a useful review sequence for any template library. Check whether the agent chose the right workflow, verified the order facts, used the approved action and amount, stated a real next step, and wrote clearly. Record why a draft needed editing. If several edits arise from the same missing question, change the agent-only check or training material instead of polishing the greeting again. For a broader QA program, see what customer service quality assurance should score.
Put the templates into a small, controlled library
Give each macro an owner, an approval date, and a link to the policy or workflow it depends on. For an open case, the internal note should also name the follow-up owner and the next promised update. Separate customer copy from internal notes. Each template needs a review trigger when its policy changes. When a return window, carrier process, or refund permission changes, update the macro and retire the old version. Test it against real, anonymized tickets: one straightforward case, one missing fact, and one exception that needs a handoff.
The email system matters when the same conversation moves between people. If your team cannot see who owns a reply or whether an outbound message failed, our email ticketing system comparison covers that operational choice. If an outside team will send these replies, our guide to outsourcing customer service email covers which decisions stay with you.
Start with the three queues that cause the most rework
Choose one return, one shipment, and one refund situation from your own queue. Write the customer message, the required checks, and the stop condition for each. Have two reviewers score the same small set of replies, resolve disagreements, and revise the templates before broad rollout. That gives agents words they can use and a decision path they can trust.