A VP of RevOps visits your pricing page at 10:14am. She spends 2 minutes 40 seconds on the page, clicks through to your comparison table, then closes the tab. Your Leadpipe pixel identifies her. The webhook fires. A Slack alert drops into #sales-hot.
At 10:16am, three reps see the alert. Each one assumes another rep will handle it. At 12:40pm your SDR finally writes her a note. By then she has already booked a demo with the competitor she was about to compare you against.
This post is not about what to put in the email. There is a separate post for that: What to do when someone visits your pricing page. This post is about one thing only, the clock. How many minutes you actually have, why most teams blow the window, and the SLA structure we recommend for any team running identification against a live pricing page.
At Leadpipe we have watched hundreds of teams turn on visitor identification. The ones who convert pricing-page visits into meetings do not have better copy. They have a shorter clock.
The answer up front: reply within 7 minutes
The outside edge of useful is 60 minutes. The inside edge, the one that produces the kind of reply rate that changes your quarter, is closer to 7.
Here is the data-backed framing we use to set the SLA:
| Time from visit to first reply | Relative likelihood of reaching the prospect | What is happening on their side |
|---|---|---|
| 0 to 5 minutes | Baseline (1x) | Tab is still open or just closed |
| 5 to 15 minutes | ~0.7x | Moved to the next tab, likely a competitor |
| 15 to 60 minutes | ~0.3x | In a meeting or on another task |
| 1 to 4 hours | ~0.1x | Day has moved on |
| Next day | cold email territory | They are no longer in evaluation mode for you |
The original InsideSales / Harvard Business Review study from 2011 found that contacting within 5 minutes was roughly 100x more likely to reach a lead than contacting after 30 minutes, and 21x more likely to qualify than after 30 minutes. The effect has held up in every replication we have seen in the 15 years since.
The practical target is a 7-minute reply SLA for Tier 1 pricing-page visitors. That is the time from webhook received to first outbound message sent. Not the time from when someone notices the alert. Not the time from when the AE opens the CRM. From webhook to first touch.
The playbook: a 7-minute reply SLA that survives contact with reality
Step 1: Define what counts as a pricing-page Tier 1 (30 seconds of config)
Not every pricing view deserves a 7-minute response. You will burn out your reps. Tier 1 is the subset worth the urgency.
Use these rules to qualify a Tier 1:
- Visited a pricing page OR a
/pricing,/plans,/buy,/compare,/demo, or/roi-calculatorURL - Stayed 45 seconds or longer on that page
- Company is in your ICP (size, industry, geography)
- Not an existing customer, not a competitor domain, not a job applicant
- Not in an EU/UK jurisdiction unless you have person-level consent (Leadpipe defaults to company-level for EU/UK visitors)
If all five are true, that is a Tier 1. Everything else routes to a slower lane.
Step 2: Route one alert to one human, not five humans (alert = action in 60 seconds)
The single biggest reason SLAs fail is diffusion of responsibility. A Slack channel with five reps produces a worse reply time than a Slack DM to one rep. Route by territory, account ownership, or round-robin, then send a DM, not a channel post. The auto-routing playbook walks through the logic.
The alert should include everything the rep needs to reply without opening another tab:
Tier 1 pricing visit - reply in 7 min
Sarah Chen, VP RevOps at Acorn (215 employees)
• 2m 40s on /pricing
• Also viewed /compare and /integrations/salesforce
• 3rd visit this month
• sarah@acorntech.com
• linkedin.com/in/sarahchen
Reply template: https://...
Mark handled: :handled:Alert to action within 60 seconds is the goal. If your rep has to click through to the CRM, enrich the record, find the template, and paste variables, you have already burned 3 minutes of the 7-minute SLA on operational tax.
Step 3: Pre-write the first reply (90 seconds to customize, 30 seconds to send)
The rep is not writing from scratch. They are customizing a template against the visit context. The template is in the alert. The rep changes three things: first name, the specific page the prospect spent the most time on, and the relevant integration or competitor from the pages viewed.
Time budget the rep actually has inside the 7-minute SLA:
| Minute | Activity |
|---|---|
| 0:00 to 0:30 | See DM, scan alert |
| 0:30 to 2:00 | Pull up template, customize three variables |
| 2:00 to 3:30 | Write one custom sentence referencing what they researched |
| 3:30 to 6:00 | Verify email is correct, send |
| 6:00 to 7:00 | Buffer, CRM logging |
Seven minutes is tight. It should feel tight. If it feels leisurely, you are routing alerts to reps who are not in a state to act.
Step 4: Escalate when the SLA is about to miss (at the 5-minute mark)
Build a timer. At minute 5, if the primary rep has not marked the alert handled, escalate to a backup. At minute 10, escalate to the sales manager. At minute 30, mark it SLA-missed and log it.
The point of escalation is not punishment. It is making sure the visitor gets reached before the tab closes on the competitor side. An honest 12-minute reply from a backup is better than a 4-hour reply from the primary.
Step 5: Log every SLA hit and miss for weekly review
You cannot manage a reply SLA you do not measure. At minimum track:
- Total Tier 1 alerts per week
- Median time-to-first-reply (goal: under 7 minutes)
- 90th percentile time-to-first-reply (goal: under 15 minutes)
- SLA-missed count (goal: under 10% of Tier 1)
- Reply rate from recipients (benchmark: 15 to 25% for identified pricing visitors)
A 7-minute median with a 90th percentile of 45 minutes means you have a tail problem. Some alerts are slipping. Usually it is after-hours or cross-territory visits with no clear owner. Fix the routing, not the reps.
Sample Slack alert template (copy this)
:fire: Tier 1 pricing visit - 7 min SLA
Who: Sarah Chen
Title: VP RevOps
Co: Acorn Technologies (215 FTE, SaaS, San Francisco)
Visit: /pricing (2m 40s), /compare (1m 10s), /integrations/salesforce (25s)
Pri: 3rd visit in 30 days
Email: sarah@acorntech.com
LI: linkedin.com/in/sarahchen
Template: https://drive.../templates/pricing-tier-1
React :handled: when sent. Auto-escalates at 5:00.The format matters less than the principle. Every piece of context the rep needs must be in the alert itself. If the rep has to leave Slack to act, you have lost 2 minutes already.
Common failure modes
Failure mode 1: The channel, not the DM. A #sales-hot channel with 7 reps produces 22-minute medians in every team we have observed. Switch to DM routing. If a rep does not claim it in 2 minutes, re-route.
Failure mode 2: Over-qualification. Teams add 11 criteria to Tier 1 and end up with 3 alerts per week. The SLA becomes meaningless because the sample is too small to build a habit. Start permissive, then tighten.
Failure mode 3: No escalation path. The primary rep is in a demo. Nobody else knows there is a hot alert. The 7 minutes expires. Always have a backup tier.
Failure mode 4: Alerts without the pre-written template. The rep spends the first 4 minutes of their SLA window looking for the right template. Build the template link directly into the alert.
Failure mode 5: Ignoring the human cadence. Reps take breaks. Reps have lunch. Reps have 1:1s. A 7-minute SLA during business hours is realistic. A 7-minute SLA at 9pm is not. Define SLA hours (we recommend 8am to 6pm in the rep’s timezone) and hand off to a batched queue outside those hours.
Failure mode 6: Emailing without context about what they viewed. The rep replies “saw you checked us out.” That is creepy. The rep should reference the topic, not the page URL or timestamp. See the warm email without sounding creepy post for the line between relevant and surveillance-y.
Measurement: how to know it is working
Three leading indicators:
- Median time-to-first-reply under 7 minutes. This is your process metric. If this breaks, nothing else works.
- SLA compliance rate above 90%. Tier 1 alerts that got a reply inside 7 minutes, divided by total Tier 1 alerts.
- Reply rate from identified pricing-page visitors above 15%. This is the output metric. If SLA is tight but replies are flat, the copy is wrong, not the clock.
Two lagging indicators:
- Meeting book rate from Tier 1 alerts. Target 8 to 15% of Tier 1 alerts turn into a booked meeting.
- Pipeline from identified pricing visits as a percentage of total inbound pipeline. Most teams we have seen hit 15 to 30% after 90 days of running this SLA.
One trap. Do not measure reply rate across all identified visitors lumped together. Tier 1 will carry a 20% reply rate and Tier 3 will carry a 2% reply rate, and the blended number tells you nothing.
What about weekends and nights?
Visitors do not only browse during business hours. You have two reasonable options.
Option A: Honest off-hours handling. State to the team that the 7-minute SLA applies 8am to 6pm, Monday to Friday, in the account owner’s timezone. Off-hours alerts drop into a queue and get handled first thing the next business morning. Your 12-hour “cold” reply is still better than a next-week reply.
Option B: Covered off-hours. Use a follow-the-sun rotation or a Zapier-driven automated first-touch that sends a pre-approved email from the account owner’s address at any hour. Your “reply” is an auto-send, but it is personalized against the visit context.
Most teams should start with Option A. Move to Option B only when pipeline volume justifies it.
Where this connects to the rest of your visitor stack
Reply speed only matters if the visitor got identified in the first place. On US B2B traffic Leadpipe identifies 30-40%+ of visitors with full contact data, deterministic, from a 2 to 5 minute JavaScript pixel install. The independent accuracy test scored this at 8.7/10 against RB2B at 5.2 and Warmly at 4.0.
Reply speed is also downstream of good routing. A 7-minute SLA dies the moment an alert goes to the wrong rep. The auto-routing playbook and the SDR playbook for identified visitors cover that logic.
For EU/UK pricing-page visitors, remember that Leadpipe defaults to company-level data, so a “Tier 1” alert will contain the company and firmographics but not a named person unless the visitor has given affirmative consent. Your SLA for those alerts targets the account, not a specific individual.
Putting it together
A pricing-page visit is not a lead. It is a 7-minute window. Everything about your alerting, routing, and rep workflow should be structured to fit inside that window.
The rule is simple. From webhook received to first message sent, under 7 minutes for Tier 1, under 1 hour for Tier 2, same-day for Tier 3. One alert, one owner, one pre-written template, a 5-minute escalation, and honest measurement every week.
If you cannot hit 7 minutes today, start by fixing the routing. Then the alert format. Then the template library. Most teams get to a sub-10-minute median inside two weeks.
Leadpipe identifies 30-40%+ of your US B2B visitors with full contact data on the Pro plan at $147/mo. No credit card to start the 500-lead trial. Start identifying visitors →
