Lead Response Time: Set a Target From Your Own Data

There is a well known genre of statistic about response speed: contact within a certain number of minutes and your odds improve by some multiple. These figures circulate endlessly, usually without a source, frequently traced back to a single study conducted in one industry a long time ago, in a period when web forms were the dominant channel and messaging barely existed.

The underlying claim is almost certainly true in direction. Speed matters, and it matters most in competitive, high-intent situations where the buyer is contacting several providers in one session. What is not reliable is the specific multiplier, and building a target around a borrowed multiplier is how teams end up chasing a number that has no connection to their own business.

The number to put on a screen

Of those six, only one belongs on a live display: the count of enquiries with no contact attempt after a set interval. The others are review metrics, looked at weekly. A live count of untouched enquiries is actionable in the moment, and teams respond to it because it names a specific queue rather than describing past performance.

Ownership at capture

The single biggest cause of slow response is not laziness, it is ambiguity. An enquiry that arrives into a shared inbox belongs to everyone, which means it belongs to nobody until someone decides to take it. Assign an owner automatically at the moment of capture, by round robin, territory or availability, and the median drops without anyone working harder.

Escalation that fires without a human

Set an interval, perhaps thirty minutes in working hours, after which an untouched enquiry escalates to a second person. The point is not to catch anybody. It is that a rep in a meeting cannot respond, and without escalation the enquiry simply waits for them to finish. Escalation converts an individual constraint into a team one.

A first response that does work

Speed only pays if the reply advances the conversation. A useful first response confirms you understood the specific request, gives one piece of genuinely helpful information, and asks exactly one question. Templates help here as a starting point provided someone fills in the specifics, because a rapid generic reply signals a machine and invites the customer to keep shopping.

Pick a target you can hit on your worst day. As an illustrative example, if your median is currently around four hours and your busiest days run at eight, do not announce a fifteen minute target. Set one hour, hit it consistently for a month, then tighten. Targets that fail regularly do more damage than no target, because they teach everyone that the published number is aspirational rather than real.

Then defend it structurally rather than motivationally. Automatic ownership, automatic escalation, an acknowledgement that buys time out of hours, and a live untouched count. Every one of those keeps working when the person who cared about response times is on leave, which is exactly when the number normally collapses.

Run the same measurement monthly with the same definitions. Two events reliably degrade response time and both are invisible until measured: volume growth, which quietly pushes the queue past capacity, and a departure, which removes the person who was informally absorbing the overflow. Catching either within a month is straightforward. Catching it after a quarter usually means explaining a revenue dip that had nothing to do with demand.

Related reading: lead management software, WhatsApp CRM, the dialer, sales automation, features, and CRM for small business.