Service-Con-201 · Domain 7 of 8

Service-Con-201 Domain 7: Contact Center Analytics

Contact Center Analytics covers turning service data into the right view for each audience: report types and formats, dashboards and dynamic dashboards, Omni-Channel and SLA reporting, real-time supervision and advanced analytics for executives.

Exam weight estimate
13%
Official objectives estimate
1
Estimated questions estimate
~8
Suggested study time estimate
6–7 hrs

About 9 min read Reviewed October 2026

Overview

Contact Center Analytics is 13% of the exam but holds a single objective: given a scenario, develop reports and dashboards in Salesforce that give relevant information to different stakeholders. That one objective covers a lot of ground, so expect around eight questions on it.

You need to know standard and custom report types (Cases, Case History, Case Milestones, Knowledge, Agent Work and User Presence Status for Omni-Channel), report formats, cross filters, bucket fields, row-level and summary formulas, historical trending and reporting snapshots. On the dashboard side, know components, filters, dynamic dashboards that run as the viewer, and subscriptions. Finally, match tools to audiences: Omni Supervisor for live queue monitoring, standard reports for team leads, and CRM Analytics or Service Intelligence for executives who want trends across large data sets.

How it's tested

Scenarios describe a stakeholder and the decision they need to make. You choose the report type, format, formula, dashboard setting or analytics tool that shows the right data at the right level, refresh rate and security scope. The audience usually decides the answer more than the data itself.

  • Right report type

    A report must combine objects, such as cases with milestones or reps with presence, and you choose or create the report type.

  • Right audience view

    Several managers need the same dashboard filtered to their data, and you choose dynamic dashboards or filters.

  • Real-time or trend

    A stakeholder needs live status or long-term trends, and you pick Omni Supervisor, snapshots or advanced analytics.

Reasoning it through

A service director wants each of twelve team leads to see a dashboard of their own team's open cases, SLA breaches and CSAT, without building twelve dashboards. A dynamic dashboard running as the logged-in user respects each lead's record access, so one dashboard serves all twelve. Live queue monitoring during the day, however, belongs in Omni Supervisor, not in a dashboard.

Objectives 1

Official objectives from the Salesforce outline, in outline order.

7.1 Given a scenario, develop reports and dashboards in Salesforce to provide relevant information to different stakeholders.Service reporting matched to each stakeholder.
What it means
Service stakeholders need different views: reps track their own queue, supervisors manage live workloads, managers watch team KPIs and SLA compliance, and executives follow trends, cost and satisfaction. Salesforce reports, dashboards, Omni Supervisor and advanced analytics each serve part of this.
What to understand
Choose report types that include the needed objects, creating custom report types when standard ones lack a relationship or need 'with or without' logic. Use summary and matrix formats for grouping, joined reports for side-by-side blocks, bucket fields for ranges, and formulas for rates such as FCR or SLA compliance. Use reporting snapshots or historical trend reporting for change over time. Use dynamic dashboards for per-viewer data, dashboard filters for slicing, and subscriptions for delivery. Use Omni Supervisor for real-time monitoring, and CRM Analytics or Service Intelligence for large-scale executive analysis.
How it shows up
A stakeholder's information need is described, and you choose the report type, format, dashboard setting or tool that meets it.
Common confusion
Using a standard dashboard for live queue monitoring that Omni Supervisor is built to provide.

High-yield concepts

The terms, rules and formulas this domain turns into questions most often.

  • Custom report type

    Defines objects and relationships a report can use.

    Remember
    Supports 'with or without' related records.
    Tested as
    Cases without activity scenarios.
    Trap
    Assuming standard types cover every join.
  • Report formats

    Tabular, summary, matrix and joined.

    Remember
    Charts need summary or matrix grouping.
    Tested as
    Format choice questions.
    Trap
    Charting a tabular report.
  • Bucket field

    Groups values into ranges without a new field.

    Remember
    Example: case age bands.
    Tested as
    Ad hoc grouping.
    Trap
    Creating a formula field unnecessarily.
  • Summary formula

    Calculation on grouped values.

    Remember
    Rates such as SLA compliance percentage.
    Tested as
    KPI reporting.
    Trap
    Using a row-level formula for totals.
  • Reporting snapshot

    Saves report results into an object on a schedule.

    Remember
    Enables trend analysis over time.
    Tested as
    Backlog trend scenarios.
    Trap
    Expecting standard reports to keep history.
  • Historical trend reporting

    Tracks changes to selected fields over recent months.

    Remember
    Covers a short recent window only.
    Tested as
    Short-term change tracking.
    Trap
    Using it for multi-year trends.
  • Dynamic dashboard

    Runs as the logged-in viewer.

    Remember
    One dashboard, data scoped per user.
    Tested as
    Many managers scenario.
    Trap
    Building one dashboard per manager.
  • Dashboard filters

    Let viewers slice a dashboard by a field.

    Remember
    Applies to compatible components.
    Tested as
    Region or product slicing.
    Trap
    Confusing them with dynamic dashboards.
  • Omni Supervisor

    Real-time monitor of reps, queues and work.

    Remember
    Supervisors can reassign work live.
    Tested as
    Live monitoring scenarios.
    Trap
    Using a refreshed dashboard instead.
  • Agent Work and presence reports

    Omni-Channel report types.

    Remember
    Handle time, capacity and status durations.
    Tested as
    Rep productivity reporting.
    Trap
    Reporting only on cases.
  • Case Milestone report

    Reports on SLA milestone completion and violation.

    Remember
    Measures entitlement compliance.
    Tested as
    SLA reporting.
    Trap
    Measuring SLAs with case age alone.
  • Service Intelligence and CRM Analytics

    Advanced analytics for service data.

    Remember
    Large-scale trends and AI insights.
    Tested as
    Executive analysis.
    Trap
    Choosing it for a simple team report.

