Service Cloud Consultant Study Guide (Winter '26): Complete Exam Prep

Case Management (32%)

The largest section. Case queues: cases in a queue are visible to all queue members — agents must accept (take ownership) to claim a case. Assignment rules: evaluated in order (top to bottom), only the first matching rule fires. If no rule matches, the case is assigned to the default case owner. Escalation rules: trigger based on case age (open case, hours since creation); can change priority, reassign, or send notification. Auto-response rules: send automated emails to contacts when a case is created (web-to-case, email-to-case). Evaluated in order — first match fires. Case teams: predefined groups of agents with different access roles (read-only, read/write) who collaborate on a case — not the same as queues. Email-to-Case: routes inbound emails to cases; On-Demand Email-to-Case (Salesforce-hosted) vs Email-to-Case (organisation-hosted). Web-to-Case: HTML form generates cases from website submissions.

Omni-Channel and Interaction Channels (11%)

Omni-Channel routing models: Queue-based routing (routes work to queues, agents manually pull or are pushed from queue); Skills-based routing (routes directly to agents matching required skills, with fallback to queue). Routing configurations: push vs pull routing, capacity models (concurrent = number of work items, effort-based = weighted capacity per item), presence statuses (online, busy, offline) control agent availability. Service channels: each channel (cases, chats, messaging sessions) has a dedicated service channel object. Interaction channels: Email-to-Case (async), Live Agent/Chat (synchronous), Messaging (SMS, WhatsApp — async), Voice (CTI/phone). Know which channel is synchronous vs asynchronous and when each is recommended.

Knowledge Management (10%)

Lightning Knowledge: articles are categorised by data categories; visibility is controlled by data category visibility settings on profiles/permission sets. Article types: in Lightning Knowledge, all articles share a single article type (unlike Classic Knowledge). Article lifecycle: Draft → Published → Archived. Agents can suggest articles to customers from cases; articles can be attached to cases for tracking. Knowledge in Service Console: Knowledge One component shows relevant articles based on case subject/description. Key exam scenario: "agents need to search and attach articles while viewing a case in the console" → add Knowledge One component to the Service Console record page. Ensure agents have the Knowledge User permission.

Entitlements and Milestones (in Service Cloud Platform)

Entitlements define the level of support a customer is entitled to (e.g., 24/7 phone support, 4-hour response SLA). Linked to accounts, contacts, or assets. Milestones are required steps within an entitlement process (e.g., “First Response” in 4 hours, “Case Resolution” in 24 hours). Milestone conditions determine when the milestone is triggered (e.g., case opened with Priority = High). Milestone actions fire at specific times: on entry, on success (milestone completed), on violation (time exceeded). Entitlement processes bundle milestones and apply to cases — activate the process on the entitlement. Key exam point: cases must have an entitlement assigned for milestones to track.

Service Console (8%)

Lightning Service Console is a Lightning app with the “console navigation” style. Workspace tabs are the primary records (e.g., open case); subtabs are related records (e.g., the account, contact) accessed from the workspace. Split view shows a list view alongside the record — agents can switch cases without leaving the current record. Macros: automated actions that run multiple steps in sequence (send email, update field, change status) with a single click — saves agent time on repetitive tasks. Quick Text stores predefined message snippets agents insert into emails/chats. Utility bar: persistent panel at the bottom of the console for frequently used tools (notes, open CTI, macros).