10 customer service email templates worth stealing

Chat snippets and email are different instruments. A chat canned response is a fast bar of melody; a support email carries the whole situation: context, decision, next steps, and tone that survives being forwarded to someone's manager. These ten templates cover the email situations that actually recur, written to be edited rather than pasted blind. (For short in-conversation snippets, we keep a separate set of fifteen.)

The rules that keep support email human

1. Subject lines state the outcome: "Your refund is processed", not "Re: Re: Re: your inquiry".
2. Decision first, story second. The reader scans; give them the verdict in the first line and the reasoning below.
3. One required blank per template. A [specific detail] the sender must fill keeps the robotic tone out and the accountability in.
4. Sign with a name. "The Support Team" is where trust goes to die.

1. The apology that does not grovel

Subject: What went wrong with [thing], and what we are doing

Hi [name],

You are right, and I am sorry: [plain-language description of what went wrong]. It happened because [honest one-line cause], which we should have caught.

What we have done: [fix taken]. What changes so it does not repeat: [concrete change]. [If applicable: we have credited/refunded X.]

If anything about this still is not right, reply to me directly.

[Name]

2. Refund confirmation

Subject: Your refund of [amount] is processed

Hi [name],

Done: [amount] is on its way back to your [card/account], arriving within [X] business days. Your [subscription/order] is [cancelled/unchanged], as you asked.

Sorry it came to a refund. If you are open to sharing what did not work, one sentence in reply helps us more than any survey.

[Name]

3. Refund declined, alternative offered

Subject: About your refund request for [item]

Hi [name],

I looked at this properly and I cannot refund it: [specific honest reason, e.g. the renewal ran on date X, outside the 14-day window]. I know that is not the answer you wanted.

What I can do: [genuine alternative: credit, prorated downgrade, extended access]. If that works, reply and I will set it up today.

[Name]

4. Bug acknowledged, with a real timeline

Subject: Confirmed: the [feature] bug you reported

Hi [name],

Thank you for the clear report. I reproduced it: [one-line description]. It is filed with engineering as [reference], currently expected in [honest timeframe, or "I will update you by [date] with a timeline"].

Meanwhile, [workaround if any]. I will email you when the fix ships; you do not need to chase us.

[Name]

5. The outage follow-up

Subject: Yesterday's [duration] outage: what happened

Hi [name],

Between [time] and [time] on [date], [what customers experienced]. The cause was [plain-language cause]. We have [immediate fix], and to prevent recurrence we are [concrete change].

If the outage cost you something specific, reply and tell me; we will make it right case by case.

[Name]

6. Feature request: honest no, or honest maybe

Subject: Your request for [feature]

Hi [name],

Thanks for laying out the use case. Straight answer: this is not on our near-term roadmap, and I would rather tell you that than promise vaguely. [If true: the closest path today is (workaround).]

I have logged your request with your reasoning attached, and if it ships, this thread is where you will hear it first.

[Name]

7. The check-in that is not a sales email

Subject: Checking this actually got solved

Hi [name],

Closing the loop on [issue]: is it fully sorted on your end? If yes, no reply needed and I will close the file. If anything still feels off, one line back and it reopens with me, not a queue.

[Name]

8. Escalation handoff by email

Subject: Bringing in [name] on your [issue]

Hi [name],

This needs someone closer to [area] than I am, so [colleague name], who [owns that area], is taking over. They have the full history; nothing needs repeating. Expect their reply by [time].

[Name]

9. The overdue reply

Subject: Late reply on [topic], with the answer

Hi [name],

This took longer than it should have, and that is on us. Here is the answer: [full answer, no padding].

[If systemic: we have changed (thing) so replies like this do not sit again.] Thanks for the patience we should not have needed.

[Name]

10. Goodbye done gracefully (cancellation confirmation)

Subject: Your cancellation is confirmed

Hi [name],

Confirmed: your account is cancelled as of [date], with access until [date]. Your data [export/retention terms]. No further charges.

If something specific drove you away, I read every reply to this address. And if you return someday, your history will be here.

[Name]

Turning templates into a system

• Store them where the team replies, with required blanks, and review quarterly like the chat set.
• Send the first response fast even when the full answer is slow; template 9 exists so you rarely need it (the FRT playbook).
• Let recurring emails become help articles. If template 4 or 6 fires weekly for the same topic, the answer belongs in your help center, findable at 2am.