Salesforce Cases

A customer writes to a company because a product stopped working. The company needs a reliable way to track that complaint from the first message to the final fix. Salesforce uses the Case object for this job. A case holds every detail of one customer issue: who reported it, what went wrong, how urgent it feels, and who owns the work.

Sales teams win customers. Service teams keep them. Cases belong to the service side of Salesforce, known as Service Cloud, and give support agents a shared workspace instead of scattered emails and sticky notes.

What a Case Record Contains

Every case stores fields that describe the problem and its progress. Agents fill some fields by hand, and Salesforce fills others automatically.

Field	Purpose	Sample Value
Case Number	Unique ID that Salesforce generates	00001045
Subject	One-line summary of the issue	Printer shows error 42
Description	Full details from the customer	Error appears after paper loading
Status	Current stage of the work	New, Working, Escalated, Closed
Priority	Urgency level	Low, Medium, High
Case Origin	Channel the customer used	Email, Phone, Web
Contact and Account	The person and company who raised the issue	Priya Shah, Bright Print Ltd
Case Owner	User or queue that handles the work	Tier 1 Support Queue

The Case Life Cycle

A case moves through stages. Each stage tells the team what happens to the issue and who must act.

+-------+     +---------+     +-----------+     +--------+
|  New  | --> | Working | --> | Escalated | --> | Closed |
+-------+     +---------+     +-----------+     +--------+
   |               |                                 ^
   |               +---------------------------------+
   |                      (solved by Tier 1)
 Customer submits issue

Most cases skip the Escalated stage. An agent solves the problem and closes the case. Complex issues move to a senior team, and the status changes to Escalated.

Ways Cases Enter Salesforce

Manual Creation

An agent receives a phone call and clicks New on the Cases tab. The agent selects the contact, types the subject, and saves the record.

Email-to-Case

Customers send a message to a support address such as help@company.com. Salesforce converts each email into a case and attaches the message to the record. Replies from agents travel back to the customer by email, and the full conversation stays inside the case.

Web-to-Case

An admin generates an HTML form from Setup and places it on the company website. Visitors fill in the form, and Salesforce creates a case from every submission.

Experience Cloud Portal

Customers sign in to a branded help site, log their own issues, and follow the status without calling anyone.

Queues and Assignment Rules

A queue is a shared waiting list. New cases land in the queue, and any member of the support team picks one up. Queues prevent a single agent from carrying an unfair share of the load.

Assignment rules decide where each new case goes. An admin writes the rules with simple conditions.

New Case arrives
      |
      v
Is Priority = High? ----Yes----> Senior Support Queue
      |
      No
      v
Is Origin = Web? -------Yes----> Web Support Queue
      |
      No
      v
General Support Queue

Escalation Rules

Escalation rules protect customers from long waits. An admin sets a time limit, such as four hours for high priority cases. A case that stays unresolved past the limit triggers an action. Salesforce can reassign the case to a manager and send a notification email.

Case Comments, Emails, and Case Teams

Agents add internal comments to share notes with colleagues. Public comments reach the customer through a portal. Emails sent from the case record store a permanent history.

A case team brings several people to one case. A support agent, an engineer, and an account manager each hold a role and see the same details.

Knowledge Articles

Salesforce Knowledge stores answers to common problems. An agent searches the article library while working on a case and attaches the best match to the record. The customer receives a consistent answer, and the team avoids rewriting the same instructions every day.

Example Scenario: Laptop Warranty Claim

Ravi buys a laptop, and the screen flickers after two weeks. He emails the support address.

Ravi sends email
      |
      v
Email-to-Case creates Case 00001201
      |
      v
Assignment rule sends it to Hardware Queue
      |
      v
Agent Meena takes the case, status = Working
      |
      v
Knowledge article suggests a driver update
      |
      v
Fix fails, Meena changes status = Escalated
      |
      v
Repair team arranges a replacement, status = Closed

Every step stays visible in one record. Ravi gets updates by email, and the manager sees the resolution time on a report.

Best Practices

• Write clear subjects so teammates scan the list quickly.
• Use required fields for Priority and Origin to keep reports accurate.
• Build reports on case status, age, and owner to find bottlenecks.
• Close cases with a reason so trends become visible over time.
• Review escalation rules every quarter as team size changes.