Customer Service Email Templates: 30 Copy-Paste Examples (2026)

A customer service email template is a reusable reply you draft once and reuse across similar conversations (order confirmations, refund requests, angry complaints, renewal reminders) so your team answers faster without sounding robotic. Below are 30 copy-paste templates organized by scenario, each with a “when to use” line, the template itself, and a short customization tip. Every template fits inside plain Gmail and works even better inside a shared inbox like Keeping.

Customer service replies work best in the 100–180 word range, and 89% of customers expect a reply within an hour — with 88% now expecting faster responses than a year ago. The goal of a good template is simple: hit the right tone fast, then get out of the way. Every template below is within that word range and uses variable syntax (like {first_name}) that drops directly into Gmail canned responses.

Jump to a category

When to use a template (and when to skip it)

Use a template when the reply is routine, repeatable, and carries low stakes — order confirmations, shipping updates, password resets, FAQ-style questions. Write from scratch when the stakes are high: a VIP threatening to churn, a public complaint that could go viral, a legal- or compliance-adjacent issue, or any scenario where the customer needs to feel personally heard. The test is simple: if getting this reply wrong costs more than the time saved by templating it, skip the template.

Here’s a simple decision rule that keeps teams from over-templating:

If you’re stretching to fit a template to the situation, that’s your signal to write from scratch. For everything else, wire your templates into Gmail canned responses so your team can fire them off in two clicks.

Anatomy of a great customer service email

A good customer service email has six parts that show up in the same order almost every time: subject line, greeting, acknowledgment, solution, next steps, sign-off. Miss any one and the email feels off — usually because the customer either doesn’t know what happened, doesn’t know what to do next, or doesn’t know who they’re talking to.

• Subject line. Specific enough that the customer can find the thread later. “Re: your order” is worse than “Your order #4823 has shipped.” Keep it under 50 characters.
• Greeting. First name if you have it. “Hi {first_name}” beats “Hello valued customer.” If the original email was formal, match the tone.
• Acknowledgment. One sentence that shows you read their message. Don’t skip this, even when you’re replying fast — “Thanks for flagging this” costs you a second and lands a lot softer than diving straight into the fix.
• Solution. The answer, in plain language. If it’s a process, use a numbered list. If there’s a wait, state it directly.
• Next steps. What happens next and what the customer needs (or doesn’t need) to do.
• Sign-off. A warm close, your name, and your role. See the guide to ending a customer email for 18 sign-offs that don’t feel corporate.

Here’s what that looks like in practice. The “before” below is what a rushed reply often looks like; the “after” is the same information with the six parts in place.

Before:

Your order is out for delivery today.

Thanks,
Support

After:

Subject: Your order #4823 is out for delivery today

Hi Sarah,

Thanks for checking in. Your order is out for delivery today and should arrive by 6 PM.

Here's your tracking link: {tracking_url}

No action needed on your end — but if it doesn't show up by tomorrow morning, just reply to this email and I'll sort it out.

Best,
Alex
Customer Support · Acme

Acknowledgment & confirmation templates

Use these when a customer emails in and you need to buy time, or when an action (an order, a ticket, a signup) needs a confirmation receipt. The goal is to acknowledge receipt of a customer email within an hour so they’re not left wondering if it went through.

1. Receipt acknowledgment (“we got your message”)

When to use: Any inbound message you can’t resolve in the next hour — buys you goodwill while you dig into it.

Subject: Got your message — we're looking into it

Hi {first_name},

Thanks for reaching out. I've got your note about {issue_summary} and I'm looking into it now.

I'll have a full answer for you within {response_window}. In the meantime, if anything changes on your end, just reply to this thread.

Talk soon,
{your_name}

• Fill {response_window} with a real number (e.g., “the next 2 hours”), not “as soon as possible.”
• Restating the issue in {issue_summary} proves you actually read the email.

2. Order confirmation

When to use: Right after an order is placed, especially if your platform doesn’t auto-send a branded confirmation.

Subject: Order #{order_id} confirmed — here's what's next

Hi {first_name},

Your order is confirmed. Here's a quick summary:

- Order: #{order_id}
- Items: {items_summary}
- Total: {total}
- Estimated delivery: {delivery_date}

You'll get another email from us the moment it ships, with a tracking link. If you need to change or cancel anything, reply to this email within the next 24 hours.

