Build This Now
Build This Now
speedy_devvkoen_salo
Blog/For Business/Nobody Owns This Lead

Lead Routing: Who Owns an Inbound Lead

Lead routing best practices for B2B: two clocks start when an inquiry arrives, and most companies only measure the second one. How an inquiry gets an owner, and in what order.

Sie möchten das Framework hinter diesen Projekten?

Holen Sie sich das Claude Code System, mit dem wir produktionsreife Software planen, bauen, testen und ausliefern.

Sehen Sie, was wir für Unternehmen bauen →
speedy_devvkoen_salo
speedy_devvWritten by speedy_devvPublished Jul 31, 20269 min readFor Business hub

Problem: Your team has a five-minute reply target. Your reports say you hit it most of the time. Revenue does not agree, because the clock you are measuring starts too late.

Quick Win: Lead routing is the rule that decides which named person becomes responsible for a new inquiry. Two clocks start the moment an inquiry arrives, and almost every company only measures the second one. The routing clock runs from arrival until a human's name is attached. The response clock runs from that moment until the person replies. LeanData writes the same thing as a formula: lead response time equals lead processing time plus the salesperson's response time, where processing covers matching, enrichment, and routing before anyone is involved (LeanData). A five-minute target measured from assignment means nothing if assignment took nine hours.

The Two Clocks Nobody Separates

Here is the arithmetic that embarrasses most sales dashboards.

An inquiry lands at 09:00. Your rules run, or fail to run, and a salesperson's name gets attached at 17:40. She replies at 17:44. Your report shows a four-minute response time and a green light. The buyer experienced eight hours and forty-four minutes of silence and already booked a call with someone else.

Nothing in that story is a discipline problem. The salesperson did everything right. The system took the entire day to tell her the deal existed.

This matters because the speed research everyone quotes measures the buyer's clock, not yours. In 2011, Harvard Business Review researchers audited 2,241 US companies by sending each one a test inquiry. Average reply time among the companies that replied within 30 days: 42 hours. Almost a quarter never replied at all. In a separate study of 1.25 million inquiries across 29 consumer and 13 business companies, firms that tried to make contact within an hour were nearly seven times as likely to reach a decision maker and have a real conversation as firms that tried even an hour later (HBR). The 2007 MIT and InsideSales study behind the five-minute rule puts it in one line: "The odds of qualifying a lead if called in 5 minutes versus 30 minutes drop 21 times" (MIT / InsideSales).

Both of those clocks start when the buyer hits submit. Yours starts whenever your rules get around to it. Until you measure the gap between those two moments, you do not know whether you have a speed problem or a plumbing problem. Our breakdown of the five-minute reply rule covers the second clock. This page is about the first one.

Wrong Owner and No Owner Are Different Failures

These get lumped together as "our routing is messy." They are not the same problem and they do not have the same fix.

Wrong owner means a name is attached, just the wrong one. In LeanData's 2017 State of Lead Management survey of 527 B2B sales and marketing professionals, respondents said roughly one in every four marketing-generated inquiries goes to the wrong account owner, and almost 80% said they were not completely satisfied with how their company routes inquiries (LeanData). Wrong owner is loud. Somebody complains and hands it over. You lose hours and some goodwill, and the report still shows the inquiry as worked.

No owner means no name was ever attached. It is silent, and it never comes up in a sales review, because a deal with no owner is nobody's number to explain. LeanData's audit guidance lists where these records hide: assigned to people who have left, sitting in shared holding lists nobody monitors, past whatever internal deadline you set, or buried in a lopsided pile under one name (LeanData).

Wrong ownerNo owner
How you find outA salesperson complainsYou count arrivals against assignments
Shows up in reports?Yes, as a worked inquiryNo, invisible
Root causeRules run, but the data behind them is staleNo rule matched, or it pointed nowhere
The fixClean the fields the rules readWrite the catch-all, name a human, set a deadline
CostHours and internal frictionThe whole deal

The fixes are unrelated, and you can solve one while still having the other. Wrong owner is a data problem, which is why cleaning up your customer records comes before any routing rewrite. No owner is a logic problem. To size it, count inquiries received against inquiries ever assigned, the ninth of the nine queries you can run tonight.

The Four Routing Methods and What Each One Buys You

Every company uses some blend of four methods, usually picked once, years ago, and never revisited.

