First Response Time Formula: How to Calculate It for Leads

The first response time formula is simple: subtract the time a lead reached out from the time you first replied. First response time = time of first meaningful reply − time of the initial inquiry. For a report across many leads, you collect those individual gaps and summarize them, ideally with the median instead of the average.

The formula takes ten seconds to learn. The decisions around it take longer: what counts as a reply, which clock you use, and which summary number you trust. This guide walks through all of it with worked examples built for service professionals such as real estate agents, contractors, insurance agents and financial advisors, who live and die by how fast they answer a new inquiry.

Astreauxcalendly.comRespond to New Leads FasterAstreaux uses conversational AI to engage new leads instantly with personalized responses and help service professionals streamline follow-up.Book a call

TL;DR

• Formula: first response time (FRT) = timestamp of your first meaningful reply − timestamp the lead came in. Aggregate FRT = sum of all individual FRTs ÷ number of inquiries.

• Use the median, not just the mean. One lead that sits over a weekend can distort an average badly. Add the 90th percentile to see your slowest 10% of leads.

• An auto-receipt is not a first response. The reply has to address the lead’s question and move the conversation forward.

• Pick one clock and keep it. Calendar hours show what the lead feels. Business hours show what your team controls. Changing between them breaks your trend line.

• Track by source. Facebook leads, website forms and portal inquiries often behave differently, and one blended number hides it.

The first response time formula, step by step

The core calculation, as Count’s metric guide lays out, is the time of the first meaningful response minus the time of the initial inquiry. In the lead world, “inquiry” means the moment a form is submitted, a text arrives, a call is missed or a lead-ad contact is created in your CRM.

Here is the single-lead version:

FRT = reply timestamp − lead timestamp

Example: a homeowner submits an estimate request on your website at 2:30 p.m. You text back a real answer at 3:15 p.m. FRT = 3:15 − 2:30 = 45 minutes.

For a period report (a week, a month, a campaign), the same source gives the aggregate version:

Aggregate FRT = (sum of all individual FRTs) ÷ (total number of inquiries)

If ten leads took a combined 150 minutes to get a first reply, the average is 15 minutes. That is the textbook formula, and it is a fine starting point. It is also where many teams stop, which is a mistake, as the next section shows.

What you need in your data

To run this calculation you need only two timestamps per lead:

1. Lead created time. When the inquiry entered any system you control.

2. First qualifying reply time. The first outbound message or call that meets your definition of a real response.

Most CRMs record the first. The second is the one that usually needs setup, because it depends on your rules. That is the next topic.

What counts as a “first response”

This is where the same formula produces wildly different numbers between two businesses.

An automatic “we’ve received your request” does not count. Giva’s guide makes the point that a true first response should be a personalized, meaningful message that addresses the inquiry and moves things forward. If you use AI, it should give substantive help, not a canned receipt.

A workable definition for a service business:

• Counts: a text, email or call that answers the lead’s actual question, offers specific next steps (two appointment slots, a price range, a question that qualifies the job) and references what they asked for.

• Does not count: an autoresponder, a “thanks for contacting us” page, a voicemail the lead never hears, or an internal task created for someone else.

• Edge case: a missed call followed by a text within seconds that says what you can do and asks one clear question. Most teams count this, as long as the text is specific.

Write the definition down and share it with everyone who touches leads. Otherwise your report measures how generous each person is when they log their own replies.

Why this matters more with automation

When software replies in seconds, a vague definition makes your numbers look perfect while leads still wait for real help. If your automation sends a stock acknowledgment, track two numbers: time to acknowledgment and time to first substantive reply. Only the second one is your FRT.

This is the gap conversational AI is meant to close. A system that answers the question the lead actually asked, in your voice, can count as a real first response. A system that only says “got it” cannot.

Calendar hours or business hours?

You have to choose which clock to run. Metabase’s guide frames the trade-off well: calendar time reflects what the customer actually experiences, which matters for always-on expectations, while business-hours tracking stops off-hours inquiries from unfairly dragging your numbers. Consistency across reporting periods matters more than which one you pick.

Worked example. A homeowner asks for a roof estimate at 9:40 p.m. Your office opens at 8:00 a.m. and you reply at 8:10 a.m.

Both numbers are true. They answer different questions. The business-hours figure tells you whether your team is fast when it is working. The calendar figure tells you what the homeowner experienced, and that is the one a competitor who replies at 9:42 p.m. will beat.

For service professionals, we recommend reporting both and putting the calendar number in front of you. Many inquiries arrive in the evening and on weekends, when people are at home thinking about their project, their move or their policy. Our related guide on what fast actually means for lead response goes deeper on benchmarks.

Why the average misleads you