Thanks for ordering with us,
{your_name}
{company_name}

• If you do auto-send a transactional confirmation, use this template as the human follow-up for first-time customers only.
• The 24-hour change window is optional — drop that line if your fulfillment is faster.

3. Ticket/inquiry confirmation with ETA

When to use: Someone submits a support request through a form, widget, or shared inbox and you want to set expectations up front.

Subject: We received your request — #{ticket_id}

Hi {first_name},

Thanks for getting in touch. Your request is logged as #{ticket_id} and one of our team is on it.

What to expect:
1. We'll send you a first response within {first_response_sla}.
2. If we need more info from you, we'll ask in this same thread.
3. Once it's resolved, we'll close the loop here.

If this is urgent, reply with "URGENT" in the subject line and we'll bump it up the queue.

Thanks,
{your_name}

• Only include the “URGENT” escalation path if you can actually honor it — otherwise drop that line.
• Numbered steps work better than prose here; customers scan these.

Onboarding & welcome templates

The first 48 hours after a signup or first purchase are when customers decide whether you’re worth their time. These three templates cover the most common onboarding moments: welcoming them, introducing their point of contact, and telling them what to expect next.

4. New customer welcome

When to use: Someone just signed up for a trial, account, or product. Send within the first hour for max impact.

Subject: Welcome to {company_name}, {first_name}

Hi {first_name},

Welcome aboard — we're glad you're here.

The fastest way to get value out of {product_name} is to do these three things first:

1. {first_key_action}
2. {second_key_action}
3. {third_key_action}

I'm {your_name} and I help new customers get up and running. If you hit a snag or have a question, just reply to this email — it comes straight to me.

Looking forward to seeing what you build,
{your_name}

• Pick three actions that map to your product’s activation event, not every feature. Fewer is better.
• “It comes straight to me” only works if it’s actually true — otherwise swap for “someone on our team will get right back to you.”

5. Account manager / CS lead introduction

When to use: A new customer is being assigned a dedicated contact — send from the account manager directly, not the shared inbox.

Subject: Hi — I'm your point of contact at {company_name}

Hi {first_name},

I'm {your_name}, and I'll be your main contact at {company_name} going forward. My job is to make sure you get the most out of {product_name}.

A few things you can always come to me for:
- Questions about how to use {product_name}
- Requests for new features or integrations
- Billing or plan changes

You can reply to this email any time, or grab 20 minutes with me here: {calendar_link}

Talk soon,
{your_name}

• If you’re in a shared inbox rather than a named account manager model, swap “I’ll be your main contact” for “our team is here to help.”
• The calendar link is optional — only include it if you actually want to book the call.

6. “What to expect” first-week email

When to use: Day 1 or Day 2 of a trial/onboarding, when the customer has signed up but hasn’t taken the key activation action yet.

Subject: What to expect from us this week

Hi {first_name},

Quick note so you know what's coming. Over the next week, you'll hear from me two more times:

- Day 3: a short check-in to see if anything's tripping you up
- Day 7: a wrap-up with tips based on how you've been using {product_name}

In between, I'm on email — if you need anything, just reply.

One thing that helps most new customers in the first week: {key_tip}.

{your_name}

• Make {key_tip} specific and actionable (“set up your first automation” beats “explore the product”).
• If you don’t actually send Day 3 and Day 7 emails, don’t promise them. Drop the schedule line.

Follow-up templates

Follow-ups are where most teams either over-nag or go silent. These three templates handle the three cases you’ll run into most often: a ticket that’s stalled on your side, a ticket you think is resolved, and a customer who’s gone quiet after you asked them a question.

7. Stuck/stalled ticket follow-up (from your side)

When to use: A ticket has been sitting in your queue longer than your SLA and you don’t yet have an answer — but you want to keep the customer in the loop before they email again.

Subject: Update on your request #{ticket_id}

Hi {first_name},

A quick update on #{ticket_id}. I haven't forgotten about it — {brief_reason_for_delay}, and I want to get you a real answer rather than a rushed one.

Here's where things stand: {current_status}.

I'll have something concrete for you by {new_eta}. Thanks for bearing with me.

{your_name}

• Be specific in {brief_reason_for_delay} — “I’m waiting on our engineering team to confirm the root cause” beats “we’re working on it.”
• Only commit to {new_eta} you’ll actually hit. Missing a second ETA is worse than missing the first.

