Service-Con-201 · Domain 3 of 8

Service-Con-201 Domain 3: Agentforce Service Solution Design

Agentforce Service Solution Design is the largest section: designing the rep's console workspace, the customer's self-service and assisted experience, and the security model that keeps customer data compliant, while weighing platform capabilities, limits and trade-offs.

Exam weight estimate
15%
Official objectives estimate
3
Estimated questions estimate
~9
Suggested study time estimate
9–10 hrs

About 11 min read Reviewed October 2026

Overview

Agentforce Service Solution Design is the heaviest section at 15%, roughly nine questions, with three objectives. Two are mirror images: analyze requirements to design the service agent (rep) experience, then the customer experience, each time weighing capabilities, limitations and trade-offs. The third asks you to secure customer data against security and compliance requirements.

For the rep experience, think Lightning Service Console: split view, subtabs, the utility bar with Omni-Channel and macros, Dynamic Forms, Path, Knowledge and Actions and Recommendations components, and generative help such as Service Replies and Work Summaries. For the customer experience, think Experience Cloud help centers, authenticated portals, Agentforce Service Agent on web and messaging, and consistent context when a conversation moves to a human. Security covers org-wide defaults, sharing sets for external users, field-level security, Shield Platform Encryption, Event Monitoring and Einstein Trust Layer masking.

How it's tested

Scenarios combine business requirements with constraints and ask for the best design, not just a possible one. Read for words like 'minimal clicks', 'without code', 'only their own cases' or 'regulated data', because those decide between console features, Experience Cloud options and security controls.

  • Rep workspace

    Reps juggle records and channels, and you choose console features that reduce clicks and keep context, such as split view, macros or utility bar items.

  • Customer journey

    Customers need self-service plus assisted help, and you design the site, AI agent and handoff experience.

  • Protect the data

    Sensitive data or external users appear, and you pick sharing, encryption, monitoring or masking controls.

Reasoning it through

An insurer's reps switch between policy, claim and case records while chatting with customers and keep losing their place. A Lightning Service Console app with split view, workspace subtabs for related records and the Omni-Channel widget in the utility bar keeps the conversation and records visible together. Building a custom Lightning page with Apex would add maintenance without meeting the need better.

Objectives 3

Official objectives from the Salesforce outline, in outline order.

3.1 Given a scenario, analyze customer requirements to determine an appropriate solution design considering capabilities, limitations, and trade-offs for the service agent experience.Designing the console workspace for service reps.
What it means
The service agent experience is what human reps see and use all day: the console app, record pages, channels, guidance and AI assistance. Salesforce now usually calls these users service reps to distinguish them from AI agents.
What to understand
Know Lightning Service Console features: workspace tabs and subtabs, split view, utility bar (Omni-Channel, macros, history, notes), Dynamic Forms and Actions, Path, related lists and highlights panel. Add guidance with Actions and Recommendations, Knowledge components, Quick Text and macros. Agentforce for Service adds Service Replies, Work Summaries and Service Planner-style guided steps. Weigh trade-offs: declarative versus custom, screen space, licensing, and how many channels a rep handles concurrently.
How it shows up
A rep productivity problem is described, and you choose the console design or feature that solves it with least effort.
Common confusion
Reaching for custom Lightning components when standard console features already meet the requirement.
3.2 Given a scenario, analyze customer requirements to determine an appropriate solution design considering capabilities, limitations, and design trade-offs for the customer experience.Designing self-service and assisted journeys for customers.
What it means
The customer experience covers how people find answers, open and track cases, and reach help across web, mobile and messaging, including when an AI agent hands off to a person.
What to understand
Experience Cloud help center and portal templates support public Knowledge, case submission and case tracking; authenticated access needs customer licenses and sharing sets. Agentforce Service Agent can answer questions and take actions on websites and messaging channels, escalating to reps through Omni-Channel with conversation context. Consider guest user security, accessibility, branding, language support and mobile. Trade-offs include public versus authenticated content, AI automation versus human contact, and cost of licenses.
How it shows up
A customer journey requirement is given, and you pick the site, channel or AI agent design that fits the constraints.
Common confusion
Forgetting that customers should not repeat themselves after an AI agent hands the conversation to a rep.
3.3 Given a set of customer data security and compliance requirements, determine a successful design to secure the data.Securing service data for internal and external users.
What it means
Service data often includes personal, financial or health details. Security design controls who can see records and fields, protects data at rest and in AI prompts, and provides audit evidence for regulators.
What to understand
Start with least privilege: private org-wide defaults for cases, role hierarchy, sharing rules, restriction rules, permission sets and field-level security. External users get access through sharing sets, share groups and Experience Cloud profiles. Shield adds Platform Encryption, Event Monitoring and Field Audit Trail; Data Mask protects sandboxes. For AI, the Einstein Trust Layer masks sensitive data and enforces zero data retention with model providers. Privacy Center and consent objects support data subject requests and retention.
How it shows up
A compliance requirement is stated, and you select the control that meets it without blocking legitimate work.
Common confusion
Using encryption to control visibility, when sharing and field-level security decide who sees data.

