How to Route Leads to Your Sales Team: Round Robin, Weighted and Rules

Every lead that arrives at your business raises one question before any other: who owns this right now? If the answer is “whoever notices it first”, you do not have a routing process. You have a race, and the people who win it are usually the ones who happen to be watching the inbox, not the ones best placed to close the deal.

Routing matters for two reasons that pull in different directions. Speed needs a clear owner, because a lead that belongs to everyone belongs to no one. Fairness needs a visible method, because a team that suspects the good leads are being handed out by favour will stop trusting the system. This guide covers the main routing methods, when each one fits, how to combine them, how to handle the awkward cases, and how to test and measure the result.

Key takeaways

Why routing deserves its own decision

In a one-person business, routing does not exist: every lead is yours. The moment a second person starts answering enquiries, a hidden decision appears. Someone, or something, decides who picks up each new lead. When that decision is left to chance it tends to be made by habit: the most responsive person takes the most, the newest person takes what is left, and the quiet one is quietly starved of opportunities.

The core routing methods

There are only a handful of building blocks. Most real setups are a mix of two or three of them.

Round robin

Leads are handed out in rotation: first to person A, next to B, next to C, then back to A. It is the easiest method to explain and the easiest to defend as fair, because everyone gets the same number over time.

Its weakness is that it treats every rep and every lead as identical. It does not notice that one rep is on holiday, another is buried in open deals, or that a particular lead needs someone who knows a certain product. A pure rotation also tends to give an unfair share of poor leads to whoever happens to be next in the queue when a batch of low-quality ones arrives.

A refinement worth knowing is rotating by workload instead of by turn: give the next lead to whoever currently has the fewest open items. That keeps the spirit of fairness while reacting to how busy people actually are.

Availability-based

The lead goes to the first person who is free. This suits situations where the thing being assigned is a time slot rather than an ongoing relationship, such as booking a discovery call or a demo.

Weighted distribution

Weighted routing gives some people a larger share than others. You might weight by capacity (a part-timer gets half the share of a full-timer), by seniority (a new hire ramps up gradually), or by track record (the person who converts a higher share of a given lead type gets more of that type).

Collective

With collective routing, the booking only works if everyone involved is free at the same time. It is used for panel-style calls, such as a technical specialist and a salesperson together, or a joint session with a partner. It is about scheduling a group, not about distributing a workload.

Rules-based routing

Rules send a lead to a person or group because of something about the lead itself. Common rule inputs:

• Source or channel. Website form to one group, inbound chat to another, a partner referral to the account manager who owns that partnership.
• Territory or region. Leads from a given area to the rep who covers it, which helps with time zones and local knowledge.
• Language. A lead writing in Spanish to a Spanish speaker. This is among the highest-value rules for the least effort.
• Deal size. Larger companies to your most experienced closers, smaller ones to a faster, lighter process.
• Product line. Leads asking about one product to the person who knows it.
• Keywords in the message. A lead mentioning “invoice” or “refund” probably belongs with support or accounts, not sales.

Rules are only as good as the information on the lead when it arrives. A rule on company size is useless if your form never asks for it. Before writing a rule, confirm that the field it depends on is reliably filled in.

Choosing a method

If you are unsure, begin with round robin by workload for new leads and add exactly one rule, usually language or product, when the cost of a mismatch becomes obvious. It is much easier to add a rule you need than to remove a rule that people have started to depend on.

Hybrid designs: rules first, rotation second

The pattern that holds up best as a team grows is two layers. The first layer uses rules to decide which group a lead belongs to. The second layer uses rotation to decide which person within that group gets it.

A small example: a team of five. Two reps handle inbound leads from smaller companies and rotate between themselves. Two handle larger accounts and rotate between themselves. One person covers a second language and gets every lead in that language, because there is nobody else to rotate with. Anything that matches no rule goes into a general pool shared by everyone.

Order matters. Put the most specific rule first and the broadest last, and decide what happens when a lead matches two rules. A lead from a large company that writes in a second language could belong to either group. Choose a precedence once, write it down, and apply it consistently.

The edge cases that break simple routing

The happy path is easy. The reason routing breaks is the awkward minority of leads. Decide how to treat each of these before they arrive.