8. Resolved-ticket follow-up (“did this solve it?”)

When to use: 24–48 hours after you’ve closed a ticket, to confirm the fix stuck and catch anything that’s still broken.

Subject: Quick check — is #{ticket_id} fully sorted?

Hi {first_name},

Just circling back on #{ticket_id}. I wanted to make sure {solution_summary} actually fixed the problem and you're not running into any follow-on issues.

If it's all good, no need to reply — I'll close this out at the end of the week.

If something's still off, just hit reply and tell me what you're seeing.

{your_name}

• “No need to reply” lowers friction and actually increases the chance they’ll speak up if something’s broken.
• This is also a natural spot to ask for a review — but only if the fix clearly worked. Bundle with template #29 if it did.

9. No-response nudge

When to use: You asked the customer for something (logs, a screenshot, confirmation) and they’ve gone quiet for 3+ business days.

Subject: Re: {original_subject}

Hi {first_name},

Bumping this thread to the top of your inbox. I'm still on standby for {what_you_need} so I can get #{ticket_id} sorted for you.

If it's no longer an issue, no worries — just let me know and I'll close the ticket. If it's still an issue and now's not a great time, a one-line "I'll circle back next week" works too.

{your_name}

• Giving the customer an easy “close it out” option is the fastest way to clear stale tickets without feeling pushy.
• After two nudges, auto-close the ticket and let them know — don’t send a third.

Complaint, apology & angry-customer templates

When something goes wrong, the order matters: empathy first, then solution. Jumping straight to the fix — even a good fix — reads as dismissive when the customer is upset. These four templates walk up the escalation ladder, from a mild complaint to a full apology when your team actually dropped the ball. For longer-form situations, see the full guide to apology letters.

10. Complaint acknowledgment (empathy first)

When to use: A customer writes in frustrated, but you don’t yet have all the facts — this is your first response while you investigate.

Subject: Re: {original_subject}

Hi {first_name},

Thank you for telling us — I can see why {specific_issue} is frustrating, especially {context_detail}.

I want to get this right, so I'm looking into it now. Here's what I'm going to do:

1. {first_investigation_step}
2. {second_investigation_step}
3. Get back to you by {eta} with a clear answer.

I'll be in touch shortly.

{your_name}

• Name the specific issue in {specific_issue} — generic empathy (“that sounds frustrating”) reads as scripted.
• Don’t promise an outcome in step 3, only a response. Outcomes you can’t guarantee become broken promises.

11. Angry-customer de-escalation

When to use: The customer is hot. Caps lock, exclamation marks, threats to switch providers. Your first job here is to lower the temperature, not to win.

Subject: Re: {original_subject}

Hi {first_name},

You're right to be upset — {specific_thing_that_went_wrong} should not have happened, and I completely understand why you're frustrated.

I'm not going to try to defend what happened. Here's what I'm doing right now:

- {immediate_action_1}
- {immediate_action_2}

I'll personally own this thread until it's resolved. If you'd prefer to hop on a quick call instead of going back and forth over email, here's my calendar: {calendar_link}.

{your_name}
{your_role}

• “You’re right to be upset” is disarming — but only use it if they genuinely are. Don’t validate invalid anger.
• Signing with your role (not just your name) tells them a human, not a bot, is on the hook.

12. Full apology (we messed up)

When to use: Your team is clearly at fault — a missed deadline, a billing mistake, a bug that cost them time or money. No hedging.

Subject: About {issue_summary} — my apologies

Hi {first_name},

I'm sorry. {what_happened} was our fault, and the impact on you — {impact_on_customer} — is not okay.

Here's what we're doing to make it right:

1. {immediate_fix}
2. {compensation_or_makegood}
3. {process_change_so_it_doesnt_repeat}

If there's anything else you need from us, tell me and I'll make it happen.

Again, I'm sorry we put you in this position.

{your_name}
{your_role}

• A process-change commitment ({third item}) is what turns an apology into a credible one. Skip it and it reads as hollow.
• Don’t over-apologize in the body — one clean “I’m sorry” lands harder than five.

13. Partial apology (we see your point, here’s our side)

When to use: The customer has a legitimate complaint, but the situation is partly outside your control (a shipping carrier delay, a documented policy they missed, a force majeure).

Subject: Re: {original_subject}

Hi {first_name},

