Customer Service Response Templates for Common Situations

These are the replies you send twenty times a week, where the customer is not angry and nothing has gone badly wrong. They are worth getting right precisely because they are routine: a slightly cold refund confirmation is not a disaster on its own, and it is a disaster four hundred times a year.

Twelve templates below, each with the situation, the wording, and the one thing to change. Complaint situations are deliberately excluded and live in the complaint response library; mixing the two is how template sets end up sounding defensive about things that are perfectly fine.

What separates a good routine reply from a bad one

Answer in the first sentence. Routine questions have answers. Put it at the top and use the rest for context. A reply that builds to the answer in paragraph three gets a follow-up asking what the answer was.

Say what happens next and who does it. Most follow-up messages exist because the first reply ended without naming the next step.

Never ask for something you already have. The order number is in the thread. Asking for it again is the fastest way to turn a neutral interaction into an irritated one.

Keep it to three to six sentences. Length signals effort to the writer and signals difficulty to the reader.

Leave one door open. A single line inviting the next question costs nothing and prevents the customer feeling dismissed.

Making templates not sound like templates

Three habits, and they are the difference between a saved reply that works and one customers can smell.

• •Open with their specific detail, not your greeting. "Your [product] order from Tuesday" before anything else.
• •Keep one sentence that cannot be templated. Reference something they actually said. One line of genuine attention redeems four lines of boilerplate.
• •Strip the formality your business does not have. If your brand speaks plainly everywhere else, "We acknowledge receipt of your enquiry" is a costume.

The twelve templates

1. Thank you, after a purchase or a kindness

Use when: someone has bought, renewed, referred you, or taken the time to say something nice. Most businesses skip this and it is the cheapest goodwill available.

Hi [Name], thank you - [specific thing they did]. [One line that is actually about them, not about you.] If anything comes up with [product/service], reply to this message and it reaches me directly.

Change: no upsell. A thank-you with a pitch attached is a pitch.

2. Refund confirmation

Use when: you have processed a refund they are entitled to.

Hi [Name], refund done. [Amount] is on its way back to your [card / account] and usually shows within [number] working days, depending on your bank. Nothing else needed from you. If it hasn't appeared by [date], reply here and I'll chase it.

Change: give the date by which they should worry, not just the window. "Within 3 to 5 working days" leaves them counting; "if it's not there by Friday" does not.

3. Delay notification, sent before they ask

Use when: you know something is late and they do not yet.

Hi [Name], a heads-up before you wonder: [item/service] won't be ready for [original date]. The new date is [date]. [One-line cause.] If that doesn't work for you, [alternative] is available, or I can cancel and refund today - just say which.

Change: send it the moment you know. A delay you announce is competence; a delay they discover is a complaint, and then you need the other article.

4. Cancellation request

Use when: they want to stop, and you want to make it easy.

Hi [Name], cancelled, effective [date]. You won't be billed again and there's nothing further to do. Your [data / access / final invoice] will [what happens], and if you ever want to come back everything will still be here.

>

If you've got a moment: what made you decide to cancel? No obligation to answer, and it won't change anything about the cancellation.

Change: cancel first, ask second, and say the asking changes nothing. Any hint that the answer is a condition of the cancellation turns a clean exit into a bad story.

5. Product or service unavailable

Use when: they want something you do not have.

Hi [Name], [item] is out of stock. Expected back [date, or "I don't have a reliable date yet, and I'd rather say so than guess"].

>

Options: I can let you know the moment it's in, [closest alternative] is available now and [one honest sentence on how it differs], or I can refund if you've already paid.

Change: never invent a restock date to end the conversation. The second message, when the invented date passes, costs far more than the honest "I don't know".

6. Technical problem reported

Use when: something is not working for them.

Hi [Name], thanks for the detail, that's enough to go on. I can [reproduce it / see it on your account] and I'm looking at it now.

>

In the meantime, [workaround, if there is one]. I'll update you by [date and time] whether or not it's fixed by then.

Change: that last clause is the important one. Committing to an update rather than to a fix is a promise you can keep, and it stops the chasing messages.

7. Pricing question

Use when: they are asking what something costs, or why.

