C_C4H56I_34 SAP Certified Application Associate - SAP Service Cloud Version 2 Questions and Answers

Service agents in SAP Service Cloud Version 2 can create cases directly from the Agent Desktop by clicking the Create button and selecting Case. This method provides a quick and straightforward way to initiate a new case while working within the Agent Desktop environment. Additionally, cases can be created from the Related Service Object facet of registered products. When viewing the details of a registered product, agents can use the Create button within this facet to initiate a case related to that specific product, ensuring the case is automatically linked to the relevant product record.

 End users can access the Customer Hub screen in Agent Desktop in two ways: manually by performing a customer identification via Agent Desktop, or automatically when an incoming phone call from a known customer is accepted. The Customer Hub screen provides a comprehensive view of the customer’s profile, interactions, cases, and registered products. It also allows end users to create new cases, tasks, or activities for the customer. To access the Customer Hub screen manually, end users need to enter the customer’s phone number, email, or name in the search field and select the customer from the search results. To access the Customer Hub screen automatically, end users need to enable the automatic customer identification feature in the Agent Desktop settings. This feature will display the Customer Hub screen for the incoming phone call if the caller’s phone number matches a customer record in the system. References = Solution Guide for SAP Service Cloud Version 2, section “Agent Desktop” and “Customer Hub”

When creating a case, you need to enter the mandatory attributes that are marked with an asterisk (*) in the user interface. These attributes are status and subject. Status indicates the current state of the case, such as new, in process, or completed. Subject is a brief description of the case that helps to identify and categorize it. Installed base and case type are optional attributes that you can use to provide more information about the case, such as the customer’s assets or the nature of the service request. References = Solution Guide for SAP Service Cloud Version 2, section “Cases”

For service levels in SAP Service Cloud Version 2, the "Initial review date" is a significant milestone that can be used to track and manage service commitments. This milestone marks the scheduled date for an initial evaluation or review of the service provided, ensuring that service level agreements (SLAs) are being met and that any issues are identified and addressed in a timely manner. This helps in maintaining high service standards and customer satisfaction.

To control the access rights of a user, you can use the following options:

• Assign employee to organizational unit: By assigning an employee to an organizational unit, you can define the scope and responsibility of the user within the organizational structure. The organizational unit determines the access rights of the user to the data and transactions related to that unit, such as cases, service orders, contracts, and products. For example, you can assign a service agent to a specific service team or region, and restrict their access to the cases assigned to that team or region.
• Assign restriction rules: By assigning restriction rules to a business role, you can further limit the access rights of the user to the data and transactions based on certain criteria, such as status, priority, category, or territory. Restriction rules can be applied to read and write access, and can be defined for different business objects, such as cases, service orders, contracts, and products. For example, you can assign a restriction rule to a business role that allows the user to read only the cases with high priority, or to write only the cases with open status.

References = Setting up user access rights and restrictions, Org Structure

To control the access rights of a user in SAP Service Cloud Version 2, one can "Assign an employee to an organizational unit," which sets the user's access level based on their role within the organizational structure. This ensures that users have access only to the information and functions relevant to their position. Another method is to "Assign restriction rules," which allows for the specification of detailed access controls based on various criteria, further refining what users can see and do within the system, ensuring data security and compliance with business policies.

To give service agents access to knowledge base articles in SAP Service Cloud Version 2, administrators need to perform specific configurations within the system. This involves maintaining the settings for the knowledge base provider, which could be an internal solution or a third-party service integrated with SAP Service Cloud. By properly configuring these settings, the system can connect to the knowledge repository and retrieve relevant articles. Additionally, setting up the knowledge base articles within SAP Service Cloud is essential. This setup includes defining article structures, content, and access permissions to ensure that agents can efficiently find and utilize the information to assist customers, thereby enhancing the quality and speed of service

Setting up SAP Service Cloud Version 2 involves several critical steps to ensure the system is configured correctly for organizational needs. One of the essential steps is "Assigning employees to organizational units," which involves mapping employees to specific divisions, departments, or groups within the organization. This step is crucial for defining roles, responsibilities, and reporting structures. Another fundamental step is "Creating an organizational structure," which lays the foundation for the system's operational framework. This structure defines the hierarchical arrangement of lines of authority, communications, rights, and duties of an organization. It is vital for establishing clear governance, operational efficiency, and effective management of the SAP Service Cloud environment.

The adaptation tool allows you to add a new button or a new field to the user interface of SAP Service Cloud Version 2. You can also change the properties of existing buttons and fields, such as the label, the visibility, the data binding, and the actions. However, you cannot create a new URL mashup using the adaptation tool. To create a new URL mashup, you need to use the administration tool. References = Solution Guide for SAP Service Cloud Version 2, section “Adaptation”, page 33.

