How to Audit Your Own Lead Response Time in One Afternoon

What counts as a lead response time audit?

A lead response time audit is a manual review of how long it actually takes your business to make first contact with a new lead, measured against when that lead actually arrived. Not when you think you responded. Not your team's guess. The timestamp.

Most owners have a rough feeling for this ('we're usually pretty fast') that falls apart the moment you pull real timestamps. The point of the audit is to replace that feeling with a number you calculated yourself, from your own records.

You don't need software for this. You need your email inbox, your call log, your form submission notifications, and about three hours. If you want the fuller context on why this matters for how AI systems get built around it, see what an AI ops retainer actually covers.

What do you need to gather before you start?

Pull these four sources for the last 30 days, or the last 25-30 leads, whichever comes first:

• Inbox: emails from your website contact form, Google Business Profile messages, and any third-party lead sources (Angi, Thumbtack, etc.)
• Call log: your phone system or cell carrier's log, showing inbound calls from unknown or new numbers
• Form submissions: the raw notification timestamps from whatever form tool you use, not the CRM entry timestamp (those can lag)
• Text/SMS log: if leads can text you directly, pull that thread history too

Export or screenshot timestamps as you go. You're building a spreadsheet, and the raw timestamp is the only fact that matters here.

How do you build the worksheet?

Open a blank spreadsheet with these columns: Lead source, Date/time received, Date/time of first real contact, Gap (in minutes), Contact method, Outcome (booked, no-show, ghosted, lost).

'First real contact' means a phone call that connected, a text that got a reply, or an email reply, not an autoresponder or a form confirmation. Autoresponders don't count because the lead knows it's automated. They're waiting for a human.

Work through each lead in order. For calls you missed and called back, the gap is the time between the missed call and your callback connecting, not just your callback attempt. A callback that rang and went to voicemail again doesn't close the gap. This distinction alone is where most owners discover their real number is worse than they assumed.

How do you calculate your real numbers?

Once you have 20-30 rows filled in, calculate four things:

• Median response time: sort the gap column and take the middle value. Use median, not average, since one lead you responded to after a weekend will skew an average badly.
• Percent responded within 5 minutes: count rows under 5 minutes, divide by total rows.
• Percent responded same day: count rows under 24 hours (or your business hours window), divide by total.
• Worst offenders: the five slowest gaps. Look for a pattern: same time of day, same source, same day of week.

These four numbers are your baseline. You don't need an industry benchmark to know if a 6-hour median is a problem. If your booked-vs-ghosted outcomes column shows most bookings clustered in the under-5-minute rows and most ghosts in the multi-hour rows, that's your own evidence, generated from your own leads.

Step-by-step checklist for the afternoon

• Block 3 uninterrupted hours (this breaks down if done in 10-minute chunks between other tasks)
• Pull the last 25-30 leads across all four sources into one spreadsheet
• Fill in received time and first real contact time for each row
• Calculate the gap in minutes for every row
• Sort by gap, identify your median and your five worst offenders
• Tag each row's outcome: booked, no-show, ghosted, lost
• Cross-reference gap length against outcome to see where the pattern breaks
• Write down the single biggest bottleneck you found (after-hours leads, weekend leads, a specific source, a specific staff member's shift)

If a big chunk of your worst gaps cluster around after-hours or weekend leads, that's usually the first fix worth making before anything more complex. Industries with legal urgency see this most sharply. Our speed-to-lead breakdown for personal injury firms walks through why that gap is especially costly there, and the same logic applies to service businesses generally.

What do you do with the results?

Once you have your baseline, you have three honest options: accept it, fix it with process changes (a rotation for who answers calls, a same-day callback rule), or fix it with a system that answers immediately regardless of staff availability.

Process fixes work until the pattern that caused the gap in the first place (nights, weekends, lunch, a busy front desk) repeats itself. If your worst offenders cluster around hours nobody is staffed, that's a structural gap, not a discipline problem.

That's usually where an AI receptionist or instant-response system gets evaluated, not because it's assumed to help, but because your own worksheet just showed you exactly which hours and sources are bleeding. See how this plays out in a specific vertical in our AI receptionist guide for med spas, or browse the full library at ClawOps guides. If you want to see how a live system handles the exact gap you just measured, ClawOps only demos what it can actually show working in real time.