MethodOptimizes forWhere it breaksBest used as
Account-based (named accounts, existing customers)Relationship continuityOut-of-date account lists, or the company name spelled differently on the formFirst rule, always
Territory (region, industry, company size)Fit and local knowledgeDefinitions change after a reorganization or a new pay plan, and the rules do not always followSecond rule
Skill or segment (product line, deal size, language)Matching complexity to competenceNeeds data on the form that buyers often will not give youThird rule, where deal types genuinely differ
Round robin (next person in the rotation)Fairness and speed of setupBlind to fit and to whether the person is availableLast rule, as the catch-all

The order matters more than the choice. Build the rules from most specific to most general. Activated Scale sets it out the same way: check for an existing account owner first, check the territory second, check the segment or specialty third, and use round robin only inside the correct pool of people (Activated Scale). Round robin as the primary method in a team with defined territories or named accounts creates conflicts almost immediately. As the catch-all, it beats leaving an inquiry unassigned.

If you run Salesforce, one structural detail is worth knowing. Only one lead assignment rule can be active at a time, the entries inside it run in the order you set, the first match wins, and anything matching nothing goes to a single default lead owner set deep in your settings (Salesforce). All of your commercial logic lives inside one ordered list. If you have never read that list top to bottom, you have never seen your routing policy.

The Rule Nobody Writes

Ask a sales leader what happens to an inquiry that matches no rule. You will usually get a pause.

The default owner setting is the most consequential line of configuration in most companies, and almost nobody knows whose name is in it. Often a long-departed administrator, a generic account, or someone who has filtered those notifications for years. Every inquiry your rules did not understand goes there, and nothing happens.

The fix is not clever. One Salesforce audit guide puts it plainly: route unmatched inquiries to a manager or a shared review list, not to a default owner, and add backup rules underneath so every inquiry still reaches a valid person when the main criteria do not match (nc-squared). The same guide proposes a metric worth stealing: track your default owner rate, the share of inquiries falling through to the catch-all, and keep it under 5%.

Three things make a catch-all real rather than decorative:

  1. A named human, not a bucket. Someone whose job includes clearing that list every morning.
  2. A deadline with an escalation. If the list is not cleared within a set number of hours, it goes to that person's manager. LeanData recommends automatically reassigning inquiries not contacted within two to four hours for the hottest ones (LeanData).
  3. A weekly count. If the catch-all is catching 30% of your inquiries, your rules are wrong and the catch-all is hiding it.

A catch-all is a smoke detector, not a fire extinguisher. Rising volume in it means your rules have drifted away from how your market actually looks.

Capacity, Not Fairness

Round robin is popular because it takes an afternoon to set up. It has one flaw that costs real money: it hands the inquiry to whoever is next, not to whoever is available.

Next in line might be on a plane, on holiday, in a customer meeting until Thursday, or already sitting on forty untouched inquiries. Fair distribution and fast response pull against each other, and pure fairness loses. LeanData puts the revenue version bluntly: a pure rotation in a team where one person closes three times as many deals as the average will cost you money (LeanData).

Three adjustments turn a rotation from fair into fast:

  • Availability first. People come out of the rotation automatically when they are away, at capacity, or outside working hours, and the rotation continues without anyone editing it (LeanData).
  • Caps, not equality. A ceiling on how many new inquiries one person receives per day stops a strong week from turning into a backlog nobody works.
  • Weighted shares. Senior people take a larger share than someone in their first month. This is not favoritism. It is matching the inquiry to the person most likely to win it.

The honest trade-off: all three make distribution less equal, and you will have that conversation with your team. Have it once, in the open, rather than pretending a rotation is fair while your best salesperson quietly complains that half her inquiries are junk.

The Cases Your Rules Probably Do Not Cover

Standard routing handles a new company arriving through a form. Four situations slip through, each with a different right answer.

Existing customers. A current customer fills in the contact form. If your rules treat every inquiry as new business, you have just routed your own customer to a salesperson who will pitch them something they already own. Match against existing accounts before anything else.

Open deals. Somebody from a company already in an active deal submits a form, often a different colleague. This should attach to the existing deal and its owner, not start a second track. It is exactly the silent break that one list every inquiry lands in is built to catch.

Partner and referral inquiries. These need their own path, because the commercial terms differ and the partner needs to be told what happened. Partner deals falling into the general rotation is one reason nobody owns partner deals.

Returning inquiries. Someone who inquired eight months ago and went quiet comes back. Routing them to a new salesperson throws away every note from the first conversation. Match on email domain and reattach to the original owner, or their replacement.

Test It This Week: Five Fake Inquiries

You do not need a project to find out whether your routing works. You need an afternoon and an email address nobody in your company recognizes.

