# Lead routing in Pipedrive for a small team: round robin, and what to do when it breaks

https://salesbond.app/blog/lead-routing-pipedrive-small-team/
Published: 2026-10-02 · Updated: 2026-10-25

Lead routing is the set of rules that decides which rep gets a new lead the moment it lands in your CRM. For three to eight reps, two rules cover most of it in Pipedrive: named accounts and existing customers go to the rep who owns them, everything else goes round robin to the team. In that order.

For existing customers, the same rule decides [who owns the renewal](https://salesbond.app/blog/customer-renewal-process-pipedrive/).

Run round robin on its own and it will hand a hot lead to someone who is on vacation, and hand a current customer’s new request to a rep who has never spoken to them. Below is how to set that order in Pipedrive’s automatic assignment, what the rotation still doesn’t know, and a monthly check that tells you whether the split is actually fair.

## Monday morning, two reps, one hot lead

A demo request lands on Sunday night from a company Maria closed two years ago. Round robin gives it to Tom. Tom emails at 8:40 on Monday. Maria sees the company name in the pipeline at 9:10 and says it’s hers, because it is: she knows the buyer, the contract, the renewal date. Tom has already started. (This is a made-up example, but every small team we have worked with has a version of it.)

Both reps are right by their own rule. The manager now spends twenty minutes on a Monday morning deciding whose deal it is, and the lead waits while they decide.

Nobody here did anything wrong, and that’s the problem. The rotation did exactly what it was built to do: it counted. Nobody ever told it that Maria’s customers are Maria’s.

## Three ways to route leads, and which one a team of five needs

For a team of five: owner-based first, round robin second. That combination isn’t on the usual list of options, so here is the list first.

Pipedrive’s own guide to lead routing describes three methods. Round robin assigns new leads “evenly across sales reps in a rotating sequence” and takes no account of lead score or a rep’s expertise. Territory routing splits leads by region or similar criteria. Rule-based routing uses conditions such as geography, lead scoring, deal size or team availability ( [Pipedrive: lead routing](https://www.pipedrive.com/en/blog/lead-routing)).

Territories need enough leads per region to keep each rep busy and a five-person team rarely has that. Scoring-based rules need a scoring model you trust, which means closed-deal history you probably don’t have yet. Round robin is honest about what it does, which is why small teams start with it. It’s also why they end up with the Monday morning scene above: a rotation has no memory of who already owns the relationship. If you do want scoring-based routing later, start with [a score reps trust](https://salesbond.app/blog/pipedrive-scores-deal-priority-criteria/), and test it on deals whose outcome you already know.

So you put the two in order. Anything with a known owner goes to that owner; whatever is left is genuinely new and can be rotated without anyone having a claim on it. That one sentence is the whole routing policy. The rest of this article is about making Pipedrive follow it, and finding out when it quietly stops.

[Account ownership is a separate question](https://salesbond.app/blog/sales-territory-planning-small-team/) from lead routing, and a short rule answers it.

## Rules in the order Pipedrive reads them

Pipedrive’s automatic assignment runs rules on three events: a deal is added, a deal is updated, a lead is added. A rule can assign to a specific user, to a team (round robin inside the team), or to the owner of the linked organization or person. You can have up to 50 rules per entity type, each with up to 160 conditions in a set and up to two sets, and rules carry a priority you set yourself. The feature is on the Professional plan and higher, and the team option needs Teams set up in your account ( [Pipedrive Help: automatic assignment](https://support.pipedrive.com/en/article/automatic-assignment)). Only Deals app admins can view and set up these rules ( [Pipedrive: automatic assignment FAQ](https://support.pipedrive.com/en/article/automatic-assignment-faq)), so on a small team routing sits with [one admin](https://salesbond.app/blog/crm-data-ownership-small-sales-team/) and becomes part of their [sales operations](https://salesbond.app/blog/sales-operations-small-team/) work.

Fifty rules is a budget for a sales floor. A team of five needs three, maybe four, and the order matters more than the conditions:

1. **Existing customer.** Condition: the linked organization has a won deal, or your customer-status field says “Customer”. Assign to the owner of the organization.
2. **Named account.** Condition: the organization carries your key-account label, or sits in a list you maintain. Assign to the named user who holds it.
3. **Everything else.** No condition. Assign to the sales team, round robin.

A fourth rule is worth it only if you have a lead source that belongs to one person by agreement, such as partner referrals. Give it its own line above the catch-all. If a source belongs to someone by agreement, [write that agreement down on one page](https://salesbond.app/blog/lead-handoff-agreement-pipedrive/) so nobody has to remember it. Customer referrals are different: they go to the rep who got them, and [a routine for customer referrals](https://salesbond.app/blog/ask-customers-referrals-pipedrive/) keeps that from depending on memory.

Build the same ladder for leads and for deals if your inbound arrives in in both places. If everything comes in through the Leads Inbox, set up the “Lead added” rules first, and let the deal rules stay empty until you need them.

The order is the point. Put the catch-all at the bottom, under every rule that names a person. A rotation rule that sits above the owner rule is the Maria-and-Tom problem written into settings. And keep people out of overlapping rules: Pipedrive’s FAQ says that someone who belongs to more than one team, or has more than one rule assigned to them, gets more opportunities. A rep who sits in two routing teams quietly gets a bigger share.

![Pipedrive lead routing ladder: existing customer to organization owner, named account to its rep, everything else round robin to the team](https://salesbond.app/wp-content/uploads/2026/10/lead-routing-pipedrive-small-team-2.png)

One more habit from small teams: we keep routing rules on “Deal added” and “Lead added”, and stay away from “Deal updated” for assignment. According to Pipedrive’s FAQ, an update only triggers reassignment when the deal moves to a new stage or pipeline; editing other fields doesn’t. That is narrower than it sounds, and still too wide for us. A deal moved to the next stage can be reassigned while someone is working it, and that is harder to explain on a Monday than a missing rule.

## What round robin doesn’t know

Availability, first. Pipedrive’s help on automatic assignment doesn’t describe working hours or availability, so a rotation on a five-person team keeps counting a rep who is on a two-week holiday. The leads it sends her sit in her inbox until she is back or until someone notices.

For vacations, the [automatic assignment FAQ](https://support.pipedrive.com/en/article/automatic-assignment-faq) spells out the fix: a Deals app admin disables any rules set for that user and removes them from any teams that have rules. It’s boring and manual. Do it before the rep leaves, undo it when they return, and write it into the same checklist as the out-of-office reply. On a team of five, that’s a couple of changes a year per person, and it takes less time than one lost lead.

Vacation is the easy case: [add the cover person as a follower](https://salesbond.app/blog/pipedrive-followers-rep-out-of-office/) and the rep keeps the deal. For [a rep who has left for good](https://salesbond.app/blog/rep-leaves-reassign-pipedrive-deals/), the open deals need a different plan.

Load is the same story. The FAQ says there is no minimum or maximum of open leads or deals per person, and no way to weight the split inside a team. Marketplace apps fill some of that gap: RouterJet, for instance, describes distributing deals to “agents who are on shift” ( [RouterJet: round robin for Pipedrive](https://www.routerjet.com/tutorials/round-robin-for-pipedrive/)). If your team runs shifts or part-time hours, that is worth a look. If it runs Monday to Friday with normal vacations, the checklist is enough.

The second thing the rotation doesn’t know is history. Pipedrive keeps the assignment history for seven days ( [Pipedrive Help: automatic assignment](https://support.pipedrive.com/en/article/automatic-assignment)). That is enough to settle a dispute the same week, which is when disputes happen anyway. It is not enough to look back at a quarter and ask whether the rotation was fair, which is why the monthly check at the end of this article is done from deals, not from assignment logs. If someone asks in November who got the lead in September, nobody will have the answer.

Named accounts are the third blind spot, and the rule order above already covers it. The rotation does not know that a company matters more than its form submission suggests; your key-account label does. Temperature labels are a different job: before anyone acts on a Hot label, the team has to agree on [what hot means](https://salesbond.app/blog/pipedrive-lead-labels-hot-warm-cold-rule/) in one observable signal.

And deal size. Round robin counts leads. A request for a two-seat plan and a request from a two-hundred-person company each count as one, and the rotation moves on. We don’t recommend routing by deal size on a small team, because at the lead stage you mostly don’t know the size, and a guess written into a rule becomes a fact nobody questions. Accept that counts will be even and value won’t, and catch the gap in the monthly check instead. If vacation cover and load keep coming up every month, that is a capacity question, and we have written about [capacity planning for a small sales team](https://salesbond.app/blog/sales-capacity-planning-small-team/) separately.

## The untouched lead: when to take it back

Routing decides who gets the lead. It doesn’t decide what happens when that person doesn’t touch it. Vendors of routing tools like to say that leads go cold in a matter of minutes; they don’t show the data, so we won’t repeat the number. What we see is simpler. A lead nobody touched by the next working morning is a lead the rotation has lost, and the rotation won’t notice.

That lead shows up on the [9am list](https://salesbond.app/blog/speed-to-lead-pipedrive/). Whoever runs the list that week hands it to the next rep in the rotation before lunch, by changing the owner in Pipedrive so the handover stays on the record. By hand, on purpose. Automatic re-routing on a five-person team makes ownership unpredictable, and unpredictable ownership is what started the Monday argument. Visitor companies need an owner too: decide [who opens the Web Visitors inbox](https://salesbond.app/blog/pipedrive-web-visitors-quality-follow-up/) each week. Email that arrives at a shared address like info@ needs the same kind of owner; in Pipedrive that is the job of [Team Inbox](https://salesbond.app/blog/pipedrive-team-inbox-shared-mailbox/).

## A monthly fairness check

Once a month we pull new deals by owner for the past month, and next to the count we put two more columns: total value, and win rate on whatever closed. Ten minutes in Pipedrive’s deal filters, or whatever report you already use for [win rate](https://salesbond.app/blog/sales-win-rate-pipedrive/). The count is what round robin optimises. The other two columns are what it can’t see.

Here is what that looks like on an invented team of two, to keep the arithmetic short. Anna got 20 new deals in the month, worth $40,000 in total; 5 closed won, so her win rate on the month is 25%. Ben also got 20 new deals, worth $100,000; 7 closed won, a 35% win rate. By count, the rotation is perfect. By value, Ben’s average deal is $5,000 and Anna’s is $2,000, two and a half times smaller. (Hypothetical numbers, chosen to make the point.)

![Hypothetical comparison of two reps with 20 new deals each: $40,000 vs $100,000 total value and 25% vs 35% win rate](https://salesbond.app/wp-content/uploads/2026/10/lead-routing-pipedrive-small-team-3.png)

Is Ben better? Maybe, but the first thing to ask is where his deals came from. In our example the answer is the first routing rule: Ben owns most of the organizations that are already customers, so every expansion request goes to him by design, and Anna gets the cold inbound. The rotation was fair. The sources weren’t.

That’s the position we hold on lead routing: a fair split is judged by the quality of what each rep receives. A rep whose entire month is first-time form fills and a rep whose month is renewals and upsells have different jobs, even if the count is identical.

When those two jobs belong to different people, the owner rule sends every renewal to [a farmer who owns the account](https://salesbond.app/blog/hunter-vs-farmer-sales-small-team/).

What you do about it depends on which split you find. If the gap is in sources, don’t break the owner rule to fix it; rotate who inherits the next orphaned customer account instead, or set the plan per rep by source, which is the same conversation as [inbound versus outbound on a small team](https://salesbond.app/blog/inbound-vs-outbound-sales-small-team/). If the gap is in win rate on the same kind of leads, routing won’t fix it. That’s coaching. And if the counts themselves are off by more than a handful, look for three things: someone stayed in the rotation while on holiday, someone sits in two routing teams, or someone has been quietly changing owners by hand. The last one is a [data ownership](https://salesbond.app/blog/crm-data-ownership-small-sales-team/) problem and worth its own ten minutes.

The same goes for [meetings booked by an outside setter](https://salesbond.app/blog/outsourced-appointment-setters-pipedrive/), which need a source of their own.

Comparing by source only works if [the source is on the deal when it is created](https://salesbond.app/blog/pipedrive-lead-source-web-forms/), not remembered later.

Start with the three columns this month, before you touch a single rule. On a team of five, the split usually tells you which rule to fix. When two reps share one deal, count it once and keep the split in its own fields, as in [shared deal credit in Pipedrive](https://salesbond.app/blog/shared-deal-credit-pipedrive/).

A disclosure, since the monthly view is where this ends: we build SalesBond, a sales management layer on top of the CRM a team already uses; we started with Pipedrive. The deals-by-owner split with value and outcome next to the count is the view we keep coming back to ourselves. If you would rather not rebuild that filter every month, Check your CRM with SalesBond.