Free Salesforce Agentforce Service Consultant Practice Test Questions

Explanation:
The requirement is to see how long a case is in each status. This is a duration/time-in-status analysis, not a simple audit of field changes. The Case Lifecycle report type is purpose-built for this: it exposes Case History fields (including Business Hours Duration) and measures time spent in each status or with each owner during the case lifecycle . Case History is the standard report type for auditing field changes (Old Value/New Value) and is often messy for clean duration analysis because it tracks every tracked field change, not just status duration . Cases with Milestones is for entitlement/SLA milestone tracking, not general time-in-status reporting .

Correct Option:

A. Case Lifecycle

This report type is specifically designed to show how long cases spend in each status and with each owner, directly answering the manager's question about status duration .

It surfaces Case History fields such as Case History Status, Case History Owner, and Business Hours Duration, enabling clean time-in-status reporting .

Using this report type avoids the noise of auditing every field change and focuses the report on lifecycle progression and bottlenecks.

Incorrect Option:

B. Cases with Milestones
This report type is tied to Entitlement Processes and Milestones, used to track SLA compliance and milestone status (e.g., Open Violation, Closed Violation) .

It does not provide a general breakdown of how long cases spend in each status across the support process; it answers SLA questions, not lifecycle duration questions.

C. Case History

Case History reports show each tracked field change as its own row with Old Value and New Value, making it an audit tool rather than a clean duration report .

While it technically contains status change data, it often includes duplicate or unrelated field-change rows and lacks the purpose-built duration fields (like Business Hours Duration) that Case Lifecycle provides for time-in-status analysis .

Reference:
Salesforce Help: "Case Lifecycle Report Type" — measures time in status/owner using Case History duration fields. Salesforce Help: "Fields Available for Solution Reports" — Case History reports expose Old Value/New Value for tracked field changes . Trailhead/Exam Guide: Contact Center Analytics domain — Case Lifecycle is the recommended report type for time-in-status analysis.

Explanation:
The disparity is that KPIs show a decrease in customer satisfaction, yet many customers provided positive testimonials. This suggests the KPI being tracked (likely CSAT) may not reflect the full picture, or that certain segments of cases are skewing the average. Option A proposes measuring CSAT for cases with and without articles attached. If cases where agents used Knowledge articles have significantly higher CSAT than those without, it would explain why some customers are very happy (those helped by articles) while the overall CSAT average drops (due to a large volume of cases where articles were not used or not helpful). This segmented view directly tests whether Knowledge adoption is the differentiator behind the inconsistent satisfaction signals.

Correct Option:

A. Measure cases with and without articles attached with high CSAT scores.

This KPI splits satisfaction results by Knowledge usage, revealing whether article-attached cases perform better or worse than non-attached ones.

If article-attached cases show high CSAT while overall CSAT declines, the problem lies in cases not using Knowledge—explaining why testimonials (from happy, article-assisted customers) conflict with the aggregate KPI.

It directly ties Knowledge management effectiveness to satisfaction outcomes, which is the core of the scenario.

Incorrect Option:

B. Measure cases with and without articles attached with high net promoter scores (NPS).

NPS measures loyalty and likelihood to recommend, not satisfaction with a specific support interaction; it is a broader relationship metric.

The scenario reports customer satisfaction KPIs and testimonials about support experiences, so CSAT is the more directly relevant metric to segment.

Using NPS would introduce a different measurement construct and may not explain a CSAT-specific disparity.

C. Measure cases with and without articles attached based on case status.

Case status (New, Assigned, In Progress, Closed) reflects workflow stage, not satisfaction outcomes.

Segmenting by status does not connect Knowledge usage to customer sentiment, so it cannot explain why satisfaction metrics and testimonials disagree.

Reference:
ExamTopics discussion for this exact question shows B (CSAT segmentation) as the community-voted answer, reflecting the logic that comparing CSAT for cases with and without articles isolates Knowledge's impact on satisfaction . Salesforce case deflection guidance emphasizes measuring CSAT on deflected or article-assisted cases to validate Knowledge effectiveness .

Explanation:
The requirement is to track how long each case is owned by each team before resolution. The Case Lifecycle report type is specifically designed for this: it uses Case History data to show the duration a case spent with each owner or in each status, making it the correct tool for measuring ownership duration per team. Historical Trending reports track changes to field values over time (not ownership duration), and Cases with Milestones reports are tied to Entitlement/SLA tracking rather than team ownership analysis.

