Quick Summary
Omni-Channel is Salesforce’s built-in engine for pushing service work, like cases, messages and calls, to reps who are online and have room for it.
You set it up with service channels, presence statuses, routing configurations and queues. It doesn’t do round robin, territories or opportunity routing, which is where a routing app like Kubaru fits.
What is Omni-Channel?
Omni-Channel is a native Salesforce feature that routes work items to users in real time based on availability, priority and capacity. It’s most commonly used by service teams to distribute customer support cases across agents.
It comes with Pro Suite and above, not Starter Suite, and skills-based routing needs Professional edition or higher with Service Cloud.
Agents don’t have to watch queues and claim work by hand. Instead, Omni-Channel delivers the next item to them inside Salesforce, in a console app like the Service Console or in a standard Salesforce app.
Omni-Channel can route work from several channels.
- Messaging
- Email-to-Case
- Phone calls (with Salesforce Voice, formerly Service Cloud Voice)
- Cases and other supported objects
At a high level, Omni-Channel is built for service-focused routing, helping teams manage agent availability and balance workloads in real time. Whether it’s the right fit depends on how complex your routing is and which objects you need to route.
Omni-Channel typically sits inside a broader support workflow. This guide to building a Salesforce ticketing system covers how the pieces fit together.
Benefits of Omni-Channel
Omni-Channel helps teams manage customer interactions more efficiently by automatically routing work to agents based on availability, capacity, and skills. This eliminates the need for agents to monitor queues or manually claim tasks, ensuring that cases and requests are handled promptly.
It supports multiple channels—such as live chat, messaging, email, phone calls, and cases—allowing agents to manage everything from a single console. By balancing workloads and prioritizing urgent items, Omni-Channel helps agents be more productive while providing faster, more consistent service to customers.
As a native Salesforce feature, it integrates seamlessly with Service Console and leverages existing dashboards and reports, simplifying setup and ongoing management for admins.
Why Listen to Us
Kubaru is a native Salesforce routing app, rated 5.0/5 from 153 reviews on the AppExchange. Teams often bring us in after Omni-Channel handles their support queues but can’t cover their sales routing.
Omni-Channel Routing
Omni-Channel routing is the part of Omni-Channel that decides which agent gets each work item, and when. You can set it up with queue-based, skills-based, or external routing.
You can also build your routing in Flow Builder with an Omni-Channel flow. A flow can send work to a queue, a set of skills, one specific rep, or an Agentforce agent.
Queue-Based Routing
With queue-based routing, Omni-Channel pushes work to the members of a queue, highest priority first and then oldest first.
Queues act as the “holding area” for work items until they’re assigned to an agent. Each queue connects your work (the Salesforce object) to a routing configuration, which holds your distribution rules.
Routing configurations decide how Salesforce prioritizes incoming work and how much capacity each record takes up. For queue-based and skills-based routing, each one uses one of two routing models.
- Least Active. Assigns work to the agent whose current work is using up the least capacity.
- Most Available. Assigns work to the agent with the most capacity left.
Each work item’s size comes from the routing configuration, and each agent’s total capacity comes from their presence configuration.
For example, if an agent has a capacity of 10 and each record counts as 2 units, they can hold 5 records at once.
Once they reach that limit, no new work is pushed to them until they close or reassign an existing item.
Skills-Based Routing
Skills represent the expertise or certifications of your agents. With skills-based routing, Omni-Channel matches the skills a work item needs, like “French” or “Technical,” with the skills of your available agents.
You tell Salesforce which skills a record needs by mapping its fields, such as Language or Case Reason, to skills. You can also give each agent a level for each skill, from 1 (novice) to 10 (expert).
See this guide on how to set up skill-based routing for the full walkthrough.
External Routing
External routing lets a third-party routing engine decide who gets each work item. When new work comes in, Salesforce notifies the outside system, that system picks the agent, and Omni-Channel delivers the work.
You turn it on by choosing External Routing as the routing model in a routing configuration. It can’t be combined with skills-based or direct-to-agent routing.
Omni-Channel vs Kubaru
Omni-Channel is built for capacity-based service routing, so sales-style methods like round robin and territories need workarounds. Kubaru overcomes this limitation with a flexible, user-friendly engine that assigns work based on capacity, schedules and existing relationships.
| Feature | Kubaru | Enhanced Omni-Channel |
|---|---|---|
| Assign Any Object | Supported | Limited. Routes service work items such as cases, leads, orders and most custom objects, but not opportunities or tasks. Accounts and contacts need custom code. |
| Cross-Object Routing | Supported (a new lead can go to the owner of its matching account or contact) | Not supported natively (needs a custom Omni-Channel flow) |
| Round Robin Assignment | Supported | Not supported (routes on user capacity only) |
| Load Balanced Assignment | Supported | Supported |
| Skill-Based Assignment | Supported | Limited. Logic beyond basic skill matching, such as AND/OR criteria, needs Flows or custom code. |
| Territory-Based Assignment | Supported | Not supported |
| Shark Tanks (pull-based distribution) | Supported | Not supported |
| User Schedules | Supported | Not supported (reps set their own status unless you build custom automation) |
| Reassignment | Supported | Manual only (reps can reassign work by hand, but unworked work isn’t reassigned automatically) |
| SLA Escalation | Supported (reassign records, update fields and send email, Slack or Microsoft Teams alerts when an SLA is close to or past its deadline) | Not supported (Omni-Channel doesn’t track SLA timers, so escalation needs entitlement milestones or case escalation rules) |
| Duplicate Matching | Supported | Not supported (needs to happen before records enter the queue) |
| Administered by Business Users | Supported (business users run Kubaru without Salesforce admin permissions) | Limited (supervisors can move reps between queues and skills, but everything else needs an admin) |
| Criteria-Based Assignment | Supported | Not Supported. Routing is limited to the queue level. |
| Workload Capacity Limits | Supported | Limited. Supports only a single total capacity limit per user. Does not allow for different limits based on the specific type of record being assigned. |
| Workload Scoring | Supported | Limited. Capacity consumption is static per configuration. It lacks the ability to dynamically calculate weight based on individual record attributes. |
| Time-Based Limits | Supported | Not Supported |
| Out Of Office Schedules | Supported | Not Supported |
| Assignment Ordering | Supported | Supported |
| Member Sync | Supported | Not Supported |
| Field Updates | Supported | Not Supported |
| Assignment Logs | Supported (detailed assignment logs indicate which skills factored into each assignment) | Not Supported (field history tracking will record ownership changes—but additional details such as skills are not recorded) |
| Customer Support | Free Lifetime Support Included (includes full onboarding, training, technical support, etc.) | Limited (Salesforce support will provide assistance with technical issues—but will not provide hands-on configuration or guidance on best practices) |
For the full feature-by-feature breakdown, see our Kubaru vs Salesforce Omni-Channel comparison.
Setting Up Omni-Channel
Setting up Omni-Channel takes 12 steps, from turning on the feature to adding it to your agents’ app. The steps need admin-level permissions like Customize Application, so setup is usually a job for your Salesforce admin.
- Enable Omni-Channel. Omni-Channel comes with Agentforce Service (formerly Service Cloud) or an add-on like Digital Engagement. Once your license is in place, switch it on in Omni-Channel Settings. Enhanced Omni-Channel is the only version since Summer ’26, so there’s nothing else to toggle.
- Create Service Channels. Service channels turn Salesforce objects, like cases or leads, into work items. This tells Omni-Channel which records it can route to your agents.
- Create Presence Statuses. Presence statuses are the options agents pick to show their availability. You’ll want at least one Online status linked to your service channels and one Busy status.
- Assign Omni-Channel Permissions. Give agents access to the presence statuses they’re allowed to use, through permission sets or profiles.
- Create Service Resources. You need these for skills-based routing. Each one links a user to their skills, and it keeps offline agents visible in Command Center for Service.
- Create Skills (Optional). Create each skill, then add it to the right agents’ service resource records.
- Create Routing Configurations. Set the routing priority, the routing model and the units of capacity each work item uses. If you’re routing by skills, check Use with Skills-Based Routing Rules too.
- Create Queues. Link each queue to its routing configuration and the object it holds, then add members if you’re using queue-based routing. For skills-based routing, you’ll also map record fields to skills under Skills-Based Routing Rules.
- Create Presence Decline Reasons. Decline reasons show you why agents turn down specific work.
- Create Presence Configurations. Presence configurations set each agent’s total capacity and which options they get, like declining work or seeing notifications. Salesforce creates a default one, so you only need more if different agents need different settings.
- Create Supervisor Configurations. Supervisor configurations set what managers can see and do in Command Center for Service (formerly Omni Supervisor).
- Add Omni-Channel to Your App. Add the Omni-Channel sidebar or utility bar item to the Lightning app your agents use. With Enhanced Omni-Channel, the sidebar works in both console and standard navigation apps.
Each step in detail, with the screens as they appear on the live page.
Step 1: Enable Omni-Channel
The first step to using Omni-Channel is ensuring you have the correct license and enabling the feature in Salesforce. By default, Omni-Channel is not active, so it must be turned on in Setup before any routing configurations can be created.
To begin, go to Setup, search for Users, and select your user record. Ensure that the Service Cloud User checkbox is checked, and be sure to enable this for every user who will need to access Omni-Channel features. Once that is confirmed, follow these steps to enable the service:
- In the Setup Quick Find box, enter Omni-Channel Settings and select it.
- Check the box for Enable Omni-Channel.
- Optional: If you plan to use Skills-Based routing, check Enable Skills-Based and Direct-to-Agent Routing now to save time later.
- Click Save.

