Why lead response time decides who gets the job

A homeowner finds water coming through her kitchen ceiling on a Tuesday afternoon. She does what everyone does now. She searches, opens three tabs, and fills in three quote forms in about four minutes.

By the time the kettle boils, one of those three companies has rung her back. That company gets the job. The other two call at half five and at nine the next morning, and both hear the same sentence: thanks, we've already had someone out.

Price didn't decide that. Reviews didn't decide it. The quality of the work certainly didn't. It came down to who picked up first, and the whole contest was over inside an hour.

Most owners we speak to already suspect this is happening. What surprises them is how narrow the window is, and how much of it gets lost to things that have nothing to do with how hard anyone is working.

#What the research actually says about response time

The number worth knowing comes from a study of roughly 15,000 leads and 100,000 call attempts, written up in Harvard Business Review. Firms that made contact within five minutes were 21 times more likely to qualify the lead than firms that waited thirty minutes.

Not 21 percent. Twenty one times.

The same work found the odds of qualifying drop by around 400 percent when response time slips from five minutes to ten. That is the shape of the thing that matters. The curve is at its steepest right at the beginning, in the stretch most businesses treat as slack.

Now set that against what actually happens on a normal week. Industry analyses of contractor phone lines consistently put missed call rates somewhere between a third and two thirds of inbound volume, depending on trade and time of day. Whatever the exact figure is for your business, it is not small, and it is not evenly spread. It clusters at lunchtime, at school run, and after five.

That combination is the whole problem in one line. The window that decides the job is five minutes wide, and the hours when you are least able to answer are the hours when the most calls come in.

#Why five minutes is hard to hit with people alone

This is rarely a discipline problem. It is a structural one.

In most small operations, the people who answer the phone are the same people doing the billable work. A plumber under a sink cannot take a call. A dental receptionist checking a patient in cannot take a call. An agent showing a property has their phone on silent. Each of those is the correct decision in the moment, and each one costs you a job that you will never hear about.

Voicemail does not rescue it. Most people who reach a voicemail box for a service they were about to buy simply move to the next result. They are not being difficult. They have a wet ceiling and a list of three numbers.

Then there is the callback tax. A missed call does not just cost you the five minute window, it costs you a slot of someone's later time to chase it, at which point you are cold calling a person who has already solved their problem. That work feels productive. Mostly it is not.

The pattern holds for forms too. A web enquiry at 19:40 that gets a reply at 09:15 the next morning is technically answered within one working day. In the buyer's experience it is thirteen hours of silence, during which two competitors called.

#What has to happen inside those five minutes

Speed on its own is not the point. Ringing back in ninety seconds and saying "can I take your details and get someone to call you" is faster failure, not success. The first contact has to actually move the job forward.

In practice that means five things happening in one conversation, in this order.

Pick up. On the first or second ring, at any hour, including when three people call at once. Concurrency matters more than most owners expect. Enquiries do not arrive politely spaced.

Identify what they actually want. A boiler that will not fire, a quote for a bathroom, and a chase on an existing job are three different conversations. Routing them correctly at the start saves the whole call.

Qualify against your own criteria. Postcode, property type, urgency, budget range, whether they own the place. These are your rules, not generic ones, and they are what stop your engineers driving to jobs that were never going to convert.

Take the action. Book the slot, issue the quote, or route to the person who can. If the conversation ends with a promise to call back, you have moved the five minute window rather than closed it.

Write the record. Structured, in the CRM, with the transcript attached. A booking that lives only in someone's head is a no-show waiting to happen.

That is the whole job of a front office, and it is why we build voice and chat agents alongside the CRM underneath them rather than selling the agent on its own. An agent that books appointments but writes nothing usable is a toy.

#Where responding faster makes things worse

Two situations, and both are worth being honest about.

The first is when your capacity is already the bottleneck. If you are booked out for three weeks and turning work away, answering every call in forty seconds mostly gets you more people to disappoint. Fix the scheduling first. Speed is a tool for winning contested work, not for creating demand you cannot serve.

The second is when the first contact cannot make a decision. A fast, cheerful, entirely useless call is worse than a voicemail, because it burns the goodwill you would otherwise have had on the callback. If an agent cannot access your diary, cannot see your pricing, and cannot escalate to a human on the ones that need it, do not put it in front of customers yet. Get the boundaries right, then go fast.

There is a narrower case too. Some enquiries genuinely deserve a considered reply rather than an immediate one. A commercial tender or a complex legal intake isn't improved by a forty second response. Speed is about the first touch. It's not an argument for rushing the work.

#What to measure before you change anything

Four numbers. None of them need new software to find.

Missed call rate by hour of day. Your phone provider has this. Look at the shape rather than the total, because the shape tells you whether the answer is coverage, staffing, or routing.

Median time to first contact. Median, not average. One reply at three days will drag an average somewhere useless. Take the enquiry timestamp and the first outbound contact for the same person, and split the result by weekday.

Callback success rate. Of the calls you return, how many actually connect and convert. This is usually the number that changes minds, because it is much lower than people assume.

Share of enquiries arriving outside working hours. For most phone-first businesses this sits between a quarter and a half. If yours is at the top of that range, coverage is your single biggest lever and no amount of daytime discipline will touch it.

Run those for two weeks and you'll know whether you have a speed problem, a capture problem, or a capacity problem. They need different fixes, and it's worth knowing which one you have before spending anything.

One caution on the data. Phone systems and web forms usually disagree about what counts as a contact, so pick one definition and hold it for the whole two weeks. We normally count the first moment a human or an agent spoke to the person, not the moment an automated acknowledgement went out. An email that says "we have received your enquiry" is not a response. It's a receipt, and the buyer reads it that way.

#Start with one number

Pick the hour of the week where you miss the most calls. Just one. Work out roughly what an average job is worth to you, multiply by a conservative conversion rate, and you have the annual cost of that single hour.

Most owners find the answer uncomfortable. It's also among the easiest things in the business to fix, because it's a coverage problem, and coverage is exactly what an agent is for. Nobody has to work later, and nothing about the way you run jobs has to change.

If you want a second pair of eyes on those numbers, tell us where the leaks are and we will map what is worth automating first. Thirty minutes, no deck, and you keep the analysis either way.