11 Customer Service Email Templates You Can Copy-Paste in 2026

Most support teams don't struggle with knowing what to say — they struggle with saying it consistently, at 11pm, on the fortieth ticket of the day, without sounding like a robot or losing their patience. A good template solves that: it locks in the right tone and structure once, so every reply after that is faster and more consistent, whether it's written by your newest hire or by you at midnight.

Below are eleven situations every customer-facing team runs into constantly, with a ready-to-use template for each. None of these are meant to be sent word-for-word forever — treat the bracketed placeholders as the parts you personalize, and treat the surrounding language as a starting point you'll gradually make your own.

First Contact: Acknowledge Fast, Then Follow Up

The single biggest driver of customer satisfaction isn't resolution speed — it's response speed. A fast "we got your message" buys you time even when the real answer takes longer.

First response / acknowledgement

When to use it: The moment a new inquiry lands, before you've had time to investigate or solve anything.

Adaptation tip: Swap in a realistic timeframe — an honest "by tomorrow" beats an optimistic "in an hour" you can't keep.

Subject: We got your message, [Customer Name]

Hi [Customer Name],

Thanks for reaching out — this is just a quick note to let you know your message has landed with our team and hasn't fallen through the cracks.

I'm looking into [brief restatement of their issue] now and will follow up with a full answer by [specific timeframe, e.g. "end of day tomorrow"]. If anything changes on your end in the meantime, just reply to this email and it'll come straight to us.

Talk soon,
[Your Name]
[Business Name]

"We're looking into it" holding reply

When to use it: You've already sent the first acknowledgement, but the issue needs more time than you originally promised — a vendor callback, an internal check, a shipping carrier trace.

Adaptation tip: Always name the next concrete step, not just "we're working on it" — vague holding replies erode trust faster than silence does.

Subject: Update on your request — still working on it

Hi [Customer Name],

Wanted to give you a quick status update rather than let this go quiet. We haven't forgotten about [brief issue] — I've [specific action taken, e.g. "escalated this to our shipping partner" / "checked with our team"] and I'm waiting to hear back.

I expect to have a real answer for you by [new specific timeframe]. Thanks for your patience — I'll be back in touch as soon as I know more, even if it's just another update.

Best,
[Your Name]
[Business Name]

Refund Requests: Approved and Declined

Refund emails set the tone for whether a customer leaves neutral or leaves as a repeat buyer. The wording matters almost as much as the decision itself.

Refund request — approved

When to use it: The request is valid under your policy and you've decided to issue the refund.

Adaptation tip: State the exact amount and the exact timeline for it to appear — vague refund emails generate a second round of "so... did this actually happen?" messages.

Subject: Your refund is on its way

Hi [Customer Name],

Good news — your refund for [order number / product name] has been approved and processed. You should see [amount] back on [original payment method] within [typical timeframe, e.g. "3-5 business days"], depending on your bank.

Sorry this didn't work out as expected. If there's anything else we can help fix, or if you'd like a recommendation for something that better fits what you needed, just let me know.

Thanks for giving us the chance to make it right,
[Your Name]
[Business Name]

Refund request — declined (politely)

When to use it: The request falls outside your stated policy (e.g., past the return window, item used, non-refundable service already delivered).

Adaptation tip: Explain the reason, point to the policy plainly, and always offer an alternative — a decline with zero alternative reads as a brush-off, even when the reasoning is fair.

Subject: About your refund request

Hi [Customer Name],

Thanks for reaching out, and I'm sorry for the frustration here. I looked into your request for [order/product], and unfortunately it falls outside our refund window of [X days] / doesn't qualify because [specific reason].

I know that's not the answer you were hoping for. What I can offer instead is [alternative — store credit, exchange, partial credit, extended support], if that would help. Let me know if you'd like to go that route, or if you have questions about the policy — happy to walk through it.

[Your Name]
[Business Name]

Late or Delayed Orders

Delays are inevitable; silence about delays is what actually costs you the customer.

