• Cert++
  • Practice
  • Certle
  • Review
  • Tracks
  • Checklist
  • Guides
  • Upgrade
Cert++
  1. Home
  3. Agentforce Service Consultant

Agentforce Service Consultant

Checklist progress

0/163Learned

Agentforce Service Consultant

Study Checklist

  • Platform Administrator
  • Platform App Builder
  • Platform Foundations
  • Platform Developer
  • Platform Administrator II
  • Agentforce Sales Consultant
  • Agentforce Service Consultant
  • Platform Data Architect
  • Platform Development Lifecycle and Deployment Architect
  • Platform Identity and Access Management Architect
  • Platform Integration Architect
  • Platform Sharing and Visibility Architect
  • Heroku Architect
  • B2C Solution Architect
  • Experience Cloud Consultant
  • Agentforce Field Service and Operations Consultant
  • Agentforce Nonprofit Consultant
  • Data 360 Consultant
  • Omnistudio Consultant
  • CRM Analytics and Einstein Discovery Consultant
  • Platform User Experience Designer
  • Platform Strategy Designer
  • B2C Commerce Developer
  • JavaScript Developer
  • Omnistudio Developer
  • Platform Developer II
  • Marketing Cloud Engagement Administrator
  • Marketing Cloud Engagement Specialist
  • Marketing Cloud Engagement Consultant
  • Agentforce Sales Foundations
  • Business Analyst
  • Marketing Cloud Engagement Developer
  • Marketing Cloud Engagement Foundations
  • Agentforce Specialist
  • Agentforce Life Sciences Consultant
  • B2B Commerce Administrator AP
  • B2B Commerce Developer AP
  • Agentforce Consumer Goods AP
  • Agentforce Financial Services AP
  • Agentforce Health AP
  • Agentforce Manufacturing AP
  • MuleSoft Integration Foundations
  • MuleSoft Developer
  • MuleSoft Developer II
  • MuleSoft Platform Integration Architect
  • MuleSoft Platform Architect
  • Tableau Desktop Foundations
  • Tableau Data Analyst
  • Tableau Consultant
  • Tableau Server Administrator
  • Tableau Architect

Checklist progress

