1. Home
  2. Guides
  3. Restoration and water damage firms
  4. Playbook

Playbookfor restoration and water damage firms

Restoration 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 restoration office runs its calling: emergency callbacks first, estimate follow-up second, referral partner blocks third, and storm lists worked carefully. It details list hygiene, an attempt cadence that fits emergency work, dispatch-ready dispositions, three-line sessions with AI summaries, and KPI ranges to plan around.

Step by step

  1. 1

    Work overnight emergency leads before anything else

    Open the morning with the unworked emergency inquiries, newest first, three lines. The five dispatch questions on every connect, and the disposition the moment the call ends so the crew can roll.

  2. 2

    Run the estimate follow-up block midday

    Call open mold and reconstruction estimates with the original scope notes attached. The fork that matters is insurance versus self-pay; the disposition captures it.

  3. 3

    Work the referral partner block weekly

    Call plumbers, agents and property managers monthly: a check-in, what they need from you, and confirmation the after-hours number is current. Log commitments and card orders.

  4. 4

    Run storm lists only inside your rules

    Work your own customers and genuine inquiries first, street by street where you already have relationships. Scrub cold lists against the national DNC and keep the pitch to inspection offers.

  5. 5

    Review summaries before dispatch and before quotes

    Verify damage details and insurance status against recordings, fix dispositions, and hand dispatch a crew sheet that reflects the calls, not a sticky note.

What this playbook covers

A restoration office’s phone work is four motions: emergency callbacks that decide the job, estimate follow-ups that close the quote, partner development that feeds next quarter, and storm response that tests all of it. This playbook structures the day and week so the emergency lead never waits behind a marketing list, and so every call produces a record dispatch and the office can act on. It assumes a three-line browser dialer on your own Telnyx numbers, coordinators making the calls, and recordings with after-call AI summaries.

List hygiene, sorted by urgency

Emergency leads are their own queue and never share a list with marketing work. Overnight forms sit at the top of the morning block, worked newest first, with the inquiry time on every row. The established business relationship from an inquiry covers 90 days under the FTC Telemarketing Sales Rule (16 CFR 310.2); after that, the registry and consent rules govern.

Estimate lists carry their own context: the scope, the insurance fork, the homeowner’s stated concern. Partner lists carry the relationship history. Storm lists are assembled per event from your own customers first, then genuine inquiries, then sourced lists scrubbed against the National DNC Registry on the 31-day cycle. Your internal DNC list applies to all of it, quiet hours run per lead, and the TCPA’s wireless restrictions at 47 CFR 64.1200 apply to every list, which is why the whole operation is human-dialed.

The calling day in blocks

Emergency callback block, first thing and all day. Overnight inquiries, then same-day forms as they arrive. Five dispatch questions per connect, disposition immediately, crew rolling. This block is not scheduled around others; others are scheduled around it.

Estimate follow-up block, midday, one hour. Open mold and reconstruction quotes, called with the original summary attached. The opener references the actual hesitation: “you mentioned the crawlspace readings worried you.” Insurance leads get documentation discipline; self-pay leads get a price conversation and a start date. Treating them as one pile loses both.

Partner block, weekly, 45 minutes. Plumbers, realtors, insurance agents, property managers. The call asks what they need and confirms the after-hours number. Dispositions: sent a job this month, asked for lunch, needs cards, dormant. Over a quarter this list tells you which relationships are real.

Storm block, per event. Own customers first, street by street where relationships exist, then inquiries, then scrubbed lists with an inspection offer. The summaries become the triage sheet: active leaks first, exposed structures second, cosmetic claims third, ranked for scheduling before out-of-town competitors eat the market.

Attempt cadence, fitted to the work

Emergency leads: attempt immediately, again within the hour, once more the same day, then a dispositioned cooldown. Estimates: three attempts over two weeks, varied hours, one voicemail. Partners: monthly touches, quarterly at minimum for active referrers. Storm lists: two attempts inside seven days of the event, then stop; a storm lead three weeks old is a canvass archive item, not a queue. Attempt caps enforce all of it, and a do-not-call disposition removes the number from every list.

