The Escalation Matrix Who should be reached when a case runs hot, and what the platform does about it.

The escalation matrix is where you record who handles escalated work, by severity and by customer tier.

What it holds

A grid mapping severity and tier to the people who should be involved, so there is a written answer to "who do we call" before the moment you need it.

What it does, precisely

This is worth being exact about, because the name suggests more than the mechanism delivers.

The matrix is a record, not a router. Escalating a ticket sets its status to Escalated, raises its priority, and stamps the time. It does not assign the person named in the matrix, and it does not notify them.

So the matrix answers "who should be handling this" for a human who is looking. It does not fetch that human.

What this means in practice

Escalation works in exactly one arrangement: somebody watches the queue for escalated tickets and acts on them. That could be a team lead's morning routine or a saved filter someone keeps open.

If nobody holds that watch, escalating is filing rather than raising, and the ticket will sit at a higher priority that no one has seen.

Decide who holds it, and say so, before the matrix is worth filling in.

The recent escalations list

The matrix shows a panel of recent escalation events. It reads from a dedicated record that nothing currently writes to, so that panel is empty and will stay empty.

Escalations themselves are real and recorded on the ticket. It is the separate event history that is not being kept. Use the ticket's own status and history rather than this panel to see what has been escalated.