Presentation is loading. Please wait.

Presentation is loading. Please wait.

SERVICE MANAGER SERVICE DESK OVERVIEW June, 2011.

Similar presentations


Presentation on theme: "SERVICE MANAGER SERVICE DESK OVERVIEW June, 2011."— Presentation transcript:

1 SERVICE MANAGER SERVICE DESK OVERVIEW June, 2011

2 Service Desk - Overview 2  The Service Desk module will serve as the primary entry point for logging and tracking all incoming interactions to the IT Help Desk.  IT Help Desk Agents will close the interaction record if the issue is resolved on the first contact.  An Incident Ticket will be created from the interaction if the issue is a service disruption and cannot be resolved by the initial interaction taker.  If the interaction is considered an incident by the agent, they can categorize the ticket as an “incident”; regardless of whether the interaction is escalated to an Incident, the “incident” categorized interaction will be considered an incident for reporting purposes  An Incident Ticket will not be created for every interaction. Interactions closed without a related incident should be considered and reported as a “First Level Resolution”.  Agents will have the ability to save Interactions

3 Service Desk – Overview (cont’d) 3  Upon escalating an interaction to an incident, the system will provide the Agent a list of existing open incidents that may be related to the interaction that is being escalated  Designated Assignees will receive an e-mail notification for all Incidents P1 through P3…Pager Notifications will only be sent for Incidents P1 & P2  When a related incident is closed, the incident’s resolution information will be added to the related interaction record.  Customers will receive e-mail notification that their interaction has been closed  Agents will have the ability to create contact records from an interaction record if a customer contacts the Service Desk and does not have a Service Manager contact record

4 To Do List 4  Is accessible upon login  Provides a central point to navigate to the most common functionalities that one would perform in Service Manager

5 Navigator 5 The Navigator has two parts: Favorites and Dashboards – Contain frequently used queries and charts Menu Navigation – Contains the users Menu Options

6 Service Manager Form 6

7 Messages  Service Manager notifies you when you have activity messages to review. For example, each time you add or change a record, open or close an Incident, complete a task or an error occurs, Service Manager generates a message. 7

8 Smart Indicators 8 Appear adjacent to an input field when there are other records (incidents, interactions) related to the given field value and launches a form that allows the user to view related records

9 Buttons  Saves the content of the screen and takes user to previous screen/new interaction screen  Saves the contents of the current screen and remains on the current screen  Performs a query of the field table based on provided information and will “fill” the field if a single match is found; otherwise will display a filtered list of records.  Finds more information on the given field by taking the user to that record  Active when there are other records (incidents, interactions) related to the given field value and launches a form that allows the user to view related records  In the web client, this shows the user the list of system messages presented in their session  Allows user to print the details of current record 9

10 Creating a New Interaction 10 From the navigation pane, expand “Service Desk” and select “Register a New Interaction” 1. Fill out all pertinent information and click “save” to create record or “close interaction” to create the record and close. Note: Required fields are indicated by a red asterisk (*).

11 Service Desk Screen – Open Interaction 11 -Full Name present for all contact Information -Critical User bands -Editable location; populated from contact record -Building/Room/Floor populated from contact record -Critical CIs displayed on forms -Priority override for defined CIs

12 Notes Section 12 To enter in Patient information click on the more button. Notes can only be entered once an interaction becomes an incident. Click on Notes to open notes where patient data can then be entered

13 Notes Section (cont’d) 13 You will get this message stating that the note was saved User, date, and data will be displayed and remain in the notes section Click back to go to previous screen

14 Using Templates 14 1. From a new interaction, select “Apply Template” 2. Choose the appropriate template by double clicking. Note: The Service Desk Management team can create new templates 3. New interaction is now pre-populated.  In Service Manager, Templates replace Service Center “Cause Codes”

15 Updating an Existing Interaction 15 From the navigation pane, expand “Service Desk” and select “Interaction Queue” 1. Open record to be updated. 2. Make updates as needed including update type and notes and click save. 3. Select “Visible to Customer” if updates should be seen by customer. 4. Save Interaction record 5. Previous updates are stored in a journal fashion.

16 Closing an Existing Interaction 16 From the navigation pane, expand “Service Desk” and select “Interaction Queue” 1. Open record to be updated. 2. Make updates as needed. 3. Fill out solution and click, “close interaction”.

17 Service Desk Screen – Escalation 17 Allows Agents to pick from complete list of Assignment Groups Assignee is required prior to escalation

18 Customer Verification 18  For Critical Customers, the “notify by” will be set to “telephone”  When the incident is closed, the related interaction will move to an “open-callback” status, and appear in the “Interactions requiring customer verification “ queue  Agent will be prompted to enter “required actions” (call customer) prior to closure

19 Service Desk Screen – Required Actions 19 If a related incident is closed and the customer requires a callback, the tool forces the user to enter a “required action” where they must either: -Record that the customer confirmed the fix -Reopen the incident

20 Access  Feel free to access the test system at:  http://srvmgr-stage.johnshopkins.edu/smuat/index.do http://srvmgr-stage.johnshopkins.edu/smuat/index.do  Note: While single sign on will be enabled for the production system, it is deactivated in the test environment. Please login with your JHED ID only. No password is needed in the test environment.  Supported Browsers:  Internet Explorer 7 & 8  Firefox 3 & 3.5 (Windows and Mac) 20

21 Summary Points  Service Desk: the primary entry point for logging and tracking all incoming interactions to the IT Help Desk.  Notifications: E-mail will be sent to assignees for all P1-P3 Incidents. Pages will be sent only for P1 & P2 Incidents.  The “Go-Live” date for Service Manager is the evening of July 8, 2011. Service Center tickets will not be transferred over to Service Manager automatically…open Service Center tickets need to be closed if possible 21


Download ppt "SERVICE MANAGER SERVICE DESK OVERVIEW June, 2011."

Similar presentations


Ads by Google