Why does lead response time matter?
The longer a new enquiry waits, the less likely it becomes a conversation. A widely cited Harvard Business Review study of online sales leads found that most companies replied slowly, and that the few that replied within an hour were far more likely to reach a decision maker.
The study is "The Short Life of Online Sales Leads" (HBR, March 2011). It audited 2,241 US companies, and the figures below are from published summaries of it, because we could not open the full article text. Only 37% of companies responded within an hour, and the average response time among those that replied within 30 days was 42 hours. Firms that contacted a lead within an hour were nearly seven times as likely to qualify it as firms that contacted later. The work covers B2B web leads from 2011, so treat the multiples as direction, not a forecast for your business. Read the original HBR article for the exact wording.
The practical point survives the caveats. A person who submits a form or calls a business usually contacts more than one. The first reply that sounds helpful has an advantage.
What should you automate to answer leads faster?
Automate the acknowledgement, not the relationship. An instant, specific first reply, missed-call text-back, and after-hours coverage by an AI agent close most of the gap, and a person takes over as soon as the lead engages.
| Gap | What to build | Tool |
|---|---|---|
| Form fills wait for a callback | Instant text and email with a booking link, sent the moment the form is submitted | GoHighLevel workflow |
| Calls go unanswered | Missed-call text-back that starts a conversation | HighLevel Missed Call Text Back |
| Nobody is online after hours | An AI chat or voice agent that answers basic questions and books a callback | AI chat agent, AI calling agent |
| Leads arrive from many places | One pipeline for ads, forms, calls and messages, deduplicated by phone and email | GoHighLevel, plus n8n for outside sources |
| Urgent leads look like the rest | Keyword or rule-based alert to a named person | Workflow if/else branches |
HighLevel's Missed Call Text Back documentation lists conditions worth knowing at the time of writing. It is part of HighLevel's own phone system, at least one number must be SMS-eligible (A2P 10DLC registration for local numbers, or toll-free verification), and it triggers on every missed call, including repeat attempts from the same caller. Test what a person sees after calling three times in a row.
What does a good first reply look like?
It names what the person asked about, says what happens next and when, and offers one clear action, such as a booking link. It is short, and it reads like a person wrote it.
- Use their words. Pull the service or question from the form into the first line.
- Say when a person will follow up. Give a real time window, and keep it.
- Offer one action. A calendar link beats three options.
- Stop when they reply. The sequence ends as soon as the person engages or books, so nobody gets a canned message after talking to your team.
- Escalate the urgent ones. Words like "urgent", "today" or a stated deadline should alert a person, not wait in a queue.
Our published dental build reports first response falling from 45 to 90 minutes to under 5 minutes, as reported by Autoesta. Results vary by business. See the dental case study for the setup.
What are the rules for automated texts and calls?
Automated marketing texts generally need prior consent under the FCC's TCPA rules, and the FCC has confirmed the rules apply to AI-generated voices. Business texting in the US also requires a registered number. Ask counsel to review your consent wording.
Give every message a clear opt-out and honor it at once. For health-related businesses, HIPAA adds rules on message content, covered in our guide to HIPAA and automation tools. Our GoHighLevel AI agents guide covers the AI-voice side. This is not legal advice.
When is faster response not the fix?
When the leads are poor, when nobody can handle the extra conversations, or when your offer does not match what people are searching for. Speed only helps if there is a good lead and a person ready to continue.
- Low volume. With a handful of enquiries a week, a phone alert to one person may be enough.
- Complex, high-trust sales. A fast text helps, but the relationship still needs a person who knows the topic.
- No follow-through capacity. Faster replies create more conversations. If no one can carry them, response time is not your bottleneck.
- Broken follow-up. If the first reply works but leads still drop, see why follow-up sequences stop converting.
How do you measure whether it worked?
Track time to first reply, the share of leads that get a reply within your target, and the booking rate by reply-time band. Compare the same measures before and after the build, over the same length of time.
| Measure | How to get it | What it tells you |
|---|---|---|
| Time to first reply | Timestamp of form or call versus first outbound message, by source | Whether the automation is actually firing |
| Share replied within target | Count of leads inside your target window divided by all leads | How many still slip through, and from which source |
| Booking rate by reply band | Booked appointments grouped by how fast the first reply went out | Whether speed matters in your market, on your own data |
| Escalation handling | Time from urgent-lead alert to a person's reply | Whether the human part keeps up |
Do not read a single week as proof. Lead quality changes with ad spend and season, so compare like periods and keep a note of anything else you changed. If a source produces poor leads, faster replies will not rescue it, and the data will show that too. Our case studies describe how we reported results on published builds.
How do you get started?
Measure your current first-response time for a week, then build the instant reply and missed-call text-back first. Add an AI agent for after-hours coverage once the basics are stable.
- Record how long each enquiry waits for a first reply, by source.
- Consolidate sources into one pipeline in GoHighLevel.
- Build the instant reply, the escalation rule and the stop condition.
- Register your numbers and confirm consent wording.
- Test end to end with a real submission, a missed call and a STOP reply.
- Remeasure after two weeks and compare.
Pricing for builds like this is on our pricing page, and the strategy call is free.
More questions about lead response
How fast should you reply to a new lead?
As fast as you can do well. The HBR study points to within an hour as the difference-maker for B2B leads, and many businesses aim for minutes. Measure your own conversion by response time, because your market may differ.
Can an AI agent reply instead of a person?
For the first reply and basic questions, yes. It should book a callback or hand over as soon as the lead needs judgment. See our comparison of AI calling and chat agents.
Does missed-call text-back work without HighLevel?
Other tools offer similar features, but we describe only HighLevel's documented behavior. Check the same conditions in any tool you consider.
What does it cost?
Autoesta's typical builds start from about $1,000 for two or three automations, at the time of writing. See the pricing guide for ranges and what changes them.