When to use this email
You need a reliable starting point for a typical support reply
The issue doesn't fit a specialized template and you want a solid base
You're training new agents and want a consistent reply structure
Tips for making it yours
Acknowledge the specific problem before jumping to the fix
Give one clear next step rather than a wall of options
Tell them exactly what you need if you have to follow up
Close by inviting more questions so they don't hesitate to reply
Other versions of this email
The same situation rarely arrives in the same shape twice. These are the two variations worth having ready.
When you don't have the answer yet
You need to acknowledge quickly but genuinely cannot resolve it in this reply.
Subject
Re: [their question] — looking into it
Hi [first name], Thanks for writing in. I've read through what you've sent and I want to give you a proper answer rather than a fast guess, so I'm checking [the specific thing] with [team/system]. I'll come back to you by [specific date/time] either way — including if I still don't have a full answer by then. If anything changes on your end in the meantime, just reply here. Best, [Your name]
When the answer is no
The request is reasonable but you cannot do it. Say so directly rather than burying it.
Subject
Re: [their request]
Hi [first name], Thanks for asking — and I'm sorry, this isn't something we can do. [One plain sentence on why, without hiding behind policy language.] What I can offer is [the nearest genuine alternative], which gets you [what it actually achieves]. It isn't the same thing, and I won't pretend it is. If that doesn't work for you, tell me what you're trying to achieve overall and I'll see if there's another route. Best, [Your name]
What not to say
- “As per our policy…”
- Signals that the rule matters more than the person. State the outcome plainly and the reason in your own words.
- “I'm sorry you feel that way.”
- A non-apology that reframes a real problem as the customer's emotional reaction. Apologise for the thing, or do not apologise.
- “Have you tried turning it off and on again?”
- Fine as a genuine diagnostic step, damaging as an opener. Show you have read what they already tried before suggesting basics.
- “This is a known issue.”
- On its own it tells the customer their problem is old news and nobody fixed it. Pair it with what is happening about it and when.
If they don't reply
Send two or three days after a reply that asked the customer a question and got no response, before closing anything.
Subject
Re: [their question] — still there?
Hi [first name], Just checking back on this one. I asked about [the specific detail] and haven't heard — no problem either way. If it sorted itself out, let me know and I'll close it off. If not, [the detail] is the one thing I need to move forward. Best, [Your name]
Questions about support emails
- What should a support email include?
- Four things: confirmation you understood the problem in your own words, the answer or the current status, what happens next and when, and how to reply. Restating the problem matters more than most teams think — it is the part that tells the customer a person read this rather than a macro fired.
- How fast should I reply to a support email?
- First response speed correlates with satisfaction more strongly than almost any other variable, and people forgive an incomplete answer far more readily than a slow one. A same-day acknowledgement that names when a full answer is coming beats a perfect reply two days later.
- Should I use templates for support emails?
- Yes, as a starting structure — never as the finished reply. A template saves the thinking about shape so you can spend it on the specifics. The moment a customer can tell which parts were pre-written, the template has cost you more than it saved.