I hear you — {specific_customer_concern} is a real pain, and I'm sorry you're dealing with it.

Here's what's going on from our side: {honest_context}.

That doesn't make it less frustrating for you, and here's what I can do to help:

- {what_you_can_offer_1}
- {what_you_can_offer_2}

Let me know which of those works, or if there's something else you'd rather we do.

{your_name}

• Lead with empathy before explanation. Reverse the order and it reads as “here’s why you’re wrong.”
• Offering two options gives the customer agency — it’s a small touch, but it de-escalates.

Refund, return & billing templates

Money-related emails have one job: remove ambiguity. Either the refund is happening or it isn’t. Either the return is approved or it isn’t. Vague language here is what turns a simple request into a chargeback.

14. Refund approved

When to use: You’ve approved a refund and want to confirm the amount, method, and timing in writing.

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

Hi {first_name},

Good news — your refund is approved.

- Amount: {refund_amount}
- Back to: {payment_method}
- Timing: {refund_eta} (standard for {payment_method})

You'll see it hit your statement within that window. If it doesn't show up by {follow_up_date}, just reply to this email and I'll chase it down with our payments team.

Thanks for giving us a chance to fix this,
{your_name}

• Always state the refund window (“5–10 business days”) — it’s the #1 reason customers email again.
• The “fix this” closing line works when the refund came from a problem. For no-fault refunds, swap for a neutral “have a good one.”

15. Refund declined (policy-based, polite)

When to use: The refund request falls outside your policy and you can’t approve it. Lead with the reason, not the no.

Subject: Re: refund request for order #{order_id}

Hi {first_name},

Thanks for writing in. I looked into your request and unfortunately I'm not able to approve a refund on this one — {specific_policy_reason}.

I know that's not the answer you were hoping for. Here's what I can do:

- {alternative_offer_1} (e.g., a replacement, store credit, or a partial adjustment)
- {alternative_offer_2}

If either of those helps, let me know and I'll get it set up today.

{your_name}

• Be concrete about the policy reason. “Per our 30-day return window” beats “per our policies.”
• Always offer an alternative when the no is policy-based. Even a small goodwill gesture cuts chargeback risk in half.

16. Return / exchange offered

When to use: The product was wrong, damaged, or just not what the customer expected and you’re offering a replacement or exchange.

Subject: Let's get you a replacement — order #{order_id}

Hi {first_name},

Sorry about the trouble with {item_name}. Let's get you sorted.

Here are your options:

1. Replacement: we send you a new {item_name} (ships today, arrives by {new_eta})
2. Exchange: swap for a different {product_category} — pick anything from {category_link}
3. Full refund: {refund_amount} back to {payment_method}

Reply with 1, 2, or 3, and I'll take care of the rest. No need to ship the original back — it's yours to keep.

{your_name}

• “Keep the original” only works for low-value items. For anything over $50, include return-label instructions instead.
• Numbering the options and asking for “1, 2, or 3” gets faster replies than an open-ended “what would you prefer?”

17. Billing question / invoice clarification

When to use: A customer is confused by a charge, invoice line item, or prorated amount and asks you to explain.

Subject: Here's the breakdown on invoice #{invoice_id}

Hi {first_name},

Good question — let me break down {charge_or_line_item} for you.

- What it is: {plain_english_explanation}
- Amount: {amount}
- Covers: {date_range}
- Why now: {billing_trigger}

If anything there looks off, or you'd like me to adjust it, reply and I'll take care of it. I can also send you a CSV of the last {N} invoices if that helps for your records.

{your_name}

• Plain-English explanations beat accounting-speak. “Charges for the 12 days you used us after your last renewal” beats “prorated MRR adjustment.”
• Offering the CSV preempts the next email from them.

Technical support templates

Technical issues need a different shape: facts up front, no fluff, but still human. These three cover the most common tech-support moments: needing more info to diagnose, confirming a bug with a workaround, and posting an incident update.

18. Asking for more info (logs, screenshots, steps)

When to use: The customer reported a bug but didn’t give you enough to reproduce it. Ask for exactly what you need, nothing more.

Subject: Re: {bug_summary} — need a couple more details

Hi {first_name},

Thanks for flagging this. I want to reproduce {bug_summary} on my end so I can figure out what's going on — to do that, could you send me:

1. The exact steps you took right before it broke
2. A screenshot of the error (or the URL you were on)
3. What browser / device you're using

