Restoration company call script for emergency lead callbacks

The opener that wins the first hour

Restoration is a response-time business, and the lead knows it. The homeowner standing on wet carpet submitted to three companies, and the winner is usually the first callback that sounds organized. The opener does three things in fifteen seconds: identifies the exact submission (“you submitted a water damage request last night about a supply line”), states the role (“I am the coordinator who gets crews out”), and asks the only question that outranks everything else: is the water off. That question tells the homeowner this caller has done this before.

The dispatch questions, in order

Water off. What is wet, room by room, and any sagging or spreading. Slab or crawlspace. Insurance claim status. Who can be there and when. The order is triage: safety first, scope second, access third. The musty smell the homeowner volunteers is worth logging verbatim, because it is a mold anxiety the tech should address on arrival, not discover.

Every answer becomes a field. In DialBreeze the AI summary writes them from the recording: damage, structure, insurance status, urgency, access window, and the homeowner’s stated concern. Dispatch reads the summary and loads the truck: extractors and air movers sized to two rooms on a slab, not a guess and not a callback to ask how bad it is.

The insurance line you do not cross

Every restoration call brushes insurance, and this is where companies generate complaints and license problems. The script holds the line out loud: “I cannot answer that honestly, and I would not trust anyone who does over the phone.” Then it pivots to what the coordinator can honestly do: explain what documentation the carrier will want, describe the mitigation process, and put the homeowner’s mind at ease about the deductible rather than the coverage.

The reason is practical as well as legal. In several states, negotiating or interpreting a policyholder’s claim requires a public adjuster license, and misrepresenting what a policy covers is a serious offense in every state. Insurance status stays a field on the record: claim not filed, filed, adjuster assigned, dispute. It is not a promise, and the recording proves it never was one.

The objections and the lines that hold

“Will my insurance cover this”

The honest refusal, every time. Coverage is the carrier’s call, the adjuster makes it against the policy, and anyone who promises otherwise over the phone is telling you what you want to hear. Then give the caller what actually helps: documentation, process, and speed. The homeowner remembers the coordinator who told the truth and moved fast.

“What will this cost me”

Never quote mitigation into a phone. Readings vary, equipment counts vary, and a phone number becomes a ceiling the invoice cannot survive. The script’s answer: a tech takes readings for free, the estimate is in writing, and if a claim is filed the homeowner’s exposure is generally the deductible. That is honest, complete, and books the visit.

“I have a plumber coming already”

Good, and not a conflict. Coordinate: mitigation and repair are different jobs, and the water sitting in carpet while the plumber orders parts is still causing damage. Offer to talk to the plumber directly. This objection is usually a scheduling question in disguise.

“Another restoration company already called”

Move fast, stay classy. Ask whether they have a crew committed with a time. If yes, wish them well and leave your number; storm markets are small and grace ages well. If the answer is vague, the 8:30 window with a named tech and a text confirmation usually wins on professionalism alone.

The voicemail variant

Company, role, the exact request they submitted, a direct callback line, and one calm promise: a coordinator can call back within the hour. No scare language about mold, no coverage talk. Emergency homeowners return calls from the company that sounded like it had a process, and the disposition is left voicemail with the attempt logged; if the lead came from an emergency form, a second attempt inside the hour is appropriate and the cadence says so.

Logging before the next dial

Disposition: emergency dispatch, inspection scheduled, estimate follow-up, claim filed, self-pay, already has contractor, no damage wrong list, do not call. Then verify the summary: rooms, structure type, insurance status against the recording. A misheard room count sends the wrong equipment, and the tech’s morning depends on the coordinator’s ten seconds of checking.

Compliance lines that frame this script

Callbacks to your own emergency inquiries generally ride an established business relationship under the FTC Telemarketing Sales Rule, which treats an inquiry within 90 days as a relationship (16 CFR 310.2). Cold storm lists are a different category: national DNC scrubbing, calling hours, immediate opt-out honoring. The TCPA’s restrictions on prerecorded and autodialed calls to wireless numbers apply regardless, see 47 CFR 64.1200, which is why every call here is human-dialed. State rules on public adjusting and claims conduct sit on top: document damage, never promise coverage outcomes. Several states require all-party consent to record, so use the approved disclosure. Nothing here is legal advice.

Coaching the script from recordings

Pull one dispatch call and one insurance-question call per coordinator per week. Listen for the water-off question first, the five dispatch questions in order, and whether the coverage line held. The AI summary flags the second category: any summary where the insurance field carries a promise instead of a status is a coaching call, and the recording settles what was actually said. One fix per week keeps a storm-season temp crew at permanent-team quality.