Cold calling guide

Roof Inspection Follow-Up Call Tracker: From Free Inspection to Signed Quote

Free roof inspections only pay off if someone calls back. Here's how to track inspection books, report-back calls, and quote callbacks so warm roofs don't go cold.

"Free roof inspection" is one of the best offers a roofing team can put on the phone. It's low commitment for the homeowner, it gets an inspector on the roof, and it turns a cold dial into a real conversation about the house. It's also one of the easiest offers to waste.

Here's how it usually goes wrong. A setter books the inspection. The inspector goes up, takes photos, finds some lifted shingles and a soft spot near the vent. Then the report sits in a truck or an inbox for three days. Nobody calls the homeowner back to walk through it. When someone finally does, the homeowner has already had two other companies out, or the urgency is gone and the answer is "we'll think about it."

The inspection wasn't the problem. The follow-up was. This post lays out a simple roof inspection follow-up call tracker: what to log, which calls to make and when, and how to keep every inspected roof moving toward a signed quote or a clean "no." It works whether your leads come from storm canvassing, cold dialing, or inbound web forms.

If you're setting up a roofing floor from scratch, start with the broader roofing sales call tracker guide. This post zooms in on the stretch between the inspection booking and the quote decision.


The four stages of an inspection lead

Every free inspection lead passes through the same four stages. Your tracker should make it obvious which stage each lead is in and who owns the next step.

  1. Booked. A setter has an inspection date and time on the calendar.
  2. Inspected. The inspector has been on the roof and has findings (photos, notes, a rough scope).
  3. Reported. Someone has actually walked the homeowner through the findings, by phone or in person.
  4. Quoted and decided. A quote is out, and the lead is either signed, lost with a reason, or on a dated callback.

Most teams track stage 1 well because that's where setters get credit. Stages 2 and 3 are where leads leak. The inspection happens, but nobody records it as done, so nobody knows the report-back call is due. A tracker that treats "inspected" and "reported" as separate outcomes fixes most of the leak on its own.


What to log on every inspection lead

Keep the fields short so setters and inspectors actually fill them in. On a busy floor, the minimum set is:

  • Address and phone. One record per property, not one per call.
  • Source. Storm canvass, cold list, inbound, referral, or a campaign tag.
  • Booked by. The setter who got the inspection on the calendar.
  • Inspector. Who went on the roof.
  • Inspection date. When it's scheduled, then marked done when it happens.
  • Findings summary. One or two lines: "lifted shingles north slope, soft decking at vent, 18-year roof." Not a full report.
  • Report-back owner and due. Who calls the homeowner to explain the findings, and by when.
  • Quote status. Not sent, sent, signed, lost, or callback.
  • Lost reason. Price, went with another company, insurance denied, no damage found, not ready.
  • Next due date. For anything still open.

If you already track storm leads, keep the same campaign tags here. Storm-sourced inspections behave differently from cold-list inspections, and you'll want to compare them later. The storm lead follow-up system post covers how to tag and pace surge lists.


The follow-up calls that matter

An inspection lead needs a small number of well-timed calls. Each one should be a dated due in the tracker, not something a rep "remembers."

1. Confirmation call (day before)

Confirm the inspection window and make sure someone can give the inspector access to the yard or attic if needed. Log confirmed, rescheduled, or no answer. A no-answer confirmation is a flag, not a cancellation. Try again the morning of.

2. Report-back call (same day or next morning)

This is the call that wins or loses most inspection leads. As soon as the inspector marks the roof inspected, a report-back due should land on someone's queue for the same afternoon or the next morning at the latest.

On the call, the rep should:

  • Explain what was found in plain language.
  • Mention that photos are available (and send them if your process allows).
  • Say clearly whether the findings look like repair, replacement, or nothing urgent.
  • Set the next step: a quote appointment, a quote sent by email, or an insurance conversation.

If the inspector found nothing worth fixing, say so and log it as "no damage found." That's a trust builder, and it's still a lead worth a dated callback after the next big storm.

3. Quote follow-up (48 to 72 hours after the quote goes out)

Once a quote is sent, set a due for two or three days later. The goal isn't to push. It's to answer questions while the inspection is still fresh. Log the outcome: questions answered, waiting on spouse, waiting on insurance, signed, lost.

Speed matters here more than script quality. The same-day quote follow-up call system post goes deeper on why the first follow-up window is so valuable.

4. Aging quote callbacks (weekly, then monthly)

Some homeowners won't decide for weeks, especially if insurance is involved. Keep them on a dated cadence instead of letting them drift. A reasonable rhythm is weekly for the first month, then monthly, with a clear stop rule after a few unanswered attempts. Rank these by roof age, quote size, and how recent the last real conversation was.


Who owns the report-back call?

This is the question that causes the most confusion on hybrid teams. The setter booked it, the inspector saw the roof, and a closer or project manager might write the quote. If ownership isn't explicit, everyone assumes someone else made the call.

Pick one rule and write it down:

  • Inspector owns report-back. Works well when inspectors are also the salespeople. They saw the roof and can explain it best.
  • Setter owns report-back. Works when setters have a strong relationship with the homeowner and the inspector sends notes quickly.
  • Closer owns report-back. Works on larger teams where closers handle everything after the inspection.

Whatever you choose, the tracker should show the owner's name on the due, and booked-by credit should stay with the setter no matter who makes later calls. Clear attribution keeps setters motivated to book quality inspections, not just any inspection.


Daily routine for an inspection-heavy floor

A short daily rhythm keeps the pipeline moving without a long meeting:

  1. Morning: clear report-back dues first. Anything inspected yesterday gets a call before cold dialing starts.
  2. Late morning: confirmations for tomorrow's inspections.
  3. Afternoon: quote follow-ups that are due today.
  4. Cold or storm-list dialing fills the remaining time.
  5. End of day: inspectors mark today's roofs as inspected with a findings line, so tomorrow's report-back queue is ready.

That last step is the one teams skip. If inspectors don't mark roofs done the same day, the morning queue is empty and the leak starts again.


What to review every week

Once the tracker is running, a weekly review takes 15 minutes. Look at:

  • Inspections booked vs completed. Big gaps usually mean confirmation calls aren't happening.
  • Completed vs reported. Any roof inspected but not reported within 24 hours is a process miss.
  • Reported vs quoted. Low numbers here can mean findings are weak, or reps aren't asking for the next step.
  • Quoted vs signed, by source. Storm, cold list, and inbound often convert very differently.
  • Top lost reasons. If "went with another company" leads the list, your report-back speed is probably the fix.

Keep the review about the funnel, not about blaming individual reps. Use the numbers to adjust who owns which calls and how quickly dues are set.


Tracking it without a heavy CRM

You don't need an enterprise CRM to run inspection follow-ups well. You need one record per property, clear stages, a named owner on every next step, and dated dues that show up on someone's queue.

If you're starting on a spreadsheet, the free call log template covers outcomes, booked by, and next due dates. It works for a small team. Once several setters and inspectors are updating the same sheet during a storm week, filters break, rows get duplicated, and report-back calls slip through.

Dialed Sales is a cold-call tracker built for high-activity teams in roofing, solar, HVAC, and other home services. Setters log one-tap outcomes, every callback and report-back gets a dated due, and boards show books, inspections, and dues cleared alongside dials. Sara AI can recap the week and point out inspected roofs that still haven't had a report-back call.

If free inspections are filling your calendar but not your signed jobs, grab the free call log template or start a free trial at dialedsales.com and put every inspected roof on a dated next step.

Put every call on rails

Log a call in seconds, get follow-ups surfaced the day they're due, and keep a live leaderboard.