Once I've got those, I can usually track it down in under an hour.

{your_name}

• Keep the list to three items max. Every extra ask drops reply rates noticeably.
• Telling them the turnaround (“under an hour”) is what gets them to actually send the info instead of giving up.

19. Known bug with workaround + ETA

When to use: The customer hit a bug you already know about. Give them a workaround now and a timeline for the real fix.

Subject: You hit a known issue — here's a workaround

Hi {first_name},

You've run into something we already know about. Short version: {one_sentence_bug_description}.

Workaround (takes about {time_estimate}):

1. {workaround_step_1}
2. {workaround_step_2}
3. {workaround_step_3}

Real fix: our engineering team has this on the roadmap and plans to ship it by {fix_eta}. I'll email you personally the moment the fix is live.

Sorry for the detour,
{your_name}

• If you don’t have a firm fix ETA, say so: “no firm date yet — I’ll update you as soon as one is locked in” beats a fake timeline.
• Promising to email when the fix ships requires a tracking mechanism (tag the ticket, set a reminder). Don’t promise if you can’t follow through.

20. Outage / incident update

When to use: Your product is down (fully or partially) and a customer has written in. Stick to facts, timestamps, and next update time.

Subject: Incident update — {product_name} degraded/down

Hi {first_name},

Yes, you're seeing it too — we're currently experiencing {incident_summary}. Timeline so far:

- {timestamp_1}: issue first reported internally
- {timestamp_2}: root cause identified as {cause_summary}
- {timestamp_3}: fix deployed / in progress

Current status: {current_status}. Estimated full recovery: {recovery_eta}.

I'll send the next update by {next_update_time} regardless of whether the fix has landed. You can also track this on our status page: {status_page_url}.

Sorry for the disruption,
{your_name}

• Commit to a “next update” time even if nothing has changed by then — silence during an outage is what breaks trust, not the outage itself.
• If you don’t have a status page, drop that line. Don’t link to a placeholder.

Escalation, transfer & policy templates

Handoffs and policy declines are where customers most often feel passed around. These three templates make the transition feel deliberate — like they’re being routed to the right person, not bounced around until someone else deals with them.

21. Handoff to specialist or manager

When to use: You’ve realized a different teammate is better equipped to handle the issue — say so, introduce them, and stay on the thread until they pick it up.

Subject: Re: {original_subject}

Hi {first_name},

Good news — I'm looping in {colleague_name}, who handles {their_specialty}. They'll be able to get you a better answer on this than I can.

{colleague_name}: quick context — {first_name} is dealing with {issue_summary}. Full thread below. I've briefed you so you don't need to re-ask for any of the details {first_name} has already shared.

{first_name}, you're in good hands. I'll stay cc'd in case anything comes up.

{your_name}

• Briefing your colleague in-thread shows the customer you’ve actually handed over context, not just forwarded the email.
• “I’ve briefed you so you don’t need to re-ask” is the phrase that cuts the most friction — it’s what customers most fear about handoffs.

22. New point-of-contact introduction

When to use: An account manager or CS lead is changing hands — a teammate leaving, a territory change, or a promotion. Send from the new contact.

Subject: Quick intro — I'm your new point of contact at {company_name}

Hi {first_name},

I'm {your_name}, and I'm taking over as your main contact at {company_name}. {previous_contact_name} is {reason_for_transition} — they've walked me through your account, so nothing should fall through the cracks.

A few things I already know about how you use {product_name}:

- {relevant_context_1}
- {relevant_context_2}

My email is always open — reply here any time. If you'd prefer a 15-minute intro call, grab time here: {calendar_link}.

Talk soon,
{your_name}

• Naming two specific things you know about their account is the single best way to prove the handoff wasn’t cold.
• Don’t bad-mouth or over-explain the previous contact’s departure — “moved to a different team” is plenty.

23. Out-of-policy request (declined with alternatives)

When to use: The customer is asking for something your policy or product doesn’t support. Be direct about the no, but leave them with something to go on.

Subject: Re: {request_summary}

Hi {first_name},

Good question. Unfortunately, {specific_request} isn't something we can do — {honest_reason} (not a fun answer, I know).

That said, here are a few ways other customers have worked around this:

- {workaround_1}
- {workaround_2}
- {workaround_3}

If none of those fit, tell me a bit more about what you're trying to accomplish and I can see if there's a better path — or flag it to our product team as a feature request.