Leads from existing customers

A new enquiry from someone who already buys from you should go to the person who owns that account, not into the rotation. Handing a loyal customer to a stranger who has no idea about their history is how relationships cool. It also protects your reps: nobody wants to discover halfway through a conversation that the prospect they are courting is a colleague’s client.

Duplicates

The same person may submit a form twice, message on two channels, or arrive once as a personal email and once from a work address. Without protection, each submission spins up a new lead and a new owner, and the customer receives two different replies from two people. Match on email address or phone number where possible, attach the new activity to the existing record, and keep the original owner.

Out of office

A lead assigned to someone on holiday is a lead that waits. Decide who covers an absence, and decide it before the absence. The simplest approach is to take absent people out of the rotation for the duration, so new leads flow to those who are working. Existing leads already assigned to them need a named cover person.

After hours

Leads arrive at night and at weekends. You have three honest options: assign them anyway so the owner sees them first thing, hold them in a shared queue that the first person in picks up, or send an immediate acknowledgement that sets a clear expectation of when someone will reply. Whatever you choose, make it deliberate. The worst outcome is a lead assigned at 11pm to someone who does not look until Tuesday, with no acknowledgement to the customer.

An overloaded rep

Fair rotation can still bury someone, for example when one person has a run of complicated deals. If your method counts leads but not workload, you will see this. Either route by open workload, or give managers an easy way to pause someone’s intake and rebalance without redrawing the rules.

Nothing matched: the fallback

Every routing design needs a last rule that catches anything the others miss. Send those leads to a named owner or a shared queue and raise an alert, so an unassigned lead is a visible problem and not an invisible one. A count of unassigned leads that is greater than zero for more than a few hours is the single clearest sign that your routing has a gap.

Fairness and incentives

Routing is a distribution of opportunity, and opportunity is income for anyone paid on results. That makes it sensitive. People notice who gets which leads, and they form theories.

• Make the rules visible. If everyone can read how leads are assigned, disputes become discussions about the rule rather than about the person who wrote it.
• Do not hide good leads. A manager who quietly keeps the best prospects, or steers them to favourites, will eventually be found out and the damage outlasts the leads.
• Match the method to the incentive. If reps are paid per deal won, an unequal split of lead quality is an unequal split of pay. If they are paid a salary plus a team bonus, rotation matters less.
• Rebalance on a schedule. Once a quarter, look at who received which kinds of leads and whether new hires have ramped up enough to change the weights.

Reassigning stale leads

A lead that sits assigned but untouched is worse than an unassigned one, because everyone assumes it is being handled. The answer is a written policy, not a hope. For example: if a new lead has had no first contact within a set number of working hours, it returns to the pool or goes to a second person, and the original owner is told. Choose the number of hours to suit your sales cycle; a fast-moving local service and a long enterprise cycle should not share a threshold.

Measuring whether routing works

You do not need a dashboard full of metrics. A few numbers tell you most of what you need.

Communicating the rules to the team

A routing rule that exists only in a settings screen is a rule most of the team has never read. Write a one-page description in plain language: what the methods are, which groups exist, what the fallback is, what happens when someone is absent, and how long an owner has before a lead is reassigned. Keep it where people already look, and update it whenever the settings change.

Test before you launch

Routing mistakes are expensive because they affect real prospects. Before turning anything on, run a set of dummy leads through it and check where each one lands.

• A lead for every rule you wrote, to confirm each fires.
• A lead that matches none, to confirm the fallback and the alert.
• A lead from an existing customer, to confirm it reaches the account owner.
• A burst of several leads at once, to confirm the spread looks even.

Use obviously fake names so test records are easy to find and delete afterwards, and remember that a test lead can trigger notifications to real colleagues, so tell the team before you start.

Common mistakes

• Routing by who shouts loudest. The rep who complains most gets the best leads. It feels like management and works like politics.
• Rules nobody remembers. A dozen rules written over two years, three of which contradict each other, are a risk, not a sophisticated system.
• No fallback. The unmatched lead is the one that gets lost, and it is usually the unusual one worth the most.
• Ignoring existing customers. Putting a long-standing client into the rotation is a good way to annoy them.
• Counting leads but not capacity. Equal numbers are not equal fairness when one person has twice the open work.

