Service-Con-201 Salesforce Certified Agentforce Service Consultant Exam Topics and Questions

This topic sets the baseline for contact center work. You need to understand what moves the metrics that matter to service leaders, and how to weigh risk against reward when a client wants something ambitious. The exam expects you to connect operational decisions to KPI outcomes and to spot the friction points in a proposed solution before they become project failures.

How Industry Knowledge is tested

Twelve percent of the exam means roughly one in eight items, so you will face multiple scenarios asking you to interpret metrics or evaluate a business case. Items typically present a contact center goal or constraint and ask which factor will move the needle or what trade-off the client must accept. You lose marks by confusing correlation with causation, by recommending features without checking whether they address the stated KPI, or by ignoring the business context when a technically sound solution carries unacceptable risk. The exam rewards candidates who can articulate why a metric matters and what levers actually change it, not those who recite definitions.

Once you know what the client needs, you have to deliver it without breaking their operation. This topic covers the consulting behaviours that keep a project on track, the deployment and training choices that determine adoption, and the data work that makes or breaks go-live. Expect questions that test your judgment on sequencing, stakeholder management, and the practicalities of moving records into a new system.

– Consulting engagement and deployment

Successful consulting means knowing when to push back, when to escalate, and when to adapt the plan. The exam tests your ability to identify the right moment for each. You also need to recommend deployment models that match the client's risk tolerance and readiness, and training strategies that fit their user base. A phased rollout suits a risk-averse organisation with complex workflows; a big-bang approach works when the configuration is simple and the team is experienced. Training must reach the right people at the right time, and the exam will ask you to choose between instructor-led sessions, self-service resources, and embedded support based on user count, geography, and skill level.

– Data migration, quality, and governance

Data work is where implementations stall. Migration is not just extraction and load; you must account for transformation, deduplication, and validation. Data quality issues multiply when volumes are large, and governance determines who owns the cleanup and the ongoing stewardship. The exam expects you to recognise when a data set is too dirty to migrate without remediation, when to use staging environments, and how to handle large data volumes without hitting platform limits. You need to know the implications of poor data quality on reporting, automation, and user trust, and the role governance plays in preventing those problems from recurring.

How Implementation Strategies is tested

At twelve percent weighting, this topic appears as often as Industry Knowledge, and the items are scenario-heavy. You will be given a client situation and asked to recommend a deployment approach, a training plan, or a data migration strategy. The exam penalises candidates who choose technically elegant solutions that ignore organisational readiness or who underestimate the effort required to clean and migrate data. Common traps include recommending a full rollout when a pilot is safer, proposing training too early or too late in the timeline, and failing to account for data volume limits or governance gaps. The correct answer balances technical capability with project risk and user impact.

This is the heaviest topic on the exam, and it demands that you design solutions for both the agent and the customer. You are balancing capabilities against limitations, and every design choice carries a trade-off. Security and compliance requirements add another layer of constraint. The exam tests your ability to recommend a configuration that works within platform boundaries while meeting the client's functional and regulatory needs.

– Agent experience design

Agents need tools that surface the right information at the right time without overwhelming the interface. The exam expects you to evaluate requirements and recommend layouts, console configurations, and automation that improve efficiency without adding cognitive load. You must understand the capabilities of Service Console, the limitations of custom components, and the trade-offs between out-of-the-box features and bespoke development. A solution that requires too many clicks or too much context-switching will hurt productivity, and the exam will ask you to spot those problems in a proposed design.

– Customer experience design

Customer-facing solutions must be intuitive, accessible, and aligned with brand expectations. The exam tests your ability to recommend portal designs, self-service flows, and interaction patterns that reduce effort for the customer while keeping support costs manageable. You need to know when to use Experience Cloud, when to embed service widgets, and when a native mobile experience is justified. Trade-offs include build complexity versus time to market, customisation versus maintainability, and feature richness versus performance. The exam rewards candidates who can articulate why a simpler design often delivers better outcomes.

– Data security and compliance

