25 Customer Support Email Templates You Can Copy Today

Good support email replies share three traits: they're fast, specific, and human. These 25 templates cover the most common scenarios your team will encounter. Adapt the voice to match your brand — don't send them verbatim.

Onboarding and getting started

Hi [Name],

Welcome — glad you're here. Your account is ready at [link].

Three things worth doing in the first 5 minutes: [action 1], [action 2], [action 3].

If you hit any questions, reply here — this goes to a real inbox.

[Your name]

Hi [Name],

Saw you logged in for the first time — how did it go?

Most people spend their first session on [common area]. If anything felt unclear, let me know and I'll walk you through it.

[Your name]

Hi [Name],

You signed up 3 days ago but haven't had a chance to explore yet — totally normal.

When you're ready, [specific first step] takes about 10 minutes and is usually the most useful starting point.

Happy to jump on a quick call if that would help: [calendar link].

[Your name]

Billing and pricing questions

4. Explaining a charge

Hi [Name],

The charge of [amount] on [date] is for your [plan name] subscription, which renews on [date].

Your full billing history is at [link]. If anything looks off, let me know and I'll take a closer look.

[Your name]

5. Upgrade inquiry

Hi [Name],

The [higher plan] adds [specific feature 1] and [specific feature 2] — the main reasons teams upgrade.

At your current usage, [specific benefit that applies to them]. Want me to switch your account? It takes about 30 seconds and you're prorated to the day.

[Your name]

6. Cancellation request — retention attempt

Hi [Name],

Got your cancellation request. Before I process it, can I ask what prompted this?

If it's pricing, I can look at options. If it's a feature gap, I'd like to know what we're missing. If the timing just isn't right, we can pause the account instead.

If you want to cancel, that's completely fine too — just reply and I'll handle it today.

[Your name]

7. Processing a cancellation

Hi [Name],

Done — your account is cancelled and you won't be charged again. You have access through [end date].

Your data stays in the system for 30 days if you change your mind. After that it's gone.

Thanks for trying [product]. If anything changes, you're welcome back anytime.

[Your name]

Refund requests

8. Refund approved

Hi [Name],

Refund approved — [amount] back to your [card/PayPal] within 5–7 business days.

If you don't see it after 7 days, let me know and I'll chase it with our payment processor.

[Your name]

9. Refund outside policy — declined but empathetically

Hi [Name],

I looked into this. Our refund window is [X days], and your purchase was [X days ago] — just outside it.

I can't process a refund for this charge. What I can do is [alternative: extended trial, credit, upgrade at discount].

Does any of that work for you?

[Your name]

10. Refund declined — final answer

Hi [Name],

I understand this is frustrating. After reviewing the account, I'm not able to process a refund — [brief, specific reason].

I know that's not the answer you were hoping for. If there's anything else I can help with, I'm here.

[Your name]

Bug reports and technical issues

11. Acknowledging a bug report

Hi [Name],

Thanks for the detailed report — this is helpful.

I've reproduced the issue and filed it with engineering as [priority]. I can't give you a fix timeline, but I'll follow up when it's resolved.

Workaround in the meantime: [workaround if any].

[Your name]

12. Bug confirmed but no timeline

Hi [Name],

This is a known issue. Our engineering team is aware and working on it, but I don't have a specific timeline.

I'll email you directly when the fix ships. Sorry for the inconvenience in the meantime.

[Your name]

13. Asking for more info to reproduce

Hi [Name],

I want to reproduce this on my end to make sure I understand the issue. A few questions:

What browser and version were you using?

Did this happen on a specific page or in a specific workflow?

Do you see any error message, or does it just silently fail?

Screenshot or screen recording (Loom works great) would speed this up a lot.

[Your name]

14. Bug fixed — notifying affected user

Hi [Name],

Quick note: the issue you reported on [date] is fixed and deployed as of [today/date].

[One sentence on what changed or what to expect.]

Let me know if you're still seeing it.

[Your name]

Delays and service incidents

15. Proactive incident notification

Hi [Name],

We're experiencing an issue with [feature/service] affecting [scope]. We're actively working on it.

Current status: [investigating / identified / deploying fix]
Started: [time]
Impact: [what's affected]

We'll update you every [30 min / hour]. More details at [status page link].

[Your name]

16. Incident resolved

Hi [Name],

The issue with [feature] is resolved as of [time]. All systems are running normally.

Root cause: [brief explanation]. We've put [measure] in place to prevent a recurrence.

We're sorry for the disruption. If you experienced data loss or other downstream issues, please let us know.

[Your name]

17. Response to angry customer during an incident

Hi [Name],

I understand — this is unacceptable and I'm sorry.

The issue started at [time] and we've been working to fix it since. Current status: [status]. ETA: [time if known, otherwise "as soon as possible"].

We'll give you [credit / extension / something specific] for the downtime once we're back to normal.

[Your name]

Feature requests

18. Logging a feature request

Hi [Name],

Thanks for this — I've logged it and passed it to the product team.

I can't promise a timeline (feature prioritization is a process), but this is exactly the kind of input that shapes the roadmap.

I'll follow up if and when this ships.

[Your name]

19. Feature already on the roadmap

Hi [Name],

This is actually on our roadmap for [quarter / "this year"]. I can't give you an exact date, but it's coming.

I'll add you to the list to get an early notification when it's available.

[Your name]

20. Declining a feature request

Hi [Name],

I appreciate you taking the time to suggest this. After consideration, this isn't something we're planning to build — it's outside the direction we're taking [product area].

A workaround that some users find helpful: [workaround].

I'm sorry I don't have better news on this one.

[Your name]

Account and access issues

21. Password reset help

Hi [Name],

To reset your password: [link to reset page] — the reset link expires after 24 hours.

If you don't receive the email within a few minutes, check your spam folder or let me know the email address you signed up with.

[Your name]

22. Locked out of account

Hi [Name],

I've unlocked your account — you should be able to log in now at [link].

If you're still having issues, try clearing your browser cache or using an incognito window.

[Your name]

23. Two accounts / duplicate account issue

Hi [Name],

I can see two accounts associated with your details — [email 1] and [email 2].

I can merge these so your history and settings carry over to one account. Which email do you want to keep as the primary?

[Your name]

Closing conversations

24. Closing an unresponsive ticket

Hi [Name],

I'm going to close this ticket since I haven't heard back in [X days]. If the issue is resolved, great.

If you're still having trouble, just reply here and I'll reopen it.

[Your name]

25. CSAT follow-up after resolution

Hi [Name],

Glad we got that sorted. One quick question: how would you rate the support experience on a scale of 1–5?

[rating link or one-click CSAT]

Takes 5 seconds and genuinely helps us improve.

[Your name]

How to use these templates

These templates work best when they're saved in your shared inbox tool as canned responses — accessible with a keyboard shortcut or a / command. The goal isn't to remove the human from support, it's to remove the time-tax on repetitive structure so agents can spend that time on personalization.

Smailor includes saved replies on all plans, with AI-assisted drafts that can suggest the right template based on incoming message content.

Start building your template library — free, no card, your domain.