When to use it: As soon as you know an order will miss its promised delivery window — don't wait for the customer to ask first if you can help it.

Adaptation tip: Lead with the new date, not an apology paragraph — customers scanning their inbox want the answer in the first line.

Subject: Update on your order [order number] — new delivery estimate

Hi [Customer Name],

Your order [order number] is running behind schedule, and I wanted to flag it before you had to ask. New estimated delivery: [new date].

What happened: [brief, honest reason — carrier delay, backorder, etc.]. I know this isn't the update you wanted, so if the new timeline doesn't work for you, I'm happy to [offer: cancel and refund / expedite the next batch / apply a credit].

You can track the latest status here: [tracking link]. Sorry for the wait — I'll flag you if anything changes again.

[Your Name]
[Business Name]

When a Customer Is Upset or Complaining

When to use it: The customer is frustrated, has already complained once, or the tone of their message signals real annoyance — not just a routine question.

Adaptation tip: Answer the emotion in the first sentence before you answer the facts; jumping straight to policy details reads as dismissive even when the information is correct.

Subject: I hear you — let's sort this out

Hi [Customer Name],

I read through what happened, and I'd be frustrated too — that's a fair reaction to [restate their specific complaint in your own words, showing you actually understood it].

Here's what I can do: [concrete resolution, or concrete next step if you need to investigate further]. I want to get this right for you, so if this doesn't fully address it, tell me directly and I'll keep working the problem with you rather than closing this out early.

I appreciate you giving us the chance to fix it rather than just walking away.

[Your Name]
[Business Name]

When You Don't Have What They're Asking For

When to use it: A customer asks for a feature, product, or service you simply don't offer — now or possibly ever.

Adaptation tip: Don't just say no — say what you do have that gets them closest, or be honest that nothing does; a flat "we don't offer that" without an alternative ends the conversation on a dead note.

Subject: About [feature/item] you asked for

Hi [Customer Name],

Thanks for asking — honest answer: we don't currently offer [feature/item]. Not trying to talk you into something else, just want to be upfront rather than have this come as a surprise later.

The closest thing we do have is [alternative, if one exists], which might cover what you actually need — happy to explain how it compares if useful. If it's a hard requirement on your end, I completely understand, and I'll pass this along as feedback since it's come up before.

[Your Name]
[Business Name]

Owning a Mistake: The Apology Email

When to use it: Something genuinely went wrong on your end — a billing error, a shipping mix-up, a missed promise — and it's your fault, not a policy edge case.

Adaptation tip: Say "I'm sorry" plainly in the first line with no "but" attached — a conditional apology ("sorry, but...") reads as an excuse, not an apology.

Subject: We made a mistake — here's how we're fixing it

Hi [Customer Name],

I'm sorry — we got this wrong. [Plainly state what happened, e.g. "You were charged twice for the same order" / "We shipped the wrong item."] That's on us, not something you should have had to catch.

Here's what we're doing about it: [concrete fix — refund issued, correct item shipped overnight, account corrected], effective [timeframe]. I've also [preventive step, if applicable, e.g. "flagged this with our fulfillment team so it doesn't happen again"].

Thanks for your patience while we sorted this out — and for pointing it out in the first place.

[Your Name]
[Business Name]

Subscription and Account Cancellations

When to use it: A customer requests to cancel a subscription, membership, or recurring service.

Adaptation tip: Confirm the cancellation clearly with the exact effective date before you ask anything else — burying the confirmation under a retention pitch reads as trying to trap them.

Subject: Your cancellation is confirmed

Hi [Customer Name],

This confirms your subscription has been cancelled, effective [date]. You won't be billed again after [last billing date, if applicable], and you'll retain access until [end of current period, if applicable].

No hard feelings, and no need to explain if you'd rather not — but if there's something specific that didn't work for you, I'd genuinely like to hear it; it helps us improve. And if you ever want to come back, your account details will be here.

Thanks for having been a customer,
[Your Name]
[Business Name]

