Your website gets visitors who are already interested. The problem isn't identifying them — it's building a workflow that puts the right visitors in front of the right BDR, fast enough to matter. Here's how to score, route, and follow up on identified website visitors the way teams who actually close deals from this channel do it.
Why Most BDR Teams Leave This Signal on the Floor
Website visitor identification surfaces something rare in B2B outbound: a warm, active, named signal. Someone is on your site right now, reading your pricing page, comparing your product to something else.
But the default response at most companies is either to dump every identified visitor into Salesforce — creating CRM clutter no one manages — or to not act at all because there are too many visitors and no clear filter. The result: a signal that could be generating pipeline gets treated like background noise.
The teams who get this right don't try to work every visitor. They build a three-step workflow: filter ruthlessly, route in real time, follow up in the window that matters.
Step 1: Filter Down to the 20% Worth Your BDRs' Time
Not every identified visitor belongs in your BDR queue. Inbound form submissions average around 1% of site traffic — which means a company receiving 300 inbound leads per month likely has 25,000–30,000 unique monthly visitors. Most of them are students, competitors, job seekers, or existing customers.
The first job is filtering down to the visitors worth acting on.
Start with ICP scoring. Define your target persona the way you'd brief a new BDR: company size, industry, seniority level, relevant tech stack. Then let that definition drive the scoring. Knock2 lets you write this as a natural language prompt — the same reasoning you'd apply manually, applied automatically to every identified visitor. That's fundamentally different from brittle if/then rule sets that break every time your ICP shifts or your product expands into a new segment.
Exclude existing customers and known accounts first. Pull your closed-won list and current customer domains into your exclusion filter. Existing customers visiting your pricing page are a retention signal — not a new pipeline opportunity — and mixing them into your BDR queue muddies both.
Look for behavioral intent, not just presence. A C-level executive who bounced off your homepage is not the same signal as a VP of Sales who visited your pricing page twice this week and read your integration docs. The page visited, time on site, and visit frequency should all feed into prioritization — with pricing pages, product pages, and comparison pages at the top of the stack.
After filtering, you're typically looking at 15–25% of identified visitors as worth BDR attention. That's a manageable, high-conviction queue.
Step 2: Build the Routing Layer That Gets to the Right Rep
Filtering is necessary. Routing is where most teams lose the efficiency they just gained.
Match to CRM ownership first. Before any identified visitor becomes a new lead, check whether the account is already in your CRM and who owns it. Nothing burns rep trust in a visitor identification program faster than finding "their" accounts routing to someone else's queue.
Route by territory and segment. If you have UK, APAC, or regional reps, build that logic into your routing rules now. A well-scored ICP visitor routed to the wrong territory is still a bad outcome — and fixing it retroactively is slower than preventing it.
Use Slack as the real-time alert layer. The workflow that converts best for Knock2 customers looks like this: a visitor hits your score threshold → a Slack notification fires with full context (name, title, company, pages visited, firmographics) → the BDR clicks one button to create the CRM record and start a sequence. That human-in-the-loop step is deliberate. Automation handles the filter; the BDR makes the final call on whether to engage and how. It takes 30 seconds and eliminates both noise and missed opportunities.
Build separate queues by intent tier.
| Signal | Tier | Action |
|---|---|---|
| Pricing page, 2+ visits, VP title, ICP company | P1 | Slack alert → follow up within 1 hour |
| Product page, first visit, Director title, ICP company | P2 | Daily digest → BDR queue today |
| Homepage only, unknown title | P3 | Automated nurture or skip |
| Existing customer domain | Exclude | Flag for CSM, not BDR |
Step 3: Follow Up in the Right Window
Website intent signals decay fast. Someone on your pricing page at 10 a.m. is not the same conversation by 4 p.m., and by tomorrow the context is cold. Companies that follow up with warm leads within 5 minutes are 100x more likely to connect than those who wait 30 minutes. The fact that this visitor was researching your solution right now is the entire advantage — don't give it away by waiting.
What the first touch should look like: Don't open with "I noticed you were on our website." That reads as surveillance and converts poorly. Lead with the relevant insight — something about their company, their apparent use case based on pages visited, or the category they're clearly evaluating. The visitor data tells you what they care about; use it to personalize the message, not to explain how you found them.
A P1 follow-up sequence looks like this:
- Hour 1: Personalized email referencing their likely use case
- Hours 2–4: LinkedIn connection with a short, relevant note
- Day 2: Phone call if no response
- Day 3: Second email with a case study or relevant resource
- Day 5: Final touch, then move to lower-cadence nurture
For P2 visitors, the same structure works on a 24-hour delay.
The Stack That Makes This Work
You don't need a 10-tool stack. The core:
- Knock2 — visitor identification, ICP scoring, and alert routing
- Slack — real-time BDR notifications with one-click CRM actions
- Salesforce or HubSpot — CRM of record for lead creation and territory routing
- SalesLoft, Outreach, or Orum — sequence execution once the BDR decides to engage
- Clay — optional enrichment layer if you want to append data before sequencing
Most BDR teams already have the last three. This workflow is about connecting them with the right trigger at the right time.
Refine Your Score Threshold Every Quarter
The most common failure mode after launching this workflow is set-it-and-forget-it. Your ICP evolves, your product expands into new verticals, and the scoring prompt you wrote in Q1 may be over- or under-scoring by Q3. Build a monthly review into your RevOps calendar: look at which P1 visitors converted to meetings versus which ones were a waste of BDR time, and adjust the scoring logic accordingly. Knock2 customers who do this consistently see their conversion rate from identified visitors improve quarter over quarter as the filter gets sharper.
Frequently Asked Questions
How fast should BDRs follow up with identified website visitors?
Treat high-intent identified visitors the same as inbound form fills — the goal is within 1 hour for P1 visitors (pricing page, repeat visitor, ICP-fit title), with same-day follow-up for P2. Companies that respond to warm leads within 5 minutes are 100x more likely to connect than those that wait 30 minutes. The intent signal is time-sensitive; the follow-up should be too.
Should every identified visitor go to a BDR?
No. After ICP scoring and behavioral filtering, typically 15–25% of identified visitors meet the bar for BDR outreach. The rest belong in automated nurture or should be excluded — existing customers, career page visitors, off-ICP traffic. Routing everything to BDRs creates noise and burns the channel fast.
What's the difference between account-level and contact-level identification for BDR routing?
Account-level tells you which company visited. Contact-level tells you the actual person — name, title, work email. Contact-level is far more actionable because you can personalize and sequence immediately. Account-level still has value: use it to find the right buyer at the account using your ICP criteria, then route to the territory owner. Knock2 provides both, with contact-level identification available for US visitors.
How do I avoid BDR burnout from too many visitor alerts?
Score ruthlessly before routing. Set a threshold so only visitors above your ICP bar and on high-intent pages trigger a real-time Slack alert. Everything else goes into a daily digest or automated sequence — not a ping that demands immediate attention. The goal is a P1 queue that rarely exceeds 10–15 alerts per BDR per day.
Can this workflow route directly to Salesforce without going through Slack?
Yes. Knock2 supports fully automated workflows that create CRM records immediately when a visitor meets a score threshold, with no human review step. The Slack routing layer is recommended when you want BDRs to have context before a record hits their queue — it surfaces the visitor's page history and intent signal in the notification, which typically improves the quality of the first touch.