Correct Option:

B. Case Lifecycle report
The Case Lifecycle report tracks the time a case spends with each owner, directly answering how long each team held the case before it moved on or was resolved .
It uses Case History duration fields to measure ownership periods, allowing managers to identify bottlenecks across teams .

This is the standard Salesforce reporting solution for ownership duration analysis in the Contact Center Analytics domain .

Incorrect Option:

A. Cases with Historical Trending report
Historical Trending tracks changes to specific field values over time using snapshots, not the duration of ownership by different teams .

It cannot natively report on how long a case was owned by each team before resolution, which is an ownership duration requirement.

C. Case with Milestone report
This report type is specific to Entitlement Management and SLA tracking, showing milestone status and compliance (e.g., Open Violation) .

It does not track team ownership duration; it answers SLA performance questions, not lifecycle ownership questions.

Reference:
Salesforce Help: "Use Case Lifecycle Reports to Measure Case Duration by Status or Owner" — cited in exam reference materials for this exact scenario . Trailhead: "Analyze Case Ownership and Lifecycle Metrics" — supports Case Lifecycle as the tool for ownership duration analysis .

Explanation:
For a global rollout spanning 100 contact centers across three continents, standardized KPI reporting requires centralized ownership of report design. A global team of experienced analysts is the right body to define consistent templates, align KPI definitions, and maintain reporting standards across all regions . This creates a single source of truth and avoids the fragmentation that results from regional voting or from relying on a single executive who may lack the technical depth to design scalable reports.

Correct Option:

A. Assign a global team of experienced analysts to create a standard report template.
A centralized analytics team ensures consistency in KPI definitions and report structure across all 100 contact centers, which is the core requirement .

Experienced analysts have the technical depth to build scalable, maintainable report templates that work across regions and data volumes .

This approach establishes a governance model for reporting standards that can be maintained as the org grows.

Incorrect Option:

B. Ask leadership, management, and agents in all regions to vote on the standard report template.
Voting introduces inconsistency; different regions may prioritize different metrics, undermining the goal of standardized KPI reporting .

A democratic approach does not ensure technical feasibility or alignment with Salesforce reporting best practices.

C. Request that the VP of worldwide support design a standard report template to provide a clear vision.
A single executive typically lacks the technical depth needed to design scalable report templates and may not account for data model or regional reporting constraints .

While executive sponsorship is valuable for vision, it is not the right role for hands-on report design across a global deployment.

Reference:
ExamTopics: Correct answer A with explanation that a global analyst team ensures KPI alignment and reporting standards across all contact centers . CertsHero: Confirms A, noting the global team provides comprehensive understanding of global KPIs for consistent performance measurement .

Explanation:
When adding a report chart to a Page Layout or Lightning Record Page, the fundamental prerequisite is that the report itself must contain a chart. The Salesforce Report Chart component only displays reports that have a chart configured; reports without charts (such as tabular reports) cannot be selected or rendered in the component . The chart must be added to the report first (e.g., via the Add Chart button in the report builder) before the report becomes available for embedding on a record page.

Correct Option:

C. The report must contain a chart.
The Report Chart component's report selection dropdown only shows reports that already have a chart configured; reports without charts are excluded from selection .

Salesforce documentation explicitly instructs users to first ensure the report has a chart before adding the Report Chart component to a Lightning page .

This is a hard technical requirement for the component to function, making it the correct consideration.

Incorrect Option:

A. The report must be used on a Dashboard.
There is no requirement that a report be placed on a Dashboard before its chart can be embedded on a record page. The Report Chart component references the report directly, independent of any Dashboard.

Dashboards and record page charts are separate consumption mechanisms; one does not depend on the other.

B. The report must have a standard Report Type.
Custom Report Types are also supported for report charts on record pages. The restriction is about the presence of a chart and compatibility with the page's object context, not whether the Report Type is standard or custom .

Requiring a standard Report Type would unnecessarily exclude valid custom report type charts.

Reference:
Salesforce Help: "Graphique de rapport" — states that in the Report Chart properties, only reports containing a chart are displayed in the dropdown . Salesforce Help: "Add a Custom Link or Filtered Report to an Account Record Page" — Step 1 instructs ensuring the report has a chart before adding the component .

