Ticket Prioritization: Impact x Urgency Matrix and Examples
Ticket prioritization made practical: an impact x urgency matrix, categories and labels, 8 messages triaged step by step and automation rules in Hodhod.
In this article
A queue worked in the order messages arrive treats a locked-out customer and a feature request as equals. Whoever wrote first gets answered first, and the person who can't pay or can't log in waits behind a question about dark mode. Ticket prioritization fixes this with a short rule that every agent applies the same way.
This guide gives you a simple matrix, a way to sort requests with categories and labels, a worked example of eight incoming messages, and the automation rules that do the repetitive part for you.
Triage first, then prioritize
Triage is the quick pass every new request gets: what is this about, who should handle it, how important is it. Prioritizing is the last of those three questions. Doing them in this order keeps priority honest, because you decide it from facts about the problem and not from how loudly the customer wrote.
Ticket prioritization: score impact and urgency separately
Two questions decide almost everything.
- Impact: how much harm does this cause, and to how many people?
- Urgency: how soon does the harm get worse, or how soon does the customer need it fixed?
Score each from 1 to 3:
| Score | Impact | Urgency |
|---|---|---|
| 3 | Money, account access or data is affected, or many customers are | Blocked right now, or a deadline within hours |
| 2 | A feature or order is broken for one customer | Needed today or tomorrow |
| 1 | A question, a small annoyance, a suggestion | Can wait several days |
Multiply the two scores and read the priority from the result:
| Impact \ Urgency | 1 | 2 | 3 |
|---|---|---|---|
| 3 | 3: High | 6: Urgent | 9: Urgent |
| 2 | 2: Medium | 4: High | 6: Urgent |
| 1 | 1: Low | 2: Medium | 3: High |
These are the same four priorities Hodhod tickets use (plus "none" for items you haven't judged yet). Adjust the cut-offs to your business, but write them down so two agents reach the same answer.
Categories and labels: sort by topic
Priority says how soon. Topic says who and how. Keep two simple tools for it.
- Categories describe what the ticket is about, one per ticket: billing, delivery, account access, bug, how-to, sales. You define them in Ticket settings. Five to eight is plenty; a long list means nobody picks the right one.
- Labels are flags that cut across categories: "vip", "payment-issue", "repeat-contact". They are what automation rules usually react to.
Pair them with teams. If billing tickets go to the billing team and bugs to the technical team, the category already answers "who".
Worked example: eight messages, one Monday morning
Here is how the matrix sorts a realistic batch. Scores are impact x urgency.
| # | Message | Category | Impact | Urgency | Score | Priority |
|---|---|---|---|---|---|---|
| 1 | "I was charged twice for my order, please refund today." | Billing | 3 (money) | 2 | 6 | Urgent |
| 2 | "Our team of six can't log in since 9. We have a client demo at 2." | Account access | 3 (six users blocked) | 3 | 9 | Urgent |
| 3 | "Gift order is due Friday and tracking hasn't moved in four days." (Wednesday) | Delivery | 2 | 2 | 4 | High |
| 4 | "How do I change the email on my account?" | How-to | 1 | 1 | 1 | Low |
| 5 | "The invoice shows our old company name. Needed before month end." (three weeks away) | Billing | 2 | 1 | 2 | Medium |
| 6 | "Yesterday's data is missing from my exported report. I present it tomorrow morning." | Bug | 2 | 2 | 4 | High |
| 7 | "Checkout says gateway timeout." (second customer in 20 minutes) | Bug | 3 (many customers) | 3 | 9 | Urgent |
| 8 | "Which plan fits a team of 20? I want to decide today." | Sales | 1 | 2 | 2 | Medium |
Working order: start with the Urgent group, and inside it handle the 9s first, so #7 and #2, then #1. Within the same priority, oldest first. Then #3 and #6, then #5 and #8, and #4 last.
Two things are worth noticing. Message 7 is not a single ticket: if a second customer reports the same checkout error, link both to one issue or merge duplicates, and tell the team it is probably an incident. And message 8 gets a middle priority but belongs to a different person. Sales requests go to the sales team, with a quick reply from the first agent who sees it.
Automation rules that set priority for you
You don't want an agent scoring every message by hand. In Hodhod, automation rules (Settings → Automation) can change priority, add an SLA, route to a team and add labels from conditions you choose. A starter set:
- Label "payment-issue" present: action "Change Priority" to Urgent, then "Add SLA" with your urgent policy.
- Label "vip" present: "Add SLA" with the faster policy.
- Label "how-to" present: "Change Priority" to Low and route to the first-line team.
- Label "billing" present: route to the billing team.
Add auto-escalation for what slips through: a ticket that is approaching or past its deadline, idle for a while or waiting too long gets a higher priority, or someone senior is notified. The rule preview shows which tickets it would have caught before you switch it on. For the targets themselves, see what an SLA is and how to set one, and for who gets notified, an escalation policy template.
Agents can still override priority by hand, and every change is recorded in the ticket timeline with the name of whoever made it. For a batch, select tickets on the list and change priority in one go.
Common mistakes
- First come, first served. It feels fair and quietly punishes people with serious problems.
- Everything is urgent. If a third of the queue is Urgent, the label tells your agents nothing. Revisit the cut-offs.
- Letting tone decide. An angry message about a small problem is still a small problem. Answer it kindly and score it honestly. Our guide to handling angry customers covers the tone part.
- Setting priority once and forgetting it. A ticket waiting on the customer for three days has a different urgency from the day it arrived.
- Too many categories. Agents choose "other", and your reports become useless.
- No written rules. If the matrix lives in one person's head, the queue changes with the shift.
To see how priorities, labels and automation rules fit together in one inbox, request a free demo. Or read about ticketing with priorities and SLAs.
Frequently asked questions
How many priority levels do I need?
Four is enough for most teams: urgent, high, medium and low. More levels make agents hesitate over the difference between neighbors.
Should the customer choose the priority?
No. Customers describe their own problem as important, which is fair, but they can't see the rest of your queue. Collect the facts (what broke, how many people, by when) and set the priority yourself.
What if impact and urgency disagree?
The matrix handles that: a high-impact problem with no deadline still lands on High, and a small problem with a deadline tonight lands on Medium or High. If the result feels wrong, change the cut-offs, not the individual ticket.
Can automation set priority from a label?
Yes. An automation rule with the condition "label is present" can run "Change Priority", for example every conversation labeled "payment-issue" becomes Urgent.
