1. Home
  2. Guides
  3. Roofing companies
  4. Playbook

Playbookfor roofing companies

Roofing company calling playbook: call blocks, cadence and KPIs

Updated September 28, 20264 min read3 primary sources

A home services rep on a call from his truck, solar panels on the roof behind

The short answer

This playbook covers how a roofing company runs its calling year: storm inquiry blocks, estimate approval lists, off-season reactivation and crew planning from call data. It details list hygiene, attempt cadence, dispositions, three-line sessions with AI summaries, and KPI ranges anchored to DialBreeze production numbers.

Step by step

  1. 1

    Stage the inquiry list within a day of the event

    Consolidate inspection requests and canvass contacts into one CSV with source, event date and neighborhood notes. Apply your internal DNC list, per-lead quiet hours and attempt caps before the session, fresh-first.

  2. 2

    Run the storm inquiry block

    Work the list newest first on three lines. Four facts on every connect: roof age and type, what they noticed, insurance status, household timing. Book the inspection window that fits their calendar.

  3. 3

    Work the estimate approval block

    Call homeowners with signed inspection reports about approve-and-schedule decisions, summaries attached. The deductible and financing conversations happen here, inside your state's rules.

  4. 4

    Run the off-season reactivation block

    Work inspection reports never converted, fall estimates and the after-the-holidays list, each called with the original objection attached. These calls fill the spring calendar.

  5. 5

    Plan crews from the summaries

    Neighborhood, roof type and wrong-roof dispositions turn the call record into a route plan and a clean crew list instead of canvass sheet guesswork.

What this playbook covers

Roofing calling runs on a season clock: storm weeks produce surges that drown unprepared offices, and off-season months starve offices that stop dialing. This playbook structures both: the storm inquiry block that books inspections while interest is hot, the estimate approval list where revenue actually materializes, and the off-season reactivation that fills the spring calendar. It assumes a three-line browser dialer on your own Telnyx numbers, human reps on every call, and recordings with after-call AI summaries.

List hygiene before the block

The storm list is staged within a day of the event: inspection requests first, canvass contacts with signed interest second, sourced lists last and only after registry scrubbing on the 31-day cycle. Every row carries source, event date and neighborhood notes, because the opener and the crew plan both depend on them. Dedupe the canvass sheets against the phone list; the same homeowner talks to two reps and deserves one call. Your internal DNC list applies to everything, quiet hours run per lead, and the TCPA’s wireless restrictions at 47 CFR 64.1200 apply to every list, which is why nothing here autodials a cell.

Calls to homeowners who requested inspections are consumer telemarketing under the Telemarketing Sales Rule: truthful disclosures, 8 a.m. to 9 p.m. at their location, DNC rules unless consent or an established business relationship applies (16 CFR 310.4). Canvass contacts are their own compliance question: the signed inspection request is your evidence, so keep it with the record.

The calling week in blocks

Storm inquiry block, storm days and the week after. Fresh-first ordering, three lines, four facts per connect: roof age and type, what they noticed, insurance status, household timing. The window that fits the household calendar is the product. Wrong roofs (rentals, replaced last year, shaded addresses) get dispositioned in one minute; they are list hygiene, not failures.

Estimate approval block, daily. Homeowners with inspection reports in hand get the approve-and-schedule conversation: the findings, the deductible discussion inside your state’s rules, financing where it applies. These calls are logged with their own dispositions and summaries, and they convert the storm into installs. A storm that produces 300 inspections and no estimate calls produced nothing.

Off-season reactivation block, weekly. Inspection reports never converted, fall estimates, the after-the-holidays list, and the 15-year-old roof flagged last year. Each gets called with the original summary attached so the call opens with their November objection instead of a fresh pitch. The 15-year roof flagged during last year’s inspection is a spring conversation with the notes attached.

Crew planning, Friday. Neighborhood and roof-type fields from the week’s summaries become next week’s routes: which streets first, which roofs need the ladder crew, which inspections share a block. The wrong-roof dispositions keep the crew list clean.

Attempt cadence and the storm clock