• Option C is correct because the customer will need to provision new tenants through SAP for Me, which is a self-service portal that provides access to SAP products, services, and support12.
• Option D is correct because the business settings will need to be activated for the tenant, which enables the tenant to use the features and functions of SAP Service Cloud Version 23.
• Option A is incorrect because the administrator does not need to create an initial user in order to log in to the tenant for the first time. The initial user is created automatically by SAP and the credentials are sent to the customer via email3.
• Option B is incorrect because any test tenant does not need to be purchased separately. The customer can choose to purchase a test tenant along with the production tenant, or request a test tenant later through SAP for Me2. References =
• Defining the Scope - SAP Learning
• Solution Guide for SAP Service Cloud Version 2
• Version 2 Onboarding Guide for SAP Service Cloud
• Set Up Guide for SAP Service Cloud Version 2 - SAP Online Help

E-mail templates are used to define the fixed content (such as subject or disclaimer) andvariable parts (such as the form of address) of the email responses that service agents send to customers. E-mail templates can also be customized to include the corporate branding, such as logos, colors, fonts, and signatures, according to the needs of the service organization. E-mail templates can be created and maintained using the Configuring Email app in SAP Service Cloud Version 2. References = Configuring Email - SAP Learning, Maintain Email Templates | SAP Help Portal, Configuring Email Templates - SAP Customer Data Cloud, Configuring Email Templates | SAP Help Portal

• Agent Desktop: This is the main user interface for service agents to manage customer interactions, cases, and tasks. It consists of several components, such as the Communication Panel, the Customer Hub, the Case Hub, and the Task Hub12.
• Templates: These are predefined sets of data that can be used to create or update objects, such as cases, emails, surveys, and reports. Templates can help to standardize and automate processes, as well as save time and effort34.

The following services cannot be activated in SAP Service Cloud Version 2:

• Live activity configuration: This is a feature of SAP Sales Cloud, not SAP Service Cloud. It allows sales representatives to track and record their interactions with customers, such as calls, emails, meetings, and tasks5.
• Initial user: This is not a service, but a user account that is created during the tenant activation process. The initial user has full access to the solution and can perform administrative tasks, such as creating other users, assigning roles, and configuring settings.

References = 1: Agent Desktop - SAP Online Help, 2: SAP Service Cloud Version 2 Feature Scope, 3: Templates - SAP Online Help, 4: SAP Service Cloud Version 2 Feature Scope, 5: Live Activity Configuration - SAP Online Help, : Onboarding Guide for SAP Service Cloud Version 2 - SAP Online Help

You can use a custom field to determine Service Level Agreements (SLAs) in SAP Service Cloud Version 2. A custom field is a user-defined field that can be added to various objects, such as accounts, cases, products, or service levels. You can use custom fields to store additional information that is not available in the standard fields. You can also use custom fields as criteria for SLA determination, by creating rules based on the values of the custom fields. For example, you can create a custom field called “Customer Type” and assign different values to it, such as “VIP”, “Regular”, or “New”. Then, you can create rules that assign different SLAs based on the customer type. This way, you can customize the SLAs according to your business needs and customer preferences. References = Configuring Service Levels, section Maintain Rules for SLA Determination; Creating Custom Fields, section Create Custom Fields.

• Option A is correct because the administrator must obtain API token credentials from the CTI provider in order to configure the phone integration in Agent Desktop1.
• Option D is correct because the administrator must integrate with a third-party CTI provider in order to enable the phone channel in Agent Desktop2. SAP Service Cloud Version 2 doesnot have native CTI, so a CTI widget adapter is used to connect the CTI provider with the Agent Desktop3.
• Option B is incorrect because the administrator does not need to add a mashup service in Agent Desktop to enable the phone channel. A mashup service is used to integrate external applications or web pages into the Agent Desktop, but it is not required for the phone channel.
• Option C is incorrect because the administrator does not need to add the phone channel to the live interaction widget to enable the phone channel. The live interaction widget is used to display the incoming and ongoing interactions from various channels, but it does not control the activation of the phone channel. References =
• Configuring Phone - SAP Learning
• SAP Service Cloud Version 2 Integration - Sinch
• Agent Console Add-On for SAP Service Cloud - SAP Online Help
• [Mashup Services - SAP Online Help]
• [Live Interaction Widget - SAP Online Help]

Enabling the phone channel in Agent Desktop within SAP Service Cloud Version 2 requires integration with external telephony solutions to facilitate voice communication capabilities. This integration is achieved through collaboration with a Computer Telephony Integration (CTI) provider. The essential steps involve obtaining API token credentials from the chosen CTI provider, which are necessary for authenticating and establishing a secure connection between the SAP Service Cloud and the telephony system. Additionally, the integration process involves configuring the necessary settings and parameters within the Agent Desktop to ensure seamless communication flow and functionality, leveraging the capabilities and services offered by the CTI provider

 You can assign maintenance plans and registered products to an installed base. A maintenance plan defines the schedule and scope of service activities for an installed base or a registered product. A registered product is an instance of a product that is associated with a specific customer. You can create and assign maintenance plans and registered products using the Installed Base work center. References = Using an Installed Base, page 4 and 7.

