- Industry
- IT Company
- Department
- Customer
- Team
- Support Operations
- Kind
- Decision-maker
- Approver
- Head of Service Delivery
- Code
- CUS-07
It decides who should own a complex case by matching the issue type, priority, client ARR, SLA tier and history to the escalation matrix and to who is on rota with capacity, from tier 2 support to the engineering team or the client's account manager. It reassigns the ticket with a case brief so the client never repeats themselves, and pages on-call for P1s and security cases.
How it works
7 steps, and a person signs off before step 7.
- 01Looks it up
Finds the record the request is about in the ticketing and service management system: the ticket, its SLA clock, the on-call rota and each candidate owner's open cases..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Forecasts, when it decides
Projects what each option will cost or return before it recommends one.
- 05Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 06Asks a person
Hands the work to Head of Service Delivery with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the ticketing and service management system: it reassigns the ticket with the case brief and pages on-call when needed. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The escalation matrix: support tiers, resolver groups by service, on-call rota, account managers by client, and when to involve engineering, security or the Delivery Director.
Reads from
the ticketing and service management system: the ticket, its SLA clock, the on-call rota and each candidate owner's open cases.
Acts in
the ticketing and service management system: it reassigns the ticket with the case brief and pages on-call when needed.
Hands back
An object with ticket_id, new_owner, resolver_group, tier, page_on_call (true or false), notify (a list of roles), case_brief and reason.
Asks a person when
The case has breached its SLA, a client executive escalated it, or the client is at or above 250000 USD ARR.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Move to tier 2 after (hours open) | 8 | A P2 or P3 still open after this many hours goes to tier 2. |
| Escalate after reopens | 2 | A ticket reopened this many times goes up a tier. |
| Client ARR that involves the account manager (USD) | 250000 | Escalations on clients at or above this ARR also go to their account manager. |
| Page on-call for | P1 and security | Which cases page the on-call engineer. |
| Most open cases per owner | 10 | An owner at this load is skipped. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Route by the escalation matrix: service, then priority, then who is on rota with fewer than 10 open cases.
- Move a case to tier 2 after 8 hours open or 2 reopens, and to the engineering resolver group when a product defect is suspected.
- Page on-call for P1 and security.
- Include the account manager on any escalation for a client at or above 250000 USD ARR or with an SLA breach.
- Every reassignment carries a case brief: what is known, what was tried, the SLA clock and what the client expects next.
See the Escalation Routing Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.