Customer Support Email Templates

15 support email templates for small businesses. Copy-paste right from the page. Free, no signup.

Templates save time on the 80% of tickets that repeat. Order confirmations. Shipping updates. Refund windows. These are the ones where a well-written template — used as a starting point, not a crutch — lets you reply in under a minute without every email feeling like homework.

These 15 templates are the ones we see small teams reach for most often. Copy them from the page, paste into Gmail or your help desk as saved replies, and swap the {{placeholders}} for the real details.

When to use templates (and when not to)

Good fits: order confirmations, shipping delay heads-ups, refund approvals, subscription cancellation confirmations, post-resolution check-ins. Anything transactional.

Write from scratch instead: angry customers with specific complaints, escalations that mention legal or reputational threats, long-time customers with a new situation, anything emotionally loaded. A template reads cold in those moments.

Order acknowledgements and fulfillment

Order confirmation

Use when: a customer has just completed checkout

Hi {{customer_first_name}},

Thanks for your order. Here is what we are sending you:

Order #{{order_number}}
{{line_items}}

We will email you again the moment your order ships, with a tracking link. If anything looks wrong, reply to this email — it goes straight to a human.

{{your_name}}

Why it works: Opens with a thank-you, shows the order, promises the next touchpoint, and offers a real reply path.

Shipping delay notification

Use when: an order is running behind the promised ship date

Hi {{customer_first_name}},

Quick update on order #{{order_number}}: it is going to ship {{new_eta}} instead of the original date. The reason is {{brief_cause}}.

Tracking will go out the moment it leaves the warehouse. If the new date does not work for you, reply to this email and I will sort out a refund or an alternative.

Sorry for the bump,
{{your_name}}

Why it works: Specific new date, one-line cause, clear opt-out — no "we apologize for any inconvenience".

Out-of-stock apology with alternative

Use when: an item a customer ordered is no longer available

Hi {{customer_first_name}},

Bad news on order #{{order_number}}: the {{product_name}} you ordered is out of stock and will not be back in time to ship what you paid for.

Two options:
1. Swap for {{alternative_product}} — similar price, in stock, would ship today
2. Full refund to your original payment method within 3 business days

Just reply with 1 or 2 and I will handle it.

{{your_name}}

Why it works: Leads with the bad news, presents two concrete options, makes the reply one character.

Problems and escalations

Product arrived damaged — replacement

Use when: a customer reports a damaged item on arrival

Hi {{customer_first_name}},

I am sorry — that is not how it was supposed to arrive. I am sending a replacement {{product_name}} today on expedited shipping at no charge to you. Tracking will follow once it is picked up.

You do not need to return the damaged one. Feel free to toss it, or keep it for parts.

If the replacement shows up in the same condition, reply to this email and I will make it right a different way.

{{your_name}}

Why it works: Takes responsibility without over-apologizing, removes the return-shipping friction, leaves a door open.

Refund request — approved

Use when: a customer asks for a refund within the return window

Hi {{customer_first_name}},

Refund processed for order #{{order_number}} — {{amount}} back to your original payment method. It should land in 3–5 business days depending on your bank.

If it is not there by then, reply to this email with a screenshot of your statement and I will chase it down with our processor.

{{your_name}}

Why it works: States the outcome in sentence one, sets expectations on timing, offers a next step if it does not land.

Refund request — outside window, alternative offered

Use when: a customer asks for a refund past the policy window

Hi {{customer_first_name}},

I cannot issue a cash refund on order #{{order_number}} — it is past our {{window}}-day return window (policy here: {{policy_url}}).

What I can do: {{amount}} in store credit, good for any future order, no expiry. If that works for you, reply and I will add it to your account today.

{{your_name}}

Why it works: Clear no, specific why, real alternative. No apologizing for the policy.

Angry customer — first de-escalation reply

Use when: a customer sends an angry or all-caps email and you need to slow things down

Hi {{customer_first_name}},

I hear you — this is not what you paid for and I want to get it fixed today.

To do that I need one thing: {{specific_info_needed}}. Once I have that, I will come back within the hour with a concrete plan (refund, replacement, or something better).

{{your_name}}

Why it works: Acknowledges the frustration without groveling, asks for one specific input, commits to a tight timeline.

Wrong item shipped — apology and next steps

Use when: the customer received the wrong product

Hi {{customer_first_name}},

That is on us — we shipped you {{wrong_item}} instead of the {{correct_item}} you ordered. Here is what is happening now:

