Case Management

Service Cloud is Salesforce's customer service and support platform — designed to help companies resolve customer issues faster, smarter, and across every channel.

Think of Service Cloud like a "Super Customer Care Center"

• Customer calls, emails, chats, or tweets about a problem
• All requests land in one unified platform
• Agent sees full customer history instantly
• Issue is resolved faster than ever
• Customer leaves happy

What is a case?

A case is a formal record created whenever a customer has a problem, question, or request. Think of it like a support ticket — it holds all the information about an issue and tracks it until it's solved.

Every case has fields like: Case ID, Subject, Description, Priority, Status, Channel (how it came in), Account/Contact linked, Owner (who is handling it), and Created Date.

Example: Rahul emails TechSupport Inc. saying: "My invoice module stopped working after the latest update." The system creates Case #10042 with Subject: "Invoice module broken after update", Priority: High, Status: New.

Case lifecycle

Once a case exists, it moves through stages. Each stage reflects what's happening with the issue right now.

• New — Just created, nobody is working on it yet.
• Assigned — Routed to an agent or team.
• In progress — Agent is actively investigating or working on a fix.
• Pending — Waiting on something — either the customer needs to reply, or a developer is fixing a bug.
• Closed — Issue resolved and confirmed.

Example with Rahul's case: New (created via email) → Assigned to Priya (billing tech agent) → In Progress (Priya reproduces the bug) → Pending (engineering team deploys a patch) → Closed (Rahul confirms it works)

Case creation methods

Cases can enter the system through different channels. The method of creation is automatically recorded as the "Origin" of the case.

·         Web-to-case: Rahul fills out a support form on TechSupport Inc.'s website. The form fields (name, email, issue description) automatically create a case record.

·         Email-to-case: Rahul emails support@techsupportinc.com. The system reads the email and creates a case instantly — subject line becomes the case subject, email body becomes the description.

·         Manual: An agent on a phone call with Rahul manually opens a new case record while talking to him and fills in the details.

·         API/Integration: TechSupport Inc.'s monitoring tool automatically detects an error in Rahul's account and creates a case via API — no human involvement at all.

·         Chat/Social: Rahul sends a message on the live chat widget. The agent clicks "Convert to Case" and a case record is created from the chat transcript.

Case assignment rules

Assignment rules are like automatic traffic cops — they look at the case details and decide who should handle it, without any manager having to manually route it.

The system evaluates rules in order. The first rule that matches wins, and the case gets routed accordingly.

Example rules at TechSupport Inc.:

• Rule 1: If Product = Billing Module AND Priority = High → Assign to Billing Tech Queue
• Rule 2: If Country = India AND Language = Hindi → Assign to India Support Team
• Rule 3: If Case Type = Bug → Assign to Engineering Triage Queue
• Default: If no rule matches → Assign to General Support Queue

Rahul's case matches Rule 1 (Billing Module + High Priority), so it goes straight to the Billing Tech Queue. Agent Priya picks it up from there.

Service Console

Salesforce Service Cloud Service Console is a centralized workspace in Salesforce designed for customer support agents. It helps agents manage customer interactions, resolve cases faster, and improve productivity by providing all required information on a single screen.

Instead of opening multiple browser tabs or switching between pages, agents can access Cases, Accounts, Contacts, Chats, Emails, Knowledge Articles, and Activities from one interface.

Example

Suppose a customer contacts support regarding a delayed shipment:

• The agent opens the Case in Service Console.
• Related Contact and Account details appear automatically.
• Previous cases and email history are visible.
• The agent checks a Knowledge Article for the solution.
• The issue is resolved without switching screens.

Console Navigation

Console Navigation is the layout style used in Service Console that allows users to work with multiple records simultaneously using tabs and subtabs.

Features of Console Navigation

• Primary tabs for major records
• Subtabs for related records
• Easy switching between records
• Persistent workspace for multitasking

Example

A support agent is handling Case #1001:

• Main Tab → Case #1001
• Subtab → Customer Contact
• Subtab → Shipment Details
• Subtab → Email Conversation

The agent can move between all related records without losing context.

Split View

Split View allows users to view a list of records on one side and the selected record details on the other side of the screen.

It helps agents quickly move through records without repeatedly going back to the list page.

Example

A support team member is reviewing open Cases:

