How do we prioritize tickets when everything is a priority?
As the guidelines from ITIL (Information Technology Infrastructure Library) for IT support tickets prioritization suggest, we prioritize tickets based on urgency and impact.
The urgency and impact are determined by:
- How many users are affected?
- Does this impact the user(s) ability to do their job?
- Is there a workaround?
URGENT | HIGH | MEDIUM | LOW (Default) | ||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Definition: An issue that impacts all users and no workaround is available.
e.g. Internet is down. Initial Response SLA
Resolution SLA
| Definition: An issue that impacts many users and no reasonable workaround is available.
e.g. A server used by the marketing department is down. Initial Response SLA
Resolution SLA
| Definition: An issue that impacts multiple users.
e.g. A server used by the marketing department is slow. Initial Response SLA
Resolution SLA
| Definition: An issue that impacts a single user
e.g. A user needs different access to the marketing department server. Initial Response SLA
Resolution SLA
|
All times are based on normal business hours of 8:30 to 5:30 Central Time
Most tickets can be expedited for faster service, which in most cases will raise rates.