Submit five inquiries yourself, deliberately different: one from an existing customer's email domain, one from the edge of your territory map, one with the company name field left blank, one from a company size you rarely sell to, and one that is a clean match for your ideal customer. One audit guide recommends the same exercise on real records, tracing five inquiries from the last week through the full path and documenting which rule matched, whether the default owner caught it, any later reassignment, and the time to first contact (nc-squared). Your own test inquiries are faster, because you know the exact minute each one was submitted.

Record four things for each:

What to recordWhat good looks like
Minute submittedYour baseline, the only honest start time
Minute a named person was assignedMinutes, not hours
Who it was assigned toA person you would have picked yourself
Minute of first human replyInside your stated target, measured from submission

The blank-company-name one is the test that usually fails. That is your catch-all, live, with a stopwatch on it.

Run this once a quarter. It costs an hour and it is the only routing report that cannot be gamed. It is also the first thing we run before we install anything inside a company, because the answer usually reframes the problem the leadership team thought they had.

Where This Breaks Down

Better routing does not fix bad inquiries. If half your form submissions are students and competitors, faster assignment delivers junk faster. Routing decides who owns an inquiry, not whether it was worth owning.

Rules drift silently. Territories get redrawn, pay plans change, people leave, and the routing rules stay exactly as they were. Nothing errors. Inquiries just start going to the wrong place. Activated Scale recommends reviewing routing rules quarterly and after any major change, including territory adjustments, new products, and new headcount (Activated Scale). Put that review on the same calendar as the change itself.

Automation multiplies bad data. Rules read the fields on the record. If company size is empty on 40% of your records, a size-based rule misroutes 40% of your inquiries. Clean inputs first, then automate.

The lost-deal statistics you will find online are mostly unsourced. There are confident numbers everywhere about the share of deals lost to slow or wrong assignment. Chase most of them and you land on a vendor page citing another vendor page citing nothing. Keep them out of your board deck. Run the five test inquiries and count arrivals against assignments in your own records instead. Your own numbers survive questioning. Borrowed ones do not.

When to Leave Routing Manual

Not every company should automate this. Under roughly ten inquiries a day, manual assignment is manageable and automation adds rules to maintain for very little gain (LeanData).

Manual is fine while three conditions hold: one named person sees every inquiry as it arrives, that person is reachable during selling hours, and there is a named backup for when they are not. Manual routing fails at the holiday, not at the volume.

Automate the moment one breaks. Two people both assume the other is watching. Inquiries start arriving outside one time zone. Volume passes what one person can sort between meetings. When ownership becomes ambiguous, the routing clock runs long and nobody sees it.


Most companies discover this the same way: they measure reply speed for a year, coach the team hard, and the number barely moves, because the delay was never in the reply. It was in the eight hours before anyone knew the deal existed. We install one list every inquiry lands in, ownership assigned at the moment it arrives, and automatic detection when a follow-up slips. See how we recover follow-up and relationships →

More in For Business

  • The 30-Day AI Pilot That Ships
    95% of AI pilots deliver no profit. The fix isn't a better model. It's a 30-day pilot scoped to one bottleneck with an output you can test the next morning.
  • Automate Accounts Receivable
    A controlled plan for accounts receivable AI automation: invoice checks, collection priorities, disputes, cash application, and human approval.
  • AI Agents vs Employees
    The honest 2026 cost of AI agents vs employees: the real all-in cost of a hire, where AI cuts costs by 85%, where AI agents end up costing more than staff, and why 95% of pilots fail.
  • AI Change Management Plan
    Build an AI change management plan with workflow owners, role-based training, human controls, adoption metrics, and a six-week rollout cycle.
  • Safe AI Contract Review
    Build a safe AI contract review workflow that extracts terms, checks an approved playbook, routes exceptions, and keeps final approval with counsel.
  • AI for the CFO
    The four finance numbers a CFO should automate first, ranked by payback: month-end close, collections and DSO, forecast prep, and board reporting.

Sie möchten das Framework hinter diesen Projekten?

Holen Sie sich das Claude Code System, mit dem wir produktionsreife Software planen, bauen, testen und ausliefern.

Sehen Sie, was wir für Unternehmen bauen →
speedy_devvkoen_salo

On this page

The Two Clocks Nobody Separates
Wrong Owner and No Owner Are Different Failures
The Four Routing Methods and What Each One Buys You
The Rule Nobody Writes
Capacity, Not Fairness
The Cases Your Rules Probably Do Not Cover
Test It This Week: Five Fake Inquiries
Where This Breaks Down
When to Leave Routing Manual

Sie möchten das Framework hinter diesen Projekten?

Holen Sie sich das Claude Code System, mit dem wir produktionsreife Software planen, bauen, testen und ausliefern.

Sehen Sie, was wir für Unternehmen bauen →