Dispositions dispatch and the office can act on

Emergency dispatch, inspection scheduled, estimate follow-up, claim filed, self-pay, already has contractor, no damage wrong list, left voicemail, do not call. The partner side adds sent a job, dormant, needs cards. Insurance status is a field with four values: none, filed, adjuster assigned, dispute. It is never a promise and never a disposition, which keeps the claims conversation inside the lines the state requires.

Three lines and the AI summary workflow

Three lines per coordinator mean the morning emergency queue clears before competitors finish their first cup, and the voicemail layer stops eating the estimate block. After each connect, the AI writes the transcript and pulls the dispatch fields: damage, rooms, water status, structure, insurance status, urgency, access window, the homeowner’s concern. The coordinator checks rooms and structure against the recording before release, because a misheard room count loads the wrong truck.

The office review is fast: summaries scanned before dispatch in the morning, summaries scanned before quotes go out in the afternoon, two recordings per coordinator per week for coaching. Storm weeks add one check: any summary where insurance status reads like a coverage promise gets pulled and coached the same day.

KPI ranges and the production benchmark

Plan around ranges; hold the emergency numbers absolute.

  • Response time on fresh emergency leads: attempt inside 15 minutes when the form arrives during business hours, and first position in the morning queue overnight. No asterisks on this one.
  • Dials per active calling hour: 70 to 100, median near 85 in DialBreeze production use, 3-line sessions, 90 days.
  • Dials per coordinator day: 400 to 650, median near 600 for a full day; storm days run higher.
  • Person-connect rate: 12 to 22 percent planned, 17.8 percent production median. Emergency queues connect far higher; storm lists lower.
  • Estimates followed up within 14 days: 100 percent of open quotes get their call; the cadence enforces it.

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

Compliance checklist for the restoration office

Callbacks to your own inquiries ride the 90-day relationship; cold consumer marketing needs registry scrubbing, calling hours and immediate opt-out honoring. Wireless restrictions under 47 CFR 64.1200 apply to every list, so no prerecorded blasts and no autodialed cell calls. Document damage; never negotiate, interpret or predict coverage unless your state licenses you to, and never imply carrier affiliation. All-party recording consent via the approved disclosure in the states that require it. Nothing here is legal advice; the claims-conduct rules vary by state and belong in your written policy with counsel’s review.

FAQ

How many dials should a restoration coordinator make per hour?
Plan 70 to 100 dials per active calling hour on three lines, with a median near 85 measured in DialBreeze production use over 90 days. Emergency callback blocks run shorter and faster; the measure that matters there is response time on the fresh lead, not volume.
What connect rate should we expect?
Hold 12 to 22 percent as the planning band, with 17.8 percent as the production median. Emergency leads connect high because the homeowner is waiting for a call; storm lists run lower. Measure emergency response separately from block volume.
How fast should an emergency inquiry get called back?
Inside an hour whenever staffing allows, and first in the morning queue when the form arrives overnight. The lead submitted to three companies hires the first credible callback. Speed is the product in this trade.
How do we keep storm calling defensible?
Work your own customers first, then documented inquiries, then carefully sourced lists with registry scrubbing and an honest inspection offer. Never imply coverage outcomes or damage you have not seen. When in doubt on a list, counsel reviews it before a block runs.
What should the AI summaries feed?
Dispatch, first: damage, rooms, water status, access window. Then estimating: scope and the homeowner's fixations. Then partner development: which partners sent work this quarter. Verify details against the recording before a truck rolls.

Sources

  1. law.cornell.edu /cfr/text/16/310.2
  2. ecfr.gov /current/title-47/chapter-I/subchapter-B/part-64/subpart-L/section-64.1200
  3. ftc.gov /business-guidance/resources/complying-telemarketing-sales-rule

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