Side by side

Concepts candidates mix up, compared on the point that decides the answer.

Live vs historical views

ConceptMeaningKey differenceCommon trap
Omni Supervisor Real-time reps and queues Live intervention Used for monthly trends
Dashboard Refreshed report summaries Periodic KPI view Used as live queue monitor
Reporting snapshot Stored scheduled results Trends over time Expected to update instantly

Per-audience dashboard options

ConceptMeaningKey differenceCommon trap
Dynamic dashboard Runs as viewer Data scoped by viewer access Not used when many managers need views
Dashboard filter Viewer picks a value Same data, sliced Assumed to enforce security
Fixed running user Runs as one user Everyone sees the same data Exposes data beyond viewers' access

Exam traps

Each trap is an answer that looks right. Learn the clue that should change your mind.

  1. Dashboard per manager

    What candidates pick
    Clone a dashboard for each team lead.
    Why it looks right
    Each lead gets their own view.
    Why it's wrong
    Clones multiply maintenance; a dynamic dashboard shows each viewer their own data.

    Clue to watch for Many managers need the same layout.

  2. Dashboard for live ops

    What candidates pick
    Refresh a dashboard often for supervisors.
    Why it looks right
    Dashboards are familiar.
    Why it's wrong
    Supervisors need live rep status and queue backlogs with reassignment, which Omni Supervisor provides.

    Clue to watch for Need to act on queues during the shift.

  3. Filters as security

    What candidates pick
    Use a dashboard filter to restrict data by region.
    Why it looks right
    Filters change what appears.
    Why it's wrong
    Filters let viewers choose; they do not enforce access. Use dynamic dashboards and sharing.

    Clue to watch for Managers must not see other regions.

  4. Standard report type suffices

    What candidates pick
    Use the Cases report type for cases without activities.
    Why it looks right
    Cases is the obvious choice.
    Why it's wrong
    Showing records lacking related records needs a custom report type with 'with or without' logic.

    Clue to watch for The report needs missing related data.

  5. Reports keep history

    What candidates pick
    Run a standard report to show backlog trend.
    Why it looks right
    Reports show current data.
    Why it's wrong
    Standard reports show current values; trends need reporting snapshots or historical trending.

    Clue to watch for Trend over months is requested.

  6. Advanced analytics always

    What candidates pick
    Use CRM Analytics for a simple team report.
    Why it looks right
    It is more powerful.
    Why it's wrong
    It adds licensing and setup cost; standard reports meet simple operational needs.

    Clue to watch for Small team, simple metrics.

Answer framework

Apply these steps to any reporting scenario in this section.

  1. Name the stakeholder and the decision they make, such as reassigning work mid-shift, coaching individual reps, planning staffing or reporting results to the board.
  2. Decide the time horizon: real time needs Omni Supervisor, periodic needs dashboards, trends need snapshots or advanced analytics.
  3. Choose a report type that includes every required object, creating a custom report type for missing or optional relationships.
  4. Choose the format, groupings, bucket fields and formulas that express the KPI, such as SLA compliance or first contact resolution.
  5. Deliver it to the audience with dynamic dashboards, filters or subscriptions, respecting each viewer's record access and avoiding duplicate dashboards.

Practice question

A contact center has 15 supervisors, each managing one team. During shifts they need to see which reps are available, how many messaging sessions are waiting, and move work between reps immediately. What should the consultant recommend?

Choose one answer

Want more like this? The Service-Con-201 practice test has questions for every domain.

Checklist

0 of 12

Tick each one you can do without notes. Your ticks stay in this browser.

Study strategy

This section rewards hands-on reporting practice. In a Developer org with sample cases, build a summary report of open cases by owner and priority, add a bucket field for case age, and write a summary formula for the share of cases closed on first contact using a checkbox. Create a custom report type for cases with or without activities, then a dashboard and switch it to dynamic. Set up a reporting snapshot to capture daily backlog.

Then review Omni-Channel reporting: the Agent Work and User Presence Status report types and the Omni Supervisor views. Read the overview of Service Intelligence and CRM Analytics for service so you know when advanced analytics is the expected answer.

High-priority ideas are custom report types, dynamic dashboards and live versus historical tools. Underestimated is the stakeholder angle: read who the report is for before thinking about how to build it. Practice by naming the audience aloud for each sample scenario you review.

FAQ

How much is Contact Center Analytics worth on the Agentforce Service Consultant exam?

Contact Center Analytics accounts for 13% per third-party copies of the current guide, about eight scored questions as a planning estimate, all from one objective.

Is CRM Analytics required knowledge?

Know when it or Service Intelligence is appropriate, such as large-scale trends and executive views. Building analytics apps is not expected.

What is the difference between Omni Supervisor and a dashboard?

Omni Supervisor shows live rep status and queues and allows reassignment. Dashboards show refreshed report data for periodic review.

When do I need a custom report type?

When standard report types lack the objects you need, or you must show records with or without related records.

Do dashboard filters restrict data access?

No. They let viewers slice data. Record access is governed by sharing and, for dashboards, by the running user setting.

Can reports show trends over months?

Use reporting snapshots or historical trend reporting. Standard reports show current values only.

Other CRM & Business Applications certifications

Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.

Test your Domain 7 knowledge

You have covered service report types, formats, dashboards, Omni Supervisor and advanced analytics. Check whether you can pick the right view for each stakeholder.

Keep going