0/163Learned

  • The difference between synchronous contact center models (phone, live chat) and asynchronous models (email, messaging)
  • How Average Handle Time (AHT) is calculated in a contact center
  • Which operational factors — agent skill mix, knowledge availability, and escalation rate — most directly influence AHT
  • How Customer Satisfaction (CSAT) and Net Promoter Score (NPS) differ as KPIs for contact center performance
  • When CSAT versus NPS is the more appropriate metric to report on contact center performance
  • How First Contact Resolution (FCR) is impacted by agent empowerment, escalation paths, and access to knowledge articles
  • How abandon rate and queue wait time are related in a contact center
  • Which configuration or staffing changes most directly reduce customer abandonment
  • What drives escalation rates in a contact center and how routing configuration, agent training gaps, and self-service availability contribute
  • How service level agreements (SLAs) and response time KPIs interrelate
  • How cost-per-contact is affected by deflection strategy choices, including self-service portals, chatbots, and knowledge base accessibility
  • What happens to KPI reporting when business hours are not configured correctly
  • How to assess the risk of consolidating multiple legacy support channels into a single omni-channel Salesforce implementation for a large enterprise
  • What organizational change management risks arise when migrating an on-premise contact center to Service Cloud, and how a consultant should address adoption resistance
  • How to identify and quantify the business value of a Knowledge Management investment in a contact center setting using measurable KPIs
  • The business challenges involved when a client wants to reduce AHT by 30% without impacting CSAT, and which solution trade-offs are most relevant
  • Given a client requesting 24/7 live agent coverage, which risks and costs must be weighed against the benefits compared to an AI-assisted self-service approach
  • When a client wants to implement an AI agent to handle tier-1 support, what risks around trust, compliance, and escalation failure must be evaluated before recommending deployment
  • How over-automation of case routing and closure can negatively affect CSAT and what business safeguards should be included when recommending automation-heavy designs
  • How to conduct a requirements-gathering workshop with stakeholders to ensure all Service Cloud use cases are captured before solution design begins
  • What activities are appropriate during a discovery phase versus a design phase in a Service Cloud implementation engagement
  • The role of executive sponsorship in a successful Service Cloud engagement and how a consultant should engage sponsors throughout the project
  • How to build and manage a project plan that accounts for user acceptance testing (UAT), change management, and go-live readiness for a Service Cloud deployment
  • How to recognize scope creep during an engagement and the appropriate steps a consultant should take to protect project timeline and budget
  • When a key stakeholder disagrees with the proposed Service Cloud solution design, how a consultant should handle the conflict and proceed
  • What a post-go-live steady-state handoff plan should include for a Service Cloud deployment
  • How a consultant transitions operational support responsibility from the project team to the client's admin team
  • What sandbox strategy (Developer, Partial Copy, Full Copy) is appropriate for different stages of a Service Cloud implementation, and why
  • When a company has 500 agents across 3 regions with different business processes, how to determine whether a phased rollout is preferable to a big-bang deployment
  • When to use a pilot group for phased deployment versus deploying to all users simultaneously, and how this decision depends on risk tolerance and data migration readiness
  • How to select between train-the-trainer, role-based, and self-paced training strategies based on agent role diversity and go-live timeline
  • How to plan a data freeze window and cutover sequence when migrating from a legacy case management system to Service Cloud with minimal disruption to agent operations
  • How to design a hypercare plan for the weeks immediately following a Service Cloud go-live event
  • What data quality issues commonly arise during a Service Cloud migration and how to address duplicate records, missing owner lookups, and incomplete case histories
  • How to design a data migration strategy for moving historical case records from a legacy CRM to Salesforce, including handling of related records and attachments
  • When to use Bulk API versus Data Loader versus third-party ETL tools for migrating large volumes of case and contact records into Salesforce
  • How large data volumes affect Service Cloud performance
  • The data governance considerations for PII handling within a Service Cloud environment
  • The data governance considerations for managing case data ownership and retention policies within a Service Cloud environment
  • The difference between a Lightning App and a Lightning Console App, and when a consultant should recommend a Service Console App over a standard Lightning App for agent workflows
  • How to design a Lightning Service Console layout that optimizes agent efficiency for a high-volume phone support team, including the use of utility bar, macros, and split view
  • The trade-offs between a single universal agent console layout versus role-specific page layouts for a multi-tier support organization
  • How Dynamic Forms and Dynamic Related Lists can be used in the Service Console to reduce page clutter and show context-relevant fields based on case record type or status
  • When a client requires agents to handle multiple cases simultaneously without losing context, which Service Console features should be recommended and why
  • When a client needs agents to see a 360-degree customer view while working a case, how to configure Related Lists, activity timeline, and external data integration in the console
  • How to configure case feed and feed filters to surface the most actionable information for agents handling technical support cases
  • How Quick Text, macros, and email templates differ in their use cases for improving agent productivity and response consistency
  • When agents are working in the field or on mobile devices, what Salesforce Mobile App capabilities and limitations must be considered for Service Cloud use cases
  • How to configure email-to-case and web-to-case to ensure consistent customer experience across inbound contact channels
  • How to design a self-service portal using Experience Cloud that minimizes case creation volume while maintaining CSAT for customers who cannot resolve issues independently
  • When a customer requires seamless escalation from a self-service chatbot to a live agent without repeating context, which Service Cloud features support this and what their limitations are
  • What configuration is required to send automated case status update notifications to customers, and how to avoid over-notification fatigue
  • How to design a post-case survey flow in Service Cloud to automatically collect CSAT scores after case closure
  • What configuration triggers the survey send in a post-case CSAT survey flow
  • The design trade-offs between a fully branded Experience Cloud customer portal versus a third-party support website integrated via API for customer-facing support
  • The difference between object-level, record-level, and field-level security in Salesforce
  • When object-level, record-level, and field-level security must be applied together to meet a compliance requirement
  • How the Case OWD (Organization-Wide Default) setting interacts with role hierarchy, sharing rules, and queue membership to determine which agents can view and edit cases
  • How to design record-level security for cases so that agents can only see cases assigned to their team, while managers can see all cases in their region
  • How to use sharing rules and manual sharing in Service Cloud to extend record visibility to cross-regional teams without opening the OWD
  • When field-level security must restrict agents from seeing customer PII on case records while still allowing access to case details, how to configure this in Salesforce
  • The stages of the Salesforce Knowledge article lifecycle from draft to published to archived
  • How Knowledge article versioning works in Salesforce
  • How Knowledge Centered Service (KCS) methodology aligns with Salesforce Knowledge workflows
  • What KCS principles should drive article creation governance
  • Which user roles can transition Knowledge articles between lifecycle states
  • The role of the Knowledge Manager, Author, Publisher, and Viewer permission sets in the article lifecycle and how they enforce governance
  • How to configure multiple Knowledge article record types in Salesforce
  • When using separate record types for internal procedures versus external FAQs is preferable to a single article type
  • How to configure data categories in Salesforce Knowledge
  • Why category hierarchies affect both article visibility and search relevance in Salesforce Knowledge
  • How to configure article approval processes using Salesforce workflow or approval processes to ensure content quality before publishing
  • How article feedback and ratings can be used to identify stale or low-quality knowledge articles and trigger review workflows
  • What happens to linked cases when a Knowledge article is archived or replaced by a new version
  • What is required to import existing articles from a legacy knowledge base into Salesforce Knowledge, including the Knowledge Article CSV import process and its limitations
  • When agents need to search and attach Knowledge articles to cases from within the Service Console, what configuration is required and which components must be added to the page layout
  • How to use the Knowledge Lightning component versus the Knowledge sidebar to surface relevant articles based on case fields and search terms
  • How data category visibility and role hierarchy interact to determine which users see which published Knowledge articles in an org with multiple customer segments
  • How to expose Knowledge articles to external customers through an Experience Cloud portal while restricting internal-only articles from being visible
  • The design trade-offs between a single article type versus multiple article types in a Knowledge implementation for a company with both internal procedures and external FAQs
  • When a company wants to use AI-suggested Knowledge articles to assist agents in real time during a chat interaction, what must be configured in Service Cloud
  • How to track Knowledge article usage metrics — views, attachments to cases, and thumbs up/down ratings — and use them to demonstrate ROI of the Knowledge investment
  • How to choose between Email-to-Case, Web-to-Case, and the Salesforce-native case submission form based on volume, routing complexity, and automation requirements
  • The difference between On-Demand Email-to-Case and standard Email-to-Case, and when each should be used based on email volume and firewall constraints
  • The design considerations when building a Web-to-Case form, including field mapping, auto-response rules, and case assignment rules
  • How to prevent spam when configuring a Web-to-Case form
  • When a company receives support requests through multiple channels (email, phone, chat, social), how to design an Omni-Channel routing strategy that routes to the right queue with the right priority
  • How to configure routing rules in Omni-Channel to handle peak volume spikes without overwhelming agents in a specific queue
  • How voice integration via Service Cloud Voice works and what telephony options are available (Amazon Connect, partner telephony, Bring Your Own Telephony)
  • When Amazon Connect, partner telephony, or Bring Your Own Telephony is the appropriate choice for Service Cloud Voice
  • When a company wants to offer both synchronous (chat) and asynchronous (messaging) support, what Service Cloud channels support each and what distinguishes them operationally
  • The use cases for Salesforce Messaging for In-App and Web (MIAW) versus classic Live Agent chat, including handoff to agent and session persistence
  • How Messaging channels (SMS/text, WhatsApp) are enabled in Service Cloud and what configuration steps differentiate messaging setup from chat channel setup
  • The use cases for social media as a service channel, including how Social Customer Service connects social mentions to case creation and agent workflows
  • When a company wants to reduce inbound case volume by enabling community-based peer support, how Experience Cloud communities can serve as a deflection channel
  • The difference between an Einstein Bot / Flow Bot and an Agentforce AI Agent in terms of configuration approach, conversation model, and suitable use cases
  • How Service Channels and Routing Configurations must be set up for each work type (case, chat, messaging) before Omni-Channel can route that work item type
  • The configuration implications of enabling Enhanced Omni-Channel versus Classic Omni-Channel, and what migration considerations apply
  • What best practices should be followed when configuring Omni-Channel capacity models to balance agent workload and customer wait times
  • The design considerations for routing work items using Omni-Channel Skills-Based Routing versus Queue-Based Routing and when skills-based is preferred
  • What the Omni-Channel Supervisor panel provides and how supervisors use it to monitor real-time agent status, queue backlog, and work item wait times
  • How to design auto-response rules for Email-to-Case to acknowledge receipt without creating agent confusion from customer replies to auto-responses
  • How to configure Embedded Service Deployments for chat, including pre-chat forms, offline support, and branding, and how this differs from a Chat Button configuration
  • How pre-chat data can be used to pre-populate case fields and speed routing in Messaging for In-App and Web
  • How pre-chat and post-chat survey configuration works in Messaging for In-App and Web
  • What requirements must be met before AI agents can reliably resolve a class of customer service requests, including data quality, knowledge coverage, and action permissions
  • When a company wants to automate tier-1 case resolution for password resets and order status inquiries, when is an Agentforce AI agent the right recommendation versus a traditional bot
  • How to determine the appropriate handoff point from an AI agent to a human agent, and what data should be passed at escalation to preserve customer context
  • What types of actions an Agentforce Service Agent can perform out of the box (e.g., case creation, knowledge retrieval, order lookups) and what requires custom configuration
  • How Agentforce for Service is configured, including topics, actions, and the agent builder interface in Salesforce
  • How to configure and publish an Agentforce Service Agent to a Messaging for In-App and Web channel, including channel linking and testing
  • The limitations of Agentforce Service Agents in terms of supported channels, action complexity, and compliance use cases that require human oversight

