← All posts

· Feedbot team

30 Customer Service Email Templates (Copy and Paste)

30 customer service email templates with subject lines for refunds, delays, complaints, outages, bug fixes and cancellations. Edit and send in a minute.

Close-up view of hands typing on a laptop indoors, showcasing technology and productivity
Photo: SHVETS production / Pexels

TL;DR. A good customer service email has a subject line that names the issue, the answer in the first two lines, numbered steps if there are any, a clear “what happens next”, and a real person’s name. Below are 30 customer service email templates with subject lines for the situations support teams handle every week: acknowledgments, refunds, shipping delays, complaints, outages, bug fixes, cancellations and follow-ups. Replace the [brackets] and send.

These are written for email, where the customer may read your reply hours later with no context. For short live chat replies, see our 50 canned responses examples.

How to write a customer service email that doesn’t need a follow-up

Every extra email in a thread is time for you and frustration for the customer. Most back-and-forth comes from replies that are missing one thing. Check yours against this list before you send:

Part What it does Common mistake
Subject line Says what the email is about, with a reference number “Re: Re: Your request”
First two lines The answer, decision or next step Three sentences of apology before the point
Body Steps, numbered; one idea per paragraph Walls of text, unexplained jargon
What happens next Who does what, by when “We’ll be in touch”
Sign-off A person’s name and how to reply “The Team”, or a noreply address

Placeholders in the templates: {name} is the customer’s first name (most help desks fill it in), and [brackets] are details you type.

Acknowledgment and follow-up templates

1. Ticket received (auto-reply)

