Most service businesses do not lose enquiries because they are bad at the work. They lose them in the gap between “someone asked” and “someone replied.” Speed to lead is the time it takes you to respond to a new enquiry, and for most small teams it is the cheapest thing to improve. In this article I cover why the first reply matters, what fast realistically means when you are busy, and the 5-minute reply system I set up for clients.
What speed to lead means
Speed to lead is the time between a new enquiry arriving and a real response reaching that person. The enquiry might be a website form, a missed call, a Facebook or Instagram message, a Google Business message, or an email.
Two things are worth separating:
- Acknowledgment: the person knows their message arrived and what happens next.
- Real response: someone answers their actual question, offers times, or gives a quote range.
An automated reply can handle the first one in seconds. The second usually needs a human. A good system does both, in that order.
Why the first reply matters
When someone sends an enquiry, they are paying attention right now. They have a leaking pipe, a toothache, a legal question, or dates for a villa. Often they have contacted two or three businesses at once. The first one to reply clearly tends to get the conversation.
There is research on this. In 2011, Harvard Business Review published “The Short Life of Online Sales Leads” by Oldroyd, McElheran and Elkington. They found that firms that tried to contact potential customers within an hour of receiving a query were nearly 7 times as likely to qualify the lead as those that waited longer. Compared with companies that waited 24 hours or more, they were more than 60 times as likely.
That study looked at companies in general, not only service businesses, and it is from 2011. I do not treat it as an exact forecast for any one business. I treat it as a clear signal about direction: interest fades fast, so replying sooner gives you better odds.
What “fast” realistically means for a small team
You might read advice that says “reply in under a minute, every time.” For a two-person clinic or a plumber on a roof, that is not realistic. Here is how I think about it instead.
| Response type | Realistic target | Who or what does it |
|---|---|---|
| Acknowledgment | Within 1 minute | Automation |
| First human reply, during hours | Within 5 to 15 minutes | Whoever is on duty |
| First human reply, after hours | First thing next opening | Named person |
| Follow-up if no answer | Same day, then next day | Automation plus a person |
The 5-minute target in this article’s title is about the system, not about a person staring at their phone. Within five minutes, every new enquiry should be acknowledged, assigned to someone, and visible in one place. The human reply follows as soon as that person is free.
The 5-minute reply system
This is the structure I set up. I usually build it in GoHighLevel because the forms, inbox, pipeline and automations sit together. The same logic works in other tools.
Step 1: Acknowledge automatically
When a form is submitted, a workflow sends an SMS and an email right away. If you text US numbers, the phone number needs A2P 10DLC registration, and the form should collect consent to receive texts.
The message should do three jobs: confirm it arrived, say what happens next, and give one easy way to continue.
SMS after a form: “Hi Maria, thanks for your message to Harbor Dental. Jess from the front desk will reply within the next 15 minutes during opening hours. If it’s easier, you can reply to this text. Reply STOP to opt out.”
Email after a form: “Thanks for getting in touch. I’ve received your enquiry about a roof inspection and I’ll reply today with available times. If anything is urgent, call or text this number: [number].”
For missed calls, the acknowledgment is a text back, which I covered in detail in missed call text back.
Step 2: Put every enquiry in one place
Enquiries that arrive in five different places get missed. I route forms, SMS, Facebook and Instagram DMs, Google Business messages and email into one inbox. In GHL this is the Conversations inbox. Each new enquiry also creates an opportunity in the pipeline, in a stage called something like “New enquiry.”
Now the question “did anyone reply to that person?” has one place to check.
Step 3: Route it to a named person
“The team will reply” usually means nobody in particular will. Each enquiry needs an owner. Simple routing rules work well:
- By service: implant enquiries go to the treatment coordinator, cleanings to the front desk.
- By location: north office or south office.
- By time: whoever is on duty that day.
The workflow then sends an Internal Notification to that person, by app push or SMS, with the name, the service, and a link to the conversation.
Step 4: Escalate if nobody replies
This is the step most setups skip. After the notification, the workflow waits, for example 15 minutes during business hours. Then a condition checks whether anyone has replied or moved the opportunity out of “New enquiry.”
- If yes: stop. A human has it.
- If no: notify a backup person, or the owner.
This turns a slow reply from an invisible problem into a visible one.
Step 5: Follow up if they go quiet
Sometimes you reply fast and the person does not answer. That is normal. They got busy. A short follow-up the same day and one the next day is reasonable. The workflow stops the moment they reply or book.
Same-day nudge: “Hi Maria, just following up on your enquiry. Would Thursday at 10am or Friday at 2pm suit you? Happy to find another time too.”
What a human reply should include
Automation buys you time. The human reply is what wins the job. A good first human reply:
- Uses their name and refers to what they asked about.
- Answers the main question, or says honestly when you need more information.
- Offers a specific next step, such as two time options or a booking link.
- Comes from a named person.
Avoid replies that only say “Please call us.” The person reached out in writing for a reason.
When you do not need all of this
If you get a handful of enquiries a week and you already reply within the hour, you do not need escalation rules or routing. An instant acknowledgment and one shared inbox may be enough. Build the system to match your volume, not the other way around.
It is also worth saying that speed does not fix everything. A fast reply with a vague answer still loses. A slow website, a confusing form or a hard-to-find phone number all happen before the first reply. Speed is one stage in the path, not the whole path.
Quick setup checklist
- Every form triggers an instant SMS and/or email acknowledgment.
- Missed calls trigger a text back.
- All channels land in one inbox.
- Each new enquiry creates an opportunity in “New enquiry.”
- Each enquiry has a named owner who is notified.
- An escalation check runs after 15 minutes during opening hours.
- After-hours messages say when you will reply.
- Follow-ups stop when the person replies or books.
- SMS consent and opt-out are handled.
To see how a form connects to an instant SMS and email in practice, read my form-to-follow-up workflow case study.
The short version
- Speed to lead is the time between an enquiry arriving and a real reply reaching that person.
- The HBR study found that contacting leads within an hour made qualification far more likely than waiting longer.
- For a small team, aim for an automatic acknowledgment within a minute and a human reply within 5 to 15 minutes during hours.
- One inbox, a named owner, and an escalation check do most of the work.
- Match the system to your volume. Small volume needs a small setup.
If you are not sure how fast you currently reply, try a simple test: submit your own website form and call your own number from a personal phone. Note how long it takes to hear back. If the answer surprises you, book a free 15-minute funnel check and I will walk through it with you. You can also get the Lead Leak Checklist to check the other stages yourself.