{your_name}

• “Other customers have worked around this” is more credible than a list of features you wish you had.
• Ending with “tell me what you’re trying to accomplish” is how you turn a dead-end “no” into a useful conversation.

Feature request & feedback templates

Two templates cover the overwhelming majority of feature-request replies: one for features that are on the roadmap, one for features that aren’t. The main rule for both: don’t over-promise. A “we’ll look into it” that goes nowhere damages trust more than a clean “this isn’t on our roadmap.”

24. Feature request — on the roadmap

When to use: The customer requested something your product team has already planned. Acknowledge it, give a ballpark timeline if you have one, and commit to letting them know when it ships.

Subject: Re: {feature_request_summary}

Hi {first_name},

Great suggestion — and good news, {feature_name} is already on our roadmap.

Current plan: {ballpark_timeline} (quarters are easier to hold to than months, so take that as a range, not a promise).

I've added you to the list of customers to notify the moment it's live. You'll hear from me directly — no marketing email.

Thanks for the nudge,
{your_name}

• Only promise to notify if you have a real mechanism (a tag, a CRM list, a reminder). Broken “we’ll let you know” promises are a top churn trigger.
• A quarter is honest and low-risk. Never give a month unless engineering has committed.

25. Feature request — not on the roadmap

When to use: The customer is asking for something you don’t plan to build. Be honest — a polite “no for now” beats a vague “we’ll consider it.”

Subject: Re: {feature_request_summary}

Hi {first_name},

Thanks for sending this in — I want to be straight with you: {feature_name} isn't on our roadmap right now.

The reason: {honest_product_reasoning}. That may change as the product evolves, but I don't want to tell you "soon" if I don't mean it.

What I can do is log your request with our product team (I've done that — it's tagged to your account). If enough customers ask for the same thing, the plan changes.

If you're open to sharing, what's the underlying problem you're trying to solve? Sometimes there's a different angle we can help with.

{your_name}

• The “what’s the underlying problem” question is the single highest-leverage line in this template — it’s where roadmap requests turn into product insights.
• Only claim you tagged it to their account if your team actually does this.

Renewal, price-change & cancellation templates

Money emails have outsized impact on retention. A clumsy renewal reminder can tank an otherwise-happy account; a graceful cancellation save can double your save rate. These three cover the most common scenarios.

26. Renewal reminder

When to use: 30 days before a plan renews, especially for annual contracts or larger accounts.

Subject: Your {product_name} plan renews on {renewal_date}

Hi {first_name},

Heads up — your {plan_name} plan will renew on {renewal_date} at {renewal_amount}.

Nothing's required from you. Your current payment method ({payment_method_hint}) will be charged automatically, and you'll get a receipt.

If anything's changed on your end — team size, plan needs, billing address — just reply and I'll sort it out before the renewal hits.

{your_name}

• Soft-pedal the auto-renewal: “nothing’s required from you” gets better retention than a cancel-now link up front.
• Reminding them their details ({payment_method_hint}) are still valid cuts failed-payment churn.

27. Price-increase notification

When to use: You’re raising prices. Send 60+ days before it hits. Explain the why briefly, then get to what it means for them.

Subject: A small change to your {product_name} pricing

Hi {first_name},

I want to give you plenty of notice: starting {effective_date}, our pricing is going up. For your plan, this means {old_price} becomes {new_price} — a {percentage} change.

The short "why": {honest_reason} (new features, infrastructure costs, expanded team — pick the real one).

What this means for you:
- Your current rate is locked in until {effective_date}
- If you renew or upgrade before then, you lock in the current price for another {duration}
- Everything else about your plan stays the same

If you want to chat before the change hits, reply here or grab time at {calendar_link}.

{your_name}

• Stating the percentage and the absolute amount both (“$12 → $14, +17%”) beats hiding either one.
• Offering a lock-in option is the most effective retention lever for price increases.

28. Cancellation save

When to use: A customer has just asked to cancel. You have one shot to understand why — without begging them to stay.

Subject: Re: canceling {product_name}

Hi {first_name},

Got it — I'll cancel your account as soon as you confirm. Before I do, would you mind sharing the main reason you're leaving? One line is fine.

I'm not going to try to talk you out of it, but the honest feedback helps us fix whatever isn't working.

