Speed-to-lead is the time between a lead arriving in your system and the first call attempt leaving for that lead. Vocapable reports it as lead-to-call time, one of the named metrics the product computes off its own call ledgers rather than a figure anyone estimates on your behalf.
In plain English, it is how long a person who has just asked to hear from you waits before your phone work begins. You will also see it written as speed to lead, or called lead response time. The clock starts when the lead record exists in your system, not when someone first looks at it. It stops when the first call attempt leaves, whether or not anyone answers. An attempt is one dial handed to your carrier, so a call that rings out still stops the clock; whether a person picked up is a separate measure, covered under call attempt vs conversation.
Why it matters when you buy calling
A lead is usually paid for before anyone calls it. Whatever you spent to produce the inquiry, whether advertising, a directory listing or a referral, is typically spent by the day it arrives, and every hour before the first call is an hour that spend sits idle.
That is the whole argument for putting an AI agent on inbound leads: the same list, the same qualification rubric and the same carrier account, worked while the lead is still warm instead of whenever a rep next reaches the queue. It keeps working after your team goes home, and the figure you manage against is your own, read off your own ledgers.
A 2011 Harvard Business Review article by James Oldroyd, Kristina McElheran and David Elkington reports that most companies are not responding nearly fast enough to potential customers’ online queries. Its full text is paywalled and it predates AI calling, so this entry repeats none of its figures; treat it as a reason to measure, not as a benchmark.
How to calculate it
Subtract the time the lead was created from the time of the first call attempt:
lead-to-call time = time of first call attempt minus time the lead was created
Then report a distribution rather than a single number, because one number hides the leads that matter most:
- The median, which is the wait of the typical lead.
- A tail figure, such as the wait that nine leads in ten stayed under.
- The share called within a target you choose, such as five minutes.
- A count of leads not yet attempted, so unfinished work does not quietly drop out of the average.
- Staffed-hours leads and out-of-hours leads on separate rows, because their delays have different causes.
Worked examples
Every number below is invented to show the arithmetic. None is a benchmark, a study result or a Vocapable figure.
The average hides the tail
Ten leads are first attempted after 1, 2, 2, 3, 4, 5, 6, 9, 480 and 1,440 minutes.
- Mean: 1,952 minutes in total across ten leads is 195.2 minutes, about 3 hours 15 minutes.
- Median: halfway between the fifth and sixth values (4 and 5), which is 4.5 minutes.
- Within five minutes: 6 of 10, or 60%. Within ten minutes: 8 of 10, or 80%.
The mean says the typical lead waited more than three hours. The median says 4.5 minutes. Both are correct arithmetic; only the full set shows eight leads attempted within ten minutes and two that waited 8 and 24 hours.
The hours nobody is at a desk
A team staffed from 9:00 to 17:00 on weekdays covers 8 × 5 = 40 of the 168 hours in a week, about 24%, which leaves about 76% uncovered. Inquiries bunch into the working day, so your real out-of-hours share will be lower; your own timestamps will say by how much. Say 200 leads arrive in a month and 30% of them, 60 leads, arrive when nobody is working. If the next staffed hour is on average 12 hours away, those 60 leads wait 60 × 12 = 720 hours between them. If every one were attempted within a minute of arriving, the total would be at most 60 minutes, or one hour.
What a faster first attempt could be worth
Suppose, purely for the arithmetic, that 12 in 100 leads called within five minutes qualify and 8 in 100 called the next day do. On 200 leads a month that is 24 qualified leads against 16, a gap of 8. If one in four qualified leads becomes a customer, that is 6 customers against 4, a gap of 2. What carries over is the shape of the calculation: leads, times the qualification rate at each speed, times your close rate, times what a customer is worth to you. Put your own numbers into the speed-to-lead calculator.
What moves it
Delay tends to sit in one of four places, and each has a different fix.
- Routing. The lead waits for someone to notice and assign it. Remove that human step.
- Hours. The lead arrives when nobody is working. Decide which hours an automated agent should cover and which you will not call in at all.
- Capacity. Many leads arrive together and there are fewer simultaneous conversations than leads. Plan for the burst rather than the average; see concurrent session.
- Rules. Some delay is correct: a lead you may not call yet should wait. Whether you may call a given lead, at a given hour, on the consent or relationship you hold, is for your program and your advisors to decide; the entries on TCPA, prior express written consent and established business relationship define the words. Report that group on its own line so a rule you followed does not read as slow service.
Common mistakes
- Starting the clock late. Measuring from when a rep opened the record, or from when the lead was routed to them, deletes the wait you were trying to find.
- Reporting only the average. One overnight lead moves a mean further than ten fast ones move it back.
- Counting a task as a response. A reminder or a queue entry is not an attempt. The clock stops when the call attempt leaves.
- Mistaking a fast attempt for a fast conversation. A near-instant attempt that nobody answers has an excellent lead-to-call time and no conversation. Read it next to contact rate.
How Vocapable reports it
The metrics reported alongside lead-to-call time are contact rate, qualification rate, refusals by reason, call-to-handoff time and cost per outcome, each computed from the platform’s own attempt and conversation records, each traceable back to the rows it was derived from.
Every one of those figures describes the traffic you ran, on your own list, through your own carrier account. None is an industry benchmark or a forecast of your results. The reporting set is set out in full on the outcomes page.
Related
The speed-to-lead calculator turns the examples above into your own figures, and the missed-call cost calculator does the same for the inbound side, where the question is how long a ringing call waits to be answered; the receptionist page covers that side. Attempts and AI minutes are priced separately, and the pricing page has the current rates. For what the software does on each dial, see the compliance page and the evidence page. Related definitions: call attempt vs conversation and concurrent session.