Automated Replies: After-Hours and Bot-to-Human Handoff

These two templates aren't written by a person in the moment — they're the words your system sends on your behalf, so they need to set expectations correctly without sounding fake or evasive.

After-hours / auto-reply

When to use it: As the automatic response outside business hours, so customers know their message landed and roughly when to expect a reply.

Adaptation tip: Give a specific reopening time, not just "we'll get back to you soon" — specificity is what makes an auto-reply feel honest rather than boilerplate.

Subject: We've got your message

Hi there,

Thanks for reaching out to [Business Name]. Our team is currently offline — our hours are [days/hours] — but your message has been received and logged.

We'll follow up as soon as we're back, typically within [timeframe, e.g. "one business day"]. If this is urgent, [alternative contact method, if available].

Talk soon,
[Business Name]

Handing off from AI/bot to a human

When to use it: Your chat widget or bot has done what it can and the question needs a person — either the customer asked for one, or the topic is too sensitive or complex for automated answers.

Adaptation tip: Have the bot summarize what it already knows in the handoff so the customer never has to repeat their question from scratch to the human who picks it up.

Subject: Connecting you with our team

Hi [Customer Name],

I've done what I can to help, but this one's better handled by a person on our team — I don't want to guess at something this important.

Here's what I've noted so far so you don't have to repeat yourself: [brief AI-generated summary of the conversation and issue]. Someone from [Business Name] will follow up by [timeframe], usually [expected response time].

Thanks for your patience,
[Business Name] Support

How AI Can Draft These Replies for You

Templates solve consistency, but they still take a person to pick the right one, fill in the specifics, and hit send — and most small teams don't have a spare hour a day for that. This is where AI-assisted support genuinely earns its keep: a tool that has read your FAQ, your policies, and your past replies can draft a response in the correct tone automatically, instead of a generic support agent guessing.

In practice, that looks like this: a customer message comes in, the AI checks it against your actual content — your refund policy, your shipping timelines, your product catalog — and either answers it directly (for the straightforward cases like "what are your hours" or "where's my order") or drafts a reply grounded in the templates and tone you've already established. The messy, emotional, or high-stakes cases — an angry complaint, an ambiguous refund edge case, anything the AI isn't confident about — get escalated to a human instead of getting a guessed answer. cswithai works this way: it answers from your own content on a self-hosted model rather than routing customer conversations through a third-party AI cloud, summarizes every conversation into your inbox so you're never digging through a dashboard to know what happened, and hands off to a person automatically when a question is outside what it should handle alone. The templates above are a good foundation either way — whether a human is typing them or an AI is drafting them for review, the underlying structure (acknowledge, be specific, offer a next step) doesn't change.

FAQ

How do I make templates not sound robotic? Read the reply out loud before sending it — if it sounds like something you'd never actually say to a person's face, rewrite that line. Keep one or two sentences genuinely personalized to the specific situation (referencing their actual order, their actual complaint) rather than sending the template verbatim; that's usually all it takes to make a templated reply feel human.

Should I use templates for complaints? Yes, but treat the template as a structure, not a script. The apology-email and complaint templates above are built around a sequence — acknowledge the emotion, state a concrete fix, invite follow-up — and that sequence should stay consistent. The specific wording inside it should change every time to match what actually happened.

How many templates does a small team actually need? Fewer than you'd think. Most support volume clusters around five or six recurring situations — order status, refunds, complaints, and a couple of product-specific FAQs. Start with the templates that match your three most common ticket types, then expand only when you notice yourself writing the same reply from scratch a third time.

Should every automated reply disclose that it's automated? For after-hours and bot-handoff replies, yes — customers generally trust a clearly-labeled automated response more than one that pretends to be a person and gets caught. Transparency here builds trust rather than undermining it.

How often should I update these templates? Review them whenever your policies change (a new return window, updated pricing, a new shipping carrier) and again every few months even if nothing obvious changed — customer language and common questions shift over time, and a template that felt natural a year ago can start to sound stiff.