• Left Side → List of open cases
• Right Side → Details of the selected case

The agent clicks each case from the list and instantly sees its details on the same screen.

Productivity Tools

Productivity Tools in Service Console help support agents automate repetitive work and handle customer requests more efficiently. These tools reduce manual effort and increase response speed.

Common Productivity Tools

1. Macros

Macros automate repetitive actions.

Example

A customer requests password reset:

• Update Case Status
• Send predefined email
• Close the Case

2. Quick Text

Quick Text stores predefined responses.

Example

·         Instead of typing:
“Thank you for contacting support. We are investigating your issue.”

·         The agent inserts a Quick Text template instantly.

3. Knowledge Articles

Agents can search help articles directly from Service Console.

Example

·         A customer asks how to update billing information.
The agent searches a Knowledge Article and shares the solution immediately.

4. Omni-Channel

Automatically assigns work items to available agents.

Eample

If Agent A is busy and Agent B is available:

• New chat or case is automatically routed to Agent B.

5. History Utility

Shows recently viewed records.

Example

·        An agent accidentally closes a Case tab.
Using History Utility, they can reopen it quickly.

Knowledge Management

Salesforce Knowledge Management is the process of creating, organizing, maintaining and sharing information so that employees and customers can quickly find solutions to common problems.

Example

A telecom company receives thousands of questions like:

• How to reset router?
• How to change Wi-Fi password?
• How to recharge plans?

Instead of agents answering repeatedly, the company creates Knowledge Articles for these topics.

Knowledge Articles

Knowledge Articles are documents that contain solutions, guides, FAQs, troubleshooting steps, or product information.

Agents and customers use these articles to solve issues quickly.

Types of Knowledge Articles

• FAQ Articles
• Troubleshooting Guides
• Product Manuals
• How-To Articles
• Policy Documents

Example

Article Title:

“How to Reset Your Password”

Article Content:

1. Click “Forgot Password”
2. Enter registered email
3. Verify OTP
4. Create new password

When customers face login issues, agents simply share this article instead of explaining the process repeatedly.

Article Lifecycle

The Article Lifecycle defines the stages through which a Knowledge Article passes from creation to retirement.

Stages of Article Lifecycle

1. Draft

The article is created but not published yet.

Example

A support manager writes an article about a new feature release.

2. Review

The article is checked for accuracy and approval.

Example

The technical team verifies whether all troubleshooting steps are correct.

3. Published

The article becomes available to agents or customers.

            Example

Customers can now search and read the article in the Help Center.

4. Archived

The article is no longer active but kept for historical reference.

Example

An article about an old software version is archived after product upgrade.

Data Categories

Data Categories are used to organize Knowledge Articles into groups so users can search and access relevant content easily.

Example Structure

Category Group: Product

• Mobile App
• Internet Services
• Banking Portal

Category Group: Region

• India
• USA
• Europe

An article about UPI payment issues may belong to:

• Product → Banking Portal
• Region → India

Example

Suppose a global company has different support articles for different countries.

Using Data Categories:

• Indian customers see India-related articles.
• US customers see US-specific articles.

This improves relevance and user experience.

Knowledge for Agents

Knowledge for Agents means giving support agents direct access to Knowledge Articles inside the Service Console.

Agents can search, open, and share articles while handling customer cases.

Example

Imagine a customer support center handling 5,000 cases daily.

Without Knowledge:

• Agents depend on personal experience
• Responses vary
• Resolution time increases

With Knowledge for Agents:

• Agents search standardized solutions
• Cases resolve faster
• Customer satisfaction improves

Omni-Channel

Salesforce Omni-Channel Omni-Channel is a Salesforce Service Cloud feature that automatically routes work items such as Cases, Chats, Leads, Messaging sessions, or Tasks to the most appropriate support agent in real time.

Why Companies Use Omni-Channel

• Faster customer response time
• Balanced workload distribution
• Reduced manual assignment
• Improved customer satisfaction
• Better agent productivity

Example — Chat Support

Suppose:

• Priya can handle maximum 3 chats
• She already has 3 chats open

New customer starts chat:

“Website not loading.”

Omni-Channel will NOT assign it to Priya because capacity is full.

Instead it routes to another available technical agent.

Omni-Channel Routing