Security requirements shape every layer of the solution. You must know how to use sharing rules, field-level security, and encryption to protect sensitive data, and how to configure the platform to meet regulatory obligations like GDPR or HIPAA. The exam expects you to recognise when a requirement demands platform-native controls and when it requires additional tooling or process. Common pitfalls include over-provisioning access for convenience, underestimating the effort required to audit and document security controls, and failing to account for data residency or retention rules. A compliant design is one that can be proven compliant, not just configured correctly.

How Agentforce Service Solution Design is tested

Fifteen percent weighting means this topic appears more often than any other, and the items are dense with constraints. You will be given a set of requirements for the agent experience, the customer experience, or both, and asked to recommend a design that balances capability, usability, and platform limits. Security and compliance scenarios add a third dimension, requiring you to layer controls without breaking functionality. The exam penalises candidates who ignore trade-offs, who recommend features the platform does not support, or who overlook the compliance implications of a design choice. The correct answer demonstrates that you have considered every constraint and chosen the least problematic compromise.

Knowledge is the foundation of case deflection and agent efficiency, but only if the content is current, findable, and structured to support both self-service and assisted support. This topic covers the article lifecycle, the principles of Knowledge Centered Service, and the configuration choices that determine whether knowledge becomes a strategic asset or a neglected repository. The exam expects you to know how to set up knowledge for success and how to configure it to serve different audiences.

How Knowledge Management is tested

At twelve percent, this topic appears often enough that weak knowledge of article lifecycle or KCS principles will cost you marks. Items typically present a set of requirements for content creation, review, or distribution, and ask you to recommend a configuration or process. You lose marks by confusing article types, by recommending workflows that do not match the client's governance model, or by failing to configure visibility and permissions correctly. The exam rewards candidates who understand that knowledge management is a content operation, not just a feature to enable. You need to know when to use categories versus topics, how to enforce review cycles, and how to surface the right article to the right user at the right time.

Customers reach you through multiple channels, and each one has design implications for routing, automation, and agent workload. This topic covers intake channel selection, interaction channel functionality, and the role of AI agents in the service process. You need to know when to use which channel, how to configure each one to meet business goals, and when agentic automation can handle work that would otherwise require a human. The exam tests your ability to recommend the right mix of channels and automation for a given set of requirements.

– Intake and interaction channel design

Intake channels determine how work enters the system. Email-to-case, web-to-case, and API integrations each have different latency, volume, and enrichment characteristics, and the exam expects you to match the channel to the business process. Interaction channels determine how agents and customers communicate once a case exists. Messaging, chat, voice, and social each have different agent concurrency, customer expectation, and tooling requirements. You must understand the functional differences, the design considerations for each, and the best practices that prevent poor customer experience or agent burnout. A poorly configured channel creates work instead of resolving it.

– AI agents and agentic service

AI agents can handle repetitive, rules-based work without human intervention, but only if the process is well-defined and the underlying data is reliable. The exam tests your ability to identify appropriate use cases for agentic automation, to understand the capabilities and limits of Agentforce agents, and to configure them to deliver value without introducing risk. You need to know when an AI agent can replace a human, when it should assist one, and when the process is too complex or too sensitive for automation. Agentic service is not a universal solution, and the exam rewards candidates who can articulate the conditions under which it succeeds and the failure modes that must be designed around.

How Intake and Interaction Channels is tested

Thirteen percent weighting means this topic appears frequently, and the scenarios often involve multiple channels or a mix of human and AI agents. You will be asked to recommend an intake approach, to choose interaction channels based on business goals, or to determine whether an AI agent is appropriate for a given process. The exam penalises candidates who ignore channel-specific constraints, who recommend automation without checking whether the process is stable enough to support it, or who fail to account for the design and configuration work required to make a channel functional. Common traps include underestimating the effort required to configure routing, overestimating the capability of AI agents in ambiguous scenarios, and choosing channels based on novelty rather than fit.

Case management is the operational core of service delivery. From creation to closure, every case follows a lifecycle shaped by routing, escalation, entitlements, and automation. This topic covers the design of that lifecycle, the strategies that deflect cases before they are created, and the configuration of service-level agreements, milestones, and assets. You also need to understand where Agentforce automation fits into case handling and when it adds value versus when it adds complexity.

– Case lifecycle and deflection