Step 2: Create Service Channels
Service Channels turn Salesforce objects (like Cases or Leads) into “work items.” This tells Omni-Channel which records are eligible to be routed to your agents. Setting this up now allows you to link these channels to your agent’s “Available” status in the next step.
How to set it up:
- Go to Setup and search for Service Channels.
- Click New.
- Service Channel Name: Enter a name (e.g., Case Channel).
- Salesforce Object: Select the object you want to route (e.g., Case).
- Click Save.

Step 3: Create Presence Statuses
Presence Statuses are the options agents select within the Omni-Channel widget to indicate their availability. These statuses determine whether an agent is “Online” and ready to receive work or “Busy” and unavailable for assignments.
How to set it up:
- In Setup, search for Presence Statuses and click New.
- Status Name: Enter a name for the status (e.g., Available or On Break).
- Status Options:
- Select Online if you want agents to be eligible for work assignments while using this status.
- Select Busy for statuses where the agent is logged in but should not receive new work (such as “Lunch” or “In Meeting”).
- Service Channels: If you selected the “Online” option, find the Service Channels you created in the previous step and move them to the Selected Channels column.
- Click Save.

Note: Repeat these steps to create at least one “Online” status and one “Busy” status to give your agents the necessary options. Simply creating these statuses is not enough to make them appear for your agents. You must also grant access to these specific statuses via Permission Sets or Profiles in the next step.
Step 4: Assign Omni-Channel Permissions
Once your statuses are created, you must grant agents the authority to use them. This is managed through Permission Sets or Profiles, where you define which specific Presence Statuses an agent is allowed to select.
How to set it up:
- Go to Setup and search for Permission Sets (or Profiles).
- Select the Name of the Permission Set or Profile assigned to your agents.
- Note: If you are using Profiles, click the name itself. Do not click the “Edit” link next to the name, or the status access section will be hidden.
- Find and click the link for Service Presence Statuses Access.
- Click Edit.
- Select the statuses you created in the previous step (e.g., Available and In Meeting) and move them to the Enabled Service Presence Statuses column.
- Click Save.

