DEV Community

XiaoShengYi
XiaoShengYi

Posted on Edited on Originally published at xiaoshengyi-toolbox.surge.sh

7 Customer Messages You Should Never Answer Manually (Copy-Ready Replies)

7 Customer Messages You Should Never Answer Manually (Copy-Ready Replies)

Most small stores do not lose sales because the product is bad. They lose them because a buyer asks a simple question at 11pm, gets no answer, and buys from the next store.

I keep a list of the messages that are almost always worth automating or templating. Here are seven, with the structure I use for each reply.

1. "Is this true to size?"

Answer with a recommendation, not a yes/no.

Great question — this style has a relaxed fit, so your usual M will work and still leave room to move. If you prefer a closer fit, size down one. Want me to check the chest measurement for you?

Why it works: it reduces the buyer's risk and gives them a reason to reply.

2. "Where is my order?"

Apologize once, give a real status, and offer a clear next step.

I'm sorry it is taking longer than expected — I'd be frustrated too. Your order left our warehouse on the 12th and is with the carrier now. Here is the tracking link. If it does not move by tomorrow evening, reply here and I will send a replacement or refund you — your choice.

3. "Can I get a discount?"

Do not invent a discount on the spot. Give a reason-based answer.

I can't stack another code on this one, but I can do this: order two and I'll upgrade you to free shipping. Want me to send a checkout link?

4. "I want to return this."

Make the process feel small.

Of course — I can help with that. Please send me a photo of the item and the packing slip, and I'll send you a prepaid return label today. Once it is scanned, your refund goes back to the original payment method within 3–5 business days.

5. "Is it in stock?"

Answer with the exact variant and a deadline.

The sand color in M is in stock and ships today if you order before 4pm. The black in M is sold out until the 22nd. Which one would you like me to reserve for you?

6. "Why did my discount not apply?"

Explain the rule, then fix the path.

The welcome code only works on your first order and cannot be combined with sale items. Your cart has one sale item, which is why it did not apply. I can either remove the sale item so the code works, or keep it and give you free shipping. Which do you prefer?

7. "This arrived damaged."

Lead with ownership, then make the remedy concrete.

I'm sorry — that is not the unboxing experience we want. Please send a photo of the damaged item and the box, and I'll ship a replacement today. You do not need to return the damaged one.

The pattern behind all seven

Every reply does three things:

  1. Acknowledges the buyer's cost — time, risk, or frustration.
  2. Gives one concrete next step — a size, a date, a link, a choice.
  3. Does not over-promise — no fake deadlines, no invented policy.

That is also the structure I use when I set up AI customer-service replies for small stores: a tone guide, a small set of approved answers, and a human review path for refunds and complaints.

If you want the full script library, it is here: customer service scripts for e-commerce.

If you want the done-for-you version, I set up the reply pack and workflow for your store — 3-day free trial, then $39–59/month: AI customer service setup.

And if you just want to try the free tools first, the toolbox is here: 9 free AI tools for small sellers.

What is the message you answer most often? I read every reply.

Top comments (0)