If there's something specific we could do to keep your account (a different plan, a pause, a feature you need), say the word. Otherwise just reply "cancel" and I'll process it today.

Thanks for giving us a shot,
{your_name}

• “I’m not going to try to talk you out of it” dramatically increases the chance they’ll share the real reason.
• Always offer a pause option if you have one — it’s the highest-converting save lever for temporary churn.

Review & thank-you templates

Closing a conversation on a high note is the single best thing you can do for retention. A thank-you email takes 30 seconds; a review request after a resolved issue doubles as a reputation engine. For the other side of the coin — when you need to respond to a negative review — see how to respond to negative reviews.

29. Review request (post-resolution)

When to use: You’ve just resolved an issue well and the customer is happy. Send within 24 hours, while the good feeling is fresh.

Subject: Quick favor — would you share your experience?

Hi {first_name},

Glad we got {issue_summary} sorted. If you've got 60 seconds, it would mean a lot if you'd leave a quick review at {review_link}.

No pressure either way — if the experience wasn't 5 stars, tell me what we could have done better and I'll take it to the team.

Thanks for being a customer,
{your_name}

• “If the experience wasn’t 5 stars” is a filter — customers who had a mixed experience reply to you instead of leaving a 3-star review.
• Only send this after a clearly resolved issue — not after a declined refund or a partial apology.

30. Thank-you for feedback

When to use: A customer took the time to write detailed feedback — positive, negative, or mixed. A quick acknowledgment closes the loop and keeps them engaged.

Subject: Thanks for the note — really useful

Hi {first_name},

Just wanted to say: thank you for the detailed feedback. The part about {specific_feedback_point} especially — I've shared it with our {relevant_team} team and it's already shaping how we think about {relevant_area}.

I'll let you know if anything tangible comes from it. Either way, I appreciate you taking the time.

{your_name}

• Quoting back one specific detail from their feedback proves it was read — generic “thanks for the feedback” replies do the opposite.
• Don’t commit to action unless you mean it. “I’ll let you know if anything tangible comes from it” is an honest hedge.

Making templates feel human (not robotic)

The number one complaint about email templates isn’t that they exist — it’s that customers can feel them. The fix is a rule we call the three-variable minimum: before you send, customize at least three things beyond the greeting. Usually that’s (1) a detail from their specific issue, (2) a phrase that matches their tone, and (3) one contextual line that proves you read what they wrote.

A few habits that help:

• Match the customer’s tone. If they wrote three short sentences, don’t reply with five paragraphs. If they wrote formally (“Dear Support,”), don’t reply with “hey!”
• Ditch the passive voice. “Your refund has been processed” reads as corporate. “I processed your refund” reads as human.
• Use the customer’s actual words. If they called it a “bug,” don’t call it a “known issue.” If they called it a “charge,” don’t call it a “billable event.”
• Drop one thing the template includes that doesn’t apply. Ruthless deletion is what separates a template from a form letter.

If you ever read a reply back and think “that sounds like a template” — it does, and the customer will spot it too. Send it through one more editing pass.

Turning templates into Gmail canned responses

Gmail’s built-in “templates” feature (formerly canned responses) lets you save any of the templates above and insert them with two clicks. Turn it on in Gmail Settings → Advanced → Templates, then compose a new email with the template body, click the three-dot menu, and choose Templates → Save draft as template. Full walkthrough with screenshots in the guide to Gmail canned responses.

The catch: Gmail templates are tied to a single Gmail account. If your whole team needs to share and reuse the same templates, you need a shared-template layer on top of Gmail — otherwise every teammate ends up maintaining their own copy, and the library drifts.

This is where Keeping comes in. Keeping turns your shared inbox (support@, help@, hello@) into a proper help desk inside Gmail — so your team can share these templates, assign incoming emails to the right person, track response times, and never step on each other’s replies. No context-switching to a separate tool, no training, no re-teaching anyone how email works. If you’re managing a shared inbox and your team is already using Gmail, you can be up and running in under 10 minutes — and every one of the 30 templates above works out of the box. Try Keeping free for 14 days — no credit card needed.

For a broader look at the tooling landscape, the guides to customer service email management software and customer service tools compare the options side by side.

Frequently asked questions about customer service email templates

If you’d rather skip the copy-pasting and let your whole team share these inside Gmail with assignments, statuses, and reply tracking, give Keeping a try — 14 days free, no credit card.