Speed to lead: where leads leak between the form and the phone

Speed to lead is the time between a customer raising their hand and a person answering them. This page walks through that stretch, shows the places a lead leaks out of it, and explains how to test your own path and write a response standard the business can keep. An owner can use it to check their own business this week, and a marketer can use it to fix what the test finds.

The stretch between the form and the phone

Say a homeowner fills out a roofing company's estimate form at 9 p.m. on a Tuesday. The ad did its job and the website did its job. What happens over the next day decides whether that form becomes a roof. The notification might go to a shared inbox the owner checks on Thursdays. The confirmation email might land in spam. The owner might call once on Wednesday afternoon, reach voicemail, and move on. By then the homeowner may have called someone else.

Nobody owns this stretch by default. Marketing gets credit for the lead, the office gets blamed for the lost job, and the hours in between belong to no one. Every lead passes through the same six steps, and each one is a place it can leak.

Raise a handThe customer fills out a form, calls, sends a message, or books online.
NotifyA specific person finds out, on a device they actually check.
AcknowledgeThe customer hears right away that a real person has the request and what happens next.
RespondA person makes contact in the channel the customer used, within a promised time.
RecordThe lead lands in the CRM with its source, the service, and a next step.
RetryIf the first attempt gets no answer, more attempts follow on a schedule.

Where leads leak

These are the leaks I look for first. Most of them are invisible from inside the business, because the office only ever sees the leads that made it through.

Leak	What it looks like	The fix
Notifications go to an unmonitored inbox	The form emails an old address, a shared inbox nobody owns, or whoever built the website.	Send every form to a named person and a backup, and send a test after any change to the site or the email accounts.
The form never sends	The page looks normal, but a broken script or a switched-off service means nothing arrives. Sometimes only some of the forms on a site are broken.	Submit every form on the live site after each change, and put an uptime check on whatever receives submissions. See contact forms that work.
The auto-reply lands in spam	The confirmation comes from an address the business's domain has not authorized to send mail, so it lands in spam or never arrives.	Send from the business's own domain with SPF, DKIM, and DMARC records in place, and check a test message in both a Gmail and an Outlook inbox.
A missed call gets no text back	The owner is on a job, the call rings out, and the caller hangs up without leaving a message.	An automatic text from the business number when a call is missed, with a real person reading the replies. See follow-up sequences.
Voicemail never gets returned	Messages sit in a mailbox only one person can reach, or nobody is assigned to return them.	Deliver voicemail as a text or email to whoever owns new leads, and treat each message as a task with a due time.
The lead reaches the CRM days later, without its source	Someone copies leads out of the inbox at the end of the week, and the source field says "Google" or nothing at all.	Forms and calls create CRM records automatically, with the source attached. See the CRM pipeline guide.
There is no second attempt	One call, no answer, and the lead is quietly dropped.	A written number of attempts across at least two channels, then a deliberate stop with a lost reason.
After hours has no fallback	An evening form fill waits until someone opens the inbox the next day, and nobody told the customer when to expect a call.	An instant acknowledgment that says when a person will call, and a morning routine that keeps that promise.
The button promises something else	"Book a call" opens a message form, or a link to the contact section lands on the page without opening the form.	Make every button do what it says. If it says book, show a calendar.

Walk the path yourself as a secret shopper

You cannot see these leaks from the inside, so go around to the front door. A secret shopper test means contacting the business exactly the way a customer would and writing down what happens next. It runs across a week, because the follow-up is part of the test.

Set up as a stranger
Use a phone number and an email address the business will not recognize, so nobody treats the test differently. Plan to run each test once during business hours and once in the evening or on a weekend.
Test every form
Submit the main contact or estimate form from a phone. Then submit the form on at least one service page and one location page, because the homepage form working tells you nothing about the others.
Test the phone
Tap the phone number on the website and confirm it dials the right line. Call and hang up at voicemail without leaving a message, then watch for a text or a call back. Call again, leave a voicemail with a callback number, and note when it gets returned.
Test every other door
Search for the service the way a customer would and follow the same listing or ad they would. Send a message on every channel the business advertises, such as Facebook or Instagram messages or a chat widget on the site, and use the booking link if there is one.
Keep a log for seven days
For each test, write down the time you reached out, the time of the first automatic reply, the time of the first human contact, the channel, what was said, and how many attempts followed.