High-yield concepts

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

  • Lightning Service Console

    Tab-based app for working several records at once.

    Remember
    Workspace tabs, subtabs and utility bar.
    Tested as
    Rep experience scenarios.
    Trap
    Using a standard app for multi-record work.

  • Split view

    List view pinned beside open records.

    Remember
    Speeds working through queues.
    Tested as
    Queue-heavy rep scenarios.
    Trap
    Confusing it with subtabs.

  • Utility bar

    Persistent footer tools in the console.

    Remember
    Holds Omni-Channel, macros, notes and history.
    Tested as
    Always-available tool needs.
    Trap
    Placing frequently used tools on record pages instead.

  • Macros

    Recorded sequence of console actions.

    Remember
    Bulk macros can run on many records.
    Tested as
    Repetitive task scenarios.
    Trap
    Expecting them to run without a rep.

  • Actions and Recommendations

    Component showing next steps and flows.

    Remember
    Guides reps through processes in the console.
    Tested as
    Guided process scenarios.
    Trap
    Building a custom component for it.

  • Service Replies and Work Summaries

    Generative AI help for reps.

    Remember
    Draft responses and summarize conversations.
    Tested as
    Productivity and wrap-up scenarios.
    Trap
    Assuming they act without rep review.

  • Experience Cloud help center

    Public or authenticated self-service site.

    Remember
    Public Knowledge plus case forms.
    Tested as
    Customer self-service design.
    Trap
    Exposing internal articles to guests.

  • Agentforce Service Agent

    Autonomous AI agent for customer conversations.

    Remember
    Escalates to reps through Omni-Channel.
    Tested as
    Customer experience scenarios.
    Trap
    Designing without an escalation path.

  • Sharing sets

    Grant community users access by account or contact match.

    Remember
    Used with high-volume customer licenses.
    Tested as
    External access questions.
    Trap
    Using sharing rules for those users.

  • Restriction rules

    Narrow record access below sharing.

    Remember
    Limit what users see even if shared.
    Tested as
    Sensitive case types.
    Trap
    Treating them as a way to grant access.

  • Shield Platform Encryption

    Encrypts data at rest.

    Remember
    Does not hide data from users who have access.
    Tested as
    Regulated data scenarios.
    Trap
    Using it as a visibility control.

  • Einstein Trust Layer

    Security layer around generative AI calls.

    Remember
    Data masking, zero data retention, audit.
    Tested as
    AI and compliance scenarios.
    Trap
    Assuming prompts send raw data to vendors for training.

Side by side

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

Visibility vs protection controls

ConceptMeaningKey differenceCommon trap
Org-wide defaults and sharing Who can see which records Record access Opening defaults to fix one team's need
Field-level security Which fields a user sees Field access Hiding fields only on page layouts
Platform Encryption Encrypts stored data Protection at rest, not visibility Expecting it to hide data from users
Event Monitoring Logs user activity Detection and audit Expecting it to block access

Rep productivity features

ConceptMeaningKey differenceCommon trap
Macros Rep-triggered action sequences Automate repeated clicks Expecting background execution
Quick Text Reusable message snippets Consistent wording Using it for multi-step tasks
Actions and Recommendations Guided flows and next steps Process guidance in context Overlooking it for guided processes