Given a set of requirements or KPIs, design a case management solution from creation to closure.

0/11

The role of case statuses in lifecycle management and how to design a status picklist that supports KPI reporting without creating agent confusion

Learn this concept
Unseen

How to design case assignment rules that route cases to the correct queue based on case origin, product, priority, and customer tier

Learn this concept
Unseen

How to use case queues, assignment rules, and Omni-Channel together to create an end-to-end routing architecture for a multi-tier support model

Learn this concept
Unseen

How email threading in Email-to-Case works so that customer replies are appended to the existing case rather than creating duplicate cases, and what can break this behavior

Learn this concept
Unseen

The use cases for case escalation rules versus workflow-based escalation, including which is more appropriate when time-sensitive SLA thresholds must be enforced

Learn this concept
Unseen

How to configure case teams to support multi-agent collaboration on a single case, and what limitations exist with case team roles

Learn this concept
Unseen

How parent-child case relationships work in Salesforce and when splitting a complex issue into child cases is preferable to managing it as a single record

Learn this concept
Unseen

How to associate multiple contacts with a single case using case contact relationships, and the limitations of the standard case contact field versus a custom relationship

Learn this concept
Unseen

How to configure case close templates and required closure fields to ensure data completeness for reporting and quality analysis

Learn this concept
Unseen

