Escalation is appropriate when a support ticket is not being resolved within the expected SLA timeframe, when the business impact is growing, or when the issue requires senior technical or management involvement. This article explains when and how to escalate effectively.
When to Escalate
| Situation |
Appropriate Action |
| SLA response time has been exceeded with no contact from support |
Reply to existing ticket first; escalate if no response within 2 additional hours |
| Issue has been open for more than 5 business days without resolution |
Request escalation to senior technical team |
| Production sending has completely stopped and the impact is growing |
Mark as Critical and explicitly request emergency escalation |
| A previous resolution did not fix the problem and the issue has recurred |
Reopen the original ticket and request review by a different engineer |
| Significant financial impact — e.g. wrong billing, fraudulent charges |
Request escalation to accounts team and attach supporting evidence |
| The issue requires a policy decision or exception beyond standard support scope |
Request escalation to team lead or account manager |
Escalate, do not duplicate. Opening a second ticket for the same issue does not speed up resolution — it splits context across two threads and can actually slow things down. Always escalate within the original ticket, or reference the original ticket number in an escalation ticket.
Escalation Path
| Level |
Handler |
How to Reach |
For |
| L1 |
Support Agent |
Reply to your existing ticket |
First contact; standard queries and configuration help |
| L2 |
Senior Support / Technical Lead |
Reply to ticket with: "Please escalate to senior technical team" |
Complex technical issues, repeated failures, deep debugging |
| L3 |
Engineering Team |
Requested by L2 when platform-level investigation is needed |
Potential platform bugs, infrastructure issues, data anomalies |
| Account |
Account Manager (Premium plan) |
Direct contact method provided at Premium onboarding |
Business relationship issues, SLA disputes, contract matters |
How to Escalate — Step by Step
- Open your existing support ticket in the portal (Support → My Tickets → [your ticket]).
- Add a reply with the following information:
- The word "Escalation Request" prominently in the first line.
- A summary of what has been tried so far and why the current resolution is insufficient.
- The current business impact — how many messages affected, estimated revenue impact, or customer-facing consequences.
- The time elapsed since submission and the SLA tier your plan entitles you to.
- Change the ticket priority to Critical or High if it is not already set appropriately.
- Submit the reply. The escalation flag is visible to team leads who review queues for stuck or breached tickets.
Escalation Reply Template
ESCALATION REQUEST
This ticket has been open since [date / time] without resolution.
My plan tier is [Standard / Priority / Premium] which entitles me
to a [X]-hour SLA for [Priority level] tickets.
CURRENT STATUS:
[Summarise what has been tried and the current state of the issue]
BUSINESS IMPACT:
[Describe the impact — e.g. "All transactional emails have been
failing for 6 hours. This affects OTP delivery for approximately
500 active users per hour."]
REQUEST:
Please escalate to senior technical support immediately.
I require an update within [1 / 2 / 4] hours.
What to Expect After Escalating
| Timeframe |
What Happens |
| Within 1 hour of escalation |
Acknowledgement from a senior agent confirming escalation has been registered and assigned |
| Within 2–4 hours |
Initial assessment update — whether the issue is platform-side, configuration, or requires engineering investigation |
| Ongoing |
Progress updates every 2–4 hours until the issue is resolved or a workaround is provided |
| On resolution |
Root cause explanation, steps taken to resolve, and preventive measures implemented |
Next Steps