Ticketing essentials for Technicians at the University of Oregon UO Service Portal training Sean, Ben, Meni & Patrick
Agenda UO Service Portal interfaces, environments and definitions Demo In class activity Review
Objectives By the end of this class, you will be able to… Log in to UO Service Portal and open the ticketing application Create a ticket Find tickets Update a ticket Set the ticket as “on hold” when waiting on information from the requestor Reassign the ticket Close the ticket
What’s not covered “Advanced” ticketing: Bomgar Service level agreements Surveys Department specific workflows
Interfaces and Environments
UO Service Portal Environments Sandbox: https://service.uoregon.edu/sandbox Production: https://service.uoregon.edu/
Side note about the sandbox Sandbox is refreshed regularly from production on the 1st Sunday of every quarter
UO Service Portal interfaces: Today - Green TDNext: For technichians TDNext is a responsive website TDClient: For end users, clients or customers who are requesting support https://service.uoregon.edu/tdnext/ https://service.uoregon.edu/tdnclient/
Common steps in working on a ticket
“Classification” in UO Service Portal Description Incident Break-fix issues Service request Request for common service Release Used as a parent ticket where you are needing to group up many service requests* *only use release when you need multiple requestors and multiple sets of tasks on individual tickets
“Status” in UO Service Portal Status Class New In Process Waiting for Customer On Hold Scheduled On Hold *On Hold will pause any active SLA Closed Completed Cancelled
Ticket creation: common fields Description Source Where did this ticket come from? Requestor Who is this ticket for? Acct/Dept Requestor’s department Service Services are things that can be ordered by users. Type Ticket types help identify what the issue is for reporting. Responsible Who will own this ticket. Title Short description of issue Longer description of issue, ideally with steps to repeat Location Where is this issue located? Impact How many people are affected? How widespread is this issue? (Only used for service outages) Urgency How severe is the issue to those affected? Priority Calculated by impact and urgency Due Date When should this ticket be completed?
Creating a Ticket
Ticket creation Go to TDNext (https://service.uoregon.edu/sandbox) Click on the "waffle" (upper left hand side) Go to “Tickets” application Click “New Service Request” Choose requestor Look up by Duck ID Choose form Populate fields Save
Updating a Ticket
Ticket updates 1. Select the ticket Usually: Actions > Update Comments & response templates Public vs. private updates Attributes to update Notify to email the update Feed updates and notifications include all changed data Tickets update every 5 mins. You have to refresh. There is no auto-refresh
Response Templates Used as a script for commonly requested issues that usually need clarification Helps provide consistent formatting of emails Similar to templates in RT
Update vs Comment Update- opens full ticket for updating multiple fields Comment – Adding a quick comment + notification option
Assigning Tasks Open ticket Select "Task/Activities" Select "+Add" and then select "Task" Fill out the fields and select "Save"
Find Tasks Assigned to You Select "Tickets" On left hand side select "Assigned to me" You will see tasks assigned to you listed Work the task assigned Complete the task
Follow up with user Use “On Hold” status Set “Goes Off Hold” date Notify user
Ticket escalation/ reassignment Use Actions > Reassign
Closing a Ticket
Ticket closure Use “Closed” Notify user
Closed tickets may reopen Tickets may reopen if requestors comment on them with in 10 days of the tech closing the ticket If a customer responds to a ticket after 10 days, the information from original ticket is cloned to a new ticket
Finding Tickets
Finding tickets with searches Go to TDNext Go to “Tickets” application Click on “Tickets” on the left Click on the green funnel on the upper right hand side Populate fields and click "Apply"
Other ways to find tickets Service Request ID (Ticket ID) Sending the link to another technician
Support for UO Service Portal Service.uoregon.edu Services Request help with the UO Service Portal UO Service Portal
Review
Agenda review UO Service Portal interfaces and environments Common steps in working a ticket Creating a ticket Finding tickets Updating a ticket Closing a ticket Review
Objectives recap By the end of this class, you will be able to… Log in to UO Service Portal and open the ticketing application Create a ticket Find tickets Update a ticket Set the ticket as “on hold” when waiting on information from the requestor Reassign the ticket Close the ticket
tHank You!