A business that passes looks like this:

Every form on the site delivers, including the service and location pages.
An acknowledgment arrives within minutes, in the inbox rather than spam, and says what happens next.
A person makes contact within the business's own stated response time, after hours included.
A missed call gets a text or a call back, whether or not a voicemail was left.
When the first attempt gets no answer, more attempts follow.
Each test shows up in the CRM with the correct source, an owner, and a next action date.

Write a response standard

A response standard is a short written promise about what happens after a customer reaches out. Without one, the real standard is whatever happened that day. Written down, it becomes something you can staff, automate, and check.

Who responds

One named person owns new leads during business hours, with a named backup. "The office" is not an owner.

By when

A response time you can keep every day, not only on your best day. Set one clock for business hours and another for after hours, such as "by 9 a.m. the next business day."

By which channel

Answer in the channel the customer used, then add a second one. A form fill gets a call plus a text or email. A missed call gets a text back plus a return call.

How many attempts

A set number of tries, spread over several days and at least two channels, followed by a final message and a lost reason in the CRM.

What counts as urgent

The requests that justify a call tonight, such as an active leak or a no-heat call in January, and whose phone rings for them.

How it gets checked

Response time recorded in the CRM and reviewed every week, not remembered.

The right numbers depend on what the customer is buying. Someone with water coming through the ceiling is on a different clock than someone planning a kitchen remodel for next spring. I do not have a universal number to give you, and I would be wary of anyone who quotes one. Pick the fastest response the business can actually staff, write it down, and tighten it once you are hitting it every week. My own contact form promises a reply within one business day, because that is a promise one person can keep.

Response standard: example for a small roofing company

Owner of new leads    Office manager. Backup: the owner.
Acknowledgment        Automatic text and email as soon as a form
                      or a missed call comes in.
First human contact   Within 1 hour, Monday to Friday, 8 a.m. to 5 p.m.
After hours           A call by 9 a.m. the next business day.
Urgent                Active leaks go to the owner's cell, any time.
Attempts              Day 1: call and text. Day 2: call. Day 4: email.
                      Day 7: final text, then mark lost with a reason.
Recorded in           The CRM: source, service, owner, next action, date.
Checked               Monday pipeline review.

The numbers in that example illustrate the shape of a standard. They are not a benchmark.

Measure response time

Response time is easy to measure once leads are records instead of emails. The CRM already stamps the moment a record is created. Add the time of the first human contact, either from the call and text log or from a field the owner fills in with one tap, and the difference between the two is your response time.

Review it weekly, split by business hours and after hours, because those are two different promises. Then count the leads that never got a human contact at all. That count matters more than the average, because an average can look healthy while a handful of leads get nothing.

How this fits the Journey Audit

In the Journey Audit method, everything on this page lives in two stages. The decision stage covers the contact form, the phone number (is it tracked, and does someone answer?), the inbox the form actually sends to, the booking link, live chat, the quote process, text opt-in, and the after-hours fallback. The onboarding stage covers what happens right after someone says yes: the welcome message, the first appointment, the first invoice, and the first piece of work.

Every touchpoint in the audit is scored on six dimensions, and two of them are this page in miniature. Tracking asks whether the interaction is recorded well enough to connect revenue back to its source. Follow-up asks what happens after the interaction: a structured next step, or nothing. The same leaks can reappear right after the sale, which is why onboarding gets scored with the same questions. If you would rather have someone run the whole test and hand you a ranked list of what to fix, that is what the Journey Audit is for.