Enterprise Service Management Office, Service Management Ticket Types
This includes Information Technology Infrastructure Library (ITIL)-based definitions, ticket classification criteria, common examples, triage guidance, and recommended training resources to support consistent ticket management practices.
Ticket Comparison Matrix
The following matrix summarizes the key characteristics of Service Requests, Incidents, Major Incidents, and Problems to support consistent classification and handling in accordance with ITIL service management practices.
| Attribute | Service Request | Incident | Major Incident | Problem |
|---|---|---|---|---|
| ITIL Definition | A request from a user or a user's authorized representative that initiates a service action which has been agreed as a normal part of service delivery. | An unplanned interruption to a service or reduction in the quality of a service. | An unplanned interruption to a service with: -Significant business impact -Requires immediate action -Requires a coordinated response |
A cause, or potential cause, of one or more incidents. |
| Core Definition | Asking IT for a standard service, hardware, or access. | Something that was working but is now broken or degraded. | Something that was working but is now broken. | The underlying root cause of one or more recurring incidents. |
| Reported By | End user. | End user or system monitoring. | End user or system monitoring | IT staff (often triggered by incident trends). |
| Urgency | Planned / Standard fulfillment time. | Immediate attention required. | Immediate attention required. | Investigated after incidents are stabilized. |
| Primary Goal | Fulfill user request efficiently. | Restore normal service as quickly as possible. | Restore normal service as quickly as possible. | Permanently eliminate root cause to prevent recurrence. |
| Common Examples |
Password Reset Requests Software Access Requests Software Installation Requests New Drive Access Requests |
Authentication Changes Email Loading Failures Wi-Fi Connectivity Drops |
Campus-wide or multi-department Wi-Fi or Network outage Canvas outage Financial system outage Mass power outage impacting IT systems Exchange email outage impacting a large group or everyone Cyber Incident impacting Enterprise system DNS service outage Data Center Outage |
A recurring issue causes the email service to fail every Monday morning, resulting in repeated email access incidents. Network congestion on the wireless network results in recurring reports of slow or dropped Wi-Fi connections. |
Actionable Triage Logic and Specific Training Mapping
The following scenarios demonstrate how to apply ticket classification criteria in practice. Each scenario identifies the appropriate ticket type, management objective, and recommended training to support effective service management and decision-making.
Scenario A: User needs something new or standard access
- Action: Log as a Service Request.
- Target goal: Fulfill pre-approved items efficiently.
- Recommended training: Customer Service Foundations (LinkedIn Learning) and IT Service Desk Management Fundamentals (LinkedIn Learning)
Scenario B: Service is broken, degraded, or inaccessible
- Action: Log as an Incident.
- Target goal: Restore normal operational state via workaround or fix.
- Recommended training: Putting ITIL into Practice: Incident Management (LinkedIn Learning)
Scenario C: Service is broken and inaccessible
- Action: Log as a Major Incident.
- Target goal: Restore normal operational state via workaround or fix.
- Recommended training: ITIL incident, major incident, and problem management (LinkedIn Learning)
Scenario D: Recurring failure or major outage with unknown cause
- Action: Log a Problem Ticket linked to affected Incidents.
- Target goal: Root cause analysis (RCA) and permanent fix.
- Recommended training: Putting ITIL into Practice: Problem Management Techniques (LinkedIn Learning)
Please contact the Enterprise Service Management Office through the ESMO Request Form.