Leads · 7 min · 2026-11-07

How to respond to a contact request within minutes without being at your desk

A contact request loses value very quickly. What research says about response time, why the shared inbox fails and how to automate the first reply.

LeadsResponse timeFormsAutomationSales

Summary

What matters before moving forward.

  • A study published in Harvard Business Review in 2011 analysed how thousands of companies responded to online requests. The conclusion: replies in the first minutes qualify far more leads than replies hours later.
  • Most companies take hours or days to reply, because requests land in a shared inbox nobody feels is theirs.
  • The first reply can be automatic and useful: it confirms the request arrived, says when and who will reply and asks for missing information.
  • The team alert has to reach the person where they are, on their phone, with the request context, not only by email.
  • Measuring the time between request and first human reply is the simplest indicator of whether the process works.

What the research says

In 2011, Harvard Business Review published The Short Life of Online Sales Leads, by James Oldroyd, Kristina McElheran and David Elkington, auditing over 2,000 companies and analysing over a million contact requests.

The main conclusion is that a request's value drops very quickly. One of the authors summed it up in an interview: a website lead is most likely to convert if contacted within about five minutes, and is almost dead after about 30.

Exact figures vary by sector and should not be copied as a guarantee. The direction is unmistakable: every hour counts.

Why companies are slow

The form sends an email to a general address. Several people have access, each assumes someone else will reply, and the request sits among invoices and newsletters.

By the time someone replies, a day has passed. The customer has asked two other companies for a quote and chosen the first that replied with something useful.

The problem is not lack of will. It is the absence of an owner and an alert.

The first automatic reply

A generic automatic reply, along the lines of we received your message, does not help much. A useful automatic reply does three things.

It confirms what the customer asked, in their words, to show the request was read by the right system.

It says when they will get a reply and from whom, with a realistic deadline, for example by the end of the business day.

It asks for the information needed to reply well first time, or offers a link to book a call. Often the customer answers within that same minute.

The alert that reaches the right person

The request should go to a specific person, set by rule: by service type, area or shift. Without an owner there is no fast reply.

The alert should reach that person where they are, usually their phone, by notification, message or SMS, with the request summary and contact. Opening email on a computer to understand the request is already a delay.

If the person does not reply within a set time, the alert moves to someone else. That is how no request gets forgotten.

Measuring response time

Record the time of each request and the time of the first human reply. The difference, on average and in the worst case, is the indicator that matters.

Split by channel and by person. The problem is often concentrated in one request type or time of day.

How Vokzar automates the reply

We review your website forms, assign each request an owner by rule and set up the useful automatic reply to the customer.

We set up an instant alert on the right person's phone, with escalation if nobody replies, and store everything in the CRM or a shared sheet.

We leave response time tracking in place to follow week by week.

Related next steps

Next steps.

Proof and validation

  • The study cited is The Short Life of Online Sales Leads, Harvard Business Review, 2011, by Oldroyd, McElheran and Elkington.
  • The five and 30 minute figures come from James Oldroyd's interview with CBS News and are indicative.
  • The effect of response time varies by sector, service and customer type.

Official documentation

Validated sources.

Technical strategy should be auditable. These sources link directly to the official documentation behind this guide.

Frequently asked questions

Common questions about this topic.

How quickly should I reply to a contact request?

As quickly as possible. Research published in Harvard Business Review shows a request's value drops sharply in the first hours, and one author points to the first minutes as the ideal window.

Does an automatic reply count as a reply?

It counts as a first reply if it is useful: it confirms the request, says when and who will reply and asks for missing information. It does not replace a human reply.

How do I make sure someone replies?

Give each request an owner by rule, with a phone alert and escalation to someone else if there is no reply within a set time.

How do I measure improvement?

Record the request time and the first human reply time, and track the average and worst case each week.

Want to apply this to your site?

Next step Technical audit