Subject: We got your message [#ticket ID]
Hi {name},
Thanks for contacting [Company]. A member of our team will reply within [response time, e.g. 1 business day].
If your question is about one of these, the answer may already be here:
- [Help article: billing]
- [Help article: getting started]
To add details, just reply to this email.
[Company] Support

2. Need more information

Subject: A quick question about your request [#ticket ID]
Hi {name},
Thanks for reaching out about [issue]. To look into it, I need one more detail:
[The email address on your account / your order number / a screenshot of the error]
As soon as I have that, I'll get this sorted.
[Agent name]
[Company] Support

3. Still working on it

Subject: Update on [issue] [#ticket ID]
Hi {name},
A quick update: I'm still working on [issue]. I've [what you've done so far], and I'm now waiting on [team / supplier / bank].
I'll send you another update by [day and time], even if it's just to say it's still in progress.
Thanks for your patience,
[Agent name]

4. Follow-up after no reply

Subject: Do you still need help with [issue]?
Hi {name},
I'm checking in on [issue] from [date]. I haven't heard back, so I'll close this request on [date].
If you still need help, reply to this email and it will reopen with the full history.
[Agent name]

5. Escalated to another team

Subject: Your request is with our [billing / technical] team
Hi {name},
I've passed your request about [issue] to our [team], who can [what they can do]. They have the full history, so you won't need to explain it again.
You'll hear from them by [day and time]. If you have anything to add before then, reply here and I'll forward it.
[Agent name]

Order and shipping templates

6. Shipping delay

Subject: Your order [#number] is delayed
Hi {name},
I'm sorry: your order [#number] won't arrive on [original date]. [Carrier] now estimates [new date]. The delay is caused by [short reason, if known].
Tracking link: [link]
If it hasn't arrived by [date], reply to this email and I'll [send a replacement / refund your order].
[Agent name]

7. Out of stock or backordered

Subject: An item in your order [#number] is out of stock
Hi {name},
[Item] from your order [#number] is out of stock. We expect it back on [date]. You can choose:
1. Wait, and we'll ship it as soon as it arrives.
2. Switch to [similar item].
3. Get a refund for this item.
Just reply with 1, 2 or 3. If we don't hear back by [date], we'll [default option].
[Agent name]

8. Wrong or damaged item

Subject: We'll fix your order [#number]
Hi {name},
I'm sorry your [item] arrived [damaged / wrong]. That's on us.
I've sent a replacement today. It should arrive by [date], tracking: [link]. You don't need to send the original back [or: here's a prepaid return label: link].
[Agent name]

9. Return instructions

Subject: How to return your order [#number]
Hi {name},
Here's how to return [item]:
1. Print the prepaid label: [link]
2. Pack the item, in its original packaging if you have it.
3. Drop it at any [carrier] location by [date].
We'll refund [amount] to your original payment method within [3 business days] of receiving it.
[Agent name]

Billing, refund and cancellation templates

10. Refund approved

Subject: Your refund of [amount] is on its way
Hi {name},
I've refunded [amount] to your [card ending 1234]. Banks usually take [5–10 business days] to show it on your statement.
Refund reference: [ID]. If it hasn't appeared by [date], reply with this reference and I'll check with our payment provider.
[Agent name]

11. Refund declined

Subject: About your refund request
Hi {name},
Thanks for explaining what happened with [order / subscription]. I've looked into it, and I can't issue a refund because [specific reason: the purchase was on DATE, outside our 14-day window].
Here's what I can offer instead: [credit / downgrade / pause / partial refund].
If there's something I've missed, reply and tell me. I'm happy to take another look.
[Agent name]

12. Failed payment

Subject: Action needed: your payment didn't go through
Hi {name},
We couldn't process your payment of [amount] for [plan] on [date]. This usually happens when a card expires or the bank declines an online charge.
You can update your payment method here: [link]
Your account stays active until [date]. After that, [what happens: it switches to the free plan / is paused]. Your data won't be deleted.
[Company] Billing

13. Price change notice

Subject: Your [plan] price is changing on [date]
Hi {name},
On [date], the price of [plan] will change from [old price] to [new price] per [month/year]. [One sentence on why, e.g. what's been added.]
Nothing changes before then. If you'd like to lock in the current price, you can switch to yearly billing before [date]: [link]. You can also change or cancel your plan any time in [Settings → Billing].
[Name], [Company]

14. Cancellation confirmed

Subject: Your subscription is canceled
Hi {name},
Your [plan] subscription is canceled. You'll keep access until [date], and you won't be charged again.
Your data will be kept until [date / for X days], so you can come back without losing anything.
If you have a moment, I'd really like to know what made you leave. Just reply with a sentence.
[Name]

15. Win-back after cancellation

Subject: [Feature they asked for] is live
Hi {name},
When you canceled in [month], you mentioned [reason / missing feature]. We've since [shipped it / changed it]: [link].
If you'd like to try again, your old account and data are still here: [link].
[Name]

Only send #15 when you’ve actually fixed the reason they left.

Complaint and apology templates

16. Response to a complaint

Subject: Re: [their subject]
Hi {name},
You're right that [specific problem in their words]. I'm sorry. It shouldn't have happened, and I understand why you're frustrated.
Here's what I've done: [action taken].
Here's what happens next: [next step and date].
If this doesn't fully fix it, reply directly to me and I'll keep working on it.
[Agent name]

17. Apology for a mistake on your side

Subject: We made a mistake with your [order / account]
Hi {name},
We [what went wrong: charged you twice / sent the wrong item / deleted your settings]. That was our error, not something you did.
I've already [fixed it / refunded / restored]. As an apology, [credit, discount or free month, if you offer one].
[Agent name]

18. Customer contacted you several times

Subject: I'm taking over your request [#ticket ID]
Hi {name},
I can see you've had to write to us [3 times] about [issue], and it's still not solved. I'm sorry. That's not the experience we want you to have.
I'm now the one person handling this, and I won't close it until it's fixed. My next update will be by [day and time].
[Agent name], [role]

Product, bug and feature templates

19. Bug report received

Subject: Thanks for reporting this bug
Hi {name},
Thanks for letting us know about [bug]. I've reproduced it and passed it to our engineers with your details.
Until it's fixed, you can [workaround]. I'll email you as soon as the fix is live.
[Agent name]

20. Bug fixed

Subject: Fixed: [the issue you reported]
Hi {name},
The problem you reported on [date] with [feature] is fixed. You may need to refresh the page or update the app to see it.
Thanks for taking the time to report it. It helped us find it faster.
[Agent name]

21. Feature request received

Subject: Thanks for your suggestion
Hi {name},
Thanks for suggesting [feature]. I've added it to our product list along with how you'd use it, which is the part our team finds most useful.
I can't promise when or whether we'll build it, but if we do, you'll be one of the first to know.
[Agent name]

22. Feature you asked for has shipped

Subject: You asked for [feature]. It's here.
Hi {name},
In [month] you asked us for [feature]. It's live today. Here's how to use it: [link].
Thanks for the push.
[Name]

Outage and incident templates

23. Service disruption

Subject: We're having issues with [feature]
Hi {name},
[Feature] isn't working properly right now. Our engineers are on it. You can follow live updates at [status page].
We'll email you again when it's resolved. Sorry for the disruption.
[Company] Support

24. Incident resolved

Subject: Resolved: [feature] issue on [date]
Hi {name},
The issue affecting [feature] from [start] to [end] [time zone] is resolved.
What happened: [one plain sentence].
What it affected: [who and what].
What we're changing: [one sentence].
If anything still looks wrong on your side, reply to this email.
[Name], [role]

25. Scheduled maintenance

Subject: Planned maintenance on [date]
Hi {name},
[Product] will be unavailable on [date] between [time] and [time] [time zone] while we [short reason]. You don't need to do anything.
[Company]

Account and security templates

26. Password reset help

Subject: How to reset your password
Hi {name},
To reset your password:
1. Go to [login link] and click "Forgot password".
2. Enter the email on your account: [email].
3. Open the link we send (valid for [1 hour]) and choose a new password.
If the email doesn't arrive in a few minutes, check spam or reply here and I'll help.
[Agent name]

27. Suspicious account activity

Subject: Please check recent activity on your account
Hi {name},
We noticed [a sign-in from a new device in LOCATION / a password change] on [date]. If this was you, you don't need to do anything.
If it wasn't, please [reset your password: link] and [turn on two-factor authentication]. We will never ask for your password by email.
[Company] Security

28. Data deletion request confirmed

Subject: Your data deletion request
Hi {name},
We received your request to delete your account and personal data. It will be completed by [date], and we'll email you when it's done.
This can't be undone. If you change your mind before [date], reply to this email.
[Company] Privacy

Thank-you and feedback templates

29. Asking for a review

Subject: How did we do?
Hi {name},
Thanks for your patience with [issue] this week. If you have 30 seconds, would you rate your experience? [link]
Every response is read by our team.
[Agent name]

30. Thanking a long-time customer

Subject: [X] years with [Company]
Hi {name},
It's been [X] years since you joined us. Thank you for sticking with us, and for [specific thing: your feedback on X / reporting bugs / referring your team].
If there's anything we can do better, reply to this email. It comes straight to me.
[Name], [role]

Subject line formulas that get opened

Situation Formula Example
Acknowledgment We got your message [#ID] We got your message [#4821]
Action needed Action needed: [what] Action needed: update your card
Good news [Outcome] + [object] Your refund of $49 is on its way
Bad news Plain statement, no spin Your order #1182 is delayed
Resolution Fixed: / Resolved: [issue] Fixed: CSV export in Safari
Follow-up Question form Do you still need help with your invoice?

Avoid all caps, “URGENT”, and vague lines like “Important update” for transactional email. They look like spam and get filtered as spam.

Mistakes that make support emails worse

  • Apologizing for three sentences before answering. One sincere sentence is enough. Then fix it.
  • Copying a template without reading the customer’s email. If they already tried what your template suggests, you’ve just told them you didn’t read it.
  • Promising dates you don’t control: shipping dates from a carrier, release dates for features.
  • Sending from noreply@. If a customer can’t reply, they’ll open a new ticket or a dispute instead.
  • Closing tickets without saying so. Tell people when you’re closing a request and how to reopen it.
  • Hiding the policy. If a refund is declined, name the rule and the date. Vague refusals lead to chargebacks.

Fewer emails in the first place

Many of these emails exist because a customer couldn’t find an answer on your site. An AI chatbot that answers from your help docs handles password resets, invoice requests and “how do I…” questions in the chat, before they become tickets. That’s what we build at Feedbot: the bot answers from your knowledge base, hands off to a person when it can’t help, and if the visitor has already left, your team’s reply is sent to them by email.

For the replies your team writes, Feedbot has reply templates (with {name} filled in automatically) and an AI Suggest button that drafts a reply from the conversation, using your templates as examples of tone. Requests only a person can handle, like refunds, become tickets you close with a reply.

If you’re working out which of these emails to automate, start with our guide to customer service automation.

Questions

Can't find an answer? Ask the bot in the corner, or write to us.

What are the 5 C's of email writing?

One common version is clear, concise, correct, courteous and complete. For support email, complete matters most: the customer should be able to act on your reply without writing back to ask what you meant.

How do you write a professional customer service email?

Use a subject line that names the issue, greet the customer by name, put the answer or next step in the first two sentences, number any steps, say when they'll hear from you next, and sign with a real name. Keep it under about 150 words.

What is a good customer service email address?

Short, role-based addresses work best: support@, help@ or hello@ your domain. Avoid noreply@ for anything a customer might answer, and make sure replies to automated emails reach a monitored inbox.

How fast should you reply to a customer service email?

Within one business day is a reasonable baseline, and within a few hours is better for anything urgent like a failed payment or a broken checkout. If you can't solve it quickly, send an acknowledgment that says when you'll reply in full.

Should customer service emails be signed by a person or the company?

By a person, with the team name underneath. A real name makes the email easier to reply to and makes the customer feel someone owns the problem. Automated acknowledgments can be signed by the team.

Put one agent on your site today

Start on the free plan. Upgrade when conversations grow.