Exam traps

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

  1. Custom by default

    What candidates pick
    Build a custom Lightning component for the rep workspace.
    Why it looks right
    It promises an exact fit.
    Why it's wrong
    Standard console features meet most needs with lower cost and easier upgrades; custom code adds maintenance.

    Clue to watch for The scenario prefers declarative or minimal maintenance.

  2. Encrypt to hide

    What candidates pick
    Use Shield Platform Encryption so only managers see a field.
    Why it looks right
    Encryption sounds secure.
    Why it's wrong
    Encryption protects data at rest; users with field access still see values. Use field-level security.

    Clue to watch for Requirement is about which users can view data.

  3. Open the defaults

    What candidates pick
    Set case defaults to Public Read Only so a team can collaborate.
    Why it looks right
    It is quick.
    Why it's wrong
    It exposes all cases to everyone; use sharing rules, case teams or queues instead.

    Clue to watch for Only one group needs extra access.

  4. Bot without exit

    What candidates pick
    Let the AI agent handle everything with no handoff.
    Why it looks right
    It maximizes automation.
    Why it's wrong
    Customers who need a person become frustrated, and complex issues go unresolved.

    Clue to watch for Complex or emotional issues are mentioned.

  5. Guest sees all

    What candidates pick
    Publish all Knowledge to the public help center.
    Why it looks right
    More content seems more helpful.
    Why it's wrong
    Internal procedures and sensitive notes must stay internal; control by channel and data category.

    Clue to watch for Articles include internal-only steps.

  6. Standard app for reps

    What candidates pick
    Give reps a standard navigation app.
    Why it looks right
    It is simpler to set up.
    Why it's wrong
    Reps working many records and channels need console tabs, subtabs and the utility bar.

    Clue to watch for Reps work several cases at once.

Answer framework

Use these steps for any design scenario in this section.

  1. Identify the user and the pain point: a rep losing context, a customer unable to self-serve, or a data exposure risk.
  2. List the stated constraints such as no code, budget, licensing, regulation, channels used and number of concurrent conversations.
  3. Check standard console, Experience Cloud and Agentforce features first, choosing declarative configuration where it meets the requirement fully.
  4. For data, apply least privilege through defaults, sharing, field-level security and restriction rules, then add encryption, monitoring or masking for compliance.
  5. Compare the remaining options by trade-off, including maintenance, user effort and customer experience, and pick the simplest one that meets every constraint.

Practice question

A health insurer's customer portal lets members view their own cases. Regulators require that diagnosis notes on cases be encrypted at rest and that internal reps outside the clinical team cannot see them. Which design meets both requirements?

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

Give this section the most time. In a Developer org, build a Lightning Service Console app: enable split view, configure workspace subtabs for contacts and assets, add Omni-Channel, macros and history to the utility bar, and place Knowledge and Actions and Recommendations on the case page. Record a macro and run it. Then build an Experience Cloud help center from the standard template, expose a Knowledge article and a case form, and log in as a customer to check what is visible.

For security, set case defaults to private, create a sharing set for customer users, and test field-level security from a restricted profile. Read the Shield and Einstein Trust Layer overviews for what each control protects. Trailhead modules on the Service Console and Experience Cloud basics cover the official material.

High-priority ideas are console features, external sharing and visibility versus protection. Underestimated is the handoff from AI agent to rep, which spans this section and the channels section.

FAQ

How much is Agentforce Service Solution Design worth on the exam?

Agentforce Service Solution Design is the largest section at 15% per third-party copies of the current guide, about nine scored questions as a planning estimate, across three objectives.

Is this section the same as Service Cloud Solution Design?

Yes in scope. Some copies of the guide still use the older Service Cloud name; the objectives on rep experience, customer experience and data security match.

Does 'service agent experience' mean AI agents?

In this objective it means human service reps using the console. Salesforce increasingly says service rep to avoid confusion with AI agents.

Do I need to know Shield in depth?

Know what Platform Encryption, Event Monitoring and Field Audit Trail each do and when a requirement calls for them, not detailed setup.

Are Experience Cloud licenses tested?

Expect high-level choices, such as when customers need authenticated access and how sharing sets grant record access to those users.

Is Apex ever the right answer here?

Rarely. Choose code only when the scenario shows that standard configuration cannot meet a stated requirement.

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 3 knowledge

You have covered rep workspace design, customer self-service journeys and data security. Check whether you can choose the simplest design that meets every stated constraint.

Take the Service-Con-201 practice test Check your Service-Con-201 readiness

Keep going