AI CRM

Lead routing: what it is and how to route leads by score, stage and channel

By Viktorio Shopov, co-founder of Sellinger. Reviewed by Asen Levov. Published . Last updated . 8 minute read.

Lead routing is the process of automatically deciding who or what handles each new lead: which salesperson, which team, or in outbound, which channel and which message. The common methods are round robin, territory, score, stage and channel. Start with the fewest rules that remove a real delay, and check that every lead lands somewhere, including the ones no rule matches.

A lead that sits unassigned for a day is a lead that has probably gone cold. Routing exists to remove that wait and to put the right lead with the right handler. This post explains the main methods, shows how to build a small rule set, and describes how routing works in Sellinger, where it mostly decides the first channel. The general definitions come from HubSpot's guide to lead routing, read on 25 October 2026. The product details come from the Sellinger app and its fact register.

What is lead routing?

HubSpot describes lead routing as the process of automatically assigning leads across a sales team, with more mature models weighing factors such as deal value, geography, specialization or lead score. The word "route" matters: the lead arrives, a rule fires, the lead goes to a destination. No person sorts a spreadsheet.

In inbound, the destination is usually a person: the right rep, queue or team. In outbound, with AI agents doing the first touches, the destination is also a channel (LinkedIn, email, WhatsApp) and a message. Both are routing decisions.

What are the common methods?

Table
Round robinLeads go to reps in rotationHigh volume, similar leads, speed mattersLead quality or fit varies widely
TerritoryLeads sorted by geography or segment, then assigned to the ownerReps own regions or industriesTerritories are not defined or data is missing
Score basedHigh scores to senior reps or faster channelsYou trust your scoringThe score is guesswork
Stage basedThe next handler depends on the pipeline stageDifferent people own different stagesStages are not kept up to date
Channel basedThe lead's channel or reachable data decides the next stepOutbound across several channelsLeads lack contact data
HybridTerritory first, then round robin insideLarger teamsRules become hard to explain

HubSpot's guide notes that leads from areas with no assigned rep need a destination too, such as a shared pool or a manager's queue. That is the rule people forget.

How do you design a small rule set?

  1. Write the delay you want to remove. "New leads wait a day for an owner" is a good reason. "It would be neat" is not.
  2. List the destinations. Who or what can receive a lead?
  3. Choose one or two signals that really separate leads: fit, source, score, channel.
  4. Order the rules. The first match should win, with the most specific first.
  5. Add a catch all at the end so no lead is orphaned.
  6. Test with ten leads before you apply it to a list.
  7. Review monthly. Look at the leads that hit the catch all.

Keep the rule set small. A rule nobody can explain is a rule that sends leads to the wrong place for months.

What does the source tell you?

The source of a lead is often the best routing input and the most ignored. On our own LinkedIn outbound, people who had engaged with posts by AI SDR vendors and automation creators booked meetings at 2.6% to 3.7% per person messaged, and people who engaged with posts by enterprise sales thought leaders at under 0.4%, as published in the Sellinger case study. The method was the same. If your sources differ that much, route them differently: more effort and a faster follow up for the strong source, a lighter touch or a test for the weak one. These are figures from one account and one offer, not a forecast for yours.

How does routing work in Sellinger?

In Sellinger, routing rules mostly answer one question: which channel does this lead hear from first? The Routing page lets you create rules that run in priority order. Each rule has a trigger and an action:

  • Triggers: the lead's channel, a tag on the lead, a pipeline stage, a score at or above a threshold, a score below a threshold, or a catch all.
  • Action: route the lead to a channel (LinkedIn, email or WhatsApp).

The first active rule that matches wins. The rules are applied when a lead's first channel is chosen. If no rule matches, the choice falls back to the segment's channel order, the agent's channel flow, or the account's default channel order. A channel is only used when the lead has the data for it (an email address for email, a profile for LinkedIn, a phone number for WhatsApp) and an account for it is connected. Leads that a person has taken over, or that are closed, are left alone by routing.

Segments add a second layer: a segment can carry its own channel order, so a list of people with no email can start on LinkedIn without any rule at all. Replies are handled by the agent and a person can take over any conversation. See lead segmentation and lead management.

Example: three rules for a small team (invented)

A seller of scheduling software for clinics sets up the following. The numbers are made up to show the shape.

Table
1Tag is "asked for pricing"Route to email
2Score at or above 70Route to LinkedIn
3Catch allRoute to email

Leads who asked for pricing get an email first. High scoring leads start on LinkedIn. Everything else starts on email. Review the catch all each month and add a rule only when you see a pattern.

How do you know routing works?

Measure the delay and the outcome, not the rule count. Three checks:

  • Time to first touch. The gap between a lead arriving and the first message. Routing should shrink it, and you should see it fall within a week.
  • Orphans. Leads with no owner or no channel after a day. The target is zero, and every orphan points at a missing rule.
  • Outcome by route. Replies and meetings per 100 people messaged for each rule's leads. If two routes give the same result, merge them. If one is far better, send more leads its way. Our post on measuring signals by reply rate shows how many people you need before a gap means anything.

Routing is a tool for removing waiting. If it does not remove any, simplify it.

What mistakes should you avoid?

  • Too many rules, with overlaps nobody tracks.
  • No catch all, so some leads wait forever.
  • Routing on a score you have not checked against replies and meetings. See lead scoring for LinkedIn outreach.
  • Routing by channel to a channel the lead cannot be reached on.
  • Never looking at what the rules did.

Common questions

What is lead routing?
Automatically assigning each new lead to the right handler, by rules such as territory, round robin, score, stage or channel, so nobody has to sort leads by hand and nobody waits.
What is the difference between round robin and territory routing?
Round robin hands leads to reps in rotation and ignores geography or industry. Territory routing first sorts leads by geography or segment and then assigns the rep who owns that territory. Many teams combine them.
What is lead routing in outbound?
In outbound, routing often means choosing the first channel for a lead, such as LinkedIn, email or WhatsApp, based on what you know about the lead and what you can reach them on.
How does Sellinger route leads?
Routing rules in the app, evaluated in priority order, can send a lead to a channel by the lead's channel, a tag, a pipeline stage or a score threshold, with a catch all rule. They are applied when a lead's first channel is chosen. Segment channel order and agent flows handle the rest.
What if no rule matches?
Have a default. In Sellinger, a lead with no matching rule falls back to the segment priority, the agent's channel flow or the account's default channel order, and a channel is used only if the lead has the data for it and an active account is connected.

How Sellinger helps

Read how it works on See the agentic CRM, or see a real campaign in Read the Sellinger case study.

Sources

See it on your own accounts

Start with a 30 day free trial, no card. Nothing is sent without your approval unless you turn that on.

Unit4ShellyRocket.ChatGetAcceptPeopleForce

Teams that have used Sellinger

Start free trial