Skip to main content

Ticket Handling, SLA, and Escalation

Ticket Handling​

Creating a Ticket​

Required information:

FieldDetails
NamePerson's full name
ContactPhone, email, Teams
LocationLocation of the incident
SourceWalk-in, phone, email, etc.
DescriptionDetailed description of the problem

Helpful but not required:

  • How long has the issue been occurring?
  • Frequency of the occurrence?
  • Screenshots of error messages
  • Customer availability

Updating a Ticket​

SLA Reminder

Tickets should not be active more than a day (excluding weekends and holidays) without an update.

  • Document ALL work performed no matter how minor
  • Include attempts to contact the customer
  • Include contact with vendors or external support
  • Update status when waiting on customer or vendor response
  • Set tickets to go off hold before SLA timer expires

Resolving a Ticket​

When the issue is fixed to the customer's satisfaction:

  1. Update the ticket status to Resolved
  2. Enter a summary of steps taken
  3. Assign the ticket to the individual who performed the fix

Escalating a Ticket​

  1. Document all troubleshooting steps and attempted fixes
  2. Notify the appropriate person before escalating
  3. For external team escalation notify the helpdesk supervisor
Escalate Immediately

Notify a supervisor immediately if:

  • A customer is acting rudely or unprofessionally
  • They indicate they will be talking to college leadership
  • You ever feel uncomfortable or unsafe

You are authorized to remove yourself from the situation.


Priority Matrix​

Ticket Priority Matrix


SLA Targets​

Operational Hours Only

Tickets submitted after hours, during weekends, or on university holidays do not count towards SLA.

PriorityInitial ResponseRecurring UpdateExpected Resolution
High30 Minutes1 Hour8 Hours
Medium1 Hour4 Hours48 Hours
Low2 Hours8 Hours72 Hours

Escalation Tiers​

Tier 1 Support​

  • First point of contact for all IT-related issues
  • Responsible for initial troubleshooting and resolution

Tier 2 Escalation - Knowledge Issues​

Escalate to Tier 2 when:

  • The issue requires specialized knowledge
  • The resolution requires access to privileged systems
  • Resolution timeline exceeds Tier 1 SLA

Tier 2 Escalation - End User Issues​

  1. Attempt resolution through communication and troubleshooting
  2. If issue persists due to user error escalate to Tier 2 or a designated supervisor
  3. Supervisors engage with the end user to address concerns
  4. Policy violations or security breaches escalate to management and security teams

Escalation Procedures​

  • Document all interactions in the ticketing system
  • Escalation paths and contact information must be clearly defined and accessible
  • Escalation triggers are monitored and tracked
  • Regular review meetings assess effectiveness