Storm leads: two attempts inside seven days, varied hours, one voicemail drop, then stop. Storm interest is front-loaded and decays fast; the third-week call damages the reputation the first call built. Estimate approvals: three attempts over two weeks, then a dated re-entry when the deductible or financing question resolves. Off-season lists: one attempt per cycle per lead. Attempt caps make the policy automatic, and the do-not-call disposition drops the number from every list, which is what the homeowner asked for and what the rules require.

Dispositions that route the work

Inspection booked, estimate follow-up, insurance claim started, deductible conversation, not interested, wrong roof, unreachable, do not call. Insurance status is a field with values, not a disposition, and never a promise. “Wrong roof” carries a reason because in two years the rental changes hands and the list lives on. The disposition set is shared by temp and permanent reps in storm weeks, which is how a surge staff runs at permanent quality.

Three lines and the AI summary workflow

Three lines clear the voicemail layer while the rep takes connects. After each connect, the AI writes the transcript and pulls the fields: roof age and type, event date, insurance status, household timing, the objection, the next step. The rep verifies roof age and event date against the recording before the next dial; a misheard age books the wrong conversation. The manager’s week is ten minutes per rep: two recordings, the summary scan for insurance promises or improvised deductible answers, one coaching fix.

The recordings are also the company’s defense. When a homeowner later recalls a promised new roof or a covered deductible, the tape shows what was actually said, and the summary shows the conversation’s shape without a replay.

KPI ranges and the production benchmark

  • Dials per active calling hour: 70 to 100, median near 85 in DialBreeze production use, 3-line sessions, 90 days.
  • Dials per rep day: 450 to 700 in storm weeks, median near 600 for a full day; off-season runs 150 to 300 by design.
  • Person-connect rate: 12 to 22 percent planned, 17.8 percent production median. Storm lists run high, off-season low.
  • Inspections booked per storm week: your own baseline; list quality and event severity decide it, so set the target after two events, not before.
  • Estimate approval follow-ups completed within 14 days: 100 percent; the cadence enforces it.

The production figures come from 37,411 dials over 90 days to 2026-09-26 in DialBreeze operation, aggregate activity, not customer results and not a promise about your storm.

Compliance checklist for the roofing office

Calling hours, disclosures, DNC and registry scrubbing where the list is not your own inquiry, per the Telemarketing Sales Rule and 47 CFR 64.1200. No adjuster impersonation or implied carrier affiliation, under the FTC’s impersonation rule (16 CFR 461.3). Deductible waivers and inducements only where your state allows them, with counsel’s confirmation before storm season, not during. Damage claims that match what inspections actually find. All-party recording consent with the approved disclosure where required. Nothing here is legal advice; the state layer changes fast and belongs in a reviewed policy.

FAQ

How many dials should a roofing rep make during storm season?
Plan 70 to 100 dials per active calling hour on three lines, median near 85 measured in DialBreeze production use over 90 days. Storm days push a rep toward 500 to 700 attempts for the day; off-season blocks run smaller by design.
What connect rate should we expect on storm lists?
Hold 12 to 22 percent as the planning band, with 17.8 percent as the production median. Storm lists with a real event attached connect at the high end; off-season lists run lower. Measure storm blocks and off-season blocks separately.
How many attempts does a storm lead get?
Two attempts inside seven days of the event, at varied hours, then a dispositioned stop. Interest after a storm is front-loaded; the third week call reads as harassment, not persistence. Canvass-to-call policy for signed inspection contacts belongs in your written rules with counsel.
How do temp reps stay at permanent quality in storm weeks?
Same disposition set, same script page, and the recordings. A manager reviews a temp's first day from the tape instead of riding along, and the AI summaries keep roof facts accurate no matter who collected them.
Which numbers should the owner watch weekly?
Attempts, connects, inspections booked and estimate approvals, each over its own window. Watch abandoned-call rate when running three lines, and drop concurrency if connects outrun the rep. The wrong-roof disposition rate tells you how clean the list is.

Sources

  1. law.cornell.edu /cfr/text/16/310.4
  2. ecfr.gov /current/title-47/chapter-I/subchapter-B/part-64/subpart-L/section-64.1200
  3. law.cornell.edu /cfr/text/16/461.3

Operational guidance, not legal advice. Rules vary by state and by campaign.

Put the script to work.

Three lines, a recording of every connected call and the notes written after you hang up.

Start a 14-day trialPricing