What are ticket priority levels?
Ticket priority levels are the ranks a help desk gives each request, commonly P1 to P4, to decide what is worked first and how fast. Priority comes from impact, how much of the business is affected, and urgency, how soon harm follows. Each level carries its own response target.
Full guide: IT support triage: what to report and when to escalate Service: Outsourced IT Help Desk
Ticket priority levels sort support requests so that a company-wide outage is not waiting behind a request for a new mouse. Most desks use three to five levels, often labeled P1 to P4 or critical, high, medium and low. The label matters less than the definition behind it: a written description of what belongs at each level, agreed before the first incident.
Priority is normally worked out from two questions. Impact asks how much of the business is affected: one person, a department, a whole office or the customers. Urgency asks how quickly the damage grows: whether work has stopped now, will stop by a deadline or is merely inconvenient. A problem that is high on both is a P1. Who is asking is not part of the calculation, though an agreement can name roles or systems, such as payroll on payday, that raise the priority.
Each level then carries targets: how fast someone responds, how often the user is updated, when the issue is escalated to a senior engineer or to management, and whether work continues outside business hours. Severity is a related term that some desks use differently, with severity describing the technical fault and priority the order of work; many small business agreements use the two words for the same thing. What must not happen is priority set by whoever shouts loudest, or every ticket marked urgent, which leaves the desk with no order at all.
Reviewed by Joel Baum, Founder. Our editorial standards.
Typical ticket priority levels, P1 to P4
| Level | What it means | Examples | How it is handled |
|---|---|---|---|
| P1 (critical) | The business is down or actively at risk | No internet or email for the office, ransomware, a failed server everyone depends on | Immediate response at any hour, a senior engineer involved, frequent updates |
| P2 (high) | A team or a key process is stopped, or one person cannot work at all | A department's shared drive is unreachable, the accounting application will not open | Fast response in staffed hours, escalated if not restored quickly |
| P3 (normal) | Something is broken but work continues | A printer fault with another printer nearby, one application misbehaving | Worked in order within the standard response target |
| P4 (low) | A request or question with no fault | New software, a how-to question, a change planned for next month | Scheduled, often for an agreed date |
Why it matters for a small business
Priority definitions decide what happens on your worst day. If the agreement does not say what counts as critical, the provider decides during the incident, and its answer may not match yours. Good definitions also protect you from yourself: when everything is urgent, the desk cannot tell the outage from the annoyance. Ask to see the levels in writing, with examples from your own business, the response target for each and the path a critical ticket takes at night.
How NetSys sets severity
NetSys publishes its response commitments at two severity levels. Critical means you are down or actively at risk: the phone response is 10 minutes and the remote response 30 minutes, with on-site response as fast as 1 hour under the agreement. Standard means something is broken but work continues: 30 minutes, 1 hour and up to 6 hours. On-site times depend on where you are and the on-site tier in your agreement.
Severity is set by business impact, from one person's printer to the whole office down, and the levels are agreed at onboarding so that an overnight alert follows a path you approved in advance. In the NetSys help desk ticketing system, staff give each ticket a category and a priority when they open it.
Where NetSys handles this
Sources
Checked on November 22, 2026.
- ITIL 4 Practitioner: Incident Management, PeopleCert (owner of ITIL)
- ISO/IEC 20000-1:2018, Information technology: Service management: Part 1: Service management system requirements, International Organization for Standardization (ISO)
- NIST SP 800-61 Rev. 3, Incident Response Recommendations and Considerations for Cybersecurity Risk Management: A CSF 2.0 Community Profile, National Institute of Standards and Technology (NIST)
Ticket Priority Levels: FAQs
What do P1, P2, P3 and P4 mean?
They are priority levels, with P1 the most urgent. In a common scheme, P1 is a business-wide outage or active security incident, P2 a serious problem affecting a team or stopping one person completely, P3 a fault with a workaround and P4 a routine request. Exact definitions vary, so use the ones in your own agreement.
How is ticket priority decided?
From impact and urgency. Impact is how much of the business is affected; urgency is how soon the harm grows. The help desk assigns the level from written definitions, and the user's own choice of priority is treated as a starting point that the desk can adjust.
What is the difference between priority and severity?
Where a help desk separates them, severity describes how bad the technical fault is and priority describes the order in which work is done, which also reflects business deadlines. In many small business agreements the two words mean the same thing. Check which one your response targets are tied to.
Who can change a ticket's priority?
Usually the help desk, following the written definitions, with a route for the client to ask for an escalation when the business impact is greater than the ticket suggests. The agreement should name who at your company can declare an emergency, so that call does not depend on who happens to phone in.
More terms
Discuss outsourced it help desk for your business.
Tell us about your current systems, the result you need and your timeline. We will discuss the work, responsibilities and pricing before you decide on an engagement.