Hi [Name], for [what they described], it's [price], which covers [what's included]. [What's not included, stated plainly.]

>

[If relevant: the cheaper option is X, and the difference is Y.] Happy to go through it if it would help, but you should have everything you need to decide from the above.

Change: answer the number first. Pricing replies that route to a call before giving a figure are the most reliably abandoned messages in any support inbox.

8. Request for more information

Use when: you genuinely cannot proceed without something from them.

Hi [Name], to sort this out I need [exactly one or two things, listed].

>

[Where to find it, if it isn't obvious.]

>

Once that's here, [what you'll do] takes about [timeframe]. If it's easier to [alternative route], that works too.

Change: ask for everything at once. A sequence of single-question emails is the most common cause of a simple issue taking a week.

9. Escalation to a colleague

Use when: it needs someone else.

Hi [Name], I'm bringing in [colleague], who handles [area] - they'll be able to [specific thing I can't].

>

They have the full history including [key facts], so you won't need to go over it again. You'll hear from them by [date and time]. I'm still on the thread if anything stalls.

Change: brief the colleague before this goes out. The most common escalation failure is a customer retelling their story to someone who has not read it.

10. Follow-up after resolution

Use when: three to seven days after you fixed something.

Hi [Name], following up on [issue] from last week. [Fix] should be working now - is it? No need to reply if all's well, but if anything's still off I'd rather know.

Change: "no need to reply if all's well" is what keeps this from being a chore. It also means the replies you do get are real signal.

11. The customer has stopped replying

Use when: you need something from them and the thread has gone quiet. Two messages, not five.

First nudge, three to five days:

Hi [Name], just bumping this in case it got buried. I still need [thing] to [outcome]. No rush if you're busy, but let me know either way and I'll plan around it.

Final message, a week after that:

Hi [Name], I'll close this off for now so it stops sitting in your inbox. Nothing is lost - if you want to pick it up, reply to this message any time and it comes straight back to me. [If there's a deadline: the one thing to flag is X, which expires on Y.]

Change: the closing message is the one that most often gets a reply, because it removes the obligation. Two nudges is the limit; after that it is pressure, not service.

12. Saying no

Use when: they have asked for something you are not going to do.

Hi [Name], I've looked at this properly rather than giving you a quick no. [The answer is no, stated plainly, in one sentence.] The reason is [honest reason, not "it's our policy"].

>

What I can do instead is [specific alternative]. If that doesn't work, tell me what would and I'll tell you honestly whether it's possible.

Change: never soften a no into a maybe. A clear no today is cheaper for both of you than three weeks of hopeful follow-ups.

Setting these up as saved replies

A template library only pays off if finding one is faster than writing one.

Name them by situation, not by content. "Refund processed" beats "Template 14". The agent is searching under pressure.

Mark the variable fields visibly. `[NAME]`, `[DATE]`, `[AMOUNT]`. A reply that goes out with a square bracket still in it is worse than no template, and it happens constantly when the placeholders look like ordinary text.

Keep the set small. Twelve to twenty covering your genuine volume. Large libraries get searched badly, and a template nobody can find is slower than typing.

Review quarterly against your actual policies. The failure mode is not a template going stale quietly; it is a stale template being sent confidently.

Track which ones get sent most. The top three are telling you something about your product or your website, not about your support team. If "where is my order" is sent four hundred times a month, the answer belongs on a page, not in an inbox.

When a template is the wrong fix

Here is the pattern worth noticing. A reply you send two hundred times is not a support problem; it is a missing answer somewhere earlier. The template makes sending it cheaper, which is useful, and it also makes the underlying gap invisible, which is not.

Before adding the twenty-first template, check whether the question has an answer on your site that a customer could reach without writing to you at all. Turning your recurring answers into a self-service page removes the message rather than speeding up the reply, and you can edit every line before it is published, which matters: a template is only useful if it says what you would actually say.

For complaints, where the goal is repair rather than speed, use the complaint response templates instead.

Frequently asked questions

How quickly should I respond to customer support emails?

Acknowledge quickly, resolve properly. An acknowledgement within the hour saying "I've got this, full answer by 2pm" buys most of the goodwill of an instant fix and costs thirty seconds. Full resolution within one working day is a reasonable standard for a small team.

Should I apologise in every support reply?

No. Apologise when something went wrong on your side. For routine questions and for things outside your control, empathy is enough: "I understand how frustrating that is" rather than "I'm sorry we got this wrong." Reflexive apologising makes routine interactions sound like incidents.

How long should a support reply be?

Three to six sentences for most situations, with the answer in the first one. Longer only when the customer genuinely needs detail, and never longer because the topic feels awkward.

How many canned responses does a small team need?

Twelve to twenty. Enough to cover real volume, few enough that an agent can find the right one in seconds. The structure in this article handles everything outside the set.

Do customers notice canned responses?

They notice bad ones. A reply that opens with their specific detail and contains one sentence that could not have been pre-written reads as personal, whatever its origin. A reply that opens with a generic greeting and answers a question they did not ask reads as a form letter, whether or not it was.

Should templates be different for email, chat and WhatsApp?

The structure stays the same; the format does not. Chat and WhatsApp need the greeting and sign-off removed, one idea per message, and shorter lines. Pasting an email template into WhatsApp is immediately obvious.