The earlier archive Written for a different audience — operations teams, business stakeholders, new joiners. It is kept unchanged, with its original date, because a dated body of work says something a rewritten one cannot.

Support Ticket Triage: A Simple Framework Anyone Can Use

It was 2:30 PM on a Tuesday. Our phone started ringing. Then our email inbox started filling up. Then the chat notifications started piling up.


The Tuesday Afternoon That Broke Our System

It was 2:30 PM on a Tuesday. Our phone started ringing. Then our email inbox started filling up. Then the chat notifications started piling up.

Three different issues had hit us simultaneously:

  1. The customer management system was timing out for multiple users
  2. The shipping label printer wasn't working in the warehouse
  3. A key supplier's portal was down

Our support team was overwhelmed. Everyone was shouting "urgent!" and no one knew where to start.

We spent the next 3 hours in chaos—running from issue to issue, feeling like we were making progress but never actually finishing anything. By 5:30 PM, the warehouse was still backed up, the customer team was frustrated, and our best engineer had spent hours on a low-priority issue.

I realized we didn't have a priority problem. We had a prioritization problem.

The Triaging Problem

Every support team faces the same challenge: How do you prioritize when everything feels urgent?

This isn't just about technical teams. Any organization that deals with requests, problems, or issues needs a way to decide what comes first.

After handling hundreds of support tickets at Auto360, I developed a framework that helped our team improve first-response times by 40% and reduced escalation confusion entirely.

It's not sophisticated. It's not perfect. But it works.

The Three-Question Framework

When faced with multiple issues, ask these three questions in order:

Question 1: How Many People Are Affected?

Immediate impact scale:

  • 🚨 Critical: 50+ users or all users affected
  • ⚠️ High: 10-49 users affected
  • 📊 Medium: 2-9 users affected
  • 👤 Low: 1 user affected

Why this matters first: One person blocked is a problem. Fifty people blocked is a crisis. The more people affected, the higher the urgency.

What I've learned: A single VIP user might complain loudly, but 50 regular users quietly affected is a bigger problem. Don't let volume confuse you—count users, not tickets.

Question 2: Is There a Workaround?

Workaround assessment:

  • ❌ None: Users cannot proceed at all
  • 🔄 Partial: Users can work, but with reduced efficiency
  • ✅ Complete: Users can accomplish tasks through other means

Why this matters second: No workaround = maximum urgency. Complete workaround = can wait for scheduled maintenance.

What I've learned: Sometimes the best support call isn't fixing the problem—it's teaching the workaround. I've had users thank me for not fixing their system because the workaround was actually faster than the "proper" solution.

Question 3: What's the Business Impact If We Wait?

Business impact scale:

  • 💰 Financial: Revenue loss or cost impact > £1,000/hour
  • 🏥 Critical: Patient safety, regulatory compliance, legal risk
  • ⏰ Time-sensitive: Deadlines, SLAs, customer commitments
  • 📉 Operational: Reduced efficiency but work continues
  • 😕 Inconvenience: Minor frustration only

Why this matters third: Some problems cost money. Some problems put patients at risk. Some problems are just annoying. Treat them differently.

What I've learned: The problem that feels most urgent to the person reporting it isn't always the most urgent for the business. Your job is to see beyond the individual complaint to the organizational impact.

Putting It Together: The Priority Matrix

Here's how these three questions combine into a clear priority system:

Priority 1: Fix Immediately

  • 🚨 Critical impact (50+ users)
  • ❌ No workaround
  • 💰 Financial or 🏥 Critical business impact

Example: Customer management system down for 50+ users during peak sales hours

Action: Drop everything. Assign your best resources. Communicate status frequently.

Priority 2: Fix Within 4 Hours

  • ⚠️ High impact (10-49 users)
  • ❌ No workaround
  • 💰 Financial or ⏰ Time-sensitive impact

Example: Warehouse label printer down affecting 12 staff during shipping hours

Action: Assign appropriate resources. Work on it. Keep stakeholders informed.

Priority 3: Fix Within 24 Hours

  • 📊 Medium impact (2-9 users)
  • 🔄 Partial workaround available
  • 📉 Operational impact

Example: 5 users experiencing slow performance but can still work, just slower

Action: Schedule for resolution. If no higher-priority issues, work on it now.

Priority 4: Fix Within 1 Week

  • 👤 Low impact (1 user)
  • ✅ Complete workaround available
  • 😕 Inconvenience only

Example: One user prefers a different report format but can work around it

Action: Add to backlog. Address during regular maintenance windows.

Priority 5: Defer or Decline

  • 👤 Low impact (1 user)
  • ✅ Complete workaround available
  • 😕 Personal preference, not business need

Example: One user wants a feature that doesn't align with business priorities

Action: Communicate why it's not being prioritized. Suggest alternative approaches.

Real-World Example: The Tuesday Chaos

Let's revisit the three issues from my chaotic Tuesday, but apply this framework:

Issue 1: Customer Management System Timing Out

  • Users affected: 50+ 🚨
  • Workaround: None ❌
  • Business impact: Financial 💰 (lost sales)

Priority: 1 (Fix Immediately)

