Beruflich Dokumente
Kultur Dokumente
0 Interaction Center
Overview
Agenda
Customer
Telephony
Web Chat
IVR
Telesales
Account and contact management Lead and opportunity management Quotation and order management
Customer service
Customer service and support Complaint management Help desk
Shared services
Employee Interaction Center Accounting Interaction Center IT service desk
Communication channels
Communication analytics
Process-based analytics
Blended analytics
IT Service Desk
* Further types of SSC service desks can be implemented on project basis, for example facility management or procurement service desk.
SAP 2008 / IT Service Desk Overview / Page 4
IT Service Desk 1 1 2 2
Integration to SAP Solution Manager Service Desk
Incident Management
7 7
Problem Management 3 3
Change Management
SAP 2008 / IT Service Desk Overview / Page 5
5 5
4 4
The IT service desk is the first entry point for customers or employees who have a request with regards to the IT infrastructure. The IT service desk is built on the SAP CRM Interaction Center. A standard business role IT Service Desk Agent is available which, in addition to generic SAP CRM Interaction Center features, offers access to
Pre-defined process types for incident, problem, and request for change management, along the IT Infrastructure Library (ITIL) best practices Integrated knowledge article search and provisioning A pre-defined interface to SAP Solution Manager for exchange of incidents
IT service desk can be used in various scenarios: Internal scenarios IT department delivering IT support to other departments Shared Service Center (SSC) scenarios SSCs offering IT- as well as further internal services globally for one corporate group External scenarios IT service providers offering services to their customers
A customer (or employee) calls the IT service desk because a printer is not working.
The customer receives an e-mail notification which informs him or her about the successful completion of the incident.
The IT service desk agent creates an incident ticket and categorizes it.
The printer issue can easily be fixed on-site and the IT support employee closes the incident.
The agent checks remotely whether the printer is connected to the network, which is the case.
An employee of the printer support team finds the incident in the worklist and checks the printer on-site.
The agent searches for solutions in the knowledge article repository but cannot find a solution which fits. As the agent cannot solve the issue on the phone, the agent dispatches the incident to the printer support team.
Agenda
Scratch pad
Account info
Toolbar
Alerts
Communication information
Branding Area
Broadcast messages
Workspace
Agent Inbox
The IT service desk agent uses the inbox to monitor and process existing incidents, problems, requests for change, and other items. Amongst others, in the inbox you can select: CRM Business Transactions (incidents, problems, ...) Workflow items E-Mails You can: Predefine quick searches and saved searches Display the inbox in a tree and table view
Account Identification
On the Account Identification, the IT service desk can identify the customer as well as the affected object or installed base.
Agenda
You can create an incident from scratch or from a template. You can copy an existing incident You can create follow-up transactions from the incident, for example, a problem or a service confirmation
In the incident you have access to Create Follow-Up Dispatch Auto Complete Find Related Problems Find Knowledge Articles Unlock Print / Print Preview Display Object Relationships
SAP 2008 / IT Service Desk Overview / Page 16
An incident can be assigned and locked to a problem (or also a request for change). In this case the incident will not be processed individually. The completion of the problem (request for change) will automatically close the incident.
If an incident is locked to a problem (request for change) but the IT service desk agent would like to process it individually after all, the agent can select Unlock to open the incident again for processing.
Agenda
You can create a problem from scratch or from a template. You can copy an existing problem You can create follow-up transactions from the problem, for example, a knowledge article or a service confirmation
In the problem you have access to Create Follow-Up Dispatch Auto Complete Find Knowledge Articles Print / Print Preview Display Object Relationships
If several incidents are probably related to the same route cause, the IT service desk can assign these incidents to the problem. The IT service desk agent can search for the incidents via F4 help, or via Find Related Incidents.
Find Related Incidents gives a list of incidents which have the same (subject/reason) categorization as the problem. The IT service desk can select the relevant incident/s and assign them to the problem.
To stop individual processing of the incidents, the IT service desk agent can lock the incidents to the problem, so that only the problem needs to be completed and the locked incidents will then be automatically closed.
Agenda
You can create a request for change (RfC) from scratch or from a template. You can copy an existing RfC You can create follow-up transactions from the RfC, for example, a service confirmation
In the request for change you have access to Create Follow-Up Dispatch Auto Complete Find Related Problems Find Knowledge Articles Print / Print Preview Display Object Relationships
Then the agent sets the RfC status to Awaiting Approval The approval step partners can now approve or reject the relevant steps Approvers can be informed via SAP Workflow
On the Item tab page of the request for change, the IT service desk can enter service products and monitor existing items and their status.
Agenda
The incident / problem / request for change can be categorized on multiple levels with several categorization blocks
To auto complete an incident / problem / request for change, the IT service desk agent needs to select a categorization and the system can then find a template which was assigned to this categorization Problems with the same categorization as entered in the incident or request for change can be proposed by the system when choosing Find Related Problems Knowledge articles with the same categorization as entered in the incident / problem / request for change can be proposed by the system when choosing Find Knowledge Articles
To help solve an issue or process a request, the IT service desk agent can search for knowledge articles from the incident / problem / request for change:
Knowledge Articles tab page: The IT service desk agent can search for relevant knowledge articles via F4 help Find knowledge articles (from the More button on header level): Proposes knowledge articles which have the same categorization as the incident / problem / request for change Suggest knowledge articles (from the Knowledge Articles tab page): Proposes knowledge articles which are assigned to the incident / problem / request for change category in the categorization schema Search Knowledge Articles: Is only available in SAP CRM Interaction Center. Here the IT service desk agent can enter search parameters, select the appropriate knowledge article/s from a result list, add them to a cart and send them via e-mail to the customer.
Service and response profiles can be assigned to several SLA-relevant objects, such as contracts, products, objects, installed bases, and business partners. In the incident, problem, and request for change, the service and response profiles can be flexibly determined from these objects based on a determination procedure. Dates like ToDo By can be automatically calculated based on the service and response profile information.
Durations
The system can automatically calculate the duration of an incident / problem / request for change. Per default, two duration types are delivered:
Work duration: Calculates the time a transaction was in work, but not in status Customer Action Total duration: Calculates the total time it took to complete the transaction
Dispatch
Dispatching allows the IT service desk agent to dispatch incidents / problems / requests for change to other employees or service teams, for example if the agent cannot solve an issue remotely. Rules for dispatching are set up in the Rule Modeler.
Reference Objects
You can schedule and execute actions in the incident, problem, and request for change:
Escalation
When the due date of an incident, problem, or request for change is exceeded it can be escalated by a background action.
Escalation level is increased Escalation date is set
Due < Current?
Related Transactions
Processing Log
The processing log provides a consolidated audit trail of changes made to a transaction Various log types are available for selection One type can be defaulted for viewing Changes to fields can be logged selectively
Agenda
Increase IT services quality and transparency Increase customer satisfaction Cut service delivery costs
Drive continuous improvement through Analytics
Weitergabe und Vervielfltigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrckliche schriftliche Genehmigung durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen knnen ohne vorherige Ankndigung gendert werden. Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte knnen Softwarekomponenten umfassen, die Eigentum anderer Softwarehersteller sind. SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, SAP Business ByDesign, ByDesign, PartnerEdge und andere in diesem Dokument erwhnte SAP-Produkte und Services sowie die dazugehrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Lndern weltweit. Alle anderen in diesem Dokument erwhnten Namen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zu Informationszwecken. Produkte knnen lnderspezifische Unterschiede aufweisen. Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP. Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderen Vereinbarung mit SAP. Dieses Dokument enthlt nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP-Produkts und ist fr SAP nicht bindend, einen bestimmten Geschftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP bernimmt keine Verantwortung fr Fehler oder Auslassungen in diesen Materialien. SAP garantiert nicht die Richtigkeit oder Vollstndigkeit der Informationen, Texte, Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente. Diese Publikation wird ohne jegliche Gewhr, weder ausdrcklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschlielich, hinsichtlich der Gewhrleistung der Marktgngigkeit und der Eignung fr einen bestimmten Zweck sowie fr die Gewhrleistung der Nichtverletzung geltenden Rechts. SAP bernimmt keine Haftung fr Schden jeglicher Art, einschlielich und ohne Einschrnkung fr direkte, spezielle, indirekte oder Folgeschden im Zusammenhang mit der Verwendung dieser Unterlagen. Diese Einschrnkung gilt nicht bei Vorsatz oder grober Fahrlssigkeit. Die gesetzliche Haftung bei Personenschden oder die Produkthaftung bleibt unberhrt. Die Informationen, auf die Sie mglicherweise ber die in diesem Material enthaltenen Hotlinks zugreifen, unterliegen nicht dem Einfluss von SAP, und SAP untersttzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewhrleistungen oder Zusagen ber Internetseiten Dritter ab. Alle Rechte vorbehalten.
SAP 2008