Connect to Intercom— Operations —
Priority Matrix
— Definition —
A Priority Matrix (also called P1/P2/P3/P4 tiers or Severity Levels) is a framework that classifies support tickets by urgency and business impact so they can be assigned appropriate SLA targets and resource levels. P1 typically represents critical production outages affecting all users; P2 is significant degradation; P3 is non-blocking issues; P4 is low-urgency requests or feature feedback. The matrix ensures that a login outage receives 10× more urgency than a UI cosmetic bug without leaving classification to individual agent judgment.
— Benchmark ranges —
Typical B2B SaaS priority levels and first-reply targets
P1 (Critical / all-users outage)First reply: < 1 hour; Resolution: < 4 hours
P2 (Major / significant degradation)First reply: < 4 hours; Resolution: < 1 business day
P3 (Minor / workaround exists)First reply: < 1 business day; Resolution: < 3 days
P4 (Low / feature request)First reply: < 2 business days; Resolution: best-effort
— Common mistakes —
- 1Letting customers self-assign priority — customers almost always mark their issue as P1. Define priority criteria that agents apply based on measurable impact, not customer urgency claims.
- 2Defining priority by customer tier rather than issue impact — enterprise customers deserve faster SLAs, but that belongs in the SLA tier structure, not the priority definition. Priority should reflect issue severity.
- 3Not defining resolution criteria for each priority level — "resolve P1 in 4 hours" without a definition of what "resolved" means for an outage invites interpretation disputes.
- 4Using priority as a proxy for ticket routing — priority (severity) and routing destination (billing vs. technical) are orthogonal dimensions. Route by topic, prioritize by impact.
— Related metrics —