15 Customer Service Email Templates (Copy and Paste)

Email is still where many customers bring their most detailed questions, and their biggest problems. Unlike chat, an email reply is read carefully, forwarded, and sometimes screenshotted. A good one solves the problem and leaves the customer feeling looked after; a vague one starts a long thread of "any update?" messages.

These customer service email templates cover the situations small support teams face every week. They're written for email specifically: a clear subject, a structure that's easy to scan, and a next step in every message. (For short replies in live chat and messaging apps, see our 12 canned responses for chat.)

What makes a good support email

A subject that says what it's about. "Your refund for order #4821" beats "Re: Re: question".
The answer in the first two lines. Many people read emails on their phone and stop after the preview.
One topic per email. If the customer asked three things, answer all three, clearly separated.
A clear next step. What happens now, who does it, and when.
A human sign-off. A first name, not "The Support Team".
No walls of text. Short paragraphs, numbered steps, and links to help articles for detail.

Use placeholders like {{name}}, {{order}} and {{agent}} so the templates fill in automatically in your help desk.

The 15 templates

1. Acknowledgement (we've got it)

Subject: We've received your message [#{{ticket}}]

Hi {{name}},

Thanks for getting in touch. Your request is with our team, and we'll reply within {{time}}. You don't need to send it again: just reply to this email if you want to add anything.

{{agent}}

2. Asking for more information

Subject: A couple of details so we can help

Hi {{name}},

Thanks for explaining what happened. To look into it, could you send:

Your order number

A photo of the item (if it's damaged)

As soon as we have these, we'll get it sorted.

{{agent}}

3. The answer, with steps

Subject: How to {{task}}

Hi {{name}},

Good news, you can do this in a minute:

Go to {{page}}

Click {{button}}

Confirm, and you're done

There's a full guide with screenshots here: {{link}}. If anything looks different, reply and I'll walk you through it.

{{agent}}

4. Delay update

Subject: An update on your order #{{order}}

Hi {{name}},

I'm sorry, your order is running late. {{reason in one sentence}}. The new expected date is {{date}}, and I'll email you as soon as it ships. If that date doesn't work for you, reply and we'll find another option, including a full refund.

{{agent}}

5. Refund confirmation

Subject: Your refund for order #{{order}} is on its way

Hi {{name}},

We've refunded {{amount}} to your original payment method. Depending on your bank, it can take {{X}} working days to appear. Nothing else is needed from you.

{{agent}}

6. Saying no, politely

Subject: About your request

Hi {{name}},

Thanks for asking. I wish I could do this for you, but {{reason in one sentence}}. What I can offer instead is {{alternative}}. Would that help?

{{agent}}

7. Apology for a mistake

Subject: We got this wrong, and here's how we're fixing it

Hi {{name}},

You're right, and I'm sorry. {{what went wrong}} was our mistake. Here's what we've done: {{fix}}. {{goodwill gesture, if any}}. Thank you for telling us; it helps us stop this happening to anyone else.

{{agent}}

8. Escalation to a specialist

Subject: I've passed your question to our {{team}} team

Hi {{name}},

This needs a specialist, so I've passed it to {{colleague}} in our {{team}} team. They have all the details from our conversation, so you won't need to repeat anything. You'll hear from them by {{time}}.

{{agent}}

9. Bug report received

Subject: Thanks for reporting this

Hi {{name}},

Thanks for the detailed report. I've reproduced the problem and passed it to our product team. In the meantime, you can {{workaround}}. I'll email you when it's fixed.

{{agent}}

10. Feature request

Subject: Your suggestion

Hi {{name}},

Thanks for the idea. I've shared it with our product team along with your use case. I can't promise a date, but requests like yours are exactly how we decide what to build next.

{{agent}}

11. Follow-up after no reply

Subject: Just checking in on #{{ticket}}

Hi {{name}},

I wanted to check whether my last email solved the problem. If you still need help, just reply here. If I don't hear back, I'll close this request in {{X}} days, and replying will reopen it any time.

{{agent}}

12. Closing a resolved ticket

Subject: Your request is resolved

Hi {{name}},

Glad we could sort this out. If anything else comes up, reply to this email and it'll come straight back to us.

{{agent}}

13. Out of office / holiday hours

Subject: We've received your message

Hi {{name}},

Thanks for your email. Our team is away until {{date}}, and we'll reply as soon as we're back. In the meantime, our help center answers the most common questions: {{link}}.

14. Responding to an angry email

Subject: I'm sorry, let's fix this

Hi {{name}},

I've read your message, and I understand why you're frustrated. That isn't the experience we want you to have. Here's what I'm doing right now: {{action}}. I'll update you by {{time}} today, even if it's just to say where things stand.

{{agent}}

15. Asking for feedback

Subject: How did we do?

Hi {{name}},

Your request #{{ticket}} was resolved recently. Did we help? One click is all it takes: 👍 / 👎. If anything could have been better, just reply and tell us.

Turn templates into one-click replies

Copying text from a document is slow and error-prone. In a help desk, save each template as a reply your team can insert with a shortcut, and go one step further with macros: one click sends the email, sets the ticket status, adds tags and assigns it. Our help desk includes macros, canned replies and automatic satisfaction surveys (template 15) in every package.

Templates 1, 11 and 13 don't even need a person: an auto-reply trigger can send the acknowledgement, and an automation can send the follow-up and close quiet tickets.

Keep templates human

Edit before sending. Add one sentence that responds to what this customer actually said.
Review every quarter. Old prices and policies in templates cause more problems than they solve.
Read the replies you get. If customers often answer a template with a question, the template is missing something.
Measure the results. Track first response time and satisfaction for email; see customer support KPIs.

When email isn't the right channel

Some conversations go faster elsewhere. Quick questions are often solved in one minute on live chat, and customers who prefer messaging can reach you on WhatsApp, Instagram or Messenger, all in the same inbox as your email tickets. For a step-by-step problem, offering a short voice or video call can save a dozen emails.

Get started

Pick the five situations your team writes about most, adapt those templates, and save them as replies today. Everything mentioned here is included in every package, including the free one; see pricing. Start free and forward your support email to see your first tickets in minutes.

Customer Service Email Templates: 15 Examples You Can Copy