Salesforce case management is the process of capturing a customer issue, assigning it to the right team, tracking the work, communicating with the customer, and closing the case with a clear outcome.

The Case record is the center of that process. It can hold the customer's question, status, priority, owner, account and contact relationships, comments, emails, files, activities, entitlements, milestones, and other information your support team needs.

A well-designed case process does more than organize tickets. It gives agents enough context to act, routes work consistently, makes escalations visible, and creates reliable data for service reporting. A poorly designed process usually creates the opposite: vague cases, manual reassignment, duplicate questions, and long threads asking the customer for information that should have been collected at the start.

This guide explains how Salesforce case management works and how to design a practical process for a modern support team.

Quick answer: Effective Salesforce case management has seven stages: intake, classification, routing, investigation, collaboration, resolution, and review. The biggest improvement most teams can make is to capture better context early - including screenshots, files, or a short customer screen recording when the issue is difficult to describe.

1. What is a Salesforce Case?

A Salesforce Case represents a customer issue, problem, question, request, or complaint that needs to be managed by a team. A case can be created manually by an agent or generated through channels such as email, a web form, an Experience Cloud site, an integration, or an API.

Typical examples include:

- A customer cannot complete checkout.
- A user needs help configuring a feature.
- An account owner reports incorrect billing information.
- A customer asks for a product change or data export.
- A partner needs an issue escalated to engineering.

The record gives everyone working on the issue a shared place to see what happened, what has already been tried, who owns the next action, and whether the customer is waiting.

For a more technical explanation of the record itself, including its fields, relationships, and API structure, see our guide to the Salesforce Case object.

Salesforce Case vs. Salesforce Support Case

These terms are easy to confuse.

A Salesforce Case is a record your organization uses to manage an issue for one of your customers or users.

A Salesforce Support Case is a ticket your organization opens with Salesforce when you need help with Salesforce itself.

This article is about the first meaning: managing your own customer service process with the Salesforce Case object.The Salesforce case management lifecycle

The exact workflow varies by company, but most effective processes follow the same basic lifecycle.

1. Intake: create the case with enough information

The first step is to capture the issue. Cases may enter Salesforce through:

- An agent creating a case during a phone or chat conversation
- Email-to-Case
- Web-to-Case or a custom support form
- An authenticated Experience Cloud portal
- A product or mobile application
- A partner integration or API
- A monitoring or incident-management workflow

The intake experience should collect only the information needed to route and begin work. Long forms create friction, but forms that are too short create clarification loops.

A useful minimum often includes:

- Contact and account
- Subject
- Description
- Product or service area
- Issue type
- Business impact
- Priority or urgency indicators
- Environment, browser, device, or version when relevant
- Error message or steps already attempted
- Supporting file, screenshot, or video when the issue is visual

Do not ask customers to diagnose the technical cause. Ask them to describe the outcome they expected, what actually happened, and the steps that led to it.
Salesforce supports several ways to collect supporting evidence. Our guide to uploading files to Salesforce records compares the main options for agents, administrators, developers, and external users.

2. Classification: turn the request into structured data

A free-text description is useful for people, but structured fields make routing, automation, reporting, and trend analysis possible.

Common classification fields include:

- Type
- Reason
- Product
- Feature area
- Channel or origin
- Customer tier
- Severity
- Language
- Region
- Entitlement or service plan

Keep the taxonomy manageable. A list with dozens of overlapping values will produce unreliable data because agents interpret the choices differently. Start with the decisions the data needs to support: routing, service-level commitments, reporting, and product feedback.

3. Routing: assign the case to the right owner

A case can be owned by a user or a queue. Salesforce provides several ways to automate distribution, including queues, assignment rules, Omni-Channel routing, Flow, and other service automation.

A practical routing model usually considers:

- Product or issue category
- Customer segment or service level
- Language and region
- Agent skill
- Current workload and availability
- Severity or business impact

Use queues when a team shares responsibility for a category of work. Use direct assignment when ownership must be explicit from the moment the case is created. Whichever model you choose, define what happens when no rule matches; an unmonitored default queue is a common source of missed cases.

4. Investigation: give the agent the full context

Once assigned, the agent needs to understand the issue before proposing a solution. The case page should bring the most useful information into one workspace:

- Customer and account details
- Recent cases and known issues
- Entitlement or support plan
- Product, asset, order, or subscription information
- Full customer description
- Email and conversation history
- Case comments
- Files and attachments
- Internal notes and activities
- Related engineering or incident records

This is where case quality matters. An agent cannot work efficiently from a subject such as "It does not work" and a one-line description.

