Escolar Documentos
Profissional Documentos
Cultura Documentos
Why Remedy
Remedy Implementation Objectives
What can support persons do with Remedy
Process Flow of a Ticket
Using Remedy
Why Remedy
Envisaged as a common Helpdesk tool for functions which involve an issue resolution workflow
Embracing industry best practices in service management
Automate our ability to submit, monitor, and manage help desk cases, change requests, and asset
inventory records.
Manage the entire range of service level agreement (SLA) processes
Bring down the number of incidents
Proactive root cause handling
Knowledge management/Self help
Reduce the cycle time for incident resolution
Auto ticketing
Auto assignment
Prioritization
Better issue capture and reporting Proactive problem solving
By implementing Remedy across GSD, NSS, HR etc; it would help present a common face to
the internal customer, for all his issue resolution needs
What Support person can do with Remedy
Creation of a Ticket
Automatic assignment of new ticket will be done to the relevant support group based on
Category, Type, Item and Location of user.
In case of reopening of ticket, the ticket will be automatically reassigned to the group that had
worked on it last
A notification regarding all reopened tickets will be sent to the group that had worked on it last.
Ticket Statuses in Remedy
This status signifies that
As soon as a call is logged in
the ticket has been
Remedy, status of ticket is set
closed by the requester
or it has auto closed to Assigned and the ticket is
upon expiry of a certain assigned to respective process
period. group
Auto closure happens
Closed Assigned The support person then
when the ticket is in manually changes the status of
resolved state for over ticket. Whenever support
a specific time period person picks the ticket, the
When a ticket is tickets gets assigned to him.
Reopened by the
requester, the ticket
comes back to the This status signifies that the
Assigned status and is Work In support personnel is working
Resolved
assigned to the process Progress on the ticket.
group again.
Common reasons are -
Intranet: https://gsd
Internet: https://gsd.cognizant.com
As the site is SSO Enabled logging in via Intranet site will directly take you to the home page of the site, where in for
Internet login you have to provide your credentials for authentication as shown below then you will land in the home page.
Your Home Page
Information Bulletin
applicable to you
Click here to
approve
solutions
Brief information of
the highlighted ticket
Logging Tickets
Viewing Ticket Details
Ticket Pickup: Assigning Tickets to Self
Click Create
request to
create a ticket on
behalf of a user
who is not able to
log tickets
himself
Enter Issue Details
Click on Refresh to
view other tickets
logged by the same
user
Highlighted Solution
Available! button indicates
Click Save to create solution present for this CTI.
ticket for the user Click to view solution
Using Remedy
Logging Tickets
Current status of
the ticket
Indicates if the
ticket has crossed
SLA and has been
escalated
To be used in
cases where ticket
is being
transferred to
another group or
another person
from the current
support group has
to work on it due
to shift change
Indicates the
changes on the
ticket so far, like
change in CTI,
priority, status etc.
View Ticket: Solutions, SLA, Attachments
Clicking Attachments
tab will show all
attachments added by
the user/process owner
to this ticket
Logging Tickets
Logging Tickets
1. Assigned As soon as call is logged in Remedy, status of ticket is set to Assigned and the
default assignment group is GSD
2. Work in The ticket status should be changed to Work in Progress by a support person
after it is assigned to him and he starts working on it
Progress
3. Pending To be used when the Support person cannot continue working on the ticket due
to reasons out of his control. Commonly used reasons are -
Requester information: Need some information from the requester; You will
receive a mail when the user provides you the requested information
For Approval : Managers Approval to be attached to proceed further
Parts: Some part of the request is resolved and some is pending
4. Resolved Indicates that the solution has been provided for the ticket
5. Closed Ticket closure will be initiated by the user and the support person cannot use
this status
When the user closes the ticket himself or the ticket gets automatically closed
due to the user not responding to the closure request, the status of the ticket will
become Closed
Using Remedy
Logging Tickets
Viewing Ticket Details
Ticket Pickup: Assigning Tickets to Self
Updating / Modifying the Ticket
Logging Tickets
Logging Tickets
After resolving a
ticket the support
person has to provide
a closure code for the
ticket, all closure
codes except
Automatically
Closed can be used
Closure Code most commonly used
1 Successful The resolution has been successfully provided for the request
2 Automatically closed Cannot be set by the support person. Is set when the user ignores
(automatically populated) the notification regarding the resolution and does not close or
reopen the ticket
4 Successful with Problems The ticket could only be partially resolved
Back
Closing the tickets
Best Practice: Closure of the ticket should be initiated through the users
User will receive a mail asking him/her to close the ticket once it is resolved
If user is satisfied he/she can close the ticket, else can reopen it
In case user does not do either of the actions, the ticket will be automatically closed.
The support person cannot under any circumstances close a ticket
Back
Using Remedy
Logging Tickets
Logging Tickets
Logging Tickets