Case routing in SAP Service Cloud Version 2 is a mechanism that automatically directs incoming cases to the appropriate service teams or individuals based on predefined criteria. The "Service Category" is one of the primary criteria used in case routing. It categorizes cases based on the nature of the inquiry or issue, ensuring that they are directed to the team with the relevant expertise. Additionally, the "Service Team" is determined during case routing, which involves assigning cases to specific groups of service agents or teams who are equipped to handle them. This ensures that cases are managed by the most suitable and knowledgeable personnel, facilitating efficient resolution.

 According to the SAP Service Cloud Version 2 documents and learning resources, the following actions can be executed by a Service Agent from the case “More Action” button:

• Summary. This action allows the Service Agent to create a summary of the case, which is a concise and informative description of the case details, such as the subject, the priority, the status, the category, the resolution, and the next steps. The summary can be used to communicate the case progress to the customer or to other stakeholders.
• Mark as unread. This action allows the Service Agent to mark the case as unread, which means that the case will appear as new in the Agent Desktop and will require the Service Agent’s attention. This action can be used to remind the Service Agent to follow up on the case or to delegate the case to another Service Agent.
• Escalate. This action allows the Service Agent to escalate the case to a higher level of authority or expertise, such as a manager or a specialist. The escalation can be triggered manually by the Service Agent or automatically by the system based on predefined criteria, such as the case priority, the SLA, or the customer satisfaction. The escalation can also involve sending notifications, changing the case status, or reassigning the case to another team or employee.

The other options are not correct because:

• Delete. This action is not available from the case “More Action” button. Deleting a case is a permanent action that removes the case and all its related data from the system. Deleting a case can only be done by an administrator or a user with the appropriate authorization in the Cases work center.
• Handover. This action is not available from the case “More Action” button. Handing over a case is a temporary action that transfers the ownership and responsibility of the case to another Service Agent for a specific period of time. Handing over a case can be done by the Service Agent or by the system based on predefined rules in the Settings > Cases > Case Handover view. References = Using Agent Desktop with SAP Service Cloud, Creating a Case Type, Configuring Case Escalation, Configuring Case Handover

You can adapt the status schema of a case type by adding or removing statuses in the existing status schema, or by creating a new version of a status schema. Adding or removing statuses allows you to customize the support process for different case types. Creating a new version of a status schema enables you to modify the existing status schema without affecting the cases that are already using it. You cannot copy or change the existing status schema directly, as this would impact the existing cases and their service level agreements. References = Creating the Statuses for Cases, Creating a Case Type

In SAP Service Cloud Version 2, there are three types of account to choose from: business or company customer (referred to as Account), individual customer, and contact. Contacts are associated with accounts and can have different roles, such as decision maker, influencer, or end user. Individual customers are accounts that represent a single person, such as a consumer or a sole proprietor. Channel partners are not a separate account type, but a role that can be assigned to an account. Groups are not an account type, but a way to organize accounts into categories, such as industry, region, or segment. References = Creating Customer Account Master Data, SAP Service Cloud Version 2 Feature Scope Description

 To create a New product in SAP Service Cloud Version 2, you need to specify the product group and the unit of measure as mandatory elements. The product group defines the category of the product and the unit of measure defines the quantity of the product. Sales area data and price are optional elements that can be added later or maintained in other systems. References = Solution Guide for SAP Service Cloud Version 2, page 88, [Create Products | SAP Help Portal]

In the All Cases worklist app, the following standard charts for cases are available:

• Cases by Source/Channel: This chart shows the distribution of cases by the source or channel from which they were created, such as email, phone, web, or chat. You can use this chart to analyze the preferred communication methods of your customers and the workload of your service agents.
• Cases by Priority: This chart shows the distribution of cases by the priority level that was assigned to them, such as low, medium, high, or urgent. You can use this chart to monitor the urgency and importance of your cases and prioritize your service actions accordingly.
• Cases by Category: This chart shows the distribution of cases by the category that was assigned to them, such as product, service, or complaint. You can use this chart to identify the main types of issues or requests that your customers have and improve your service quality and efficiency. References = Creating the Statuses for Cases; All Cases Worklist

To integrate external systems into Agent Desktop, you need to have SAP Event Mesh and SAP Cloud Integration as prerequisites. SAP Event Mesh is a cloud-based event bus that enables applications to communicate with each other using events. SAP Cloud Integration is a cloud-based integration platform that allows you to connect your applications with other SAP and non-SAP cloud and on-premise applications. These components enable you to create mashups that integrate external system functions into Agent Desktop, such as creating service orders and service quotations in SAP S/4HANA or SAP S/4HANA Cloud Service Management. References = Integrate External SAP Systems into Agent Desktop with Mashups | SAP Help Portal, Introducing Agent Desktop in SAP Service Cloud Version 2 - openSAP Microlearning