Lead Follow-Up: The Response Delay That Loses Quotes

A small business owner who gets a quote request usually assumes they answer fast enough. The trouble is that "fast enough" rarely gets measured, while the prospect on the other end is almost always comparing more than one supplier at the same time. The first business to respond with something useful tends to keep the edge, regardless of how good the work is once it starts. Here is how I help a client measure their own response time from data they already have, before touching anything automated.

Why does a slow response lose quotes in the first place?

Because a prospect who fills out a form or calls a service business rarely reaches out to only one company. They often contact two or three suppliers the same day, then move forward with whoever answers first with something useful, not necessarily whoever quotes the lowest price. A callback two days later arrives after the prospect has already picked someone else, and the business never finds out it lost the job, since nothing distinguishes a lead lost to slow follow-up from a lead that was never serious to begin with.

How do you measure your own current response time?

By comparing, for every lead from the past few weeks, the time of the original request against the time of the first real contact from the business. The original request is the timestamp on the web form, the email, or the missed call. The first real contact is the moment someone called back, replied by email, or answered in the site's chat, not the moment the lead got added to a spreadsheet. Most CRMs and web forms already store both timestamps somewhere; the real work is pulling them side by side for a sample of roughly thirty requests.

Why does the median response time beat the average?

Because an average gets skewed by one or two outliers that do not reflect what usually happens. A request that comes in Friday night and gets handled Monday morning can add several hours to an average calculated over thirty requests, even if most prospects were contacted within twenty minutes. The median, meaning the number that sits exactly in the middle once every request is sorted from fastest to slowest, gives a more honest picture of what a typical prospect experiences.

What do you do if you do not have a CRM yet?

Pull the same two timestamps from whatever you already use, even if that is just a shared inbox and a call log. A business running on a Gmail inbox and a paper appointment book can still build the sample: the email's received time is the request, and a note of when someone called back or replied is the first contact. It is slower to assemble than exporting a report from a CRM, but the measurement itself does not require any new software, only the habit of writing down when a request came in and when someone answered it.

Should evenings and weekends count in the calculation?

Only if the business genuinely intends to respond during those hours, otherwise the number paints a misleading picture of the problem. A request that comes in Saturday at 10 p.m. and gets handled Monday morning is not necessarily a service failure if the business does not operate on weekends, as long as the prospect knows that upfront, for example through an automatic message that states when someone will get back to them. The more useful calculation splits requests received during business hours from requests received outside them, so a handful of Sunday-evening submissions do not artificially inflate the median response time of a business that answers very quickly during the week.

How do you tell whether the delay is costing you customers?

By comparing the conversion rate of requests against how long it took to respond to each one, not just looking at the delay on its own. Once the sample of requests is sorted by response time, add a column noting whether each prospect became a customer or not, then group the requests into a few buckets, for example under fifteen minutes, between fifteen minutes and two hours, and over two hours. If the conversion rate in the first bucket is clearly higher than the other two, response time explains a real share of the lost quotes, not just a general feeling the owner has. If the three buckets look similar, the problem is probably somewhere else, in the price or the quality of the proposal itself.

What response time should you aim for once you have the number?

A delay the business can sustain, set from its own median response time rather than a number picked at random. For a service business that receives requests during business hours, aiming for a reply within an hour of the request is a realistic target for most of the day, with a longer window accepted only outside business hours. No verified benchmark exists for this industry, so the useful target is one the team can hit almost every time, tracked against the gap between that target and reality.

Who should own the first response?

One clearly identified person at a time, with a named backup for absences, rather than a shared inbox where everyone assumes someone else will answer. In many small businesses, requests land in a general email address that three people supposedly monitor, which in practice means nobody feels responsible for answering within the hour. Naming one person responsible for the first response during each shift, with a designated backup for vacations or sick days, closes that kind of coverage gap without adding headcount.

What do you do once the target is set?

Make it visible and trackable for the person answering requests, not just for the owner. A target that only lives in the owner's head changes nothing about the daily behaviour of the front-desk person or the rep handling requests. I recommend clients post last week's median response time somewhere the team sees regularly, and review that number weekly rather than once a quarter, so drift gets caught before it turns into a habit.

How do you automate the first touch without losing the human side?

By clearly separating the automatic acknowledgment from the real, personalized follow-up. An automatic email or text sent within minutes of a request confirms to the prospect that it was received and gives them a sense of when to expect the next contact; that message never replaces the personalized call or email that follows, it just buys time while someone frees up to respond properly. My CRM and lead management work starts from that distinction: automate the instant acknowledgment of a request, then route it to the right person based on clear rules, without ever letting the prospect think a full answer has already been given.

What data should you keep to track progress over time?

The same pair of timestamps, request and first contact, for every lead, broken down by source if the business has more than one. A simple table with the date, the time of the request, the time of first contact, and the source is enough to calculate the median response time every week, without needing a complicated tool. That same data also helps spot whether one channel in particular, such as calls that come in after closing, consistently lags behind the others, which points to where an automation is worth adding first instead of changing everything at once.

Drafted with AI assistance, checked and published by Marven Salgado.