When to use this email
The issue needs higher-tier access or expertise
You're handing the case to a manager or specialist team
The customer needs to know who's now responsible
Tips for making it yours
Name the person or team taking over, not just "a specialist"
Promise a specific update time, not "soon"
Reassure them they won't have to re-explain the issue
Stay on the thread so the handoff feels smooth
Other versions of this email
The same situation rarely arrives in the same shape twice. These are the two variations worth having ready.
Escalating to engineering
The problem is a bug or an outage, and the fix now depends on a team that does not talk to customers directly.
Subject
[issue] is with our engineering team
Hi [first name], I've reproduced what you're seeing, so this isn't something on your end. It's a [bug / configuration issue] and I've raised it with our engineering team as [ticket reference]. I want to be straight with you about timing: engineering work doesn't run to the same clock as support, so I can't promise a fix date yet. What I can promise is an update from me by [date], whether or not there's news. In the meantime, [workaround, or "there isn't a workaround I can offer, and I'm sorry"]. Best, [Your name]
Escalating for the second time
The first escalation did not resolve it and the customer has come back. Acknowledge that directly rather than restarting the process silently.
Subject
Re: [issue] — taking this further
Hi [first name], You shouldn't have had to chase this twice, and I'm sorry you did. I've taken it to [manager / senior team] myself rather than sending it back through the same route. [Name] now owns it directly and has read the full thread, including what we already tried. You'll hear from [name] by [specific date/time]. If that slips, contact me directly at [email] and I'll pick it up. Best, [Your name]
What not to say
- “I've escalated this to the relevant team.”
- Names nobody and commits to nothing. The customer cannot tell whether anything actually happened, which is the exact anxiety the email exists to settle.
- “Someone will get back to you as soon as possible.”
- "As soon as possible" sets no expectation, so any delay reads as being ignored. A specific date you can hit beats a vague one you cannot.
- “Unfortunately this is outside my control now.”
- True, and irrelevant to the customer. It reads as washing your hands of the problem. Stay named on the thread even when you are no longer doing the work.
- “Please resubmit the details to our specialist team.”
- Making someone re-explain a problem they have already described is the single fastest way to turn an escalation into a complaint. Carry the context yourself.
If they don't reply
Send this on the date you promised an update, even when there is nothing new to report. A silent deadline does more damage than a delay you acknowledged.
Subject
Update on [issue] — still with [team]
Hi [first name], I said I'd update you today, so here I am — though I don't have a resolution yet. Where it stands: [one line on what has actually happened since]. Next update from me by [new specific date]. Thanks for your patience with this one. Best, [Your name]
Questions about escalation emails
- Should I tell the customer their issue is being escalated?
- Yes, always. An escalation that happens silently looks identical to being ignored — the customer sees a conversation go quiet either way. Telling them converts an uncertain wait into a managed one, and it is the difference between a delay they tolerate and a delay they complain about.
- What should an escalation email include?
- Four things: what is being escalated, who is now responsible by name, when the customer will next hear something, and confirmation that they will not have to repeat themselves. Anything beyond that is optional. Anything missing one of those four will generate a follow-up question.
- How quickly should I escalate a support ticket?
- As soon as you know you cannot resolve it at your level — not after you have exhausted every idea. Time spent proving you cannot fix something is time the customer experiences as silence. An escalation matrix that defines the trigger for each level removes the judgement call entirely.
Define who handles what at each level with our free escalation matrix template →