For a visual or multi-step problem, the fastest next action may be to request a short screen recording. A customer can show the exact clicks, state changes, and error messages that a screenshot or written description misses.

With Videolink's Salesforce integration, teams can add video context to Salesforce records and request a video from the customer directly from the case workflow. The customer can record the issue without turning the support interaction into a scheduled meeting.

5. Collaboration: keep internal and customer communication distinct

Cases often involve several audiences:

- The customer
- The case owner
- A specialist or escalation team
- Product or engineering
- An account manager or customer success manager
- A partner or implementation consultant

Use the appropriate Salesforce feature for each type of communication:

- Case comments for public or private notes associated with the case
- Email for direct customer communication and a complete correspondence trail
- Activities for calls, tasks, and follow-up work
- Chatter or collaboration tools for internal discussion where appropriate
- Related records for defects, incidents, changes, or engineering work
- Files or video context when the issue needs visual evidence

Avoid copying the same information into several places. Define a source of truth for the current customer-facing response and another for internal investigation notes if your process requires separation.

The visibility of a comment depends on how it is created and configured. Read our full guide to Salesforce Case Comments for public and private comment behavior, setup considerations, and common limitations.

6. Escalation: act before a case becomes overdue

Escalation should be based on clear conditions, not on an agent remembering to ask for help.

Examples include:

- A high-severity case has no owner after 15 minutes.
- A customer has not received a first response within the target time.
- The case remains in a waiting-for-agent status too long.
- The issue affects multiple customers.
- A strategic account reports a business-critical problem.
- A milestone is approaching or has been violated.

Salesforce escalation rules can trigger actions when a case remains unresolved for a defined period. Flow and other automation can support more detailed scenarios, such as notifying a manager, changing priority, creating an engineering record, or assigning the case to a specialist queue.

Escalation is not simply raising the priority. It should change the response: who owns the issue, who is informed, what timeline applies, and how the customer is updated.

7. Resolution and review: close the case with usable data

A case should be closed only when the issue is resolved according to your policy. Before closure, capture enough information to make the outcome useful later.

Recommended closure data includes:

- Resolution summary
- Root cause or cause category, when known
- Resolution code
- Product or feature involved
- Whether a workaround was used
- Related problem, incident, bug, or knowledge article
- Customer confirmation, when required
- Follow-up task or product feedback

A strong resolution summary explains what was wrong and what fixed it. "Resolved" is not useful for the next agent, the customer, or a reporting team.

After closure, analyze recurring patterns. Cases are not only operational records; they are a direct source of information about product friction, documentation gaps, onboarding problems, and customer risk.

2. How to set up Salesforce case management

Use this implementation sequence to avoid configuring isolated features without a coherent workflow.

Step 1: define the service process before configuring Salesforce

Map the current process from customer request to closure. Identify:

- Entry channels
- Teams and responsibilities
- Triage decisions
- Status transitions
- Service-level commitments
- Escalation paths
- Required customer communications
- Closure criteria

Do not begin by recreating every field and status from a legacy system. Start with the decisions agents and managers need to make.

Step 2: design statuses around responsibility

A good status tells the team what is happening and, ideally, who is expected to act next.

A simple model could include:

- New
- In Progress
- Waiting for Customer
- Waiting for Internal Team
- Resolved
- Closed

Avoid using status values as a substitute for issue type, priority, or escalation level. Each field should answer a distinct question.

Step 3: configure fields, layouts, and record types

Show the fields agents need for the current task and hide irrelevant fields. If different support processes genuinely require different stages or data, use record types and page layouts carefully.

Keep the case page focused. A record with dozens of empty fields makes important information harder to find.

Step 4: add queues and assignment logic

Create queues for clear operational responsibilities, then configure assignment rules, Flow, or Omni-Channel according to your distribution model.

Test each intake channel. A routing rule that works for manually created cases may behave differently for cases created through email, a portal, or an integration.

Step 5: configure notifications and escalation

Decide who should receive notifications for:

- New high-priority cases
- Reassignments
- New customer responses
- New case comments
- Milestone warnings
- Escalations
- Reopened cases

Too many alerts are ignored. Send notifications only when the recipient is expected to take an action.

Step 6: standardize information collection

Create guidance for customers and agents. For technical cases, ask for:

1. The intended outcome
2. The actual result
3. Reproduction steps
4. Time and environment
5. Exact error text
6. Relevant files or visual evidence

For issues that are hard to explain, add a Request a Video action to the case. A short recording often captures the sequence, page state, and user behavior more clearly than a long description.

Step 7: build reports and dashboards

Track a small set of metrics tied to service outcomes. Useful measures include:

- New and closed cases by period
- Open backlog
- Backlog age
- First response time
- Time to resolution
- Reopen rate
- Escalation rate
- Cases by product, reason, and channel
- Cases waiting for the customer vs. waiting for an agent
- Service-level or milestone attainment

Use median and distribution views where possible. Averages can hide a small group of very old or very complex cases.

3. Salesforce case management best practices

Make the first case description actionable

Use prompts and examples instead of a blank text box. "Tell us what you expected, what happened, and the steps to reproduce it" produces better information than "Describe your problem."

Use video selectively

Not every case needs video. A password reset or address change can be handled with structured fields and text. Video is most useful when the issue involves:

- A sequence of clicks
- Intermittent behavior
- A visual defect
- A complex configuration
- An error that depends on page state
- Hardware, equipment, or a physical environment
- A user experience that is difficult to describe

Separate priority from customer frustration

A frustrated customer deserves an empathetic response, but priority should follow a consistent impact model. Define severity using factors such as affected users, business process impact, availability of a workaround, data risk, and time sensitivity.

Automate predictable work, not judgment

Automate classification suggestions, routing, notifications, reminders, and repeatable data updates. Keep human review for ambiguous issues, customer-sensitive decisions, and complex resolutions.

Keep customer-facing and internal notes clear

Agents should always know whether a comment will be visible to the customer. Use templates and interface guidance to reduce accidental disclosure of internal information.

Link cases to reusable knowledge

When a case reveals a repeatable answer, update or create a knowledge article. When it reveals a product defect, link the case to the relevant engineering or incident record. The goal is to prevent the next customer from requiring the same investigation.

Review the taxonomy regularly

Products, teams, and customer needs change. Review case reasons, routing rules, statuses, and reports at least quarterly. Merge values that agents use inconsistently and add new values only when they support a real operational decision.

4. How video improves Salesforce case context

Text and screenshots are useful, but they often fail to capture movement and sequence. A customer may report that a button "does nothing," while a recording shows that a validation message appears briefly, the page refreshes, or the user follows an unexpected path.

A video-enabled case workflow can work like this:

1. The customer opens a case with a written description.
2. The agent determines that visual context is needed.
3. The agent clicks **Request a Video** in Salesforce.
4. The customer opens the request link and records their screen or camera without scheduling a call.
5. The recording is associated with the case, giving the agent and any escalation team the same visual evidence.
6. AI captions or a summary can make the recording easier to review and search, depending on the Videolink configuration.

Video is only one part of a complete service stack. Our overview of Salesforce customer support software covers tools for visual issue capture, telephony, automation, knowledge management, document generation, and reporting.

5. Recommended Salesforce case management checklist

Before launching or redesigning your process, confirm that:

- Every intake channel creates a complete, correctly owned case.
- Required fields support routing or investigation rather than adding unnecessary friction.
- Status values make the next responsibility clear.
- Queues have active members and a monitored fallback process.
- Assignment, notification, and escalation rules have been tested.
- Agents can find recent customer history, comments, files, and related records quickly.
- Public and private communication is clearly separated.
- Customers have a simple way to provide additional evidence.
- Visual issues can be captured with a screenshot or video request.
- Closure requires a meaningful resolution summary.
- Dashboards measure backlog, speed, quality, and recurring demand.
- A Salesforce administrator owns ongoing process governance.

6. Frequently asked questions

What is case management in Salesforce?

Case management in Salesforce is the process of recording, assigning, tracking, communicating about, resolving, and reporting on customer issues through the Case object and related service features.

What is the difference between a Case and a ticket?

They are often used to mean the same thing. "Ticket" is a general support term. "Case" is the Salesforce record used to manage that support request.

Can customers create Salesforce Cases?

Yes. Cases can be created through email, web forms, Experience Cloud, APIs, integrations, and other service channels. The best channel depends on the customer's identity, the information you need, and your security model.

Can you attach a video to a Salesforce Case?

Yes. A team can upload a video as a Salesforce File, link to externally hosted video, or use an integration designed to place video context in the case workflow. The right approach depends on file size, playback experience, storage, sharing, retention, and security requirements.

How can an agent request a video from a customer?

With Videolink's Salesforce integration, an agent can send a video request from the case workflow. The customer opens the link, records the issue, and returns visual context without needing a scheduled call.

Which Salesforce features are used for case automation?

Common options include queues, case assignment rules, escalation rules, auto-response rules, Flow, Omni-Channel, entitlements, milestones, and integrations. The correct combination depends on the service process and Salesforce edition.

Sources and further reading

- Salesforce, Case Management Best Practice Guide
- Salesforce Developers, Case Object Reference
- Videolink, Request a Video for Customer Support