Skip to content
automation

Speed to lead: what slow replies cost a business, and how to fix it

Speed to lead is the time from inquiry to first useful reply. How to measure it on every channel, what slow replies cost, and how to fix the causes.

A buyer fills in your contact form at 10:40 on a Tuesday. They fill in two other firms' forms too. The first firm to reply with something useful gets the first real conversation.

Speed to lead is the time between a new inquiry arriving and your first useful reply. In an established company, no single person sets that time. It depends on which inbox the lead lands in, who owns it, and whether the answer needs facts from another team.

This guide covers how to measure speed to lead on every channel, what slow replies cost, and how to fix the causes. Our free lost-revenue calculator puts a monthly figure on it. Fixing it is a common first project in business process automation.

What is speed to lead?

Speed to lead is a clock with two ends.

  • It starts when the inquiry reaches you: the form is submitted, the email arrives, the phone rings, the chat opens.
  • It stops at the first reply that moves the conversation forward: an answer to the question, a booked call, or the one or two questions you need answered to quote.

An automatic "we got your message" email does not stop the clock. It is worth sending, but track it apart from the real reply.

Measure it per lead, on every channel, and keep the leads that never got a reply in the count. A lead with no reply is the slowest reply of all, and it is the easiest one to leave out of a report.

What do slow replies cost?

The direct cost is lost deals. The math has four parts:

  1. New leads a month,
  2. times the share you lose because the reply came too late,
  3. times your close rate,
  4. times your average deal value.

That gives a monthly figure. The lost-revenue calculator runs it for you, with a rule-of-thumb loss for each reply speed that you can change if you know your own numbers. Its percentages are Raileon's working estimates, not industry statistics, and the result is an estimate, not a measurement.

There are quieter costs too.

  • Paid leads go cold. If you pay for clicks or listings, a lead that waits a day was bought at full price and used at a discount.
  • Sales time goes to chasing. A rep who reaches a buyer after they chose someone else spends the same effort for nothing.
  • The pipeline report is wrong. Leads nobody answered still sit in the CRM as open, so the forecast counts deals that are already gone.

Many articles quote a five-minute rule and large multipliers for fast replies. Those figures come from private studies, some more than a decade old, and we found no public government data on reply times to check them against. Treat them as direction. Your own numbers are the ones to act on.

How do you measure speed to lead?

Use a recent stretch of real leads, not a guess. Ninety days is enough for most firms.

  1. List every channel. Web forms, the main inbox, personal inboxes, phone lines, chat, texts, partner referrals and listings.
  2. Record two times per lead: when it arrived and when the first useful reply went out.
  3. Keep the unanswered leads. Mark them as never answered instead of dropping them.
  4. Use the median, not the average. A few very slow replies pull the average away from what a typical buyer sees. Also track the share answered within your target and the share never answered.
  5. Split the results by channel, by team and by hour. Business hours, evenings and weekends usually look very different.
Channel Where the clock starts Common gap
Web form The submission time saved with the form The form goes to an inbox nobody owns
Shared inbox The email's arrival time Everyone assumes someone else replied
Phone The call log Missed calls with no callback owner
Chat or text The first message Messages after hours wait until morning
Referral or partner The email to one person It sits in that inbox and never reaches the CRM

The rows are a starting point. Your own channels and gaps come from the list in step 1.

Why are established companies slow to reply?

Rarely because people do not care. Usually because of how the work is set up.

  • No single owner. A lead lands in a shared inbox, and each person assumes someone else has it.
  • Routing by hand. Someone has to read the lead, decide the region or product, and forward it. That person is in a meeting.
  • The answer sits with another team. Pricing, stock, scheduling or a technical detail lives outside sales.
  • The CRM comes first. The rep types the lead into the CRM before replying, so the reply waits for the typing. Our CRM automation page shows how leads can be logged with their source as they arrive.
  • Nights and weekends. Leads arrive when the office is closed, and Monday starts with a backlog.
  • Missed calls. A caller who reaches voicemail may not leave a message, and a missed call with no message is easy to never return.

What is missed call text back?

Missed call text back is an automatic text sent to a caller whose call was not answered. It tells them the call was seen and what happens next.

A good one does four things:

  • Names your business, so the caller knows who is texting.
  • Says who will call back and roughly when, and the team keeps that promise.
  • Offers a way forward without waiting, such as a link to book a time or a reply by text.
  • Creates a callback task in the CRM for a named person, with the caller's number and the time of the call.

