How lead routing and ownership rules create duplicates

Lead routing is meant to get every new lead to the right rep fast. It does that well, as long as every new record is a new person.

When it isn't, routing hands the same person to the team again and again. Ownership rules add to it: a rep who can't find the existing record creates another one. The duplicates themselves may start elsewhere, but routing turns each one into extra work for sales.

In this post, I'll walk through how routing and ownership rules create and spread duplicates. I'll share one case from a team I worked with, and what I'd change.

Routing treats each new record as a new person

Routing workflows often start when a record is created. They read a few fields, pick a rep and assign the record. Unless the workflow is built to check, it doesn't ask whether the person already exists.

So a duplicate gets the same treatment as a real new lead. It enters the queue, a rep gets notified, and someone starts working a person the team already knows.

What I see: A team I worked with had a sign-up flow where the login page was easy to lose. Sales couldn't change that page. People signed up again almost immediately, over and over, until they purchased.

A workflow put every new sign-up straight into a round-robin for onboarding and sales follow-up. Someone who signed up 10 times in three days entered the round-robin 10 times. With a constant flow of sign-ups and re-sign-ups, the queue was full of people who were already in it.

What to do: Look at where repeat records come from before you change the routing. In that case, the cause was a page sales couldn't edit, so the fix needed whoever owned the sign-up flow.

Round-robin spreads one person across reps

Round-robin assigns the next record to the next rep in line. That's fair for new leads, and it's what makes duplicates expensive.

Each duplicate goes to whoever is next, so one person can end up with several owners. Each rep sees a fresh lead with their name on it, and each one reaches out.

The person gets several emails or calls about the same sign-up. Reps lose time, and the conversion numbers for each rep stop meaning much.

What to do: Before a record enters the round-robin, check whether the person already exists. If a match exists, send the record to its current owner. Which fields to match on depends on what your sign-up flow collects, often email first, then name with company domain.

Ownership rules that hide records create new ones

Some teams limit what reps can see to the records they own. That protects ownership, but it also hides existing records from the rep searching for them.

A rep gets a call from a prospect, searches the CRM, finds nothing and creates a new record. The prospect was there all along, owned by someone else.

Other rules push the same way. If a rep only gets credit for records they create, creating a new one is the safest way to get paid.

What to do: Let reps find any record, even ones they can't edit. If the record belongs to someone else, give the rep a clear way to ask for it.

Forms and sign-ups feed the router

Routing only spreads what reaches it. Forms, sign-ups, chat tools and lead imports decide how many duplicates get that far.

A form tool that creates a new contact on every submission sends each one to routing. So does a sign-up flow that creates a record before checking for an existing one. We cover the form side in why web forms create duplicate contacts, and the sign-up side in CRM deduplication for SaaS companies.

What to do: Make forms and sign-ups update an existing record when the email matches. Then decide whether a repeat sign-up should trigger routing at all, or just update the existing owner.

Decide which owner wins before you merge

Once a duplicate has been routed, the records can have different owners. Merging them means choosing one.

What counts as a duplicate, and who keeps it, is case by case. Some teams keep the first owner, since they made first contact. Others keep the rep with the most recent activity, since they're the one the prospect knows.

Leads make this harder, because they arrive fast and often get routed before anyone looks. Duplicate leads form faster than contacts for that reason.

What to do: Write down the ownership rule and use it every time. Start with the obvious duplicates, such as one email routed to two reps. Reject a match only when you're certain it isn't a duplicate.

What I'd change, in order

1. Find where repeat records come from, even if the fix sits outside sales.
2. Check for an existing record before anything enters the round-robin.
3. Send matches to the current owner instead of the next rep in line.
4. Let reps search all records, even the ones they can't edit.
5. Make forms and sign-ups update records when the email matches.
6. Write down which owner wins when duplicates are merged.

Route each person once

Routing does what it's told: each new record gets an owner. When the same person arrives as several records, routing hands them out several times. Ownership rules can add more by hiding what already exists.

The fixes sit on both sides of the router. Reduce the repeat records coming in, check for an existing person before assigning, and agree on who keeps a customer when duplicates are merged.

Frequently asked questions