How Scalry handles this

Scalry has routing tools in two places, and it is worth being clear about what each does.

For appointments, team booking pages distribute bookings among your team members using one of four strategies: round robin, availability-based (the first person who is free), weighted distribution, or collective, where everyone must be free. That covers the demo-and-discovery-call end of routing, including the weighting and panel-call cases described above.

For conversations, assignment rules come in three types: round robin, channel based and keyword match, applied across the team members you choose. The round-robin logic picks the member with the fewest open conversations, which is the workload-aware rotation described earlier rather than a blind turn-taking. Channel and keyword rules let you build the first layer of a hybrid design, for example sending one channel to one group and messages that mention a given word to another.

Contacts and deals each have an owner, which gives you the record you need to treat existing customers differently. Tasks can be created with due dates, so a first-contact commitment can become a concrete item on someone’s list, and proactive insights flag overdue follow-ups, which helps you notice a lead that has gone quiet.

There are limits worth stating plainly. Scalry does not have a dedicated territory-routing feature, and it does not automatically reassign a stale lead on its own. If you want a reassign-after-a-set-number-of-hours rule, that is something you would set up yourself as an automation workflow, and you would need to decide the threshold and what counts as contact. The tooling makes the policy enforceable; the policy itself is still yours to write.

Questions to ask before you commit

Whichever way you are leaning, these are the questions that change the answer. Work through them against your own numbers rather than anyone's feature matrix — including this one.

• Who owns a new lead in the first five minutes, and does everyone agree? If the answer varies by person, you have found the gap.
• Does anything differ between leads that should change who handles them? Language, product, region and size are the usual candidates.
• What happens to an enquiry from an existing customer?
• Where does a lead go when no rule matches, and who is alerted?
• How long can an assigned lead sit untouched before it moves, and is that written down?
• When did we last review the rules? If nobody can remember, schedule it now.

If you cannot answer the first three, you are not ready to choose between Scalry and how you route leads today yet — you are still deciding what you need, which is a cheaper problem to solve first.

A two-week plan to get routing under control

Days 1 to 4: choose the simplest design

Pick one base method and at most one or two rules. Decide the fallback, the absence cover, the existing-customer rule and the stale-lead threshold. Put it all on one page.

Days 5 to 9: build and test

Set up the assignment, then run the dummy leads described above. Fix anything that lands in the wrong place, and share the draft with the team for comments before it goes live.

Days 10 to 14: launch and watch

Switch it on, check the first day’s leads by hand, and look at time to first contact and the unassigned count at the end of the week. Put a review in the calendar for a quarter ahead so the rules do not drift.

Frequently asked questions

What is the fairest way to assign leads to a sales team?

For similar reps selling the same thing, a rotation that favours the person with the fewest open items is hard to argue with. Fairness also depends on transparency, so publish the rules and review them regularly, whatever method you choose.

What is the difference between round robin and weighted distribution?

Round robin gives everyone an equal turn. Weighted distribution gives some people a larger share, for instance because they have more capacity, are more senior or convert a given type of lead better. Weighting is more flexible but needs visible, justified weights to avoid looking like favouritism.

Should existing customers go through the same rotation as new leads?

Usually not. A new enquiry from someone who already buys from you should go to the person who owns that account, because they know the history. That only works if the contact or deal records its owner.

What should happen to leads that match no rule?

They should land with a named owner or in a shared queue and trigger an alert. An unmatched lead is often an unusual one, and a silent failure there is how valuable enquiries get lost.

When should an unworked lead be reassigned?

Choose a threshold that fits your sales cycle, such as a set number of working hours without first contact, and write it down as a policy. Define precisely what counts as contact, and treat reassignment as a safety net rather than a punishment.

How many routing rules do I need?

Fewer than you think. Start with one base method and add a rule only when you can name the specific problem it solves, such as language or product knowledge. If you cannot explain the setup in about a minute, it is probably too complicated.

How do I know if my lead routing is working?

Track time to first contact by owner, conversion by owner and by rule, and the number of unassigned leads. Interpret small-team numbers cautiously, and use them to ask questions rather than to settle arguments.