Skip to content
Tutorials Center
My learning

Topics

Lesson 8 of 36 ยท CRM and Platform Concepts

Cases, Queues and Service Basics

Learn how Service Cloud handles customer problems: cases, statuses and priorities, queues, assignment and escalation rules, Email-to-Case, Web-to-Case and Knowledge.

When a customer has a problem, the company records it as a case. This lesson covers the case object, how cases reach the right person through queues and assignment rules, how escalation rules protect response times, and how Knowledge and email channels fit in.

The Case object

A case records one customer issue. Standard fields include:

  • Case Number: an automatic number, unique per org.
  • Subject and Description.
  • Status: New, Working, Escalated, Closed (admins can add values).
  • Priority: High, Medium, Low.
  • Origin: Phone, Email, Web (where the case came from).
  • Type and Reason: optional categories.
  • Account, Contact: who the customer is.
  • Owner: a user or a queue.

A case record page has a feed for comments and emails, related lists for emails, attachments and child cases, and often a Knowledge component to suggest articles. A support agent normally works in the Service Console, a tabbed app that keeps several cases and contacts open at once.

Case statuses

Statuses have two groups: Open and Closed. Each value marks whether it counts as closed. Editing them is done in Setup > Object Manager > Case > Fields > Status. The same place lets you set up support processes, which assign different status lists to different record types.

Queues

A queue is a shared list of records waiting for an owner. Instead of assigning a case to one person, you assign it to "Tier 1 Support", and any member can pick it up. Queues work for leads, cases, orders, and custom objects (the ones you enable).

To create a queue:

  1. Setup > Quick Find > Queues > New.
  2. Give it a label and optional queue email.
  3. Select the supported objects (for example Case).
  4. Add members: users, roles, public groups.
  5. Save.

A user takes a record from a queue by changing the owner to themselves (the Accept button on list views or the Change Owner action).

Python Stand-in: a queue and picking up cases

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Assignment rules

Case assignment rules decide the owner automatically when a case is created, based on its fields. A rule has ordered rule entries; the first entry whose criteria match wins. For example:

  1. If Priority equals High and Account Type equals Premium: assign to the "Premium Support" queue.
  2. If Origin equals Email: assign to "Email Team".
  3. Everything else: assign to "Tier 1 Support".

Only one assignment rule is active at a time per object. Rules run when records are created through channels that support them (Web-to-Case, Email-to-Case, API with assignment header, or a user checking Assign using active assignment rule). Lead assignment rules work the same way for leads.

Python Stand-in: ordered assignment rule entries

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Order matters: if the catch-all were first, nothing else would ever match.

Escalation rules

An escalation rule reacts to cases that sit too long. Each entry has criteria, an age limit and actions. When a case matches and stays open past the limit, Salesforce can reassign it (to a manager or a queue) and send email notifications. Business hours (Setup > Business Hours) decide when the clock runs, so a weekend does not count against a team that is off.

Related tools:

  • Entitlements and milestones: contractual response and resolution times for premium customers.
  • Omni-Channel: pushes work to available agents by capacity and skill.
  • Service Level Agreements tracking in the console.

Case channels

  • Email-to-Case: emails sent to a support address become cases, replies are threaded on the case. The recommended flavor is On-Demand Email-to-Case, where your mail system forwards support mail to a Salesforce routing address.
  • Web-to-Case: an HTML form on your site creates cases. Its form uses a default limit per day, so check your edition's allowance.
  • Phone: an agent logs a case while on the call, often using Open CTI softphones.
  • Chat and messaging: Digital engagement products create cases.
  • Experience Cloud: customers create their own cases in a portal.

Salesforce Knowledge

Knowledge is a library of articles (how-tos, known issues). Agents attach articles to cases and customers can search them. Articles have a lifecycle: Draft, Published, Archived, with versions and translations. An admin enables Knowledge, sets up data categories and article types or record types, and gives users the Knowledge User permission.

Email notifications and templates

Admins create email templates (Lightning or Classic) with merge fields like {{{Case.CaseNumber}}} for use in auto-response rules, flows and agent replies. Auto-response rules send an acknowledgement as soon as a web or email case arrives.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What is a queue used for?

    A queue is a shared owner; members pick up records and become their owner.
  2. 2. If two assignment rule entries both match a case, which one is used?

    Entries are evaluated in order and the first one whose criteria match decides the owner.
  3. 3. What does an escalation rule do?

    Escalation rules act on cases that have not progressed within the time you define.
  4. 4. Which channel turns incoming support emails into cases?

    Email-to-Case creates cases from email and threads replies back onto them.

Summary

  • A case records one customer issue; its owner can be a user or a queue.
  • Queues share work; assignment rules route new cases by ordered entries; escalation rules react to cases that wait too long.
  • Cases arrive from email, web, phone, chat and portals; Knowledge articles help resolve them.
  • Business hours and entitlements make time-based rules fair and contractual.

Next: Standard and Custom Objects