Illustrative simulator with generic Lightning-style styling, not the real product interface. The leads, reps and numbers are fictional, no real systems or data are involved, and the routing logic is a simplified model.
Good leads lose their value when they reach the wrong person, or nobody. Below is a Lightning-style Leads list view with a routing component beside it. Pick a rule, then search, filter and sort the list, and select a lead to see why it landed with its owner.
Sales
HomeLeadsAccountsOpportunitiesReports
LeadsNew this week
In a real environment
Data sources
Standard Lead fields such as Country, State, Lead Source and Rating. A region is not a standard field, so derive it from country and state or add a custom field.
Lead Owner, which can be a user or a queue, and a count of open leads per user from a report or a scheduled count.
Rep availability from Omni-Channel presence or a custom out-of-office field on the user. Confirm which one your org uses.
Limits and prerequisites
Lead assignment rules check entries in order, the first match wins, and each entry assigns a user or a queue. Only one rule is active at a time, and a final entry with no criteria can catch the rest.
There is no built-in round robin rule type. The documented pattern uses an autonumber field, a formula and one entry per user.
Capacity-aware routing uses Omni-Channel: a flow that ends in a Route Work action, called from a record-triggered flow for leads. A service channel for the Lead object and the licensing are things to confirm in the target org.
Search, list view filters, sorting and row selection are ordinary list view behavior. The Routing result column, the decision trace and the side panel are illustrations: a real build would use a custom field set by the flow, a stored reason, and a report or a Lightning page component.
Sales Territories can also link leads, but Salesforce guidance favors standard lead assignment rules or a separate process for lead routing. Territory here is only a region field.
How it would be validated
Replay a sample of past leads through the proposed rules in a sandbox and compare the owner each rule picks with the actual owner.
Report on leads still owned by a queue, and on leads whose owner was out or over the limit when the lead arrived.
Pilot one region first and review the leads that fell through before widening the rule.
What this demo does not claim: it shows no response times, conversion or fairness results, the six leads and three reps are fictional, and the tie-break choices (first match, most room first) are illustrative. The counts shown are simple tallies of this simulation, not benchmarks. The capacity rules model what an Omni-Channel flow could do and are not a copy of a specific configuration. The interface styling is generic and is not the product itself.