Issue 2: Shipping Label Printer

  • Users affected: 8 📊
  • Workaround: None ❌
  • Business impact: Time-sensitive ⏰ (shipping deadline)

Priority: 2 (Fix Within 4 Hours)

Issue 3: Supplier Portal Down

  • Users affected: 3 📊
  • Workaround: Complete ✅ (call orders in)
  • Business impact: Minor inconvenience 😕

Priority: 4 (Fix Within 1 Week)

Result: We focused on the customer system first, the printer second, and didn't waste time on the supplier portal. The supplier portal got fixed during scheduled maintenance later that week.

Why This Framework Works

1. It's Objective (Mostly)

By using a consistent framework, we reduce personality politics and loud complainers getting priority.

2. It's Transparent

When a stakeholder asks "why isn't my issue being fixed?" you can show them the framework. They might not like the answer, but they understand the logic.

3. It's Fast

Three questions. That's it. You can triage a dozen issues in 5 minutes.

4. It's Adaptable

Adjust the thresholds for your organization. 50 users might be critical for a small company but medium for a large one.

5. It Reduces Guilt

Support teams often feel bad about not fixing everything immediately. This framework gives permission to prioritize and defer.

Implementing This Framework

Step 1: Define Your Thresholds

Based on your organization size and needs, define what "critical," "high," and "medium" impact mean for you.

Step 2: Train Your Team

Make sure everyone knows how to use the framework. Practice with hypothetical scenarios.

Step 3: Use It Consistently

The power of this framework comes from consistency. Don't make exceptions based on who's asking.

Step 4: Communicate It

Let stakeholders know how prioritization works. This sets expectations and reduces surprise when their issue is deferred.

Step 5: Review and Adjust

Every 3-6 months, review whether your thresholds are still appropriate. As your organization grows, so will your scales.

Common Pitfalls (And How to Avoid Them)

Pitfall 1: Letting VIPs Jump the Queue

The Problem: The CEO's computer issue gets Priority 1 treatment even if only 1 user is affected.

The Solution: Include executive support as a separate category. VIP issues might be Priority 2 (Fix Within 4 Hours) instead of Priority 4, but they don't automatically jump to Priority 1.

Pitfall 2: Counting Tickets, Not Users

The Problem: One issue submitted by 15 different users looks like 15 issues with "1 user affected" each.

The Solution: Group related tickets. Count unique users, not ticket count.

Pitfall 3: Ignoring Partial Workarounds

The Problem: A workaround that takes twice as long is treated as "workaround available" and deprioritized.

The Solution: Note the efficiency of workarounds. A workaround that's 80% efficient might warrant higher priority than one that's 30% efficient.

Pitfall 4: Not Communicating Status

The Problem: You've prioritized correctly, but people don't know their issue is being addressed.

The Solution: For Priority 1 and 2 issues, provide status updates every 30-60 minutes. For Priority 3 and 4, provide at least an initial "we're aware" response.

A Simple Triage Template

You can copy this into a ticket system or use it as a worksheet:

Triage Assessment
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Issue: [Brief description]

1. How Many People Are Affected?
   [ ] 1 user
   [ ] 2-9 users
   [ ] 10-49 users
   [ ] 50+ users

2. Is There a Workaround?
   [ ] None
   [ ] Partial (explain: ___________)
   [ ] Complete (explain: ___________)

3. Business Impact If We Wait?
   [ ] Financial > £1,000/hour
   [ ] Critical (safety, compliance, legal)
   [ ] Time-sensitive (deadline, SLA)
   [ ] Operational (reduced efficiency)
   [ ] Inconvenience only

Priority: [ 1 / 2 / 3 / 4 / 5 ]
Target Resolution: [ Immediately / 4 hours / 24 hours / 1 week / Deferred ]
Assigned to: _______________

The Hard Truth

Perfect prioritization doesn't exist. Sometimes you'll make the wrong call. Sometimes priorities will conflict. Sometimes the framework won't account for unique situations.

But having a framework is infinitely better than having no framework.

Our team went from chaos to clarity in about 2 weeks. Incidents that used to take all day to untangle now took an hour. Stakeholders stopped shouting "why is my issue not fixed?" and started trusting our judgment.

The right priority system isn't about getting everything right. It's about making consistent, defensible decisions that your team can rally behind and your stakeholders can understand.


Quick Reference Cheat Sheet

PriorityImpactWorkaroundBusiness ImpactResponse Time
150+ usersNoneFinancial/CriticalImmediate
210-49 usersNoneFinancial/Time-sensitive4 hours
32-9 usersPartialOperational24 hours
41 userCompleteInconvenience1 week
51 userCompletePreferenceDeferred

What prioritization challenges does your team face? I'd love to hear what's worked (or hasn't) for you.

#SupportOperations #TriageFramework #ServiceDelivery #CheatSheet #ITSupport #TeamManagement

The archive

Every article, 2013–2026

Thirty dated articles on application support, delivery, infrastructure and data — plus the recent writing on CI/CD reproducibility and offline-first design.

The recent work is written for a specialist audience, and it is where the measurement discipline is set out in full.

Recent writingOpen Source Impact