The lead-response bottleneck: how fast to answer a new lead
Answer a new lead while they are still deciding: a reply window you can keep every time, such as within the working hour it arrives. A rushed reply can promise a price or date nobody scoped, so write a reply policy by lead type, let a system draft from your rules, and have a person approve each reply.
A new lead fills in the form on your site while you're on a client call. You see it hours later, write a careful reply in the evening, and send it. Some of those leads write back. Others have already booked a call with whoever answered first, and nothing in your CRM tells you which ones.
Why a slow reply loses the lead
This is a delay problem. A lead keeps deciding while your reply is on its way, and the decision doesn't pause for your calendar. If you're slow to respond, they look at others in the market, and the first useful answer they get becomes the one every later reply is measured against. So a slow reply hands the decision to whoever answers first.
Rushing fails in the other direction. A reply written between meetings to beat the clock can promise a price or a start date before anyone has scoped the work, and a number in writing is hard to walk back. A rushed reply can start the relationship on the wrong foot. Both failures come from the same place: the only person who can write a good reply is the person with the fullest calendar.
What slow replies cost you
The cost is the work you would have won from leads that chose someone else while your reply was waiting. It never shows up on a report, because a lead that leaves before you answer leaves no record of leaving. The rushed reply has a cost too: a scope promised too early, followed by a discount or an awkward walk-back.
How big that is depends on your own leads and what a signed client is worth to you. The calculator works it out from your numbers, so the estimate is yours and borrows nothing from someone else's study.
What the system looks like
I'd build it so the slow part stops being the writing. A lead arrives by form or email, and a screen stops junk before anything else runs. A reply is drafted from rules you wrote: what you take on, what you turn down, and what never goes in a first reply. The draft reaches a phone, a person approves or edits it, and the reply goes out logged against the lead.
I built a lead-to-reply system and ran one test lead through it, which went from form to scored and drafted in 5.35 seconds. That's the drafting time. What's left of the wait is the approval, and that's where I want the wait to be, because a person should read what goes out under your name.
- Lead arrives by form or email
- Screen: junk stops here
- Reply drafted from your own rules
- A person approves or edits itHUMAN
- Reply sent and logged with the lead
The rules start as a reply policy you can write on one page. This is the shape I'd give it, with each kind of lead answered by a different route.
| Lead type | Who answers | What the first reply must do | What waits for a person |
|---|---|---|---|
| A new lead that fits what you do | A drafted reply, approved by a person | Thank them, answer what they asked, and offer a time to talk | Price, scope and start date |
| A new lead with a vague ask | A drafted reply, approved by a person | Ask the questions you'd need answered before a call | Whether it's worth a call at all |
| A lead outside what you do | A drafted decline, approved by a person | Say no kindly, and point them somewhere useful if you can | Any exception you want to make |
| An existing client asking for more | You or the account lead | Confirm you've seen it and say when they'll hear back | Everything about scope and price |
| Junk, spam and sales pitches | Nobody | Nothing, because the screen drops it before a draft is written | Nothing |
What stays with you
The system takes the writing off the clock, and you keep the judgment. A person approves every reply before it's sent, and can change any line first.
- Price and scope. Your rules can say a draft never names a price, and you add one yourself once the work is scoped.
- Which leads are worth a call. The screen drops junk, and a borderline lead reaches you with its draft so you make that call.
- Tone. You edit a draft the way you'd edit a colleague's email, and when you keep making the same edit, it belongs in the rules.
- Exceptions. A former client, a referral from a friend or a lead you want to say yes to against your own rules is yours to handle.
Questions
Is an auto-responder good enough for new leads?
An auto-responder tells the lead you got their message, which beats silence. It doesn't answer their question, so they keep looking. An approved draft answers what they asked, in your words, inside the window you set.
Can I reply to a lead too fast?
Only if the speed puts a price, a scope or a start date in writing before you've scoped the work. Keep those out of the first reply and answer what the lead asked, and a fast answer carries no extra risk.
What about leads that come in during evenings and weekends?
Set your window for working hours and say so in the first reply, which is honest and better than silence. If you want to answer sooner, a drafted reply takes a moment to approve, and you choose which leads are worth it.
Should AI answer my leads without me?
I wouldn't let it. A draft written from your rules saves the writing time, and a person approving it keeps price, scope and tone in check. A system that sends on its own can promise something you then have to walk back.
How do I find out how fast my firm replies now?
Take last month's leads from your CRM or email, and for each one note when it arrived and when the first reply went out. The gaps, and the leads that never got a reply, are your current policy, whether anyone wrote it down or not.
Who on my team should answer new leads?
Whoever can stand behind what the reply says. In a small firm that's often the owner, which is why replies wait. A drafted reply lets the owner stay the approver without also being the writer.
Related
- A drafted reply to each lead, approved from my phone before it sendsAI drafts replies to lead emails that pass a junk screen, from my business facts. Risky asks get flagged, and nothing sends until I approve it on my phone.
- Website form leads, scored and answered with a reply I approveA system I built: each website form lead is checked, added to HubSpot once and scored. Gmail sends the drafted reply when I approve it in Telegram.
- Speed to leadSpeed to lead is the time between a lead reaching you and a real reply going back. Why it matters, an example, and how a system shortens it.
- What do slow replies to leads cost you?Multiply your leads, the value of a won client, your close rate and your own estimate of leads lost to slow replies to see the revenue at risk.
- The follow-up bottleneck: why follow-ups fall through the cracksFollow-ups slip when the next step lives in someone's head. They hold when every open lead carries a next step, a date and a drafted nudge a person approves.
- The four places a lead diesLeads drain out of a pipeline in four places: never recorded, never answered, never followed up and never closed out. How to count each one this week.
- How do I approve email replies from Slack before they go out?Approving email replies from Slack, Telegram or Google Chat: what the built-in apps do, where an approval loop breaks, the send-once rule, and what I'd pick.