A well-designed case lifecycle routes work to the right agent, surfaces the right information, and closes cases as quickly as possible without sacrificing quality. The exam expects you to design that lifecycle from creation through closure, accounting for assignment rules, escalation criteria, and status transitions. Case deflection strategies reduce volume by solving problems before a case is created, using Experience Cloud sites, Agentforce agents, and Knowledge articles to provide answers without human intervention. You need to know when deflection is feasible, how to measure its effectiveness, and how to configure the tools that deliver it. A deflection strategy that frustrates customers or agents is worse than no strategy at all.

– Entitlements, SLAs, and milestones

Entitlements define what support a customer is owed. Service-level agreements specify when that support must be delivered. Milestones mark the critical moments in a case lifecycle, and business hours determine when the clock is running. The exam tests your ability to configure these elements so that the platform enforces the client's service commitments and alerts agents before a breach occurs. You must understand how entitlements interact with case creation, how SLAs and milestones drive escalation, and how business hours affect deadline calculations. Assets add another dimension by linking cases to the equipment or products under support. Configuration errors in any of these areas lead to missed SLAs, incorrect routing, and lost customer trust.

– Agentforce Service automation

Agentforce automation can handle case assignment, status updates, and field population without manual intervention, but only when the rules are clear and the data is clean. The exam expects you to differentiate the use cases where automation improves consistency and speed from those where it introduces errors or removes necessary human judgment. You need to know the capabilities of workflow rules, Process Builder, Flow, and agentic automation, and when to use each. The correct choice depends on the complexity of the logic, the volume of cases, and the need for auditability. Automation that runs incorrectly is harder to fix than no automation at all.

How Case Management is tested

At thirteen percent, this topic appears as often as Intake and Interaction Channels, and the scenarios are operationally detailed. You will be given a set of KPIs or business requirements and asked to design a case lifecycle, configure entitlements and SLAs, or recommend where automation should be applied. The exam penalises candidates who design lifecycles that do not scale, who configure SLAs without accounting for business hours or entitlement limits, or who automate processes that require human discretion. Common traps include confusing milestones with escalation rules, failing to link assets to entitlements, and recommending automation without checking whether the underlying data supports it. The correct answer demonstrates operational thinking, not just feature knowledge.

Reports and dashboards turn data into decisions, but only if they show the right metrics to the right people at the right level of detail. This topic tests your ability to design reporting solutions that meet stakeholder needs without overwhelming them with noise. You need to know which report types suit which questions, how to structure dashboards for different audiences, and how to avoid the common mistakes that make reports slow, inaccurate, or misleading. The exam expects you to think about reporting as a design problem, not a configuration task.

How Contact Center Analytics is tested

Thirteen percent weighting means you will face multiple reporting scenarios, and they will ask you to choose the right report type, filter logic, or dashboard component for a given stakeholder need. The exam penalises candidates who recommend report types that do not support the required grouping or summarisation, who build dashboards that run too slowly because they ignore row limits or filter efficiency, or who fail to match the visualisation to the audience. Common traps include using summary reports where matrix reports are needed, building dashboards without considering the refresh schedule or the user's permissions, and recommending custom report types without checking whether a standard one already exists. The correct answer demonstrates that you understand how stakeholders consume information and how the platform delivers it efficiently.

Service operations rarely exist in isolation. You need to connect Agentforce Service to telephony systems, knowledge bases, CRM platforms, and external data sources. This topic covers the integration use cases that matter in a contact center context, the technical and operational considerations that shape integration design, and the third-party solutions that extend platform capability. The exam expects you to know when integration is necessary, what each integration pattern can and cannot do, and what risks come with connecting systems.

How Integrations is tested

At ten percent, this is the lightest topic on the exam, but it still appears often enough to affect your result. Items typically present a business requirement that demands data or functionality from an external system, and ask you to recommend an integration approach or evaluate a proposed design. You lose marks by recommending integration patterns that do not match the latency, volume, or security requirements, by ignoring the operational cost of maintaining an integration, or by failing to account for the limitations of third-party APIs. Common traps include assuming real-time integration is always feasible, underestimating the effort required to map and transform data between systems, and recommending custom integrations when a pre-built connector already exists. The correct answer balances technical feasibility with operational sustainability.