Lead response time: why the first five minutes decide the job

What is happening on the customer's side

Picture the customer at 7.40pm with a phone. They have searched, opened three websites, and filled in three forms or rung three numbers. Now they are waiting, and they are still in the mood to decide.

The first firm to respond gets to have the conversation while that mood lasts. They confirm the area, suggest a time, give a rough price. By the time firm two replies the next morning, the customer has mentally hired firm one and firm two's message is an interruption. Firm three's reply, two days later, lands in a problem that no longer exists.

The job did not go to the best tradesperson or the cheapest. It went to the one who was there.

Why five minutes rather than an hour

Sales research across industries has for years pointed the same way: the odds of reaching and qualifying a lead fall sharply after the first few minutes and collapse after an hour. We will not pretend there is a trades-specific study with a clean number, and the exact curve depends on the trade.

What we can say from running lead systems is that there is a difference in kind, not just degree, between replying while the customer is still looking at their phone and replying after they have put it down. Five minutes is a reasonable proxy for 'still looking'. An hour is 'put it down'. Next morning is 'moved on'.

Emergency trades sit at the sharp end. A locksmith or drainage engineer who replies in 20 minutes has lost the job to one who replied in two. Project trades have more slack, but even for a £15,000 extension the first builder to respond sets the tone and the benchmark.

Measure yours before you fix it

Most tradespeople guess they respond 'pretty quickly'. Measure it for two weeks. For every enquiry, record the time it arrived and the time the customer first heard back from you by any channel. Then look at the median and the worst 20 per cent.

A typical result for a busy sole trader, as a worked example: web forms answered at a median of four hours, with the worst fifth answered the next day or never. Missed calls returned at a median of 90 minutes. Texts answered within 20 minutes, because texts are easy to glance at.

That pattern tells you where to act. The web form and the missed call are where the time goes, and both can be fixed by automation rather than by you working harder.

Fix 1: Acknowledge automatically, in seconds

You cannot personally reply in five minutes from under a floor. A system can. The moment a form is submitted or a call is missed, the customer gets a text: who you are, that you have the enquiry, roughly when you will call, and a question that keeps them engaged, such as asking for a postcode or a photo.

This does not close the job. It stops the clock. The customer who has had an acknowledgement is far less likely to keep ringing down the list, because they now have a conversation open with someone.

The missed call version of this is covered in detail in our missed call text back setup guide. The web form version is the same logic with a different trigger.

Fix 2: Route the notification to where you will see it

Web form enquiries that arrive as emails are the slowest, because email is checked in the evening. Route them as a text or an app notification to your phone as well. If you have a second person, route them to both and make it clear who owns the reply.

A notification that arrives in a channel you look at every 15 minutes converts a four-hour median into a 15-minute one without any other change.

Fix 3: Make the first human reply a text, not a call

When you surface from the job and see three enquiries, a quick text to each takes two minutes. Three calls take 20 and two of them go to voicemail. Text first: 'Hi Jo, Dan from DJ Plumbing. Got your message about the leak under the sink. I can be with you tomorrow at 9 or Thursday at 2, which suits?' Then call the ones who need a conversation.

This matters because response time is measured by the customer from when they hear back, not from when you decided to reply.

Fix 4: Let an AI take the call when you cannot

For firms taking a dozen or more calls a day, a missed call text back is a plaster. An AI receptionist answers, takes the details, checks your availability and books a slot, and the customer never experiences a missed call at all. LeadFly publishes a fixed monthly price for this; We Build Trades bundles AI follow-up into its platform. We compare the options in AI receptionists for trades.

The trade-off is that some customers dislike talking to a machine, so the handoff to a human has to be smooth and the AI has to be honest about what it is.

Fix 5: Give the system a status so nothing is dropped

Fast first response is wasted if the second response never comes. Every enquiry needs a status, and a status of 'new' that has not changed in an hour should nag you. That is the job of even the smallest CRM, described in a CRM for a one-van business.

It is also how you keep measuring. A CRM that timestamps enquiry arrival and first contact gives you the response-time report for free, every month, without the two-week spreadsheet exercise.

What this means for how you spend

A trade business considering spending £500 more a month on ads to get more enquiries should first ask what happens to the enquiries it already has after 6pm. In the worked example above, cutting response time from four hours to five minutes on web forms would plausibly recover more jobs than a 30 per cent increase in enquiry volume, at a fraction of the cost.

It is also why we judge agencies partly on whether their systems include the response layer. Lead Wave, for instance, builds an automatic text to every enquiry within seconds into its Facebook ads offer; Get Work texts the tradesperson about each new lead. The agencies in our marketing systems for trades ranking are assessed on whether they connect generation to response, because one without the other is half a system.

Fast response is not a marketing channel. It is the thing that decides whether the channels you pay for produce anything.

Frequently asked questions