how to prioritize P1 vs P2 vs P3 support tickets

TL;DR

Priority is impact times urgency, not how loudly the customer complains. P1: critical function broken for many users, drop everything. P2: important function broken or degraded, same-day. P3: minor issue or single user, this week. P4: question or cosmetic, whenever. Write the definitions with examples from your own product, assign priority at triage in under a minute, and let customers escalate the priority but never set it.

The query

how to prioritize P1 vs P2 vs P3 support tickets

Use this when

• Agents assign priority by gut feel and it is inconsistent
• P1s are piling up and nothing is actually urgent
• You need a triage playbook for the team
• Customers demand P1 for everything

Not for

• Engineering incident severity (related but different)
• Setting SLA time targets per tier
• Capacity planning or staffing

Definitions

P1: critical

A core function is broken for many users, or one enterprise customer is fully down. Revenue or data is at stake. Drop everything, all hands, update every 30 minutes.

P2: high

An important function is broken or degraded, or a core function is broken for one user. Same-day response and active work until resolved.

P3: normal

Minor bug, single-user issue, or a question that needs a real answer. Resolved within the normal queue flow, this week.

P4: low

Cosmetic issues, questions answered by docs, nice-to-haves. Batched and handled when the queue allows.

Steps

1. Score impact first

How many users, and how central is the broken function? "All users cant log in" is P1. "One user cant export" is P2 or P3 depending on the function.

Expected output: an impact call (many/few users, core/edge function) before any priority label.

2. Score urgency second

Is there a deadline (payroll day, launch day), data loss in progress, or money moving? Urgency upgrades, it never downgrades.

Expected output: a yes/no on time pressure and its source.

3. Assign the priority and write one line of why

"P2: exports broken for one Pro user, no workaround, no deadline." The one-liner keeps priorities auditable and stops priority inflation.

Expected output: every ticket carries a priority plus a one-line justification.

4. Triage new tickets within 15 minutes

Priority assignment is a triage job, not a resolution job. Scan, score, label, route. A wrong priority fixed in an hour beats a perfect priority assigned tomorrow.

Expected output: no untriaged ticket older than 15 minutes during business hours.

5. Review priorities weekly

Pull the week's P1s and P2s. If half the P1s were really P2s, the definitions need sharper examples, not stricter agents.

Expected output: a weekly priority audit that feeds back into the definitions.

Variant phrasings

support ticket priority levels explained

The four definitions above. Add two real examples per level from your own product, abstract definitions drift within a month.

P1 P2 P3 priority definitions for customer support

Impact times urgency, with the one-line justification rule. Priority inflation is the number one failure mode, the weekly audit in step 5 is the fix.

how to triage support tickets by priority

Steps 1 through 4 as the triage runbook. Triage is a separate motion from solving, staff it that way at volume.

Why it happens

Without written definitions, priority becomes a negotiation: the loudest customer wins, the politest loses. Agents default to over-prioritizing because under-prioritizing feels riskier. The result is a queue where everything is P1 and nothing is. Written definitions with examples move priority from a feeling to a call, and the one-line justification makes the call checkable.

Edge cases

• Customer demands P1: acknowledge the urgency, assign by your definitions, and explain the call. "I hear this is urgent for you. By our definitions this is a P2, which means same-day work, here is what happens next."
• Priority disputes between agents: the triage lead decides, fast. Log the dispute and sharpen the definition, dont relitigate the ticket.
• Everything is on fire: when the queue is all P1, you dont have a priority problem, you have an incident. Switch to incident mode.
• VIP or enterprise customers: tier by contract if you must, but keep it explicit in the definitions. Hidden VIP rules breed resentment and inconsistency.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_dolAMzktBzWcUaEpuU0xkw