The mean is easy to compute and easy to wreck. Metabase warns that a simple arithmetic mean is easily skewed by extreme outliers, such as a ticket that sits open over a weekend, and recommends the median to represent the typical experience, plus the 90th percentile for the slowest 10%.

Here is a worked example with ten leads in one week. These numbers are illustrative, not client data. Times are in minutes from inquiry to first meaningful reply:

2, 3, 4, 5, 6, 8, 12, 15, 45, 1,440

The last lead came in Friday night and was answered Saturday night (24 hours).

The mean says you take two and a half hours to reply. The median says a typical lead hears from you in 7 minutes. Neither is wrong, but only the pair tells the story: you are quick most of the time, with a tail of slow leads, and one of them waited a full day.

The Count guide also recommends the median over the average for aggregate reporting. And a general warning from performance engineering applies here too: an average can hide severe failures for individual users, just as an average of very hot and very cold stays comfortable on paper. If your routing breaks for one lead source, the mean may barely move while real prospects go unanswered.

How to calculate median and percentiles in practice

You do not need a data team.

1. Export leads from your CRM with lead created time and first reply time.

2. Add a column: reply time minus created time, in minutes.

3. In a spreadsheet, use MEDIAN() on that column. For the 90th percentile use PERCENTILE(range, 0.9).

4. Sort the column descending and read the top five rows. Those are the leads to investigate.

If your CRM can report percentiles directly, use that, but still check the slowest rows by hand. The pattern is usually obvious: Sunday inquiries, one source, one team member’s territory.

Segment before you summarize

Giva argues that a single aggregate FRT misleads because response time should vary by priority, and suggests tracking several tiers instead of one number. Leads work the same way. A hot inbound request for a showing is not the same as a newsletter signup.

Split your report along three lines.

By lead source

Website form, phone, text, portal inquiry, social ad. If you run Facebook lead ads, track them on their own. Those contacts are created instantly and the person may have tapped a form in a few seconds, so their intent can cool fast. A source-level view shows where your process is leaking.

By time of day and day of week

Put inquiries into buckets: business hours, evenings, weekends. Most teams find that off-hours FRT is far worse than they assumed. That is where automation earns the most.

By lead quality or intent

If your CRM scores leads or tags them, compare FRT for hot leads against cold ones. If your best leads wait as long as your worst, your routing has no priority logic.

Setting a target for your business

First, a caution. Published benchmarks vary by industry and channel, and many come from customer support, not sales. Use them as a sanity check, not a promise. For lead-based businesses, the useful target is the one you can sustain every day, including nights and weekends, and it should be stricter for new inbound leads than for general questions.

A practical approach:

1. Measure your current median and 90th percentile for four weeks.

2. Set a median target about half of where you are now, and a 90th percentile target that removes the overnight tail.

3. Review monthly, and tighten when you hit the target for two months running.

For the research behind why speed matters in sales, see our breakdown of what the lead response management study really proves. It separates what the study says from what is often claimed about it.

Response time ROI: connecting FRT to revenue

Response time becomes a business case when you tie it to bookings. You do not need a perfect model. You need your own funnel numbers.

Track, by FRT bucket (for example under 5 minutes, 5 to 30 minutes, 30 minutes to 4 hours, over 4 hours):

• Number of leads

• Percent that replied

• Percent that booked an appointment or estimate

• Percent that became customers

A simple ROI sketch with made-up numbers, to show the arithmetic:

Multiply the extra bookings by your close rate and average job or commission value. Your real conversion rates by FRT bucket will replace the hypothetical ones after a month or two of tracking. Do not borrow someone else’s conversion lift. Your market, price point and lead source will set your own.

If you are still building the case, our speed-to-lead tactics cover how teams move from slow to fast without adding headcount.

Reading your results and finding the cause

Once you have median, 90th percentile and a few segments, the question is why a number is high. Most causes fall into four groups: no one was notified, the lead was routed to the wrong person, the team could not reply at that hour, or the reply was slow because it was written from scratch each time.

Feedback loops help here. Pairing your response data with what customers actually say about the experience shows which delays hurt most. This overview of customer feedback and revenue growth covers how to turn that kind of input into decisions.

A short diagnostic checklist:

• Is the slowest 10% concentrated in one source, one agent or one time window?

• Do alerts reach a phone, or only an email inbox?

• Is anyone responsible for new leads on weekends?

• Are replies typed from scratch, or do templates cover your top five questions?

• Do you count the autoresponder as a first reply? If so, your real FRT is higher than reported.

How to improve lead response time

Improving the number means removing waiting at each handoff. These steps are ordered by effort, lowest first.

1. Fix notifications. Push alerts to the phone of whoever owns the lead. A form that only emails a shared inbox is the most common source of slow replies.

2. Write reply templates for common questions. Keep them short, with placeholders such as “Hi {{firstName}}, thanks for asking about {{service}}.” Personalize the first line and the question at the end.

