Lead response time: how to measure the gap from enquiry to first call

Lead response time is the gap between the moment someone enquires and the moment your business makes contact. It sounds easy to measure, but most teams can't get an honest number. The CRM records when a lead was created, not when the person hit submit. A missed dial gets counted the same as a real conversation. And overnight enquiries either get quietly left out or drag the average around.

This guide covers how to measure lead response time properly. It explains which timestamps to capture, why first attempt and first conversation need to be tracked separately, how to treat out-of-hours enquiries, and how to report by lead source so the number leads to decisions.

What lead response time should actually measure

Before you build a report, agree on what the number is for. For most sales and marketing managers, the real question is: how long does a prospect wait before a person (or a voice agent acting for us) is actually talking to them?

That question has several parts, and you can't fix what you can't separate:

• Delay between the enquiry and your systems knowing about it
• Delay between your systems knowing and someone being responsible for it
• Delay between someone being responsible and the first call attempt
• Delay between the first attempt and a real conversation

A single "response time" figure blends all of these together. When it gets worse, you won't know whether the cause is a broken form integration, a routing rule or an understaffed Friday afternoon.

The timestamps to capture

Capture each of these as its own field, stored with the date and time to the second, in a consistent time zone. Australian businesses working across states should store everything in a single reference zone and convert only for display. Otherwise a Perth lead and a Sydney rep will produce nonsense.

Enquiry submitted

This is when the prospect actually acted: they submitted a web form, sent a lead ad, made a booking request or replied to a campaign. Take it from the source wherever you can, such as the form platform, the ad platform's lead payload or the marketplace notification. Don't rely on your CRM's "created" date.

Enquiry received

This is when the lead landed in your CRM or calling system. The gap between submitted and received is your integration lag. It's usually small, but when a sync fails or batches overnight, it can quietly add hours that no sales rep could ever have recovered.

Lead assigned

This is when the lead was routed to a person, queue or automated caller. If leads wait in an unassigned pool, this timestamp exposes it.

First call attempt

This is when the first outbound dial was placed, whatever happened next. Pull it from your phone system or dialler logs, not from a rep ticking "called" in the CRM afterwards. Manual logging is often done in batches and makes response look slower or faster than it really was.

First conversation

This is when someone first actually spoke with the prospect. Define "conversation" clearly, for example as a connected call where the prospect was identified and the purpose of the call was discussed. Voicemails, wrong numbers and immediate hang-ups don't count.

Appointment booked or qualified outcome

This one isn't strictly part of response time, but capturing it lets you link speed to results in your own data, without relying on anyone else's claims.

First attempt versus first conversation

This is where most reports go wrong. Time to first attempt measures your team's discipline. Time to first conversation measures the prospect's experience. Both matter, and they can tell very different stories.

A team can have a fast first attempt and a slow first conversation if reps make a single dial, leave a voicemail and move on. A team with a slower first attempt can still reach people sooner if its follow-up cadence is well designed: a quick retry, a call at a different time of day, an SMS saying who called.

Report both, plus the gap between them. Then look at:

• Attempts before first conversation. If it takes many dials to reach people, look at call timing, caller ID presentation and whether the number shows up as a known business.
• Leads with attempts but no conversation. These often fall out of the process entirely. Track how long they sit before the cadence stops.
• Leads never attempted. Report these as their own group, not as an infinitely long response time that breaks your average.

When you report on how fast your team calls, use the first attempt. When you report on the customer experience, use the first conversation.

Handling out-of-hours enquiries

Enquiries arrive at night, on weekends and on public holidays, and how you treat them changes your number dramatically. There are honest options, and each has trade-offs.

Option: measure clock time

Count every minute from submission to contact, whatever the hour. This is the prospect's real experience and the most honest number. The downside is that it can make a well-run daytime team look poor, and it may hide improvements during business hours.

Option: measure business-hours time

Pause the clock outside your trading hours. This is fairer to the team and useful for staffing decisions. The risk is that it hides the fact that a Saturday morning enquirer may wait until Monday, by which time they may have booked elsewhere.

Option: report both, split by when the enquiry arrived

This is the most useful approach. Tag every lead as in-hours or out-of-hours based on when it was submitted. Report clock-time response for both groups, and business-hours response for the in-hours group. Now you can see your team's performance and the gap your customers actually experience.

A word of caution about calling outside normal hours. There are rules in Australia about when telemarketing calls can be made and who can be called, and how they apply depends on the type of call and whether the person has consented. Responding to someone who has just asked you to contact them may be treated differently from a cold call, but don't assume. Check the current requirements with the ACMA or get legal advice before you change your calling hours or automate after-hours follow-up.

Reporting by source

A blended response time across all channels hides most of what you need to know. Break it down by lead source: paid search, social lead forms, organic web forms, comparison or marketplace sites, referrals, events and so on.

Reporting by source tells you a few things:

• Where integration lag lives. Some sources deliver leads in real time and others don't. Comparing submitted against received, source by source, shows which ones need fixing.
• Where routing breaks down. If a particular campaign's leads land in a queue nobody watches, assignment time for that source will stand out.
• What marketing is really buying. If a channel's cost per lead looks good but its leads wait longest for a conversation, the comparison with other channels isn't fair. Marketing and sales should look at this report together.
• Which sources are time-sensitive. Your own data will show whether contact speed affects booking rates differently by channel. Leads from shared marketplaces, for example, may also be getting calls from other businesses, so it's worth checking whether speed matters more there.

Keep the source taxonomy tidy. If "Facebook", "FB lead ad" and "Meta" all appear as separate values, the report is worthless. Lock down source values at the point of capture.

Building the report: practical steps

1. Audit your current fields and find out where each timestamp comes from and whether it's system-generated or entered by hand.
2. Fix the data source for any timestamp currently logged manually, especially first attempt and first conversation.
3. Agree on and write down definitions for "conversation", "in-hours" and each lead source.
4. Use the median rather than the average, because a handful of very slow leads will distort an average badly.
5. Look at the slow end separately: list the slowest leads each week and find out why they were slow.
6. Show leads never attempted and leads attempted but never reached as counts, not folded into the time figures.
7. Review weekly with sales and marketing in the same room, by source and by in-hours versus out-of-hours.

Questions to ask your team and your vendors

• Does our CRM's created date reflect when the prospect submitted, or when the record synced?
• Are call attempts logged automatically by the phone system, or entered by reps?
• What happens to a lead that arrives at night or on a public holiday, and who owns it?
• How many attempts do we make before we stop, and over what period?
• Can every lead source pass its original submission time into our system?
• Do we hold a record of each lead's consent to be contacted, and when it was given?

Closing the gap

Once you're measuring properly, the fixes are usually obvious: repair slow integrations, tighten routing, design a proper follow-up cadence and decide how to cover out-of-hours enquiries. Speed is the hardest part to staff for. That's what we built Dialessa for: an AI voice agent that calls new enquiries within a minute, books the appointment and follows up past leads whose consent is still current. Whatever you choose, start with honest timestamps. Without them, any lead response time figure is a guess.