1. Cases & Case Management
What is a Case?
A Case is the core object in Service Cloud. It tracks customer issues, questions, and requests from creation to resolution. Each case can have related emails, activities, knowledge articles, and child cases.
Case Creation Methods
- Email-to-Case: Automatically creates cases from incoming customer emails. On-Demand Email-to-Case handles high volumes without firewall requirements.
- Web-to-Case: Creates cases from a web form. Limit: 5,000 submissions per day.
- Manual: Agents create cases directly in Salesforce.
- Social Customer Service: Creates cases from Twitter, Facebook, Instagram posts.
- API/Integration: External systems create cases via API.
Case Assignment Rules
Assignment Rules automatically route cases to users or queues based on criteria (case origin, priority, product, customer type). Only one active assignment rule per object, but that rule can have up to 25,000 rule entries.
Auto-Response Rules
Auto-Response Rules send automated email responses to customers when cases are created. Only ONE active auto-response rule per object. Used to confirm receipt and set expectations.
Escalation Rules
Escalation Rules automatically change case priority or reassign cases that haven't been resolved within a defined time limit — preventing SLA breaches by triggering actions when cases age out.
Case Teams
Case Teams allow multiple users to collaborate on a complex case with defined roles. Each team member gets appropriate access (Read or Read/Write) to the case and related records.
💡 The Service Console provides a multi-panel workspace where agents can see the case, account, contact, knowledge, and activity all in one screen — maximizing efficiency.
2. Entitlements & SLAs
Entitlements
Entitlements define the level of support a customer is entitled to based on their contract (e.g., 24/7 phone support, 4-hour first response, next-day on-site service). They link to Accounts, Contacts, or Assets.
Entitlement Processes
An Entitlement Process is a timeline of steps (Milestones) that cases must complete to meet SLA terms. Processes can be applied to Cases or Work Orders.
Milestones
Milestones are measurable steps in an entitlement process with specific time targets. Examples:
- First Response — respond within 4 hours
- Resolution — resolve within 24 hours
When a milestone is at risk (approaching its deadline), warning actions fire. When violated, completion actions fire. Milestones can be required or optional.
SLA Tracking Flow
- Customer has a Service Contract defining support terms
- An Entitlement is created (linked to Account/Contact/Asset)
- An Entitlement Process defines the Milestone timeline
- When a case is created and linked to the Entitlement, Milestone tracking begins
- Actions fire when Milestones are approaching or violated
Entitlement Processes can be applied to Cases AND Work Orders — not just Cases. Many candidates assume they only apply to Cases. Also, only ONE active Entitlement Process can run per case at a time.
3. Omni-Channel
What is Omni-Channel?
Omni-Channel is Salesforce's intelligent routing engine that distributes work items (cases, chats, social posts, custom objects) to available agents based on their skills, capacity, and priority — in real time.
Key Omni-Channel Concepts
| Concept | Description |
|---|---|
| Routing Configuration | Defines how items are routed (Least Active, Most Available, or Queue-Based) |
| Service Channel | Represents a work item source (Cases, Chats, Leads, custom objects) |
| Presence Status | Defines agent availability states (Available, Busy, Away) |
| Presence Configuration | Sets the total capacity for agents using a presence config |
| Queue | Holds work items waiting to be assigned |
| Skills | Attributes assigned to agents (language, product expertise) for skills-based routing |
Routing Models
- Queue-Based: Routes to whichever agent in the queue picks up next
- Skills-Based: Routes to agents with matching skills
- Least Active: Routes to the agent with the fewest open work items
- Most Available: Routes to the agent with the most remaining capacity
Omni-Channel Supervisor
Real-time dashboard for supervisors showing agent availability, workload, queue backlogs, and handle times. Supervisors can reassign work, monitor status, and spot bottlenecks instantly.
💡 Capacity settings determine how many simultaneous work items each agent can handle. Different channels can have different capacity weights — e.g., each chat might use 1 capacity unit, each complex case might use 2.
4. Knowledge
What is Salesforce Knowledge?
Salesforce Knowledge is an article management system where teams create, manage, review, and publish articles for internal agents, customer portals, and public help centers — reducing case volume and resolution time.
Article Lifecycle
- Draft: Article is being written/edited
- In Review: Undergoing approval/quality review
- Published: Live and visible to the configured audience
- Archived: No longer published, but retained for reference
Knowledge Article Channels
- Internal App: Visible to agents in Salesforce
- Customer: Visible to authenticated Experience Cloud users
- Partner: Visible to partner portal users
- Public Knowledge Base: Visible to anonymous web visitors
Einstein Article Recommendations
Einstein automatically analyzes case details and surfaces relevant Knowledge Articles in the Service Console — helping agents resolve cases faster without manual searching. This directly improves First Call Resolution (FCR) rates.
Case Deflection
Case Deflection measures how effectively self-service tools (knowledge, chatbots, communities) prevent customers from submitting support cases — reducing support costs and improving customer experience.
5. Channels (Chat, Email, Social)
Email-to-Case
Monitors a support email address and automatically creates Cases from incoming emails. The email thread stays linked to the case. On-Demand Email-to-Case handles unlimited volume without server-side configuration.
Live Agent / Messaging (Chat)
Enables real-time web chat between customers and agents. Agents can handle multiple simultaneous chats. Chat Buttons control when the chat widget appears (based on agent availability) and which queue receives the chat.
Social Customer Service
Connects Twitter, Facebook, and Instagram to Service Cloud. Customer posts become cases, and agents respond directly from within Salesforce — no need to switch between tools.
Service Cloud Voice
Integrates telephony (Amazon Connect or partner providers) directly into Salesforce with real-time call transcription, Einstein guidance, and automatic activity logging — creating a unified agent desktop.
Quick Text
Quick Text stores pre-written messages that agents insert using shortcuts in any text field. Dramatically speeds up chat and email responses by eliminating repetitive typing.
Macros
Macros automate multi-step actions with one click — for example, updating case status, selecting an email template, and sending the email simultaneously. They save significant time on repetitive case-handling workflows.
| Channel | Tool | Daily Limit |
|---|---|---|
| Web form | Web-to-Case | 5,000/day |
| Email-to-Case | No limit (On-Demand) | |
| Real-time chat | Messaging/Live Agent | No hard limit |
| Social media | Social Customer Service | Varies by platform |
| Phone | Service Cloud Voice | No hard limit |
6. Einstein & AI in Service Cloud
| Feature | What It Does |
|---|---|
| Einstein Case Classification | Auto-recommends field values (Type, Priority, Reason) from case subject/description |
| Einstein Article Recommendations | Surfaces relevant knowledge articles in the console based on case details |
| Einstein Reply Recommendations | Suggests pre-written replies for agents during chat interactions |
| Einstein Case Routing | Uses AI to route cases to the right queue or agent based on content |
| Einstein Bots | Chatbot that handles common queries, collects info, and escalates to agents |
| Service Cloud Voice + Einstein | Real-time call transcription and next-best-action during phone calls |
Einstein Bots
Einstein Bots handle common customer queries through chat without agent involvement. They collect information, answer FAQs, and seamlessly transfer to human agents with full context when escalation is needed. Bots reduce agent workload and provide 24/7 availability.
Case Swarming
A modern support model where instead of escalating cases tier by tier, a swarm of experts collaborates simultaneously on complex cases using Slack or Chatter — dramatically reducing resolution time by eliminating handoff delays.
7. Service Cloud Cheat Sheet
| Item | Key Fact |
|---|---|
| Web-to-Case daily limit | 5,000 submissions/day |
| Auto-response rules per object | 1 active rule maximum |
| Entitlement Process applies to | Cases AND Work Orders |
| Milestone types | Required or Optional |
| Knowledge article states | Draft, In Review, Published, Archived |
| Knowledge channels | Internal, Customer, Partner, Public |
| Chat Button controls | When chat shows AND which queue receives it |
| Omni-Channel routing models | Queue-Based, Skills-Based, Least Active, Most Available |
| Dynamic Dashboards (Enterprise) | 5 maximum |
| Key KPIs | FCR (First Call Resolution), CSAT, AHT (Average Handle Time) |
| Case Teams | Multiple users collaborate on one case |
| Macros | Multi-step automation for agents (one-click actions) |
| Quick Text | Pre-written message shortcuts for agents |
| Service Cloud Voice provider | Amazon Connect (primary) or partner telephony |
8. Common Exam Traps
Web-to-Case limit is 5,000 submissions per day. Web-to-Lead is 500/day. These are commonly confused on the exam — remember Service gets 10x more than Sales.
You can only have ONE active auto-response rule per object (one for Cases, one for Leads, etc.). However, that rule can have up to 25,000 rule entries with different criteria.
Entitlement Processes can apply to both Cases AND Work Orders. Many candidates assume they only apply to Cases. Field Service Work Orders also need SLA tracking.
Omni-Channel routes ANY work item — Cases, Chats, Leads, Social Posts, and custom objects. It's not limited to cases. The channel type is configured via Service Channels in Setup.
Assignment Rules route the case to the right agent/queue. Auto-Response Rules send confirmation emails to the customer. They are separate features serving different purposes — don't confuse them.
Escalation Rules change priority, reassign, or send notifications — but they do NOT automatically close cases. Closing requires agent action or a separate automation (Flow).
Knowledge articles go through: Draft → In Review → Published → Archived. The exam tests knowledge of this lifecycle, particularly that archived articles are retained but not visible to end users.
Chat Buttons in Live Agent/Messaging control two things: when the chat widget appears (based on agent availability) AND which queue or skill group receives the incoming chat. One deployment can have multiple buttons.
🎯 Practice Mode
Instant feedback and study tips after each answer.
📝 Exam Mode
Answer all 50 questions then submit for your score.