UCL Service Desk Agent Playbook
This page documents the best practices in managing the service desk from the service desk agent perspective.
Tier 1
Tier 1’s role, etc.
Process For Handling Cases
Confirm Contact details are correct on Case Submission
Complete Case, if possible
If not possible, assign to appropriate queue for Tier 2 processing.
For Cases that belong to programs, change Record Type to Program Support and then assign to the appropriate program Queue.
Case Reasons
Reason |
|
---|---|
Configuration update |
|
Data request |
|
Equipment request |
|
Not Supported/Declined |
|
Permissions request |
|
Scheduling request |
|
Software request |
|
Training |
|
Project request |
|
Incident |
|
Other |
|
Queues
Queue | Description | Request Types |
---|---|---|
Operations | This queue is for incoming Operations cases. |
|
Technology Services Support | This queue is for incoming Technology Services Support cases. |
|
Incident Management | Placeholder for ISM Incident Management. Notification: Queue email address ce-systems@utah.edu |
|
Information Systems Management | This queue is for incoming Information Systems Management cases. |
|
Data Analytics | This queue is for incoming Data Analytics cases. |
|
Exam Services | This queue is for incoming Exam Services cases. |
|
Marketing | This queue is for incoming Marketing cases. |
|
Media Production | This queue is for incoming Media Production cases. |
|
HR | This queue is for incoming HR cases. |
|
Tier 1 Support | Placeholder for Service Desk Management. |
|
Unknown |
|
|
Notes:
If a person named in the text of the case (example: Hello Angie, etc.), then the case can be directly assigned to said person. Always make sure the send email notification box is checked before assigning the case.