By completing this step, you ensure that the Omni-Channel widget will be visible to your agents and that they have the specific availability options needed to start receiving work.
Step 5: Create Service Resources
A Service Resource record represents an agent and stores their skills and proficiency levels for skills-based routing. It also enables the agent to appear in Command Center for Service while offline. Basic queue-based routing does not require this record, although other features, including some Voice configurations, do.
How to set it up:
- Click the App Launcher (9-dot icon) and search for Service Resources.
- Click New.
- Note: If the “New” button is missing, you may need to ensure the “Agent” Record Type is assigned to your Profile within Object Settings.
- Name: Enter the agent’s name.
- User: Search for and select the corresponding Salesforce User.
- Resource Type: Select Agent.
- Active: Ensure this checkbox is checked.
- Click Save or Save & New if you have more users to add.
- Create a unique Service Resource record for each user who needs one for skills-based routing, offline visibility, or their Voice configuration.

Step 6: Create Skills (Optional)
Note: If you are not using skills-based routing and prefer to route work purely through Queues, you can skip this step and proceed to the next section.
Skills are used to categorize the expertise or certifications of your agents. When using skills-based routing, Omni-Channel matches the requirements of an incoming work item (like a “French” or “Technical” tag) with the skills assigned to your available agents.
How to set it up:
- In Setup, search for Skills and select it under the Omni-Channel menu.
- Note: If “Skills” does not appear, go back to Step 1 and ensure you checked the “Enable Skills-Based and Direct-to-Agent Routing” box.
- Click New.
- Name: Enter a descriptive name for the skill (e.g., Technical Support or Spanish).
- Assign Users/Profiles: Skip this section.
- Click Save.

