The Parcel Was Three Days Late. The Reply Made It Worse.

The order shipped on a Tuesday. The tracking page said "in transit" for 5 days straight. On day 6 the customer emailed: "Where is my order? Your site said 3 to 5 days."

The reply she got back was the one every store sends. "We apologise for any inconvenience. Unfortunately delays with our courier are outside our control. Please allow a further 5 to 7 working days."

That reply cost the store a repeat customer, because it told her three things: we don't know where it is, we're not going to find out, and we've decided it's the courier's problem (so by extension, yours).

Get the prompt: Answer 'where is my order?' emails without losing the customer. Paste the customer's message and your tracking facts, get back a reply that's honest, specific, and ends with a date.

Why the standard reply fails

Most "where is my order" replies are written to close the ticket. So they lean on two crutches: a stock apology and a blame shift.

The customer can smell both. What she wants is much simpler. Tell me what you know. Tell me what you don't. Tell me what happens next, and when.

That's a hard email to write when you're 40 tickets deep at 4pm. Which is exactly why it doesn't get written.

What the prompt asks for

The prompt makes you paste 6 things before it writes a word: the customer's message, the order facts (date, promised window, carrier, last scan), what you know about the cause, what you can offer, your store voice, and the customer's history with you.

That last one matters more than it looks. A first-time buyer and a customer on order number 14 should get different remedies. The prompt uses it.

Then it writes three things: the reply itself (under 150 words), a follow-up for the date you promised in two versions (parcel moved, parcel still stuck), and a one-line internal ticket note so whoever picks it up next knows what was committed.

A worked example

Say the inputs are: the customer email above, order placed 15 September, promised 3 to 5 days, Evri, last scan "at local depot" on 17 September, no update since. Cause: unknown, though Evri has a known backlog in that region this week. Can offer: reship at our cost or a full refund. Voice: warm, plain. History: second order.

The reply comes back roughly like this:

"Hi Sarah, you're right, that's a day past what we promised and I'm sorry. Here's what I can see: your parcel reached the Leeds depot on the 17th and hasn't scanned since. Evri has a backlog in your area this week, but I won't assume that's the whole story. I've opened a trace with them this morning. I'll check again on Thursday and email you either way. If it still hasn't moved by then, I'll send a replacement that day at no cost, or refund you in full, your call. Thanks for ordering with us again. I'd like to get this right."

Then the Thursday follow-ups, both pre-written. And the ticket note: "Evri trace opened 23/09, promised update Thu 25/09, reship or refund if no movement."

Compare that with the template reply. Same delay. Same missing parcel. One of them keeps the customer.

Where the value is

Time first. A good version of this email takes 10 to 15 minutes to write by hand when you care about it, and roughly 60 seconds with the prompt. Multiply by however many of these you get a week.

Consistency second. Your best support person writes this email well. Your newest hire writes the "outside our control" version. The prompt closes that gap on day one.

And the follow-up. The promise ("I'll check Thursday") is the part that rebuilds trust, and it's the part that gets forgotten. Having both versions written before Thursday arrives means it happens.

If late deliveries are a pattern rather than a one-off, the fix sits upstream. A clear shipping and returns policy stops half these tickets arriving, and an abandoned cart sequence that states delivery times plainly sets the expectation before the sale.

How to use it

Open the where-is-my-order prompt and copy it into ChatGPT, Claude, or whichever model you use.
Fill the 6 inputs. Be honest in "what we know". If the answer is "no information at all", say that. The prompt is built to handle it.
Send the reply, diary the follow-up date, paste the internal note into the ticket.

Grab the prompt here and run it on the next late-parcel email in your inbox.