Roof lead response time: how to measure the wait and what it costs you

Why response time matters more in roofing than in most trades

Roofing leads come in two very different moods, and both punish slow replies.

The first is the urgent lead: water through a ceiling, shingles in the yard after a windstorm, a skylight dripping onto the kitchen table. These homeowners contact several companies at once and go with whoever gives them a clear next step first.

The second is the planned lead: someone selling the house, a homeowner who noticed curling shingles, a couple budgeting for a replacement next spring. They're less rushed but they're collecting quotes, and the company that replies quickly and professionally sets the standard everyone else is measured against.

Add the size of the ticket, often five figures for a full replacement, and a few lost leads a month becomes real money.

Step 1: build a two-week response log

You need five columns. Create them in a spreadsheet or on paper.

Fill it for 14 consecutive days, including a weekend or two. Pull timestamps from your form notification emails, your phone's call history and your texting app. Don't round; "around lunchtime" hides the pattern.

A few rules keep the log honest:

• A missed call counts as a lead the moment it rings out, even if no voicemail was left.
• "First reply" means the homeowner received something. A note on the office whiteboard doesn't count.
• If a lead never got a reply, mark it. These are the most important rows.

Step 2: calculate your median wait

Sort the "human reply" gaps from shortest to longest and pick the middle one. That's your median response time.

Here's a sample from a hypothetical two-crew roofer's log of 36 leads:

• 9 leads answered within 15 minutes
• 8 answered between 15 minutes and 2 hours
• 11 answered between 2 and 8 hours
• 5 answered the next day or later
• 3 never answered

The median here sits in the 2-to-8-hour band. Notice that 19 of 36 leads, more than half, waited over two hours or never heard back. The office manager in this example had guessed "usually within the hour".

Now look at when the slow ones arrived. In most roofing logs, the pattern is obvious once you see it: leads after 4 p.m., on Saturdays, and on days when every crew was on a roof. That tells you exactly where an instant text would help.

Step 3: put a dollar figure on the wait

Next, compare outcomes for fast and slow leads in your log. You'll need a bit more data for this to be reliable, so combine your two-week log with what you remember from the past season if needed.

Suppose your records suggest you book inspections for 55% of leads answered within 15 minutes and 30% of leads answered after two hours. Suppose 45% of inspections turn into signed jobs, and your average signed job is $11,000.

For a month with 80 leads, where 40 are currently answered slowly:

1. Slow leads booked: 40 × 30% = 12 inspections
2. If those leads had been answered fast: 40 × 55% = 22 inspections
3. Difference: 10 inspections
4. Signed jobs from the difference: 10 × 45% = 4.5 jobs
5. Revenue at stake: 4.5 × $11,000 = about $49,500 a month

These are illustrative inputs, not industry statistics. Plug in your own. Even if your gap is a quarter of this example, it's usually more than the cost of fixing it.

Step 4: fix the wait in layers

Speed improves fastest when you fix it in layers, from cheapest to most involved.

Layer 1: an instant first text. Every lead, from every source, gets an acknowledgement from your business number within a minute. It confirms a real company received the request, asks one sorting question and names a time for a human reply. Template:

Hi [Homeowner first name], [First name] from [Business name] here. Got your roof request. Any water coming inside right now? Reply YES or NO, and I'll get back to you by [time]. Reply STOP to opt out.

Layer 2: routing. YES replies alert whoever handles leaks. NO replies go to a shared queue with a 20-minute claim rule, so leads don't sit unowned.

Layer 3: booking by text. Instead of a callback, the next message collects the address, roof type and age, and offers two inspection windows. See inspection booking by text.

Layer 4: after-hours and storm rules. Separate wording for evenings, weekends and storm surges, so the promise in the text is always true. The storm triage guide covers surges.

Step 5: measure again

Repeat the two-week log a month after making changes, in similar weather. Compare:

• median time to first reply (should drop to about a minute)
• median time to human reply
• leads never answered (should be close to zero)
• share of leads reaching a booked inspection

If the instant reply time dropped but bookings didn't move, look at the human follow-up. A fast first text followed by a six-hour silence only delays the problem.

Common mistakes when measuring

• Measuring only form leads. Missed calls are often the biggest source of unanswered leads, and they leave no trace unless you look at call history.
• Excluding storm days. They're your highest-value days. Track them separately rather than dropping them.
• Counting an auto-reply as the whole job. It's the first layer, not the finish line.
• Changing everything at once. If you redo your ads, website and texting in the same month, you won't know which change mattered.

What to do with your number

If your median wait is already under 15 minutes and nearly no leads go unanswered, your bottleneck is probably elsewhere, such as pricing, reviews or the estimate itself; estimate follow-up may help more. If your median is measured in hours, instant text reply is likely the highest-value fix available to you.

Either way, you now have a real number. Bring it to a free consultation through the contact page, or set up the first layer yourself using the instant reply service page as a checklist.