1. The correct {{correct_item}} ships today on expedited shipping
2. A prepaid return label for {{wrong_item}} is on the way to your inbox — drop it in any mailbox
3. No charge for either

Tracking for the replacement will follow shortly.

{{your_name}}

Why it works: Owns the error, numbered steps so the customer knows exactly what happens next.

Billing and account

Duplicate charge — investigating

Use when: a customer reports they were charged twice

Hi {{customer_first_name}},

I see both charges on my end. I have refunded the duplicate {{amount}} to your original payment method — it should appear in 3–5 business days.

If you see anything else off on your statement, reply with the details and I will look at it today.

{{your_name}}

Why it works: Confirms the customer is seeing what they are seeing, states the action taken, sets a return-door for more.

Subscription cancellation confirmation

Use when: a customer cancels a recurring subscription

Hi {{customer_first_name}},

Confirmed — your {{plan_name}} subscription is cancelled. You will not be charged again. You can keep using the service until {{end_of_period}}, then it will switch off.

If you change your mind before then, reply to this email and I will turn it back on with no gap.

Thanks for giving it a try,
{{your_name}}

Why it works: No guilt trip, no "are you sure", just clear confirmation and a low-friction reactivation path.

Proactive and relationship

First-response acknowledgement

Use when: a real reply will take longer than 2 hours but the customer should not wonder if you got the message

Hi {{customer_first_name}},

Got your message. I am looking into this now — expect a real reply from me within {{timeframe}}.

If anything new comes up in the meantime, feel free to reply on this thread.

{{your_name}}

Why it works: Proves a human saw the message, commits to a specific timeframe, keeps the thread open.

Post-resolution follow-up

Use when: a ticket was closed 24–48 hours ago and you want to confirm it actually worked

Hi {{customer_first_name}},

Checking in on the {{issue}} from earlier this week — did the {{resolution}} actually sort it out for you?

If not, reply and I will pick it back up. If yes, no reply needed.

{{your_name}}

Why it works: Makes the reply optional, which increases reply rate for cases where something is still broken.

Review or feedback request after positive resolution

Use when: a customer just had a good outcome and is in a good moment to share it

Hi {{customer_first_name}},

Glad we got {{issue}} sorted. If you have 30 seconds, would you mind leaving us a quick review here: {{review_link}}

It genuinely helps people find us. If not, no worries — appreciate you either way.

{{your_name}}

Why it works: Asks only after a win, gives a time estimate, makes the no-answer answer easy.

Edge cases

The polite catch-up

Use when: a customer emails "I never heard back" and you find their original message sitting in a queue

Hi {{customer_first_name}},

You are right — your {{date}} message did not get a reply, and that is on us. Sorry about that.

On the original question: {{answer}}.

If that covers it, nothing else needed. If not, reply here and I will come back within the hour.

{{your_name}}

Why it works: Skips the defensive explanation, gives the answer they were originally waiting for, offers a fast next step.

Saying no to a feature request

Use when: a customer asks for something you will not build

Hi {{customer_first_name}},

Thanks for writing in about {{feature}}. Being honest with you: it is not something we are planning to build.

The reason is {{brief_reason}}. If that changes, I will email you directly.

In the meantime, a couple of tools that do this well: {{alternative_1}}, {{alternative_2}}.

{{your_name}}

Why it works: Direct no, one-line why, and a useful alternative — customers remember honesty, not yeses that never ship.

How to write your own support emails

  • Lead with the outcome, not the apology — customers want the fix, not the sorry
  • Skip "we apologize for the inconvenience" unless something is actually late
  • Use the customer's first name once, not three times
  • Keep it under 150 words — most support emails can be
  • End with a specific next step (reply here, wait for tracking, etc.)
  • Sign with a real human name, not "the team"

Templates are a starting point

Paste any of these verbatim and they will land fine once or twice. Paste them 50 times a week and the thread starts reading like a form letter. A good pattern: keep the template structure (opener, key facts, specific next step, sign-off) but rewrite one sentence each time in language that fits what the customer actually said.

When your inbox outgrows canned replies

Templates in Gmail drafts start to crack around 50+ tickets a day. You lose track of who replied already, who is waiting, and which version of which template was sent. That is when a help desk with proper saved replies, customer history, and ticket status earns its keep.

Auxx.ai is an all-in-one support inbox and CRM for small businesses — saved replies, customer timelines, and ticket tracking in one place. See how Auxx.ai works →

Frequently asked questions

Related free tools

Sending the same reply on repeat?

Auxx.ai unifies your support inbox, canned replies, and customer history in one place.

See how Auxx.ai works