Handling tickets
- You’ll get an email when someone submits a request or one is moved to your queue which contains a link you can click to open in Zoho.
- It may be easier to simply go to Nexus Service Desk Admin website to see all requests
- Pick tickets from the queue you are working and fill out details of ticket with customer info to start (details below in Training/FAQ section).
- There are three ways to work on a ticket:
Reply (on website): emails person. Reply to email (of new ticket) also emails person
Comment: Private - does not go to person, use for detailed repair notes, equipment models, etc. Public comments are seen by all and emails the ticket requestor and any registered CC'd contacts.
- Resolution: how it was fixed, doesn’t go to person unless you tick ‘Notify Contact’
- Reply or Comment to indicate you’re working on the issue so the person (& other techs) know. We aim to respond within 15 minutes at T1. Either to acknowledge receipt of issue, notify work in progress, or request additional details such as screenshot/model/serial #s/ etc.
- Status: Set to "Waiting for customer" after replying or finishing any work that can be done without input. Set to "On Hold" if you’re waiting on parts or external, non-Nexus 3rd party. Automatically changes to open upon receiving any reply.
- Close Ticket (bottom-right): indicates the problem is resolved. By default, and in general, emails the requestor and if you reply and close does generate a separate response and closure email - this is okay and expected.
- I usually like to ask person if it’s OK to close as resolved. There are going to be many cases where an experienced tech is confident an issue is resolved (such as adding to/removing from distribution lists) where you do not need to confirm. Use your judgement.
1. Press the @ key
2. then their first name
3. Then click on their name
This Works in Zoho Desk and Teams
The agent will not usually be emailed unless you tag them.
They will not always be emailed even if you tag them.
Sometimes they will be emailed if they are not tagged (if no one has accepted assignment of the ticket yet, for example.)
Please follow up with the agent via Teams, phone call, or in person, if they don't respond to a tag.
Training/FAQ/Important Elements of a Ticket
|
Field
|
Required?
|
Expected Data
| Example/Explanation |
|
Contact Name
|
Yes
|
Full name of customer
|
Pulled from contact properties |
| ContactLookup | Yes | Search with First, Last or Email (should display Last when complete) | Matches zoho contact properties |
|
Email
|
Yes
|
Email address of customer
| Internal/external as appropriate |
|
Title
|
Yes
|
Job Title of Customer
|
|
|
Organization
|
Yes
|
Assigned Company of Customer
| Agency name in Nexus-(agency) format or SERCC/Walden Crossing/Aspen House |
|
Phone Number
|
Yes
|
Valid phone number that can reach the Customer
|
|
|
Tags
|
No
|
*
|
|
|
Contact Agency
|
Yes
|
Assigned Company of Customer
|
|
|
Phone
|
Yes
|
Valid phone number that can reach the Customer
|
|
|
Request Type
|
Yes
|
Other is not a valid response
| Add/Change/Move/Troubleshoot |
|
Product Name
|
Yes
|
Product Family/Brand/Platform
*
| Dell Laptop/Hardware/Peripheral/
3CX/etc.
|
|
Device Name
|
No
|
Hardware name, as applicable
|
|
|
Program/Department
|
Yes
|
Department of the Customer
| Minimum: department code
|
|
Location
|
No
|
Physical location of the issue or remote / off-site
*
| Most agencies have separate programs/locations/department options - i.e. Admin, Nursing, "Marseille", "P4", "Castle", etc. |
|
Priority
|
No
|
Internal use field. Not currently tied to SLA timers.
|
|
|
Channel
|
Yes
|
Closest available option to the submission method
| Email/Chat/Phone/etc. |
|
Classification
|
No
|
*
| Question/Problem/Feature/Others
|
*potential changes and
revisions to come later