Sales & GTM Strategy

Speed to Lead: How Fast to Dial and How to Measure It

Speed to lead decides how many paid leads ever talk to sales. How fast to dial, how to measure it honestly with medians, and how to tie it to booked calls and revenue.


Speed to lead is the time between a lead raising their hand and your team making contact. Everyone agrees it matters. Few teams measure it properly, and fewer still connect it to the numbers they actually care about: booked calls, shows, and revenue. Instead, there’s a vague sense that “we call pretty quickly,” a sales manager who checks the CRM when the close rate dips, and an ad budget that’s paying for leads who go cold before anyone dials.

This post is practical. It covers how fast you should actually dial, why the answer depends on how the lead came in, how to measure speed to lead without fooling yourself with averages, and how to build a report that shows what slow follow-up costs in ad dollars.

Why speed to lead matters more for paid leads

An organic referral who emails you will wait a day. A lead from a Meta ad will not. They tapped an ad between other things, filled in a form in 20 seconds, and went back to scrolling. Their intent peaks in the minutes after they submit and drops fast. By tomorrow, they may not remember your company name. By next week, they’ve booked a call with whoever called first.

That’s why speed to lead is really a paid-acquisition metric, not just a sales metric. Every lead that goes cold before contact is ad spend you paid for and threw away. If your cost per lead is $40 and a slow follow-up process loses an extra 15% of leads to non-contact, you’re effectively paying $47 per lead you reach. Nobody sees that in Ads Manager.

How fast should you dial?

The honest answer: as fast as you can sustain, with a sharp drop-off in value after the first few minutes. Some practical targets by lead type:

Lead type Target first dial Why
Meta instant form Under 5 minutes No site visit, lowest context, intent fades fastest
Landing page opt-in, no booking Under 5 minutes Same as above, slightly more context
Application with qualifying questions Under 15 minutes Higher intent, but still shopping
Booked call, confirmation or setter call Within the hour They’ve committed; you’re protecting show rate
Inbound call request / “call me now” Under 2 minutes They asked for it explicitly
Webinar registrant Before the event, same day Warm them up, increase attendance

Two caveats. First, these are targets for the first attempt, not first contact. Many leads won’t pick up the first time, which is why the follow-up sequence matters as much as the first dial. Second, speed only helps if the person dialing is competent. A rushed, scripted call from someone who doesn’t know the offer can do more damage than a thoughtful call 20 minutes later.

The follow-up sequence after the first dial

A reasonable starting cadence for a high-intent paid lead:

  1. Dial within 5 minutes. No answer: leave a short voicemail and send a text immediately.
  2. Dial again within 30 minutes, from the same number so they recognize it.
  3. Dial again in 2 to 4 hours.
  4. Next day: morning and late afternoon dials, plus a text.
  5. Days 3 to 7: one dial and one message per day.
  6. After that: move to nurture.

Change the numbers to suit your market, but write them down. A cadence nobody can describe is a cadence nobody follows.

Defining speed to lead precisely

Before you measure, decide exactly what you’re timing. The common definitions:

  • Lead to first dial. The time from form submit to the first outbound call attempt. This measures your process.
  • Lead to first contact. The time to the first connected conversation. This measures process plus luck.
  • Lead to booked call. The time to a meeting on the calendar. This measures outcome.
  • Booked call to confirmation contact. For appointment-setting funnels, the time from booking to the first human touch, which affects show rate.

Track at least the first two. Lead to first dial is the one your team controls, so it’s the one to set targets on.

Also decide how to handle edge cases:

  • Leads that arrive overnight or on weekends. Either measure business-hours time, or report them separately. Don’t let a 3 a.m. lead with a 9 a.m. dial wreck your average, but don’t hide them either; if 30% of leads arrive after hours, that’s a staffing question.
  • Leads never dialed. These are the most important ones. Report the percentage of leads with no dial at all, separately from timing.
  • Duplicates and existing contacts. Someone who was called yesterday and resubmits today shouldn’t count as a fresh lead with a slow response.

Why you should use the median, not the average

Response time data is badly skewed. Most leads might get a call in 3 minutes, and a handful wait three days because they fell through the cracks. An average blends those into a number that describes nobody.

Take ten leads with response times of 2, 3, 3, 4, 4, 5, 6, 8, 12 minutes and one at 2,880 minutes (two days). The average is about 4 hours 53 minutes. The median is 4.5 minutes. The median tells you what a typical lead experiences. The average tells you something’s wrong, but not what.

