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

In the Customer Hub in Agent Desktop, a service agent can perform the following actions:

• Edit customer details: The agent can update the customer’s personal and business information, such as name, address, phone number, email, account, and contact person. The agent can also add or remove tags to the customer1.
• View customer details: The agent can see the customer’s basic information, such as name, address, phone number, email, account, and contact person. The agent can also see the customer’s tags, which are keywords that help to categorize and identify the customer1.
• Access interactions and notes in the timeline tab: The agent can view the chronological history of interactions with the customer, such as cases, calls, emails, chats, surveys, and visits. The agent can also see the notes that were added by other agents or by the customer2.

The agent cannot perform the following actions in the Customer Hub in Agent Desktop:

• Create a new e-mail message or a new case from the What Would You like to do? area: This action can only be done from the Communication Panel, which is a separate area in the Agent Desktop that shows the incoming and outgoing communication items, such as emails, calls, chats, and messages3.
• Launch a customer survey: This action can only be done from the Survey tabstrip, which is a separate tabstrip in the Customer Hub that shows the surveys that were sent to or received from the customer. The agent can launch a new survey from this tabstrip by selecting a survey template and a communication channel4.

References = 1: Customer Hub - SAP Online Help, 2: Timeline - SAP Online Help, 3: [Communication Panel - SAP Online Help], 4: [Survey - SAP Online Help]

In SAP Service Cloud Version 2, when a new case type is created and activated without assigning a service catalog, the recommended approach to address this oversight is to utilize the "Create New Version" action. This action allows administrators to create a new iteration of the existing case type, wherein the necessary service catalog can be assigned. Following the assignment of the service catalog, this new version of the case type can then be activated, effectively updating the case type configuration to include the previously omitted service catalog. This process ensures that the case type is correctly configured with all required components, including the service catalog, without the need to deactivate or delete the original case type

In SAP Service Cloud Version 2, access restrictions are governed by a set of rules thatdetermine user permissions and access levels. When there is a conflict between access rights, "Unrestricted access rights override any restrictions you have defined." This means that if a user is granted unrestricted access rights in one area, these rights will take precedence over any other specific restrictions that might have been set, ensuring that users retain access to critical functions and information necessary for their roles.

• 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 use mashups and actions to grant user access to an SAP S/4HANA transaction in SAP Service Cloud Version 2 as an administrator. Mashups are web-based applications that combine data or functionality from different sources, such as SAP S/4HANA. Actions are predefined or custom operations that can be executed on business objects, such as opening an SAP S/4HANA transaction. To enable user access to an SAP S/4HANA transaction, you need to create a mashup for the transaction URL and configure the relevant action to call the mashup. References = SAP Service Cloud Version 2 | SAP Help Portal, SAP Service Cloud Version 2 Integration Guides for SAP S/4HANA, SAP Service Cloud Version 2 Mashups, SAP Service Cloud Version 2 Actions

A determination is a rule that assigns a value to a field based on the value of another field or a calculation. For example, you can create a determination that sets the priority of a case based on the urgency and impact fields. A page layout, a workflow, and an autoflow are not used for field calculations. References = [Solution Guide for SAP Service Cloud Version 2 - SAP Online Help], [SAP Service Cloud Version 2 Feature Scope]

 To set up an organizational structure for a new implementation, the following options are possible:

• Assign an employee to several organizational units. This is possible by using the Employee Assignment function in the Organizational Management work center. An employee can be assigned to multiple organizational units with different validity periods and functions. For example, an employee can be a sales representative in one unit and a service agent in another unit.
• Use the Reporting Line function for selection. This is possible by using the Reporting Line function in the Organizational Management work center. This function allows the administrator to select an organizational unit and display its reporting line, which shows the hierarchical relationship between the unit and its parent and child units. The administrator can also edit the reporting line by adding, removing, or changing the position of the units. References =
• Setting up an organizational structure - SAP Learning, section Assigning Employees to Organizational Units, slide 8-9
• Set Up Guide for SAP Service Cloud Version 2, section Organizational Structure, page 11-12

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”

Creating an incident in SAP Service Cloud Version 2 involves utilizing the built-in support framework provided by SAP. This framework is designed to streamline the process of reporting and managing issues directly within the SAP ecosystem. Logging an incident through the SAP for Me portal is a critical step in this process, as it serves as a centralized platform for customers to access various SAP services, including support and incident management. Additionally, activating the Built-In Support feature within the SAP Service Cloud environment enables users to directly report issues from within the application, ensuring that incidents are captured accurately and routed to the appropriate support channels for resolution

When you create or edit an installed base, you can assign different objects to it at item level. The objects that you can assign are:

