Master the Salesforce CRT-261 Exam: Essential Study Tips and Strategies

Salesforce Console for Service is a tool that can implement the requirement of displaying a history of all of today’s changes to a case in the order that occurred on a single page view. Salesforce Console for Service is a workspace that allows agents to manage multiple cases and interactions on a single screen. It includes a feed-based layout that shows a history of all the changes to a case, such as comments, emails, and edits to case fields, in chronological order. Verified References: : https://help.salesforce.com/s/articleView?id=sf.console2_overview.htm &type=5 : https://help.salesforce.com/s/articleView?id=sf.console2_feed_based_layouts.htm &type=5

Interaction Log and Path for Cases are features that a consultant should integrate into the Service Console to assist agents with a standardized agent-customer dialog. Interaction Log is a component that allows agents to log notes and activities related to a record, such as calls, emails, tasks, or events. Agents can use the Interaction Log to capture important information from their conversations with customers and track their actions. Path for Cases is a feature that allows agents to see where they are in the process of resolving a case and what steps they need to take next. Path for Cases displays key fields and guidance for each stage of the case lifecycle, such as New, Working, Escalated, or Closed. Agents can use Path for Cases to follow a consistent and effective support process. Verified References: Service Cloud Consultant Certification Guide & Tips, Use the Interaction Log Component, Set Up Path for Cases

Attachments and .html files in Classic Knowledge are moved to the Files object, Visualforce pages refer to Classic article types, and article numbers change during migration are statements that should be considered when migrating an existing knowledge base into Salesforce Lightning Knowledge. These statements reflect some of the changes and challenges that may occur during the migration process. For example:

• Attachments and .html files in Classic Knowledge are moved to the Files object because Lightning Knowledge does not support attachments on articles. Files can be related to articles using rich text fields or file fields.
• Visualforce pages refer to Classic article types because Lightning Knowledge does not support Visualforce pages on articles. Visualforce pages need to be replaced with Lightning components or other solutions.
• Article numbers change during migration because Lightning Knowledge uses a different numbering system than Classic Knowledge. Article numbers are prefixed with KA in Lightning Knowledge instead of KB in Classic Knowledge.

Verified References: Service Cloud Consultant Certification Guide & Tips, Migrate Your Salesforce Classic Knowledge Base to Lightning Knowledge

This solution will meet the requirements, as Process Builder can be used to create workflows that send notifications to the product development team based on case criteria, such as priority and product type. Case teams can be used to help agents collaborate with other teams, such as product development, by granting them access to the case and displaying them in a related list on the case detail page. Verified References: Set Up Case Teams and Process Builder Overview

These are two reasons why the integration is failing after migrating from Classic Knowledge to Lightning Knowledge. The URL formats for articles change when migrating from Classic Knowledge to Lightning Knowledge, so any integration that relies on URLs needs to be updated accordingly. Also, users need to have Modify All permission on the article type object to delete archived articles in Lightning Knowledge, whereas in Classic Knowledge they only needed Delete permission on the article type object. Verified References: : URL Formats for Articles Change When Migrating from Classic Knowledge to Lightning Knowledge : Delete Archived Articles in Lightning Knowledge

These are two actions that can address the lack of quality checking in the Knowledge One widget in the Salesforce Console. Setting up an intuitive Data Category hierarchy is an action that can help organize and filter knowledge articles by topic or type. Data Categories can help agents find relevant articles based on their search criteria or case information. Enabling and configuring wildcards for article searches is an action that can help improve the accuracy and flexibility of article searches. Wildcards are symbols that can be used to replace one or more characters in a search term, such as * or ?. Wildcards can help agents find articles that match partial or variant words. Verified References: : https://help.salesforce.com/s/articleView?id=sf.knowledge_categories_overview.htm &type=5 : https://help.salesforce.com/s/articleView?id=sf.knowledge_categories_manage.htm &type=5 : https://help.salesforce.com/s/articleView?id=sf.knowledge_search_wildcards.htm &type=5

Embedded Chat Window is the functionality that a consultant should recommend implementing to resolve the issue of heavy amount of phone calls and customer complaints about the hold time. Embedded Chat Window is a feature that allows customers to interact real-time with support agents from their computers and mobile devices. Embedded Chat Window can be added to any website or mobile app with a few lines of code. Customers can initiate a chat session by clicking on a chat button or widget, and agents can respond using the Service Console. Embedded Chat Window also supports features such as pre-chat forms, chat transcripts, chat transfer, file transfer, and chatbot integration. Embedded Chat Window can help reduce the volume of phone calls and improve customer satisfaction by providing an alternative and convenient channel for customers to get support for complex product issues. Verified References: Service Cloud Consultant Certification Guide & Tips, Embedded Chat Service Overview

Enabling suggested articles on new cases, enabling article submission during case close, and creating an email template to send articles as PDF attachments are recommendations that a consultant should make to assist agents with the resolution of cases using Knowledge. Suggested articles are a feature that automatically recommends relevant articles to agents based on the case information. Agents can view the suggested articles in the case feed or the knowledge sidebar, and attach them to the case or email them to the customer. Article submission during case close is a feature that allows agents to create new articles or update existing articles from the case resolution page. Agents can use this feature to capture and share their knowledge after resolving a case. An email template is a type of template that can be used to create and send emails from Salesforce. An email template can include merge fields, images, links, and other formatting options. An email template can also include a knowledge article as an attachment or a link. Agents can use this feature to send an email with the article to the customer from the case record page or the Service Console. Verified References: Service Cloud Consultant Certification Guide & Tips, Suggested Articles Overview, Submit Articles During Case Close, Create Lightning Email Templates

Using an auto-launched flow to capture details is the recommended method to consistently capture new caller details. An auto-launched flow is a type of flow that runs in the background without user interaction. An auto-launched flow can be triggered by various actions, such as creating a record, updating a field, clicking a button, or invoking a process. An auto-launched flow can perform various tasks, such as collecting inputs, updating records, creating records, or calling external services. Using an auto-launched flow to capture details can help ensure that support agents enter the necessary information for new callers, such as their name, email address, phone number, or reason for call. Verified References: Service Cloud Consultant Certification Guide & Tips, Create an Auto-Launched Flow

This is the main consideration when enabling “Use standard Salesforce sharing” in Sharing Settings under Knowledge Settings, because it changes how article access is controlled. When this setting is enabled, article access is controlled by organization-wide sharing defaults and sharing rules, instead of data categories and data category visibility settings. This means that data categories are only used for filtering and organizing articles, not for restricting access. Verified References: : Control Article Access with Sharing Settings