Industry surveys keep finding the same gap: most customers expect a support
reply within an hour; the average online store takes over twelve. Templates
exist to close part of that gap, so here are the seven that cover the bulk
of a D2C inbox, free to steal. Swap the {placeholders}, keep the structure:
first sentence answers the question, one email carries the whole
resolution.
1. WISMO: parcel on the way, but slow
Subject: Your order {order}: here’s where it is
Hi {first name},
your parcel is with {carrier} and had its last scan on {date} in {city}. Delivery is currently expected by {date}. You can follow it live here: {tracking link}.
If nothing has moved by {date + 2 days}, we’ll chase it with {carrier} ourselves and get back to you without you having to ask.
{name} from {shop}
Why it works: a concrete status, a concrete date, and the next step is on you, not the customer. (Better still is telling them before they ask: the WISMO playbook.)
2. Marked as delivered, but nothing arrived
Subject: Your order {order}: we’re on it
Hi {first name},
thanks for flagging this. That’s annoying, and we’ll sort it out together. The tracking shows a delivery on {date} at {time}, but that clearly doesn’t match what you’re seeing.
Two quick favors, purely because they resolve a surprising number of cases within hours: could you check whether a neighbor or household member accepted it, and whether it’s waiting at {pickup shop}?
Meanwhile we’ve opened an investigation with {carrier}. If the parcel hasn’t surfaced by {date}, we’ll send a replacement or refund you, your choice.
{name} from {shop}
The tone matters more than usual here: the customer half-expects to be treated as a suspect (why you owe them the benefit of the doubt).
3. Return request: confirmation with label
Subject: Your return for order {order}
Hi {first name},
done, your return is registered. Your prepaid label is attached; just drop the parcel at any {carrier} point by {deadline}.
As soon as the return shows its first scan, we’ll refund {amount} to your original payment method. That usually takes {X} days end to end.
{name} from {shop}
“Refund on first scan” is the policy worth adopting: fast for the customer, safe for you (the legal details).
4. Defect report: warranty intake
Subject: Your {product}: let’s fix this
Hi {first name},
sorry to hear that. We’ll take care of it. So we can resolve this in one go rather than ping-pong, could you reply with:
- a short description of what happens (and when it started),
- a photo or short video showing the issue,
- confirmation this is for order {order}.
As soon as we have that, we’ll get back to you within one working day. If it’s a defect, you choose whether we repair it or send a replacement, so feel free to tell us which you’d prefer.
{name} from {shop}
One structured intake email replaces three round-trips. It also asks for a preference instead of announcing a solution, because under the legal guarantee EU consumer law lets the customer choose between repair and replacement (what the law requires on defects). What happens after intake is on our page about warranty claims management.
5. Cancellation / address change: the race with fulfillment
Subject: Your order {order}: {cancelled / address updated}
Hi {first name},
good timing: your order hadn’t shipped yet, so we’ve {cancelled it and refunded {amount} / updated the delivery address to {address}}. Refunds typically arrive within {X} days.
{name} from {shop}
And the version where the parcel already left: honesty plus the escape hatch. “It’s already on its way; you can simply refuse the parcel at the door or use the attached return label, and we’ll refund on first scan.”
How to run the cancellation itself in Shopify or WooCommerce, without a double refund and with correct stock, is in cancelling an order in Shopify.
6. The angry customer
Subject: Re: {their subject}
Hi {first name},
you’re right. {name the concrete failure: two emails unanswered, a week’s delay, the wrong item}. That’s below the standard we hold ourselves to, and I’m sorry.
Here’s what happens now: {the concrete fix, with a date}. I’m handling this personally until it’s resolved.
{name} from {shop}
No “we apologize for any inconvenience”, no policy lecture. Acknowledge specifically, fix concretely. This is also the template that prevents public one-star versions of the same email.
7. Saying no: the goodwill decline
Subject: Your request for order {order}
Hi {first name},
thanks for your patience while we checked this. I’ll be straight with you: {the ask, e.g. a refund eight months after the return window} is outside what we can do, because {one clear sentence on why}.
What we can offer: {the alternative (discount, spare part at cost, repair)}. If you’d like that, reply and it’s done.
{name} from {shop}
A clear no with a real alternative beats a vague maybe that costs three more emails.
Where templates hit their limit
Look back at the placeholders: {last scan}, {expected date}, {amount},
{deadline}, {hadn't shipped yet}. Every template above is a shell around
a lookup: tracking, order, return window, fulfillment status. The
template saves the typing; the lookup is the actual work, and it’s why a
“templated” inbox still eats hours
(the cost math).
That’s the line between macros and resolution: a system that pulls the live data, fills the shell and sends the result, with the refund or label behind it fully prepared for your one-click release. The templates above are what its output reads like; the difference is nobody had to assemble them. More on our page about automating customer service, from reply to action.