Speed to lead: how fast a small business should answer an enquiry, and how to make it automatic

Speed to lead is the time between a potential customer contacting you and your business responding to them, first with an acknowledgement and then with a real answer. For a small business the practical target is two-part: an automatic confirmation within a minute, so the person knows the message arrived and what happens next, and a personal reply within a time you state openly and keep, such as the same day or one business day.

Faster is better, and the research everyone quotes points the same way. Before you build a rule on it, look at what that research measured, because many "respond in five minutes or lose the lead" articles are built on one study from 2007.

What do the speed to lead studies say?

The numbers you see most often come from the Lead Response Management Study, presented in October 2007 by Dave Elkington, then CEO of InsideSales.com, and James Oldroyd, a professor at MIT's Sloan School at the time. According to the study summary, it looked at three years of data from six companies, more than fifteen thousand web leads and more than one hundred thousand call attempts, all taken from the InsideSales.com calling system. It reported that the odds of contacting a lead were 100 times lower if called after 30 minutes instead of 5, and the odds of qualifying the lead 21 times lower. It also found that after 20 hours, extra dial attempts did more harm than good.

Three things about this study matter before you build a business rule on it:

• It is about phone calls to web leads. It does not tell you how fast to answer an email or a chat message.
• It is vendor data. The data came from a company that sold calling software, analysed with an academic. That does not make it wrong, but it is not an independent peer-reviewed paper.
• It is old. People's habits around forms, phones and messaging have changed a lot since 2007.

A separate and also widely quoted article, "The Short Life of Online Sales Leads" by Oldroyd, McElheran and Elkington in the Harvard Business Review (March 2011), audited how quickly companies responded to web leads. Its public summary says that "most companies are not responding nearly fast enough". The detailed figures are behind HBR's paywall, so I am not repeating them here.

My reading: the direction is clear and matches common sense, a person who just filled in your form is thinking about your offer now and about something else in an hour. The exact multipliers are not a law of nature, and you do not need them to make a decision.

How fast should a small business respond?

Split the response into two steps, because they have different jobs.

Step 1: the automatic confirmation, within a minute. Its job is not to sell. Its job is to tell the person that the message arrived, what happens next and when. A good confirmation repeats what they asked about, says who will reply and by when, and gives one useful thing in the meantime (prices, a short guide, an answer to the most common question). It should say plainly that it is an automatic message.

Step 2: the personal reply, within a time you can keep every single week. For a business of 10 to 100 people that is often "the same business day" or "within one business day". A promise of five minutes that you keep on Tuesday and break on Friday does more damage than an honest "by tomorrow" that you always keep.

Missed phone calls deserve their own rule. A call that nobody answered is an enquiry too, and a text message back saying who you are and when you will call is the phone version of step 1.

Why speed alone can backfire

A faster first response can move the bottleneck to sales. If enquiries arrive faster than the team can handle them, they still wait, just one step further along. Before increasing intake, check sales capacity, delivery and the administrative work that follows.

<!-- REMOVABLE BLOCK START: past-company story. Needs Lidia's yes (see story_source in front matter). If not confirmed, delete everything down to REMOVABLE BLOCK END; the section reads correctly without it. --> I saw this in the B2B services company I used to run. We built a lead generation system that brought in more enquiries, faster, with part of the first contact automated, and then the sales team stopped keeping up: enquiries waited for a salesperson instead of waiting for the form. What helped was not more speed at the front. We slowed the intake down, automated part of the salespeople's routine, and then went down the chain the same way: delivery, accounting, quality control. <!-- REMOVABLE BLOCK END -->

How to make the first response automatic

You do not need an AI system for most of this. A typical setup:

1. One entry point per channel, all going to one place. Website form, email and messenger enquiries land in your customer database (CRM), with the source recorded so you know where they came from.
2. An automatic confirmation sent the moment the enquiry is saved, written by you, marked as automatic, with the reply time you can keep.
3. A task for a named person, with the deadline matching what the confirmation promised.
4. A missed call text back, if phone enquiries matter in your business.
5. A reminder or escalation when the task is still open close to the deadline.
6. A weekly look at the numbers: how long enquiries waited for a personal reply, and how many got none.

Where AI helps is in drafting replies to common questions so the person answering spends less time typing; the person still reads and sends it. There is more on that in AI email replies for customer service, and on when an assistant should talk to customers at all in AI agents for small businesses. Before connecting any of this, it helps to set up the customer database properly; the CRM setup checklist covers that, and the rest of the series is under enquiries, CRM and customer support.

For the next steps after the first reply, see lead follow-up automation. For our planned implementation, see how this site is being set up to handle enquiries.

From our own system: how I am setting up enquiries on this site

This is the setup I am building for elivance.eu, described as a plan, not as results:

• Every enquiry from the form or the site assistant is saved first, before anything else happens, so a failure in one tool does not lose it.
• The visitor gets an instant confirmation, and I reply personally within one business day.
• The enquiry goes into our customer database with its source, I get a task, and a notification reaches me without the person's name or email in it.
• If one of those steps fails, it is retried and I get an alert instead of the enquiry silently disappearing.

This is the intended workflow. It must pass an end-to-end test with TEST records before launch; I am not presenting it as a working system or a measured result.

Speed to lead checklist

• Do you know your current average time to a personal reply, measured rather than guessed?
• Does every channel end up in one place?
• Does the confirmation say who replies and by when?
• Is there a named person for every enquiry, with a deadline?
• Do missed calls get a response?
• Can your team handle more enquiries if the response gets faster?

Want this set up for your business?

The lead system covers exactly this: enquiries into your customer database with an automatic acknowledgement and a task for your team, missed call text back and agreed follow-ups. If you want to talk it through first, the call is free.

Sources

• Lead Response Management Study (InsideSales.com and James Oldroyd, MIT Sloan), summary presented 16 October 2007, PDF copy hosted by Mortech, accessed 18 October 2026.
• Oldroyd, McElheran, Elkington, "The Short Life of Online Sales Leads", Harvard Business Review, March 2011, hbr.org, public summary accessed 18 October 2026.