Ticket Priorities Explained (Business Down vs Single User)

Last updated

May 12, 2026

Reviewed by

Reviewed by: IT Service Delivery Lead

Speakable Summary

Ticket priority should be based on businessimpact not urgency feelings. Book a Fit Check to define priorities that keepwork moving and reduce chaos.

Opening

Most SMB support chaos comes from one problem.Everything gets labeled urgent.

When all tickets are treated the same, truebusiness down events wait behind small requests. Then leadership losesconfidence and staff start using side channels like texting technicians.

This page explains simple ticket priorities inplain English. It shows how to separate business down events from single userissues and how to make priorities consistent.

Direct Answer

Business down tickets affect core workflows formany people and must be prioritized first. Single user tickets are importantbut should follow a normal queue unless impact grows.

LINK: IT Support page
LINK: Managed IT Services
LINK: Managed IT Pricing

What’s included vs what’s usually extra

Typically   included in priority-based support

Usually   extra as a project

Priority definitions and examples

Custom dashboards and KPI automation

Triage rules and escalation paths

Full workflow redesign across departments

Update cadence for business down events

Large tool migrations and integrations

Ticket closeout notes and trend tags

Dedicated on-site staffing programs

Vendor escalation during outages

Vendor replacement projects

●    
Define business down in one sentence

●    Require triage that assignspriority and next step

●    Require update cadence forbusiness down tickets

Included means practical rules that keeppriorities consistent. Extra means custom reporting systems and major processrebuilds.

Primary Intent Block (DEFINITION)

If you only do one thing this week

●    Define business down and who candeclare it.

●    Use three or four priority levelswith simple examples.

●    Require a next update time forbusiness down incidents.

People

Priority rules protect staff time and reducestress. They prevent constant “urgent” pings and keep expectations consistent.

Device

Device issues can be business down when manyusers lose a core workflow. Device issues are usually single user when only onelaptop is affected.

Account/App

Account issues can be business down when manyusers cannot sign in or email fails broadly. Account issues are usually singleuser when one person is locked out.

Operations

Operationally, priorities drive triage,escalation, and communication cadence. Good priorities also make reporting andrepeat issue reduction easier.

Simple priority levels for SMBs

Priority 1: Business Down

Business down means a core workflow is stoppedfor multiple people. Examples include office internet down, email down for manyusers, phones down, or a line-of-business system outage.

Priority 1 requires immediate triage and a definedupdate cadence. The ticket should show an owner and the next update time.

Priority 2: Major Impact

Major impact means a key person or key workflowis blocked but the whole business is not down. Examples include a billingmanager unable to send invoices or a front desk unable to use scheduling.

Priority 2 should be worked quickly afterPriority 1 is contained. It should still include a clear next step and anexpected update.

Priority 3: Single User Blocked

Single user blocked means one person cannot workbut the business is still operating. Examples include one laptop failing toboot or one mailbox login failure.

Priority 3 should be handled in a normal queuewith clear expectations. Repeated Priority 3 issues may signal a standardsproblem.

Priority 4: Request or Minor Issue

Requests include access requests, new softwarerequests, and minor questions. Minor issues include small glitches where workcan continue.

Priority 4 should be scheduled and handled predictably.Requests should still get closeout notes so history is preserved.

LINK: Help Desk
LINK: FAQ

How to decide business down vs single user

Use impact not emotion

Ask how many people are affected and whatworkflow is blocked. If revenue, patient flow, scheduling, or billing isstopped for many people, it is business down.

If one person is blocked, it is usually a singleuser priority. If that person is a bottleneck role, it may be major impactinstead.

Define who can declare business down

Many SMBs assign this to the office manager or adesignated leader. This prevents every user from labeling their own issue asPriority 1.

Clear ownership reduces conflict. It also keepsthe help desk from being pulled in ten directions.

Set an update cadence for business down

The most important communication rule ispredictable updates. Even short updates reduce stress and stop repeatedfollow-ups.

Vendor incidents need updates too. Case numbersand timestamps should live in the ticket.

‍