Linking Skills to the Resource: Once your skills are created, you must link them to the Service Resource records you created in Step 5:
- Go back to the Service Resource record for your agent.
- Click the Related tab.
- In the Service Resource Skills list, click New.
- Note: If you don’t see this list, go to Object Manager > Service Resource > Page Layouts. Select Service Resource Layout, click Related Lists in the top palette, and drag the Service Resource Skills list onto the page.
- Select the Skill and set a Start Date.
- Click Save.
- Assign Skill Level: Once saved, you can assign a Skill Level (1–10) to the record. If the field did not appear in the previous step, click Edit on the new skill record to add the level now.

Step 7: Create Routing Configurations
Routing Configurations act as the “brain” of Omni-Channel. They determine how Salesforce prioritizes incoming work items and how much of an agent’s total capacity each individual record consumes.
How to set it up:
- In Setup, search for Routing Configurations and click New.
- Routing Config Name: Enter a name for these rules (e.g., Standard Case Routing).
- Routing Priority: Enter a number to set the order of importance, with 1 being the highest priority.
- Routing Model: Choose the logic Salesforce uses to find an agent:
- Least Active: Assigns work to the agent with the fewest total number of open items.
- Most Available: Assigns work to the agent with the most remaining “empty” capacity.
- Units of Capacity: Enter the amount of capacity each record requires (e.g., if you set this to 2 and an agent has a total capacity of 10, they can handle exactly 5 of these cases at once).
- Use with Skills-Based Routing Rules:
- Check this box if you intend to route work based on the skills we created in Step 6.
- Leave this unchecked if you want to route work based purely on who is a member of a Queue.
- Click Save.
Note: If your agents manually reassign records, go back to your Service Channel (Step 2) and select this Routing Configuration in the “Default Routing Configuration for Reassign Action” field. This ensures that moved records still follow your defined capacity and priority rules.

Important: These rules only become active once they are linked to a Queue. You will perform this connection in the next step.
Step 8: Create Queues
Queues act as the “holding area” for work items before they are assigned to an agent. In an Omni-Channel setup, the Queue is the bridge that connects your work (the Salesforce Object) to your distribution rules (the Routing Configuration).
Note: If you are using Skills-Based Routing, you still need to create a queue. It serves as the entry point for the work before Omni-Channel evaluates an agent’s specific skills to make the final match.
How to set it up:
- In Setup, search for Queues and click New.
- Label: Enter a name for the queue (e.g., Technical Support Queue).
- Routing Configuration: This is the most important step. Search for and select the Routing Configuration you created in the previous step.
- Supported Objects: Under the Available Objects list, select the object you are routing (e.g., Case) and move it to the Selected Objects list.
- Queue Members:
- Queue-Based Routing: Add the specific Users or Public Groups who should receive work from this queue.
- Skills-Based Routing: You can leave this section empty. Salesforce will find agents based on their skills instead of their membership here.
- Click Save.

Important Note for Skills-Based Routing: If you are using skills, you must complete one final task to tell Salesforce how to match a record to a skill. Follow these steps to map your fields:
- In Setup, search for Skills-Based Routing Rules and click New Skill Mapping Set.
- New Skill Mapping Set
- Skill Mapping Set Label: Enter a descriptive name (e.g., Case Skill Mapping).
- Object: Select the object you are routing (e.g., Case).
- Click Next.
- Select Fields
- Choose the field(s) that contain the criteria needed to determine a skill (e.g., Language or Case Reason).
- Click Next.
- Map Field Values to Skills
- Field Value: Select the specific value that triggers the requirement (e.g., Complex Functionality or Spanish).
- Skill: Select the matching Skill you created in Step 6.
- Skill Level (Optional): Enter a minimum proficiency level if required, otherwise leave it at the default (0).
- Click Done and then Save.

Step 9: Create Presence Decline Reasons
Presence Decline Reasons provide insight into why agents are unable to accept specific work assignments. When an agent clicks “Decline” on a new work request, they will be prompted to select a reason (e.g., Currently on a Call or Researching Case), which then appears in supervisor reports.
How to set it up:
- In Setup, search for Presence Decline Reasons and click New.
- Decline Reason Name: Enter a descriptive name (e.g., In Meeting).
- Click Save.
- Repeat these steps for any other common reasons you want to track.

