The lead came in on Friday. Someone saw it on Tuesday.
Most B2B leads are not lost on the website. They sit in a shared inbox with no owner until the person has signed with someone else. The HubSpot setup that gives every lead an owner and an alert in minutes.
The form works. The thank-you page shows. The lead lands in HubSpot. And then it sits there, because the notification went to an inbox three people share and none of them owns, and the one who usually checks it was at a conference. By Tuesday the lead has a quote from a competitor. Nothing on the website failed. The leak is between the form and the first human reply, and in my audits it is the most expensive one on most B2B sites, because every lead that reaches it has already cost the price of a click or a year of content.
- A lead without an owner is a lead nobody answers. Assign it by rule, in minutes, from every source.
- The alert has to carry the context: who, what company, what they asked for. A “new submission” email gets ignored.
- A deadline with an escalation is what makes the rule real.
- Measure first reply time per lead. It is the number that moves pipeline, and almost nobody tracks it.
Where the time goes
I ask new clients for a simple thing: the last twenty leads, with the time the form was submitted and the time the first personal reply went out. The median is rarely under a day. The spread is the interesting part. Some leads are answered in ten minutes, because the right person happened to be looking. Some wait four days. The difference is never the lead. It is whether anyone was told, and whether anyone owned it.
Fifty-two hours between a form and a reply, and fifty-one of them had nothing to do with writing the reply. That is the shape on almost every site I measure. It is also why routing beats any amount of landing page work: you can double the conversion rate of a page and still lose the leads two days later.
The workflow that decides, the moment a lead is created, who owns it, how they hear about it and by when they must reply. Done well it takes seconds and the person never thinks about it. Done badly it is a Slack channel called #leads that everyone has muted.
The setup
Four parts. I build them in this order because each one is useless without the one before it.
- One source propertyEvery lead gets a “lead source” the moment it exists: website form, chat, LinkedIn lead form, event import, referral. HubSpot sets some of these itself; the rest come from hidden form fields and the import template. Routing rules read this one property, so it has to be right first.
- An assignment ruleBy territory, by product interest, by company size, or simply round-robin among the people who sell. The rule is the business decision; the workflow just applies it. A lead that matches no rule goes to a named fallback owner, never to “unassigned”.
- An alert with contextEmail and Slack, to the owner, within a minute: name, company, what they asked for, the page they came from, a link to the record. One glance tells the owner whether to call now or tomorrow. The default HubSpot notification tells them a form was submitted.
- A deadline and an escalationA task on the record due in four business hours. If it is still open, the alert goes to the manager and the lead stays visible until someone writes. This is the part that makes the other three stick.
<!-- The source and the page, set on every form so routing can read them -->
<input type="hidden" name="lead_source" value="website-form">
<input type="hidden" name="source_page" value="/services/wordpress-speed">If the team is two people and leads alternate between them, that is a routing rule, and it beats “whoever sees it first” by a day on average. Start there. Add territories when you have territories.
The context that makes the first reply better
The alert is where most setups stop and where the biggest gain is left. A lead who wrote “we run on WordPress and the site is slow on mobile” should get a reply that mentions WordPress and mobile, not “thanks for reaching out, when are you free for a call”. So the alert carries the message, the page they came from, and whatever the site already knows: the plan they looked at, the article they read, the country. The owner spends the saved minutes on the reply instead of on finding the record.
Enrichment tools that look up the company and fill in employee count and industry are useful in the alert and dangerous in the rule. When the lookup fails, which it does for a third of small companies, a rule that depends on it sends the lead to the fallback. Route on what the person told you; enrich for context.
Measure it
One number: time from lead created to first personal reply, per lead, as a property on the record. HubSpot can set it from the first logged email or call. Then a report, by owner and by source, looked at weekly. The first week after routing goes live it drops from days to hours. The useful part is the weeks after, when it shows who is slipping and which source gets ignored.
52 hMedian first reply before routing, at the company above
40 minMedian first reply three weeks after
0Leads without an owner after the fallback rule
Where this fits with the rest of the site
Routing is the last step of the funnel, which is why I do it as part of the deep audit rather than as a separate conversation. Speed brings people to the page, tracking tells you who converted, consent keeps it legal, and routing is what turns the form into a reply. Fix the first three and leave the fourth, and you have measured, consented, faster-arriving leads that still wait until Tuesday.
Case · US moving companySpeed first, then the lead flowServer response from 650 ms to 57 ms, and every form submission routed to the branch that serves the address.650 ms → 57 msServer response, cached- Every form, chat and import sets a lead source
- A rule assigns an owner within a minute, with a named fallback
- The alert carries the message, the company and the page
- A task with a deadline is created on the record
- An unanswered task escalates to a manager
- First reply time is a property, and someone looks at it weekly
Questions from this article.
That is when it matters most. With three leads a week, each one is a third of the pipeline, and a reply on Tuesday instead of Friday is the difference between a call and a “we went with someone else”. Volume is an argument for routing, not against it.
The same shape works in all three: a source property, an assignment rule, an alert, a deadline. The names of the workflow tools differ. HubSpot is what most of the sites I work on use, so it is what the service page quotes.
They go through the same routing, which is the point. A lead from the chat widget, a LinkedIn lead form or a CSV import from an event gets an owner by the same rules as a website form. Otherwise you fix the form and the chat leads keep waiting.
A short alert with the name, company, what they asked for and a link to the record. Not a notification that a form was submitted. The difference is whether someone opens it.