IT Support Ticket Priority Levels: P1 to P4 Response Times Explained

When every ticket looks urgent, none of them gets handled first. Priority levels fix that. They give each request a clear place in the queue and a deadline, so the outage affecting every customer is answered before the question about changing a password.

TL;DR

• Most teams use four levels: P1 Critical, P2 High, P3 Medium and P4 Low.
• Decide priority from two questions: how many people are affected (impact) and how soon it hurts the business (urgency).
• Good starting targets: P1 first reply in 1 hour and fix in 4, P2 in 2 and 8 hours, P3 in 6 and 24 hours, P4 in 24 hours and 3 days.
• Count targets in business hours unless you offer round-the-clock support.
• Review the levels monthly. If more than one ticket in ten is P1, your definitions are too loose.

What are ticket priority levels?

A priority level is a label on each support ticket that says how quickly it must be answered and fixed. The labels are usually written P1 to P4, or Urgent, High, Medium and Low. Each level carries two deadlines: a first response time, the time to the first real reply, and a resolution time, the time to fix the problem.

What do P1, P2, P3 and P4 mean?

• P1, Critical. The service is down or unsafe for many customers, or money is being lost right now. Examples: the website or app will not load, payments are failing, a data breach is suspected.
• P2, High. A major feature is broken for some customers, or one important customer cannot work, and there is no workaround. Examples: invoices will not send, one branch cannot log in.
• P3, Medium. Something is broken or slow, but a workaround exists. Examples: a report shows the wrong totals, a form field will not save on one browser.
• P4, Low. Questions, how-to requests, small cosmetic issues and feature ideas. Examples: how do I export contacts, can you change the colour of this button.

How do you decide a ticket's priority?

Ask two questions and combine the answers.

1. Impact: how many people does this affect? Everyone, a group, or one person.
2. Urgency: how soon does it hurt the business? Right now, today, or it can wait.

Then read the result:

• High impact and high urgency: P1.
• High impact but it can wait a little, or one person who cannot work at all: P2.
• A small group affected, with a workaround: P3.
• One person, no real time pressure: P4.

Write two or three real examples from your own business under each level. Agents decide faster from examples than from definitions.

What are typical response times for each priority?

These targets suit most small and growing support teams, and they are the defaults in QuiQ Help Desk:

• P1 Urgent: first reply within 1 hour, resolved within 4 hours.
• P2 High: first reply within 2 hours, resolved within 8 hours.
• P3 Medium: first reply within 6 hours, resolved within 24 hours.
• P4 Low: first reply within 24 hours, resolved within 3 days.

IT teams that run critical systems often tighten P1 to a 15 or 30 minute response with someone on call. A team that only works weekdays should count the targets in business hours, so a ticket that arrives on Friday evening is not overdue by Saturday morning. For more targets, including QA scores, see our SLA examples for customer support.

What is the difference between priority and severity?

Severity describes how bad the problem is technically. Priority describes how soon you will act on it. They usually move together, but not always: a severe bug in a feature nobody uses can be P3, while a small error on the checkout page during a sale can be P1. Your queue should sort by priority.

What happens when a ticket misses its deadline?

It should escalate on its own, not wait for someone to notice. Common steps are a reminder to the owner when the deadline is close, then a move to a manager or a senior queue once it is missed. Track how many tickets miss their target each week. One missed P1 tells you more about your process than fifty P4s answered on time.

How QuiQ Help Desk sets and tracks priorities

• Priority on arrival. Every new ticket is read, categorised and given a priority the moment it lands, and agents can change it with one click.
• Deadlines from the priority. Each ticket gets a first response and a resolution target from its priority. You set the hours per level under Settings, Help Desk, Response and resolution deadlines, and they count through your business hours.
• Every channel, the same rules. Email, website chat, WhatsApp, the customer portal and tickets your team creates all follow the same deadlines.
• Escalation built in. A ticket that misses its target is escalated and listed under Targets missed, and the Desk shows what is overdue and what falls due in the next 8 hours.

The full setup takes about ten minutes. See Set up Quiq Help Desk, or read how to set up a help desk for a small business.