Use both, for different jobs:

  • Median for your headline speed-to-lead number and targets.
  • Percentage over target (for example, “% of leads not dialed within 15 minutes”) for catching the leads falling through the cracks.
  • Average only as a smoke alarm. If it suddenly jumps while the median is stable, a batch of leads got missed.

In Callix, you can measure this with Time Between Events, set up under Settings → Knowledge Base → Time Between Events. Pick a start and end event, choose median or average, and add the result to any metric, report or table widget. Times read in days and hours (like 2d 4h), and because they sit in a table widget, you can break them down by campaign, funnel or rep.

Measuring dials: getting the data in the first place

Speed to lead is only measurable if every dial is logged with a timestamp and tied to the right contact. That sounds obvious; in practice it’s where most measurement breaks.

  • Use a dialer that logs automatically. Reps who log calls by hand log them late, or not at all.
  • Make sure dials match to contacts. If a rep dials from a personal phone, or the dialer can’t match the number to a CRM record, the dial exists but not on the lead.
  • Decide what an unknown number means. A rep calling a number that isn’t in your CRM might be a referral, a personal call, or a lead that came in through a channel you’re not tracking. Most teams don’t want every such call creating a new lead record.

Callix connects to dialers including Close, GHL, Aloware, SendBlue, YourAtlas and Project Blue, and each one has a Create prospects from dials switch: turn it off and a call to a number Callix doesn’t know is still recorded and analyzed without adding a new prospect. Analyzed dials appear on a Dials tab in Deal Analysis with their outcome, lead score, duration and date, filterable by rep.

Connecting speed to lead to revenue

The report that changes behavior isn’t “our median is 11 minutes.” It’s “leads called within 5 minutes book at twice the rate of leads called after an hour, and here’s what that’s worth.”

Build a table that buckets leads by response time and follows each bucket through the funnel:

First dial within Leads Booked Book rate Closed Revenue
0–5 minutes 310 87 28% 14 $56,000
5–30 minutes 240 50 21% 8 $32,000
30 min – 4 hours 180 25 14% 4 $16,000
4+ hours 120 10 8% 1 $4,000
Never dialed 50 2 4% 0 $0

The numbers are illustrative, but this is the shape most teams find. Now do the arithmetic for the business: if the 350 leads dialed after 30 minutes (or never) had booked at even 21%, that’s about 74 calls instead of 37. At an 18% close rate and a $4,000 offer, the gap is worth roughly $26,000 a month in revenue you already paid for.

One honest caveat: correlation isn’t causation here. Leads that get called fast might also be higher quality (they came in during business hours, from better campaigns). Check the pattern within a single campaign before you make big claims, and if you can, run a real test: route half of incoming leads to an instant-dial queue for two weeks.

Breaking it down by rep, campaign and time of day

Once the basic number is in place, slice it:

  • By rep. Who is fast, who is slow, and does it show in their booked calls? Fast reps with low book rates have a different problem from slow reps.
  • By campaign and funnel. Some funnels might be routed to a queue nobody watches. Instant form leads often get slower treatment because they arrive in a separate inbox.
  • By hour and day. Plot median response time by hour. The gaps usually line up with lunch, shift changes, and Monday-morning backlog.

Fixing slow speed to lead

The fixes are usually operational, not technological:

  1. Route leads to a person, not a pool. Round-robin assignment with a notification beats a shared inbox. See automating lead routing without losing leads.
  2. Cover the hours your ads run. If ads run 24/7 but setters work 9 to 5, either schedule ads to business hours, add shift coverage, or send an instant text with a booking link for after-hours leads.
  3. Give reps context. The ad they clicked, the form answers, any previous history. A fast call that starts with “So, what made you fill in the form?” wastes the speed.
  4. Review the misses weekly. Pull every lead that waited over an hour and ask why.
  5. Tie it to comp or recognition. What gets measured and rewarded gets done.

The bottom line

Speed to lead is one of the cheapest ways to make paid acquisition more efficient: no new creative, no new budget, just reaching the people you already paid for while they still care. Measure lead-to-first-dial as a median, track the share of leads never dialed, bucket response times against booked calls and revenue, and review the misses every week. For the qualification side of the same problem, see qualifying leads without losing good-fit prospects, and for how call data ties into the rest of the funnel, see our sales intelligence overview.

Book a demo