Contact response time

Contact response time is the average elapsed time between a contact getting in touch and the first meaningful human reply they receive. If a prospect submits a form at 9:00 and a sales rep replies at 9:42, that contact waited 42 minutes. Average those waits across every contact in a period and you have your contact response time.

The metric matters because the first reply sets the tone for the entire relationship. A fast reply tells a prospect they are dealing with a serious, attentive team. A slow reply, or none at all, pushes them towards whoever answers first. In competitive deals the first responder often wins by default, regardless of product strength.

Response time is also a leading indicator. It moves before pipeline, before win rate, and before churn. A queue that quietly slips from minutes to hours will not show up in revenue for weeks, but it is already costing conversions. Watching response time gives you a chance to intervene before the damage reaches the numbers everyone else watches.

Take each contact that received a first reply in the period. For each one, subtract the time they reached out from the time of the first human reply. Sum those gaps and divide by the number of contacts replied to. If three contacts waited 10, 20, and 30 minutes, the average contact response time is 60 / 3 = 20 minutes.

The averaging method matters as much as the formula. A simple mean is easily distorted by a handful of contacts who waited days. The median, or a percentile such as the 90th, often tells a truer story about the typical experience. Many teams report both the median and the 90th percentile so a few outliers cannot hide a slow tail.

Be deliberate about business hours. A contact who arrives at 6pm and gets a reply at 9am the next day waited fifteen hours on the clock but only a few minutes of working time. Decide whether to measure calendar time or business-hours time, document the choice, and apply it consistently so comparisons stay honest.

1. 1

   Inbound timestamp

   The moment each contact first reached out or was created in the CRM. This is the start of the clock.

2. 2

   First human reply timestamp

   The moment a person, not an automation, sent the first reply to that contact.

3. 3

   Contacts replied to

   The count of contacts that received a first reply during the period. Contacts still waiting are tracked separately as unanswered.

4. 4

   Business-hours rule

   A defined working calendar so out-of-hours waiting time is either excluded or clearly flagged.

Contact response time looks like a single number, but it is the sum of several distinct delays. A metric tree separates those delays so a slow average points to a specific cause rather than a vague sense that the team is behind.

Benchmarks vary sharply by channel and by intent. Inbound demo requests and live chat carry the highest expectations because the contact is actively waiting. Email and lower-intent enquiries tolerate longer waits. The ranges below are typical targets, not hard rules, so calibrate against the channels you actually run.

Improving response time is rarely about asking people to work faster. It is about removing the delays between a contact arriving and a person being able to act. Address routing, alerting, capacity, and coverage in turn.

1. 1

   Counting automated replies as responses

   Instant auto-acknowledgements make the average look excellent while real contacts still wait for a person. Always measure to the first human reply.

2. 2

   Reporting only the mean

   A single slow case of several days can drag the mean up or be lost inside it. Report the median and a high percentile alongside it so the slow tail cannot hide.

3. 3

   Ignoring business hours

   Mixing calendar time and working time makes teams across time zones look slow when they are not. Pick one rule, document it, and apply it everywhere.

4. 4

   Excluding contacts who never got a reply

   If the metric only averages contacts that were answered, a growing pile of ignored contacts stays invisible. Track unanswered contacts separately and never let them fall out of view.