How the case merge feature works, its limitations, and when a consultant should recommend merging duplicate cases versus linking them

Learn this concept
Unseen

The difference between public and private case comments, when each is visible to customers in a self-service portal, and how to control comment visibility

Learn this concept
Unseen

Given a set of requirements, explain how case deflection strategies are delivered in Experience Cloud sites, Agentforce, and Knowledge.

0/4

  • How to configure a self-service Experience Cloud site so that customers who search for help see Knowledge articles before being offered a case creation form
  • How Agentforce contributes to case deflection by resolving common requests autonomously, and how to measure deflection rate as a KPI
  • When a company wants to reduce inbound case volume by 20%, which combination of Knowledge, Experience Cloud, and Agentforce features should be recommended and why
  • How to track and report on case deflection events from a self-service portal to demonstrate ROI of the deflection investment

Explain the capabilities, use cases, and how to configure service entitlements, milestones, assets, business hours, and service-level agreements

0/8

  • The difference between a Service Contract, an Entitlement, and an Entitlement Process in Salesforce
  • When a Service Contract, Entitlement, or Entitlement Process is used to model a customer's support agreement
  • How entitlements work in Service Cloud and how they enforce SLA policies on cases
  • The difference between entitlement processes and milestones in Service Cloud
  • How business hours are configured in Salesforce and how they affect milestone time calculations when a case is open across a weekend or holiday
  • What milestone completion criteria and actions are available in an entitlement process, and how violation actions trigger alerts or escalations
  • When a company has different SLA tiers for different customer contracts, how to configure multiple entitlement processes with different milestone timelines
  • How assets are related to cases and entitlements, and the use case for tracking product-specific support history through the asset object

Differentiate the use cases and capabilities of Service Cloud automation.