Omni-Channel Routing is the process of automatically assigning work items (Cases, Chats, Leads, Messaging sessions, Tasks, etc.) to the most suitable available agent.

Routing decides:

• Who should get the work
• When they should get it
• Based on what conditions they should get it

Types of Omni-Channel Routing

1. Queue-Based Routing

Most common routing method.

Work goes to a queue first, then Omni assigns it.

Example

·         Billing Queue

·         Tech Queue

2. Skills-Based Routing

Routing based on agent skills.

Example

·         Customer speaks French.

·         Omni routes case only to agents having:

·         Skill = French Language

3. External Routing

Work assigned by external systems.

Example

·         Third-party AI engine

·         External workforce management system

Agent Workload Management

Agent Workload Management ensures that customer work (Cases, Chats, Tasks, etc.) is evenly distributed among support agents based on their capacity and availability.

Example:

A support agent, Rahul, already has 5 active cases and his maximum capacity is full. When a new high-priority case arrives, Salesforce’s workload management prevents assigning it to Rahul and instead routes it to Priya, who has available capacity. This ensures no agent is overloaded and customers receive faster responses.

Presence Status

Presence Status shows whether a support agent is available to receive work through Omni-Channel.

Example:

An agent sets their status to “Available for Chat” in the Omni-Channel widget. Now, they will receive incoming chat requests automatically. If the agent changes status to “Busy” or “Offline,” no new work (like cases or chats) will be routed to them until they become available again.

Entitlements & Service Contracts

Service Contracts define the agreement between a company and a customer (like warranty or support period), while Entitlements define what support a customer is eligible for (response time, service level, etc.).

Example:

A customer buys a laptop with a 1-year service contract. As part of it, they also get an entitlement that says “High Priority support with 24-hour response time.” When the customer raises a case within the contract period, Salesforce automatically checks the entitlement and ensures the case is handled within the promised SLA.

Entitlement Management

Entitlement Management is used to control and track the level of support a customer is eligible for based on their service contracts, warranties, or support plans.

Example:

A customer purchases a premium support plan that includes 24x7 support and 1-hour response time. When the customer logs a case, Salesforce automatically checks their entitlement and allows only eligible support actions while ensuring the case is handled within the defined SLA.

Service Level Agreements (SLAs)

Service Level Agreements (SLAs) are predefined commitments between a company and its customers that define how quickly and efficiently customer issues must be handled. SLAs specify key service targets such as first response time, resolution time, and escalation rules, ensuring that customer support follows a consistent and measurable standard.

Example

A company defines an SLA where high-priority cases must receive a first response within 1 hour and must be resolved within 24 hours. When a customer logs a high-priority issue, Salesforce automatically starts the SLA timer. If the agent does not respond within 1 hour, the system flags the case as “at risk” and escalates it to a senior agent or manager to ensure the commitment is met.

Milestones

Milestones are individual, measurable steps within a Service Level Agreement (SLA) that track specific time-bound service goals for a case. Each milestone represents a critical support activity such as first response, resolution time, or follow-up action, and Salesforce monitors them automatically to ensure compliance with service commitments.

Example

A company defines an SLA for premium customers with two milestones:

• First Response Milestone: Agent must respond within 1 hour of case creation
• Resolution Milestone: Case must be resolved within 24 hours

When a customer raises a high-priority case, Salesforce starts tracking both milestones. If the agent responds in 45 minutes, the first milestone is completed successfully. However, if the case is still open after 24 hours, the resolution milestone is breached, and the system automatically escalates the case to a senior support manager.

Case Resolution Tracking

Case Resolution Tracking is the process of monitoring and managing the complete lifecycle of a customer case from creation to closure. It helps support teams ensure that every issue is resolved within defined timelines (SLAs), with proper updates, ownership, and status changes recorded at each stage.

This tracking provides visibility into how long a case takes to resolve, which agent handled it, what actions were taken, and whether service standards were met. It also helps organizations identify bottlenecks, improve response time, and maintain customer satisfaction.

Example

A customer raises a case for a payment deduction issue. Salesforce assigns the case to a billing agent and starts tracking it. The agent updates the status from New → In Progress → Waiting for Customer → Resolved. During this process, Salesforce records how long each stage takes and checks it against the SLA. Once the issue is fixed and the customer confirms resolution, the case is marked as Closed, and the full resolution history is stored for reporting and analysis.