In 2011, researchers at Harvard Business School, MIT, and InsideSales audited 2,241 US companies by submitting real test leads through their own web forms and timing how long it took anyone to respond. The average company took 42 hours. Thirty-seven percent replied within an hour, sixteen percent took between one and twenty-four hours, twenty-four percent took longer than a day, and twenty-three percent never replied at all, according to the study published in Harvard Business Review.
That study is now more than a decade old, and the number everyone still quotes from it hasn't moved much. Speed to lead, the gap between a prospect reaching out and a business actually responding, is still the single most measurable, most fixable leak in most sales pipelines, and most companies still treat it like a scheduling inconvenience instead of the revenue problem it is.
TL;DR:
- A 2011 audit of 2,241 companies found an average speed to lead of 42 hours, with 23% of companies never responding to a test lead at all, per the Harvard Business Review study.
- Speed to lead degrades fast: the longer a lead sits unanswered, the colder it gets and the more likely a competitor reaches them first.
- Most CRMs notify a human before anyone replies, which is the actual bottleneck. Automation that removes that step is what moves response time from hours to seconds.
- GoHighLevel's missed call text back feature fires an SMS automatically on a missed call, a native setting documented on GoHighLevel's own help site, and it is one piece of a full speed-to-lead system, not the whole system.
- The fix isn't a faster human. It's removing the human from the first response entirely and only looping them in once a lead is already engaged.
What speed to lead actually measures
Speed to lead is the time between a prospect's first action, a form submission, a missed call, a chat message, a booking request, and the business's first real response. It is not the time to close a deal. It is the time to acknowledge that a human or a system is now paying attention to this specific person.
That distinction matters because speed to lead is almost entirely under a business's control, unlike close rate, which depends on price, fit, and a dozen other variables nobody can automate away. A slow close rate might mean the offer is wrong. A slow speed to lead almost always means the process is wrong, and the process is the part you can fix this week.
Why the 42-hour average still happens in 2026
The HBR study is old, but the underlying bottleneck it exposed hasn't changed: most response processes still route through a human who has to notice a notification, open a tool, and type a reply. Every one of those steps adds delay, and delay compounds.
A few of the usual points where speed to lead breaks down:
- The lead lands in an inbox or CRM tab nobody is watching in real time. Email notifications especially have a built-in lag, both from delivery and from how often people actually check a crowded inbox.
- The call goes to voicemail and nobody follows up same-day. Our missed call text back guide covers this specific failure mode: the caller doesn't leave a message, and without an automated text, there's nothing in the system to act on until someone manually reviews the call log.
- The lead gets assigned to a rep who is in a meeting, driving, or off that day. A single point of ownership with no fallback means every lead's response time is capped by whichever rep happens to be unavailable.
- There's no defined target. Without an explicit response-time goal, "get to it when I can" becomes the default standard, and that standard drifts slower every quarter as the team gets busier.
None of these are exotic problems. They're the same five or six failure points showing up at almost every business that hasn't deliberately built a faster path, which is exactly why speed to lead is one of the highest-leverage things a GoHighLevel automation build fixes first.
Building a speed-to-lead system that doesn't depend on a human noticing first
The fix isn't hiring someone to watch the lead queue more closely. It's restructuring the first response so a human isn't the first point of contact at all.
1. Automate the first message, not just the notification
A workflow that fires an SMS, email, or WhatsApp message the instant a lead comes in, before any human sees an alert, closes almost the entire gap by itself. In GoHighLevel, that's a workflow triggered on form submission or missed call, firing a multi-channel first touch within seconds rather than waiting on a rep to open the notification.
GoHighLevel's missed call text back feature is the clearest native example of this: enable it under Settings, Phone System, Voice, then Voicemail and Missed Call Text Back, write the message, and set a ring timeout, exactly as documented on GoHighLevel's help site. The caller gets a reply before they've finished dialing the next business on their list.
2. Let AI handle qualification before a human has to
An instant message buys time, but it doesn't close a deal by itself. Pairing the instant response with an AI qualification layer, one that answers basic questions, confirms intent, and books a time on a calendar, means a lead can go from form submission to a confirmed appointment without waiting on anyone's schedule. That's the layer our AI automation team builds on top of a GHL foundation when a business needs more than a canned text reply.
3. Route around unavailable reps instead of queuing behind them
Single-owner lead assignment caps your fastest possible response time at the availability of one person. A round-robin or skills-based routing rule, with an automatic reassignment if the first rep doesn't act within a set window, keeps the system's speed independent of any one person's calendar.
4. Set an explicit target and track it like a real metric
"As fast as possible" isn't a target a team can be held to. A concrete number, five minutes for inbound form leads, instant for missed calls, under an hour for lower-intent inquiries, gives the system something to be measured against. As an illustration: if a business currently averages four hours and moves its target to fifteen minutes, that's not a vague aspiration, it's a specific automation and routing problem to solve, with a before-and-after number to check against each month.
Where GoHighLevel alone stops being enough
Native GHL workflows handle the core of a speed-to-lead system well: instant SMS, missed call text back, basic routing. Where it runs into limits is anything that needs to reach outside GHL, pulling inventory data before replying, checking a separate scheduling system, or running logic too complex for the native workflow builder.
That's the gap our workflow automation team fills by connecting GHL to n8n or custom APIs, so a lead's first message can reflect real-time information instead of a static template, without losing the instant response time that makes speed to lead work in the first place.
The next step
Pick one channel, your missed calls or your form leads, and measure how long it actually takes today between the lead landing and a real human or system response. Most businesses that run this test for the first time are shocked by their own number, because nobody has ever timed it end to end before.
Once you have that number, the fix is almost always the same: automate the first response so it happens before anyone has to notice the lead came in at all. Tell our GoHighLevel automation team your current average, and we'll scope the workflow that gets it down to seconds.