0/7

  • When to use case assignment rules versus escalation rules, and how they differ or overlap in functionality
  • When to use auto-response rules versus workflow rules or flows, and how they differ or overlap in functionality
  • The use case for Screen Flows launched from a case record versus background automation using Record-Triggered Flows in a Service Cloud context
  • How macros in the Service Console differ from Quick Actions and when each is the more appropriate automation tool for agent productivity
  • How Einstein Case Classification uses AI to automatically populate case fields at creation, and what training data and configuration is required
  • When a company wants to automatically update case fields when a related contact record is updated, which automation tool is most appropriate and why
  • How email alert workflow actions differ from Case Comment notifications, and when each is the appropriate mechanism for keeping stakeholders informed
  • The difference between summary, matrix, and joined report types in Salesforce
  • When a joined report is necessary for contact center analytics across multiple objects
  • When an executive stakeholder wants a high-level view of contact center health, which standard Salesforce report types and dashboard components are most appropriate
  • How to design a case management dashboard for a contact center manager that shows open case volume, SLA compliance, and average handle time by queue
  • How to design role-appropriate report access using folder sharing and public group assignments in Salesforce to ensure the right stakeholders see the right data
  • How dynamic dashboards work in Salesforce and when they are the appropriate choice over standard dashboards for showing individual agent-level metrics to each agent
  • How to use Omni-Channel reporting objects (AgentWork, UserServicePresence) to report on agent availability, handle time, and routing efficiency
  • When a company needs to track SLA compliance using entitlement milestones in reports, which report objects are required and what limitations exist
  • How to report on Knowledge article usage and deflection by embedding article view and attach metrics into case reporting
  • How to build a report that tracks First Contact Resolution (FCR) rate by case type and agent, and what custom fields or process requirements support this metric
  • How to use bucketing and cross-filters in reports to segment case volume by resolution type, priority tier, or channel without creating custom fields
  • How row-level formula fields in reports can calculate derived metrics (e.g., days to resolve, SLA breach percentage) without requiring custom formula fields on the object
  • How to configure report subscriptions and dashboard scheduling to deliver automated KPI summaries to team leaders without manual effort
  • The limitations of standard Salesforce reporting for contact center analytics and when to recommend CRM Analytics (formerly Tableau CRM/Einstein Analytics) as a supplement
  • The use cases for CTI (Computer Telephony Integration) adapters in Service Cloud and how Open CTI supports third-party telephony providers without native telephony
  • How Service Cloud Voice differs from Open CTI in terms of architecture, native capabilities, and the telephony provider options supported
  • How Salesforce External Objects using Salesforce Connect differ from standard integration approaches, and when external objects are the preferred solution for real-time data display
  • When a company has customer data in an external ERP and agents need real-time account information while working a case, which integration pattern (external objects, Apex callout, MuleSoft) is appropriate and why
  • The use case for MuleSoft as an integration middleware for Service Cloud versus direct API integration, and the criteria that justify the added architectural complexity
  • How to evaluate and recommend AppExchange solutions for common Service Cloud gaps (e.g., advanced telephony, field service, customer surveys) including compatibility and licensing considerations
  • The considerations for integrating a third-party field service management system with Service Cloud, including bidirectional sync, case handoff, and scheduling data

Prepare for the Exam

Play Today's Certle
Back to track

Study Community

Ask questions and get the latest info from other Agentforce Service Consultant studiers.

Go to Discord

How parent-child case relationships work in Salesforce and when splitting a complex issue into child cases is preferable to managing it as a single record

Explainer

Learn More

Practice Question

Keep going

Next conceptHow to associate multiple contacts with a single case using case contact relationships, and the limitations of the standard case contact field versus a custom relationship

Checklist progress

0/163 (0%)

0 of 163 concepts learned

Tip: You can filter concepts by status.

Prepare for the Exam

Play Today's Certle
Back to track

Study Community

Ask questions and get the latest info from other Agentforce Service Consultant studiers.

Go to Discord

Explainer

Parent-child case relationships link multiple case records to track a single issue or divide work among different agents. This structure allows teams to group similar cases for tracking or split complex issues into manageable parts for resolution.

Core information
  • Cases link via the Parent Case field, which requires an existing parent case to be specified.
More details and nuances
  • A parent case must exist before it can be selected in the Parent Case field.