Customer Support Escalation Matrix Format (Word, Excel and PDF)

An escalation matrix answers one question before it is urgent: when a customer's ticket is not moving, who takes it next, after how long, and how do you reach them? Written down, the answer stops depending on one agent's judgement, on who happens to be online, or on how loudly the customer complains.

Search for the term and you will find several different documents with the same name. An HR escalation matrix routes an employee grievance. A project escalation matrix routes a decision that the working team cannot settle. A procurement matrix routes approvals by value. This page is about the fourth kind: the customer support matrix, where the trigger is the ticket clock and the levels are the people who can fix or reassign a customer's problem.

The format below is deliberately plain. A matrix that fits on one page gets used. One that needs a manual does not.

The trigger column carries most of the value. It is also the column people fill in worst, usually with words such as urgent or after a while. The next two sections show how to turn it into numbers.

The sample is for a small team with a ticket owner, a team lead and an admin. The times that it refers to are set out in the next section, so the matrix and the timers stay in step.

Read the matrix as a sequence. The ticket owner works every ticket from the moment it is created. If the first reply is late, or the ticket has gone quiet, or most of the time for resolution has gone, the team lead is brought in to reassign or to help. If the resolution target is reached and the ticket is still open, the admin or head of support decides what happens and speaks to the customer. At each step, the customer is told who has the ticket now.

The triggers come from the targets you promise customers. If you do not yet have response and resolution targets, write them first, by priority, because a matrix without timers is only a list of names. The ticket SLA calculator shows how due times are worked out in business hours, and the glossary entry on the service level agreement explains the terms.

1. Choose a first-response target and a resolution target for each priority, in business hours.
2. Level 2 starts when the first-response target passes with no reply.
3. Level 2 also starts when a chosen share of the resolution target is used and the ticket is still open. The sample uses 75%.
4. Level 3 starts when the resolution target is reached and the ticket is still open.

These are the example timers behind the sample matrix. They are illustrations of the method, not recommendations. Replace every number with your own.

Check the arithmetic: 75% of 8 hours is 6 hours, 75% of 24 hours is 18 hours, and 75% of 40 hours is 30 hours. A ticket that is not answered within its first-response target moves to level 2 at that point, whichever of the two conditions comes first. The Excel file does this sum for you: type the targets and the share, and the escalation times follow.

One condition in the sample needs a word of caution. The line "no update for [X] business hours" is a rule for people to follow by looking at the age of their tickets. Choose X with care: too small and every ticket escalates, too large and the line means nothing.

One owner at a time

Escalating a ticket does not mean the first person is off the hook without a word. Say whether the owner stays on the ticket while the team lead helps, or whether the ticket is reassigned. The sample says reassign or support, and each team should pick one as its default.

Roles first, names second

Write the role in the matrix and the name beside it. When someone leaves or goes on leave, you change a name, not the structure.

A backup for every level

The notes column is for this. If the team lead is unreachable for a day, the matrix should already say who stands in.

Tell the customer at every move

A short message does the job: your ticket has been passed to [name], who will reply by [time]. The customer does not need to know the internal levels, only who has the problem now.

Review what reached level 3

Once a week, read the tickets that reached the top. Look for a repeating cause: a product fault, a slow supplier, a missing answer in your help material. Fix the cause, and the next month has fewer escalations.

Free working files, with no sign-up and no watermark. Each one has the sample matrix, the example timers and a short how-to. Our name appears only on a note that you delete before using the file.

• Escalation matrix format in Word (.docx): an editable table with the six columns, the three sample levels, blank rows and the example timers.
• Escalation matrix format in Excel (.xlsx): the same matrix, plus an SLA timers sheet with formulas: type the first-response and resolution targets and the share for level 2, and the escalation times fill in.
• Escalation matrix format in PDF: a one-page form for printing and filling in by hand, or for pinning up beside the support desk.

On the Growth plan, HelloGrowthCRM can escalate a ticket by time: after the threshold you set, it alerts the ticket owner, the team lead or an admin in the app, can reassign the ticket to the team's manager, or both.

• Time thresholds you set. A rule acts when a ticket passes a threshold, and rules can be set up as separate levels so that a first alert and a later alert reach different people. The rules are checked every five minutes.
• Roles, not named individuals. The target of a rule is the ticket owner, a team lead or manager, or an admin. When the ticket owner has managers, the alert goes to them, and if there are none it falls back to admins.
• Once per ticket. A rule fires one time for a given ticket, so the alert is not repeated on every check.
• In-app alerts. The alert is a notification inside HelloGrowthCRM. It is not an email, an SMS or a WhatsApp message, so the contact channel column of your matrix still matters for reaching people who are away from the screen.

The rest of the matrix stays with your team: the backups, the message to the customer, the weekly review of level 3, and the judgement about when a ticket needs a phone call rather than a notification. We say this plainly. HelloGrowthCRM's ticketing is built for the everyday requests that a growing business receives, and it is not a full IT service desk. For asset management or complex multi-team escalation, a dedicated service desk will suit you better. For a small team that today manages escalation in a WhatsApp group or a spreadsheet, tickets with an owner, an age and time-based alerts are a clear step forward.

1. Day 1: write the response and resolution targets for each priority, using the calculator if you want to check the due times.
2. Day 2: download the format, fill in the three levels with roles, names and backups.
3. Day 3: turn every trigger into a number and check each against your targets with the timers table.
4. Day 4: walk the team through it using three real tickets from last month, and see where each would have moved.
5. Day 5: put the matrix where the team will see it, and set up any time-based rules your tools support.
6. The following week: review the first tickets that reached level 2 and level 3, and adjust the times.

If you are building the support process from scratch, the ticketing feature page shows how tickets, owners and ageing fit together, and the SLA calculator helps with the timers. When your matrix is ready, you can try the ticket rules on a HelloGrowthCRM plan that includes them.