• Product: This is a generic product that is not serialized or tracked individually. You can assign a product to an installed base to indicate the type or category of the product that is installed at the customer site. For example, you can assign a product called “Laptop” to an installed base to represent any laptop that belongs to that installed base.
• Registered product: This is a serialized product that has a unique identifier and can be tracked individually. You can assign a registered product to an installed base to indicate the specific product that is installed at the customer site. For example, you can assign a registered product with a serial number “123456789” to an installed base to represent a particular laptop that belongs to that installed base. A registered product can also have warranty and maintenance plan information associated with it.
• Functional location: This is a logical or physical location where the products are installed or used. You can assign a functional location to an installed base to create a hierarchical structure of the installed base. For example, you can assign a functional location called “Office A” to an installed base to represent a sub-location within the installed base where some products are located. A functional location can also have other functional locations, products, or registered products assigned to it as sub-items.
• Maintenance plan: This is a plan that defines the schedule and scope of the maintenance activities for the products. You cannot assign a maintenance plan to an installed base at item level. A maintenance plan can only be assigned to a registered product as a sub-item. For example, you can assign a maintenance plan called “Annual Service” to a registered product to indicate the frequency and type of service that the product requires.
• Warranty: This is a contract that defines the terms and conditions of the warranty coverage for the products. You cannot assign a warranty to an installed base at item level. A warranty can only be assigned to a registered product as a sub-item. For example, you can assign a warranty called “Standard Warranty” to a registered product to indicate the duration and scope of the warranty that the product has. References = Using an Installed Base; Using Installed Bases and Registered Products

To link customer e-mails with cases, you need to do the following configuration steps in SAP Service Cloud Version 2:

• Maintain and activate at least one e-mail channel: You need to create an e-mail channel for each support e-mail address that you want to use to communicate with your customers. You also need to configure the settings for the e-mail channel, such as the technical e-mail address, the sender name, the sender e-mail address, and the reply-to e-mail address. You also need to verify and activate the e-mail channel, so that the incoming e-mails are forwarded from your company’s e-mail server to the tenant’s technical e-mail address.
• Create a case routing rule: You need to create a case routing rule for each e-mail channel, to define how the incoming e-mails are processed and assigned to cases. You can specify the criteria for the case routing rule, such as the e-mail channel, the sender e-mail address, the subject, or the body of the e-mail. You can also specify the actions for the case routing rule, such as creating a new case, updating an existing case, assigning a case type, assigning a team or a processor, or sending an auto-reply e-mail. References = Configuring Email, section Communication Channel Configuration - Email; Providing Expedited Service, section Inbound Email Linked to a Case.

 One of the main uses for warranty management in SAP Service Cloud Version 2 is to associate a warranty with a registered product. This allows the service agent toautomatically determine the warranty coverage and validity when creating a case for a customer who owns the registered product. The warranty can include information such as the duration, the coverage option, and the start date. The warranty is created in the Products work center and then assigned to the registered product in the Registered Products work center. References = Managing Warranties - SAP Learning, Creating a Warranty - SAP Learning, Solution Guide for SAP Service Cloud Version 2, page 88

Business roles are used to assign work centers and views to users, and also to define access restrictions and authorizations for each view. By using business roles, you can control which views are visible and editable for different users or groups of users. For example, you can restrict access to certain accounts, products, or tickets based on the user’s organizational unit, territory, or other criteria. References = Apply Access Contexts and Restriction Rules, Restricting access the right way in SAP Cloud for Customer

When creating a new business user in SAP Service Cloud Version 2, it is mandatory to maintain certain key elements. "Employee" information is crucial as it links the user account to an individual's employee record within the organization, providing context and defining the user's position and role within the company. Additionally, assigning a "Business role" is essential as it determines the access levels, permissions, and functionalities available to the user based on their responsibilities and tasks within the organization.

You can find existing cases in SAP Service Cloud Version 2 in two ways:

• In the My Cases Summary card available in the home page. This card shows you the number of cases assigned to you, grouped by priority and status. You can click on any of the numbers to open a list of the corresponding cases. You can also click on the View All button to see all your cases in a table view.
• In the case worklist by choosing the Case app from the menu. This app allows you to view, filter, sort, and search for cases based on various criteria. You can also create new cases, edit existing cases, and perform actions on cases from this app. References = Solution Guide for SAP Service Cloud Version 2, section Cases.

 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

 The categories in the service catalog can be used for service level determination, a filter option for the case summary, and case responsibility determination. Service level determination is the process of assigning a service level agreement (SLA) to a case based on the category and other attributes. A filter option for the case summary allows the user to view cases by category or subcategory. Case responsibility determination is the process of assigning a case to a service agent or a service team based on the category and other criteria. References = Configuring Categories, Creating the Statuses for Cases, Service Categorization with Machine Learning

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

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.

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

The language adaptation tool allows you to rename the labels of UI elements, such as thecases facet, in different languages. You can access the tool from the user menu by clicking on Settings and then Language Adaptation. You can select the language and the scope of the adaptation, and then search for the label you want to change. You can also export and import the adaptations as CSV files. References = Solution Guide for SAP Service Cloud Version 2, page 16.

The language adaptation tool allows you to rename the labels of UI elements, such as the cases facet, in different languages. You can access the tool from the user menu by clicking on Settings and then Language Adaptation. You can select the language and the scope of the adaptation, and then search for the label you want to change. You can also export and import the adaptations as CSV files. References = Solution Guide for SAP Service Cloud Version 2, page 16.