How to enable the “Decline” feature: Simply creating the reasons is not enough; you must enable the decline functionality within your agent settings. You can do this by editing the Default Presence Configuration (which we will cover in detail in the next step).
Step 10: Create Presence Configurations
Presence Configurations act as the master settings for your agents. This is where you define an agent’s total workload capacity and determine which specific features they can access, such as the ability to decline work or see notifications.
How to set it up:
- In Setup, search for Presence Configurations.
- Click New (or edit the Default Presence Configuration).
- Capacity: Enter the maximum number of “Units of Capacity” an agent can handle at once.
- Example: If you set this to 10 and your cases are weighted at 2 (from Step 7), the agent can handle 5 cases simultaneously.
- Agent Settings: Check the boxes for the features you want to enable, such as Allow Agents to Decline Requests or Display Dashboard on Login.
- Assign Decline Reasons: In the Decline Reasons section, select the reasons you created in Step 9 and move them to the Selected Decline Reasons list.
- Assign Users/Profiles: Select the specific users or entire profiles that this configuration should apply to and move them to the selected list.
- Note: If you are editing the Default Presence Configuration, the “Assign Users/Profiles” section will not be available. This is because the Default config automatically applies to anyone who isn’t assigned to a custom one.
- Click Save.

Step 11: Create Supervisor Configurations
Supervisor Configurations define what your managers can see and do within the Omni-Channel Supervisor dashboard. This ensures that supervisors have the correct visibility into agent activity and the ability to intervene when a queue needs attention.
How to set it up:
- Navigate to Setup: Search for Supervisor Configurations in the Quick Find box and click New.
- Omni Supervisor Configuration Name: Enter a descriptive name (e.g., Support Manager Configuration).
- Which Supervisors Are Impacted? Select the specific Users or Profiles who should have this configuration and move them to the Selected list.
- Note: If a manager does not appear in the search list, verify that they have been assigned a Service Presence Status via a Permission Set or Profile.
- What Appears in Omni Supervisor for These Supervisors?
- Select Visible Agents: (Optional) Select specific Public Groups or Profiles if you want to restrict this supervisor’s view. If you leave this blank, they will be able to see all agents.
- Select Visible Agentforce Agents: (Optional) Select any AI agents if your team is utilizing Agentforce.
- Select Visible Queues: (Optional) Select specific Queues to restrict this supervisor’s view. If you leave this blank, they will be able to see all queues.
- Define Visible Skills: (Optional) Select specific skills if your organization uses Skill-Based Routing.
- Define Actions: Check the boxes for the administrative powers you want to grant.
- Define Visible Tabs: These may be pre-selected by default. Verify that the tabs you want (e.g., Service Reps and Queues Backlog) are in the Selected Tabs list. If not, move them over manually.
- Click Save.
Step 12: Add Omni-Channel to the Utility Bar
The final step is making the Omni-Channel widget visible to your agents. You do this by adding it to the Utility Bar of your Lightning Console App, which places the widget at the bottom of the agent’s screen for easy access.
How to set it up:
- In Setup, search for App Manager.
- Find the Service Console app (ensure it is the Lightning version), click the dropdown arrow on the far right, and select Edit.
- In the App Settings menu, select Utility Items (Desktop Only).
- Click Add Utility Item.
- Search for and select Omni-Channel.
- Panel Settings: You can keep the default width (340) and height (480) or adjust them to fit your team’s preferences.
- Click Save.