It buys time; it does not replace the callback. It also does not fit every call. An existing client with an urgent service problem should reach a person or the service line, not a sales message. Some numbers cannot receive texts, so the callback task matters as much as the text. Phone carriers also have their own registration steps for business texting from a regular number; start them before you plan to go live.

What rules apply to fast texts and emails?

Speed does not change the rules. Two federal ones matter most for lead follow-up, and your counsel should confirm how they apply to you.

  • Texts. The FCC's rule on automated calls and texts, 47 CFR 64.1200, sets when consent is needed and how it ends. A person can revoke consent by any reasonable method, and a reply of "stop", "quit", "end", "revoke", "opt out", "cancel" or "unsubscribe" counts. Requests must be honored within a reasonable time, not more than ten business days.
  • Emails. The FTC's CAN-SPAM compliance guide says you must honor an opt-out within 10 business days, and the law makes no exception for business-to-business email. Whether a message counts as commercial depends on its content, and the FTC says the law views those categories narrowly.
  • Outside senders. The same guide says you can't contract away your legal responsibility. A tool or outside firm that sends for you does not take the duty with it.

Build the stop list into the system, so an opt-out on one channel stops the follow-ups it should.

How do you speed up replies without losing quality?

A fast reply that says nothing loses to a slower one that helps. The fix is mostly structure.

  1. Give every lead an owner the moment it arrives, by rule: region, product, size or a rotation.
  2. Log it automatically with its source, so nobody types before they reply.
  3. Draft the first reply from the inquiry itself. Answer what they asked, ask the one or two questions you need, and offer a time to talk.
  4. Keep a person on the send button at first. Fixed messages, such as an after-hours note, can be approved once.
  5. Set the follow-up schedule, and stop it the moment the lead replies.
  6. Plan nights and weekends. Decide what an after-hours lead gets and when a person picks it up.
  7. Report reply times every week, by channel and team, next to the pipeline.

Our guide on how to automate business processes covers mapping these steps before anything is built.

How Raileon builds lead follow-up

Raileon designs, builds and runs custom systems inside the tools a business already uses. For speed to lead, that means every lead logged with its source, the first reply drafted the moment a lead arrives, follow-ups on the schedule you set that stop when the lead replies, and a weekly view of reply times. Missed calls can be part of the same build: logged in the CRM, with a named owner for each callback.

By default, anything a customer will see waits for your approval, and every action is recorded. Once you trust a message, you can choose to let it go out on its own.

It starts with a free 20-minute call with the founder, then a written proposal: what we build, what needs your approval and the price. Builds are priced by scope after that free discovery. Monthly care (hosting, monitoring, fixes and updates) starts from $1,999 a month. More on our business process automation work.

FAQ

What is speed to lead?

It is the time between a new inquiry arriving and the first useful reply from your business. Measure it per lead, on every channel, and count the leads that never got a reply.

What is a good speed to lead?

There is no official benchmark. Measure your own median first, then set a target for business hours and a clear promise for nights and weekends. The target that matters is beating the other firms the buyer contacted.

What is missed call text back?

It is an automatic text sent to a caller whose call was not answered. It says who will call back and when, and it creates a callback task. It buys time; it does not replace the callback.

Does an automatic reply count as a reply?

Track it, but separately. An acknowledgment tells the buyer you got the message. The clock that matters stops at the first reply that answers their question or books the next step.

Find out how fast you really reply

Pick one channel, pull last month's leads and find the median reply time. On a free 20-minute call, we'll look at where your leads arrive, who answers them and what would make the first reply faster.

Book a free 20-minute call

About the author

Konstantin, Founder & CEO of Raileon

Konstantin

Founder & CEO, Raileon

Konstantin has spent more than 15 years in systems, processes, automation and development. He has built businesses from scratch, from early crypto to tech ventures that led to acquisitions, and founded Raileon to build the software and automation he wished he'd had.

  • 15+ years in IT, automation and development
  • Founder & CEO of Raileon
  • Based in North Miami, Florida

Let's put your operations on rails

Book a 20-minute call with our team in Miami, Florida, and we'll show you exactly what Raileon would automate for your business.

Book a 20-minute call

No commitment. No credit card. Just a conversation.