Salesforce Queues: Complete Setup Guide
Quick Summary:
A queue is a shared record pool that multiple users can pull work from — commonly used for unassigned leads or support cases waiting for the next available team member.
What Is a Salesforce Queue?
A queue holds records that haven't yet been assigned to a specific individual, visible to all queue members, who can then claim (take ownership of) a record to work on. This is the standard pattern for support case routing and lead distribution — records enter the queue automatically, and the team pulls from it rather than waiting for manual individual assignment.
Queue vs Role vs Public Group
| Mechanism | Best For | Assignment Style |
|---|---|---|
| Queue | Team-based record pools (support tickets, unassigned leads) | Pull -- team members claim records |
| Role | Reporting hierarchy and data visibility | N/A -- not a routing mechanism |
| Public Group | Sharing and permission grouping | N/A -- not a routing mechanism |
How to Create One
Go to Setup → Queues and click New.
Name the queue and select which objects it supports.
Add members — individual users, roles, or public groups.
Optionally enable email notifications so members are alerted when new records arrive.
Configure assignment rules (for Leads/Cases) to automatically route matching records into the queue.
🚫 Common Mistake
Creating a queue but never connecting it to assignment rules or automation, leaving records to accumulate unassigned unless someone manually moves them in — the queue exists but doesn't actually receive work automatically.
💡 Pro Tip
Combine queues with Omni-Channel (where licensed) for genuinely intelligent routing — skill-based assignment, capacity limits per agent — rather than relying on basic queues alone for high-volume support operations.
Frequently Asked Questions
Can a queue receive records automatically via assignment rules?
Yes, Lead and Case assignment rules can route records directly to a queue based on criteria, rather than requiring manual assignment.
Can any object have a queue, or just standard objects like Case and Lead?
Custom objects can also support queues, as long as the object has "Allow Salesforce Queues" enabled during setup.
Do queue members get notified when a record is added?
This depends on configuration — queue email notifications can be enabled so all members receive an email when a new record enters the queue.
Can a user be a member of multiple queues?
Yes, users can belong to as many queues as relevant to their role, and can also be added via their role or a public group rather than individually.
How do I find a queue\'s ID for use in automation or API calls?
Queue IDs can be found in Setup → Queues, or queried via the Group object (queues are technically a type of Group record) with Type = 'Queue'.
What happens to records in a queue if the queue is deleted?
Records remain but lose their queue-based ownership assignment — they typically need to be reassigned, so queues with active records generally shouldn't be deleted without a reassignment plan.
Can queue-based routing use round-robin or skill-based logic?
Native queues use simple FIFO (first-in, first-out) style assignment; true round-robin or skill-based routing typically requires Omni-Channel or additional automation on top of the base queue.
Can a queue own records the same way an individual user can?
Yes — a queue can be set as a record's Owner field value, functioning similarly to a user for ownership purposes, until a team member takes the record.
Is there a limit to how many records a queue can hold?
There's no meaningful practical limit tied to the queue itself — queues can hold as many unassigned records as needed.
Can queues be used with Flow to automate record routing logic?
Yes, Flow can assign a record's Owner to a specific queue based on any criteria you define, giving you more sophisticated routing logic than assignment rules alone provide.