Correct Option

C. The Old Value and New Value fields are available for viewing only.
Salesforce Case History reports include the Old Value and New Value fields to show what a tracked field contained before and after a change. However, these fields have a reporting limitation: you can't use them in standard filter conditions to search report results in the Case History report type, according to Salesforce's support reporting guidance. The consultant should keep this restriction in mind when designing report filters.

Incorrect Options

A. The Data Type and New Value fields are available for viewing only.
The Data Type field identifies the data type associated with a tracked field change, and New Value captures the value after the change. However, Salesforce's documented limitation for Case History reports specifically concerns filtering on both Old Value and New Value. Data Type is not the field identified in that limitation, so option A does not accurately describe the key consideration.

B. The User and New Value fields are available for viewing only.
Case History reports include information about who made a change, along with the new field value. But the reporting restriction is not specifically about the User and New Value fields being view-only. The relevant limitation is that the Old Value and New Value fields cannot be used in filter conditions in this report type. Therefore, option B is incorrect.

Reference
- Salesforce Help: Tips for Effective Support Reporting

Explanation
Cloud Kicks provides customer support 24 hours a day, so it needs to measure how long cases remain open accurately. The standard Age field calculates elapsed calendar time, which may not reflect the duration based on configured business hours. Salesforce provides the Business Hours Age reporting field to calculate case age according to defined business hours. However, because CK operates 24/7, this feature has an important limitation: it isn't available for reporting when the organization's default business hours are set to 24 hours a day, seven days a week.

Correct Option
C. Enable Business Hours Age in Setup and add the field to the report.
This is the expected exam answer. Enabling the Case Duration/Age in Business Hours feature exposes the Business Hours Age field in supported Case reports. The consultant can then add that field as a report column to measure case age using configured business hours. Note that Salesforce documentation specifies that business hours must be less than 24 hours for this feature to work, so CK's 24/7 configuration must be considered before implementation.

Incorrect Options

A. Create a custom formula field to calculate the case age.
A formula field can calculate elapsed time between case creation and closure, or between case creation and the current time for open cases. However, creating a formula does not automatically account for configured business hours, weekends, and holidays. It may therefore fail to provide the business-hours-based measurement that this question is testing.

B. Create a report snapshot of the number of open cases per day.
A report snapshot captures and stores report values at scheduled intervals, making it useful for historical trend analysis. However, tracking the daily number of open cases does not directly calculate the average age of individual cases. It is not the appropriate solution for correcting the case-age calculation.

Reference
- Salesforce Help: Improve Case Tracking and Reporting by Enabling Business Hours Age

Explanation
Universal Containers (UC) has experienced increasing customer call wait times. The consultant should recommend analyzing call data to identify peak calling periods and ensure adequate agent staffing during those times. Reports help support managers understand call volume patterns and allocate resources effectively. This data-driven approach addresses a likely operational cause of long wait times: insufficient agent availability during periods of high demand.

Correct Option

B. Create reports to analyze data in order to understand peak times and ensure adequate staffing.
Reports allow UC to evaluate call volumes, agent availability, response times, and other contact center performance metrics. By identifying periods when call demand exceeds available staffing, managers can adjust schedules and allocate agents more effectively. Salesforce's contact center analytics guidance specifically highlights using historical interaction data to identify peak periods and optimize staffing to reduce customer wait times.

Incorrect Options

A. Set up analytical snapshots to capture key case information and create historical trending reports.
Analytical snapshots capture and store aggregated report data at scheduled intervals, making them useful for tracking historical trends. However, they primarily support historical analysis rather than directly identifying current call demand and helping managers plan staffing around peak calling periods. Reports focused on call volume and agent availability are the more direct recommendation for this scenario.

C. Create case escalation rules to route high-priority cases directly to supervisors for resolution.
Case escalation rules automatically escalate cases that meet specified criteria, such as exceeding a response-time threshold. They help ensure cases receive timely attention but do not directly reduce telephone queue wait times. The problem concerns customers waiting to speak with support agents, so analyzing call patterns and ensuring sufficient staffing is the better solution.

Reference
- Salesforce: How to Use Call Center Analytics