Congratulations! Your agents can now open the Service Console and use the Omni-Channel widget to set their status to “Available.” Once active, they will begin receiving work items automatically based on the routing rules you configured.
Limitations of Omni-Channel
Omni-Channel handles real-time service routing well, but these limits show up as your routing needs grow.
- Service work items only. Omni-Channel only routes records that a service channel turns into work items. That covers cases, leads, orders, messaging sessions and most custom objects, but not opportunities or tasks. Assigning accounts and contacts takes custom code.
- No cross-object routing. Omni-Channel routes each work item on its own queue, skills and fields, never on who owns related records. Sending a new lead to the rep who owns the matching account or contact takes a custom flow.
- Admins own most of the setup. Supervisors can move agents between queues and skills. Changing a queue, a routing configuration or a presence setting needs the Customize Application permission, and anything beyond basic routing means Flows or custom code.
- No SLA escalation. Omni-Channel ranks waiting work by priority and age, but it doesn’t watch SLA timers or escalate anything on its own. That job falls to entitlement milestones or case escalation rules, which are separate features.
When a Routing App Is the Better Fit
If you’re routing live service work, like cases, messaging and calls, Omni-Channel does that job well. It pushes each item to whoever’s online and has room for it. A routing app tends to be the better fit when
- You need to route opportunities, tasks, accounts or any other Salesforce object, not just service work items.
- Your sales team wants round robin, territories or shark tanks rather than capacity-based routing.
- You want a new lead to go straight to the rep who already owns the matching account or contact.
- You’d like unworked records reassigned, or escalated when an SLA is about to slip, without building flows yourself.
- The managers who run the team, not your Salesforce admin, need to update routing rules whenever territories or teams change.
Kubaru is a native Salesforce app that covers every item on that list. It assigns any standard or custom object, and your business users can change the routing rules themselves without full Salesforce admin access.
Schedule a demo to see it on your own records.
Conclusion
Setting up Omni-Channel is a significant milestone in transforming your Salesforce instance into a real-time service engine. By following these 12 steps, you’ve moved beyond basic queues and into a world of automated, capacity-based routing that ensures your agents are never overwhelmed and your customers receive faster responses.
However, as your organization grows and your routing requirements become more nuanced, it’s important to remember that native tools are just the starting point. Whether you stick with a pure Omni-Channel setup for live support or choose to bridge the gap with a tool like Kubaru for more flexible distribution, the goal remains the same: getting the right work to the right person at the right time. With this foundation in place, you’re now ready to scale your operations and provide a more seamless experience for both your team and your customers.
FAQ
What’s the difference between Omni-Channel and assignment rules?
Assignment rules decide who owns a new lead or case. They check the new lead or case against criteria you set, like region or product, and send it to a user or a queue.
Omni-Channel then pushes work from a queue to an agent who’s online and has capacity. Since the rules can’t see who’s available, the two often work together, with assignment rules filling the queues and Omni-Channel handing out the work.
What’s the difference between Omni-Channel and Live Agent?
Live Agent was Salesforce’s web chat product, later renamed Chat, and it came with its own chat routing. Omni-Channel is the routing engine that decides which agent gets each piece of work, including chats.
In Lightning Experience, chats had to go through Omni-Channel. Salesforce retired legacy Chat on February 14, 2026, and its replacement, Enhanced Chat (formerly Messaging for In-App and Web), is routed with Omni-Channel flows.
Does Omni-Channel work with Sales Cloud?
Omni-Channel can route leads for sales teams, but it has no round robin or territory routing. It’s licensed through Agentforce Service (formerly Service Cloud) or a paid add-on like Digital Engagement, so Sales Cloud on its own doesn’t include it.
What happens to work items if no agents are online?
By default, work items wait in the queue until an agent sets an online status. Omni-Channel then pushes the highest-priority, oldest items to them first.
An Omni-Channel flow can check who’s online when work first arrives and send it to another queue instead. On its own, Omni-Channel won’t move work that’s already waiting over to a different team.
Does Omni-Channel automatically reassign a record if an agent stops working on it?
No. Once an agent accepts a work item, it stays with them. If that agent goes to lunch, loses their connection or forgets the open item, Omni-Channel won’t pull it back on its own.
Reps can transfer or reassign work by hand. To move unworked records automatically, you’ll need a tool with automated reassignment.
Which objects support Omni-Channel routing?
Omni-Channel routes the objects you turn into work items through a service channel. Salesforce lists cases, chats, messaging sessions, voice calls, leads, orders, work orders, incidents, contact requests, social posts and custom objects without a primary object.
Opportunities and tasks aren’t on the list, and accounts and contacts can only be assigned through custom code.
How does Salesforce determine an agent’s “Capacity”?
Capacity is calculated based on “units” defined in your Routing Configuration. For example, if an agent has a total capacity of 10 and each record is weighted at 2 units, the agent can handle up to 5 records at once. Once they reach their 10-unit limit, no new work is pushed to them until they close or reassign an existing item.
Can I set different capacity limits for different types of work?
In native Omni-Channel, an agent has a single “Total Capacity” (e.g., 10 units). While you can weight different records differently (e.g., a Case is 5 units and a Lead is 2), you cannot easily set a rule that says “Agent A can handle 3 Cases AND 2 Leads, but never more than 2 Leads.” Managing complex, multi-object workload balance often requires manual intervention or a more advanced distribution tool.





