B2B Lead Routing: How to Route Website Leads by Intent

Lead routing decides which rep gets a lead and how fast. Most B2B teams set it up once, usually as a round-robin rule in the CRM, and never look at it again until a big customer complains that three different reps contacted them in the same week. Website leads suffer most, because the website knows far more about the visitor than the form fields capture, and almost none of that context reaches the routing rule.

This post covers how to route website leads properly: match to the account before anything else, route by intent instead of arrival order, include the anonymous high-intent visits that never become leads, and measure whether routing is helping or hurting.

Why Website Lead Routing Breaks

The cost of slow or wrong routing is well documented. In a study published in Harvard Business Review, Oldroyd, McElheran and Elkington reported that, across 1.25 million leads, firms which tried to contact a lead within an hour were nearly seven times as likely to qualify it as firms that waited even an hour longer. Every routing hop, every queue, every "unassigned" bucket eats into that hour.

The usual failure points:

• Routing on the lead, not the account. A new contact from an existing customer, or from an account an AE is already working, goes into round-robin and lands with a stranger.
• Every form treated the same. A newsletter signup and a pricing-page demo request enter the same queue with the same SLA.
• Missing context. The rep sees a name, email, and company. They do not see that three colleagues from the same company read the pricing page this week.
• Anonymous intent ignored. Our 2026 B2B personalization research found that only 5-10% of website visitors ever fill out a form. Routing that starts at the form only sees that small slice.

Step 1: Match Lead to Account Before Anything Else

The first routing decision is not "which rep is next?" It is "does this person belong to an account someone already owns?"

1. Normalize the email domain and match it to existing CRM accounts. Handle subsidiaries and regional domains with an alias table.
2. If the account has an owner, route to the owner. Customers go to the account manager. Open opportunities go to the AE on the deal. Target accounts go to the named rep.
3. If there is no match, create or enrich the account with firmographic data before routing, so territory and segment rules have something to work with.
4. Only then fall back to territory or round-robin.

Lead-to-account matching is the step that prevents the "three reps, one customer" problem. Tools like LeanData and Chili Piper are built around it, and HubSpot and Salesforce can do a basic version with workflows and assignment rules if your domain data is clean. Our post on connecting website personalization data to your CRM covers the account matching schema we recommend.

Step 2: Route by Intent Tier, Not Arrival Order

Not every website lead deserves the same treatment. Define three or four intent tiers from what the visitor did before and during the conversion, and give each tier its own path and SLA.

Write the SLA as a clock that starts at form submit, not at assignment, and decide in advance what happens when it is missed: reassignment to the next available rep, or an alert to the team lead. An SLA without a consequence is a suggestion.

The tier comes from your scoring model. If you do not have one yet, our lead scoring model template gives you fit and behavior tables you can adapt in an afternoon.

Step 3: Send Website Context with the Lead

A routed lead should arrive with enough context for the rep to open the conversation without research. At minimum:

• Pages viewed in the last 30 days, with late-stage pages highlighted
• Number of other people from the same company on the site in that period
• The campaign or source that brought them, including self-reported source if you ask for it
• Which personalized experience they saw (industry, segment, variant), so the rep's opener matches the message the buyer already read

That last point gets missed. If your website showed a logistics visitor a logistics case study and a "see it on your Salesforce data" CTA, the SDR's first email should not open with a generic pitch. Our guide to aligning sales and marketing with visitor data has a handoff template for this.

Step 4: Route Anonymous High-Intent Accounts Too

The highest-value change most teams can make is routing accounts, not just leads. When company-level identification shows an ICP account with several visitors on pricing and integration pages, nobody has filled in a form, so classic lead routing never fires. That account still has an owner, or should.

Set up an account-level alert:

1. Identify the company from the visit.
2. Match it to the CRM account and its owner (same logic as step 1).
3. When the account crosses a threshold (for example, two or more visitors and a pricing view in seven days), notify the owner in Slack or email with the pages viewed.
4. If the account has no owner, assign it by territory, the same as a lead would be.

Markettailor's visitor identification provides the company match and page history that this alert needs, so owners hear about the account while it is still researching, not after a competitor has booked the first call.

Worked Example: Three Requests on the Same Afternoon

Here is how the rules above handle three website conversions that arrive within an hour of each other.

Request 1: a demo request from a new contact at an existing customer. Simple round-robin would send it to the next SDR, who would pitch the product the company already pays for. With account matching, the domain matches a customer account, so the request goes to the account manager as a likely expansion conversation, with the pages the contact viewed (a second product line's pricing page).

Request 2: an ebook download from an unknown mid-market software company. No account match. Enrichment shows a good fit. The visitor read two blog posts and nothing else. That is research tier: the lead goes into nurture, and the account goes on a watch list. Two days later, a colleague from the same company reads pricing and the integrations page. The account crosses the high-intent threshold and is routed to the territory SDR, with both visitors' page history attached.

Request 3: a contact-sales form from a 4-person agency using a personal email address. Poor fit for a sales-led motion. Instead of taking an SDR's time, the visitor gets an automated reply pointing to the self-serve plan and a recorded product tour.

Same afternoon, three very different paths, and no rep wasted time on the wrong one.

Round-Robin: Where It Fits and Where It Fails

Round-robin is fine as the last fallback for unowned, mid-tier leads. It fails when it is the whole system:

• Out-of-office reps keep receiving leads. Use availability-aware round-robin, or the lead waits days.
• Equal distribution is not fair distribution. Ten research-tier leads and one hand-raiser are not equivalent. Weight by tier, or run separate rotations per tier.
• No collision protection. When several SDRs work from shared lists or the same territory, two of them can pick up the same prospect. Teams that run outbound off shared lists usually need lead reservation, where opening a lead locks it to one rep for a set period. Dialbrew's lead reservation is one example of that pattern.

How to Measure Lead Routing

Report these monthly, split by intent tier:

• Time to assignment: from form submit or alert to owner assigned. Should be seconds for automated rules.
• Time to first touch: from assignment to first call or email. Track the share handled within your SLA, not just the average, because averages hide the leads that waited three days.
• Misroute rate: share of leads reassigned manually after routing. Above a few percent, your matching or territory rules need work.
• Conversion to meeting by tier: if research-tier leads convert as well as high-intent ones, your tiers are not separating anything.
• Duplicate contact rate: accounts contacted by more than one rep in the same week.

For the response-time side of this in more detail, read our post on speed to lead for B2B demo requests.

Start Here

1. Add account matching in front of your current round-robin.
2. Split hand-raisers into their own path with a minutes-level SLA.
3. Attach page history to every routed lead.
4. Add one account-level alert for anonymous high-intent visits.
5. Review misroutes and SLA misses every month.

To see which accounts are researching you today and would trigger an account-level alert, book a walkthrough on our pricing page.