Speed to Lead: Where the Minutes Actually Go, and the Four Fixes That Work

I used to think our response time was about fifteen minutes.

Then a client asked me to prove it, and I went and counted. The median was just over four hours. Not because anyone was lazy, and not because the software was slow. The form fired instantly, the alert landed instantly, and then it sat in a notifications list behind eleven other things until somebody looked.

The software was never the bottleneck. The handover was.

That is the part the GoHighLevel sales pages skip, and it is why so many agencies buy an automation tool and watch their response time stay exactly where it was. So here is where the minutes really go, and the four fixes in the order they pay back.

What does speed to lead actually mean?

The clock starts when someone asks you for something. It stops when a real person answers them.

That second half is where people cheat. An instant auto-text isn't a reply, it's a holding message, and if you count it as one your dashboard looks great while your bookings stay flat. Measure the first outbound human message and nothing else.

One more thing worth settling early: use the median, not the average. One lead you answered three days late drags an average into fiction, and that's the number most people quote, because it's the one the tool shows first.

Where does the five minute rule come from?

It comes from the Lead Response Management study, led by Dr James Oldroyd with InsideSales, built on data from 2004 to 2007 across six firms, more than 15,000 leads and over 100,000 dials.

Two findings get quoted everywhere. Replying inside five minutes rather than thirty made contact about 100 times likelier, and qualifying about 21 times likelier.

Now the part almost nobody says out loud. That study is nearly twenty years old. It looked at web leads in a world before everyone texted, before most people would pick up a number they didn't know, and before a form fill meant filling three forms in a row on three sites.

Does that make it wrong? No. The direction has held up in every study since, and it matches what I see in pipelines each week. But treat those numbers as proof that speed matters hugely, not as a stat to put on a slide. If a prospect asks where 21x comes from, you want to know the answer.

So where do the minutes actually leak?

Four places, and only one of them is software.

Form to CRM. Usually fast, sometimes not. A native form writes straight to the contact record. A third-party form might batch, or retry, or quietly fail on a field that doesn't match. Worth testing once rather than hoping.

CRM to notification. Also usually fast, and also the one people blame.

Notification to a human. Here's your problem. The alert landed at 2:04pm, your account manager was on a call until 2:40 and then went to lunch. Nothing is broken. Somebody is just busy, which is the normal state of a person.

Human to the actual reply. They open it, see it needs a quote, decide to do it properly later, and later turns out to be tomorrow.

Add those up and you get four hours out of a stack that answers in under a second. The leak is human, which is why buying more software rarely fixes it.

Which four fixes pay back first?

In this order. The first one is free and does most of the work.

One. Escalate when nobody picks it up. If the lead isn't marked contacted within ten minutes, alert a second person, then a third at twenty. This one rule has saved more pipelines than any change I've made to the messages, because it fixes the real failure, which is that one person was busy. Build it as a wait step with a condition, not as a nudge someone has to recall.

Two. Text first, and text from a real number. A text gets read in minutes. An email gets read when they next open email, which might be Thursday. Keep it short, use their name and the thing they asked about, and make it answerable in one word.

Three. Put a booking link inside the first message. Half your speed problem goes away if the lead can book without waiting for a human at all. People skip this one because it feels like it cheapens the chat. It doesn't, it respects their time.

Four. Kill the forms nobody reads. If a lead fills in eight fields and then waits four hours, you've taken their effort and given nothing back. Cut the form to name, number and one question, and qualify properly on the call instead.

The mechanism underneath all four is the same. The form writes to the shared contact record, a workflow reads that record and fires the text, the escalation step watches whether anyone marked it contacted, and the booking link writes the appointment back onto that same record. One record, four jobs, no spreadsheet. I covered the common builds in GoHighLevel workflow automation use cases.

What should you fix if you only have an hour?

Build the escalation rule. That's it.

Open your lead workflow, add a wait of ten minutes after the first text, then a condition that checks whether the contact has been marked as contacted. If they haven't, notify a second person. Give it twenty minutes and notify a third.

It took me about fifteen minutes to build the first time and it immediately caught a case I'd have sworn didn't exist: a Friday afternoon where one person had four leads land inside an hour and answered three.

Everything else on this page is worth doing. But if you do one thing, do that, because it's the only fix that works when the problem is simply that somebody was busy.

What about the calls you miss entirely?

A missed call is a lead with a worse response time than any form, because nobody even knows it came in.

The fix is a text back that fires the moment the call drops. Not an hour later. Within seconds, from the same number they dialled, saying you missed them and asking what they need. People reply to those at a rate that still surprises me, mostly because the other option is ringing the next firm on the list.

Two things decide whether it annoys people. Don't fire it when your team already rang back, and don't fire it at 11pm. Both are conditions on the workflow and both get skipped, usually because nobody thinks about the edge cases until a customer complains about one. The full build is in GoHighLevel missed call text back.

How do you measure this honestly?

Two numbers on one dashboard, reported weekly.

Median time from form submission to first human message. And the share of leads answered inside ten minutes, which is the number that really moves when you fix something, because a median hides the tail.

Then one habit that costs nothing. Put response time on the client report, next to cost per booked call. When a client's own team is the slow part, and often it is, the number says it before you have to. That one column has saved me a few awkward chats about lead quality that were never really about lead quality.

One more thing on measurement, because it decides whether any of this sticks. Pick the day of the week you review it and keep it. Monday works, because the weekend tail is visible and still fresh. If you look at response time only when something has gone wrong, you'll only ever see the bad weeks, and you'll start making changes to fix a number that was never typical in the first place.

And keep one eye on the sources separately. An average across every channel can look fine while one source, usually the one somebody set up and forgot, sits at nine hours on its own and quietly drags your booking rate down with it.

Watch it for a month before you change anything else. Most agencies find their problem is one person, one hour of the day, or one source nobody owns.

We build it, you own it

GoHighLevel is the software and HighLevel bills you for it. GHL Spark is a separate company. We set the account up and take nothing on the platform fee.

What we build is the chain. The form writes cleanly to the contact record, the first text goes out in seconds from the right number, the escalation rule catches a busy human, the booking link skips the wait, missed calls get texted back with the right conditions on them, and the two numbers land on a dashboard so you can see whether any of it worked.

Where to go next

If you would rather start from a build that already has this wired in, our ready-made workflows ship with the follow-up, escalation and missed call steps configured.

Or bring your own numbers to a free consultation and we will find where your four hours are hiding.