In a Case History report , Salesforce tracks field changes for any fields that have field history tracking enabled. For each tracked field, the Old Value and New Value are recorded, providing an audit trail of how and when data changed. These two fields — Old Value and New Value — are available for viewing only and cannot be edited or updated.

This report helps service managers analyze how cases evolve over time and identify process bottlenecks or data integrity issues.

Option A is incorrect because “Data Type” is not a tracked field in history reports.

Option B is incorrect because the “User” field (who made the change) is editable in user management, not view-only within this report type.

Referenced Salesforce Materials:

Service Cloud Consultant Exam Guide – Contact Center Analytics Domain.

Salesforce Help: “Case History Reports and Field History Tracking Behavior.”

Salesforce Trailhead: “Track Field History for Auditing and Reporting.”

To enable case creation without login while preventing spam, using Web-to-Case with reCAPTCHA enabled is recommended. reCAPTCHA provides an additional layer of security by verifying that case submissions are made by humans, effectively reducing the likelihood of spam cases and maintaining the integrity of case data in Salesforce.

By creating a separate folder for quick texts for each product line and sharing these folders with respective public groups associated with each product line ' s support reps, Universal Containers can ensure that support reps have access only to the quick texts relevant to their product line. This approach maintains organized access control and supports standardization while catering to the unique needs of each product line.

To maintain article quality while increasing the number of Knowledge articles, implementing an approval process for article creation is recommended. This process allows for the vetting of articles by subject matter experts or managers before publication, ensuring that only high-quality content is made available in the knowledge base.

Agentforce for Service includes standard topics out-of-the-box that cover core customer service interactions such as:

Account and Case Management (viewing or creating support tickets),

Knowledge-Based Question Answering , and

General Information Inquiry Topics .

Option C — Answering a question about insurance policy and enabling the customer to open a new support ticket — fits within these standard topics without requiring customization. The Service Agent can automatically retrieve policy information from Salesforce Knowledge and launch the standard “Open Case” topic for ticket creation.

Option A (warranty claims and inspection scheduling) and B (real-time stock level lookup) require custom topics and actions , as they depend on external integrations and unique business processes beyond standard Service Agent scope.

Referenced Salesforce Materials:

Salesforce Spring ’24 Release Notes – Agentforce for Service: Standard Topics Overview.

Service Cloud Consultant Exam Guide – Interaction Channels Domain.

Salesforce Help: “Use Standard Topics in Agentforce for Common Customer Service Scenarios.”

To prevent customers who use abusive language from starting future chat sessions, creating an IP blocking rule is the recommended feature. This allows administrators to block specific IP addresses from accessing the chat service, effectively preventing abusive customers from initiating new sessions and maintaining a positive and safe environment for both customers and service agents.

To provide automated self-service on an ecommerce site for customers to check order status, creating an Einstein Bot is recommended. Einstein Bots can be integrated into websites and configured to provide real-time, automated responses to common customer inquiries, such as order status updates, enhancing the customer experience by providing instant access to information without human intervention.

Salesforce Service Cloud Voice provides features to protect customers ' sensitive data and ensure privacy during voice calls. One such feature is the ability for agents to pause and resume call recordings when sensitive information is being exchanged. This functionality is controlled through Sensitive Data Rules, which can be configured to allow agents to manually pause and resume recordings during a call.​

This approach ensures that sensitive information is not stored in call recordings, aligning with privacy requirements and compliance standards. Additionally, it allows the organization to continue recording calls for training and quality assurance purposes, excluding only the sensitive segments.​Genesys Cloud Resource Center

In planning sessions with Cloud Kicks, the recommended approach is to first gather organizational vision, then map out processes, plan key performance metrics, and finally, incorporate a plan for gathering user feedback. This structured approach ensures alignment with organizational goals, efficiency in processes, measurable outcomes, and continuous improvement based on feedback.

When moving images into Salesforce Knowledge, it ' s important to ensure that each image file size does not exceed Salesforce ' s maximum file size limit, which is typically 25 MB. Adhering to this constraint ensures that images can be successfully uploaded and displayed within Knowledge articles.