- Two hours is long enough for a prospect to contact two or three competitors and start a conversation with one of them
- Lead conversion rates drop significantly as response time increases — the research is consistent across industries
- The annual cost of slow response is calculable from your own enquiry volume and average job value
- Most businesses underestimate this cost because lost leads disappear silently, with no explanation
- The solution is a first-response system that operates independently of whether a person is available
Two hours does not sound like much. In most business contexts it is a reasonable window for a reply — a working morning, a busy afternoon. But in lead response terms, two hours is often the difference between winning a job and never knowing it existed.
This is not about being unusually slow. A two-hour response time is common, perhaps even typical, across many service businesses. It is the product of someone being on a job, in a meeting, at lunch, or simply not in the habit of checking messages frequently. It does not feel like negligence. The cost is real regardless.
What two hours means to a prospect
When a prospect sends an enquiry, they are in an active phase of decision-making. They have identified a need, searched for options, and taken the step of making contact. For the next ten to twenty minutes, this is the thing they are thinking about. Then something else claims their attention and the mental energy around this decision disperses.
Two hours later, if no one has responded, the prospect is doing something entirely different. The enquiry they sent feels like a background task. If a competitor responded within fifteen minutes and started an actual conversation, that prospect has mentally moved on. Your response, when it arrives, is not entering a decision. It is entering a conclusion.
For urgent enquiries — someone who needs a plumber tonight, a removal company this weekend, or a childminder by Monday — two hours is not a delay. It is a disqualification. The prospect has already found someone who was available and responsive.
What the conversion data shows
Research on lead response consistently shows the same pattern. The probability of successfully contacting and converting a lead is highest in the first five minutes after an enquiry arrives. It remains elevated through the first thirty minutes. By the time two hours have passed, conversion rates have dropped to a fraction of what they were in that initial window.
One widely cited study found that leads contacted within five minutes were nine times more likely to convert than those contacted after an hour. A two-hour delay performs worse than that still. These are aggregate numbers and the specifics vary by industry and enquiry type, but the direction is consistent: response time and conversion rate are directly linked, and the relationship is steep at the beginning.
The implication for a service business running on standard working-hours availability is significant. Every enquiry that arrives outside a narrow window of active monitoring faces a structural conversion disadvantage.
How to calculate your business's cost
The calculation is straightforward. Start with the number of enquiries your business receives in a typical month. Take your current conversion rate — the percentage that turn into paid jobs. Now estimate what proportion of enquiries arrive when you are not available to respond within thirty minutes. For many businesses, this is at least a third of total enquiry volume, once evenings, weekends, and busy working periods are accounted for.
Apply a conservative assumption: slow-response enquiries convert at half the rate of fast-response ones. That may be conservative. Multiply the lost conversions by your average job value. That is your monthly cost from response delay alone. Multiply by twelve for the annual figure.
A business receiving forty enquiries per month, converting thirty percent on fast responses and fifteen percent on slow ones, with a third of enquiries arriving when response is slow, and an average job value of £350, loses roughly £840 per month — over £10,000 per year — from response delay alone. The numbers will differ for every business. The principle is consistent.
Want to run the numbers for your business?
Book a free discovery call. We will work through your enquiry volume, response times, and job value to show you what faster response is likely worth.
Book a free discovery callThe compounding effect over a year
The annual figure is the honest one. A single month of slow response feels manageable. Twelve months of it, compounded across every enquiry that arrived in a gap window, represents a meaningful share of potential revenue that the business never received.
There is a secondary effect too. Jobs won from faster enquiry handling tend to convert to repeat business and referrals at the same rate as any other job. Every lost enquiry is not only a lost first job — it is a lost relationship. The customer who went to your faster competitor may have become a regular. That cascade is impossible to quantify, but it is real.
How to calculate how many leads you're losing to slow response covers the full calculation framework in more detail.
The fix is a system, not more effort
The solution to a two-hour response time is not asking people to check their phones more often. That approach is unreliable, unsustainable, and ineffective outside working hours. The solution is a first-response layer that operates independently — something that sends a relevant, specific reply within seconds of an enquiry arriving, whether it is 8am or 11pm.
At its simplest this is an automated acknowledgement. At a more capable level it is an AI-configured system that reads the enquiry, constructs a relevant reply, asks a qualifying question, and keeps the prospect engaged until a person picks up the conversation. EveryCatch Speed-to-Lead operates at that second level — responding in under 60 seconds, across every channel, at any hour.
The two-hour delay is not a discipline problem. It is a systems problem. It does not disappear by working harder at it. It disappears when a system takes it off the table entirely.