3. Reply by text first when it fits. Text is fast to read and answer. Our guide to an SMS-first lead flow explains how to structure a first message, and our piece on instant lead response covers consent. Follow the rules on texting consent that apply to you.

4. Route by intent, not just by round-robin. Send hot requests to the person who can answer them, and keep a backup when that person is on a job site or in a showing. See how lead routing and outreach automation work.

5. Cover nights and weekends. Either schedule coverage or let automation hold the conversation until a person takes over.

6. Automate the first reply, then measure the quality. This is the largest lever for off-hours leads, and it only helps if the reply is substantive.

For trades, our contractor follow-up templates and automations show what a useful first message looks like for estimate requests.

FRT for real estate, contractors, insurance and advisors

The formula is the same across professions. What changes is who the lead is and when they write.

• Real estate agents: Inquiries come in while agents are at showings or open houses. Your 90th percentile usually reveals more than your median, because the slow replies cluster on busy weekend afternoons. Track portal leads and website leads separately.

• Contractors: The person asking for an estimate is often contacting several companies. Track time to first reply and also time to a booked estimate, since the goal is a scheduled visit.

• Insurance agents: Quote requests are time-sensitive, often triggered by a renewal or life event. Measure from the quote request to the first reply that asks the right qualifying question.

• Financial advisors: Leads are fewer and the sales cycle is longer, so a median over a small sample can swing. Look at every lead’s FRT individually and focus on nurturing after the first reply.

For all four, a second metric pairs well with FRT: time to booked appointment. A fast reply that never books a call is only half the job.

Our perspective: speed is only useful if the reply is good

We built Astreaux around a problem we see over and over: service professionals do not lose leads because they are careless, they lose them because they are busy. You are on a roof, in a closing, or with a client, and a new inquiry sits unanswered.

That is why we think about FRT in two parts. The first is speed, and software wins that part easily. The second is substance, and that is where most automation fails. A reply that sounds like a robot, or that only confirms receipt, may improve the number on a dashboard while doing nothing for the lead.

So our approach is to learn how each business speaks, reply instantly in that voice, ask the next useful question, and move the lead toward a booked appointment. We also believe in measuring honestly: use the median and the 90th percentile, count only meaningful replies, and look at the slowest leads first. If your numbers look great and your bookings do not move, the definition of “response” is probably too generous.

— Jamaal

Automating the first reply with Astreaux

If your 90th percentile is high because leads arrive when you cannot answer, automation is the fastest fix. Astreaux is an AI-driven lead management platform that replies to new leads instantly with conversational AI trained on your business’s voice, nurtures prospects, books appointments, and connects to over 7,000 apps and your CRM and ad platforms, so inquiries from forms and ads flow in without manual copying. Its analytics help you track pipeline performance, so you can check your own FRT before and after.

To see how an instant reply works in practice, including consent considerations, read our walkthrough of replying to leads in minutes, or see how inbound lead automation books appointments.

A one-week FRT audit you can run

Here is a plan you can finish in a week with no new tools.

1. Day 1: Write your definition of a first response and choose calendar or business hours (ideally track both).

2. Day 2: Export the last 30 to 90 days of leads with created time, source and first reply time.

3. Day 3: Compute individual FRTs, then the mean, median and 90th percentile.

4. Day 4: Segment by source and by time window. Highlight any bucket where the median is more than double the overall median.

5. Day 5: Read the ten slowest leads one by one. Note the cause of each delay.

6. Day 6: Pick the single biggest cause and fix it: notifications, coverage, templates or routing.

7. Day 7: Set targets and put the median and 90th percentile on a recurring report.

Repeat monthly. The goal is a steady trend line, not a perfect week.

FAQ

What is the formula for first response time?

First response time equals the timestamp of your first meaningful reply minus the timestamp of the initial inquiry. For a period, add up all individual response times and divide by the number of inquiries, or better, report the median. Keep the same definition and clock every time.

Should I use the average or the median?

Use the median as your headline number and add the 90th percentile. The average is pulled up by a few very slow leads, such as an inquiry that waited over a weekend. The median shows the typical experience, and the 90th percentile shows the slow tail.

Does an automatic reply count as a first response?

Not if it only confirms receipt. A first response should address what the lead asked and move the conversation forward. If your automation does that, count it. If it does not, track acknowledgment time and meaningful reply time separately.

How do I measure response time for Facebook leads?

Take the time the lead-ad contact was created in your CRM, or the time you received it, and subtract it from your first meaningful reply. Track Facebook leads as their own segment, since their pattern often differs from website or phone leads.

Sources

• Count: First Response Time metric guide

• Metabase: First-Response Time definition and tracking

• Giva: What Is First Response Time

• Customer feedback and revenue growth