What a storm does to your phones

After a hailstorm, the phones fill faster than your office can answer them, and your estimators are up on roofs. Every unanswered inquiry goes to the next roofer on the homeowner's list. For a few days, the whole county is calling the same contractors.

The surge also mixes good leads with weak ones. Picture one hour. A homeowner has water on the ceiling. A past customer in the storm path wants a check. A neighbor wants a number. A property manager has six buildings. Without a way to sort them, the first call gets the first slot, whatever it is worth.

Today the sorting happens in someone's head. One person plays voicemails in order, calls back whoever sounds most urgent and loses track of the rest. That works on an ordinary week. A storm week breaks it.

Qualification fixes that. It means asking a few set questions, scoring the answers against your rules and routing each lead to the right next step before anyone sits on hold. The goal is simple. The lead that needs an inspection first gets it first.

Storm work is also a trust test. Homeowners are stressed and comparing contractors. Fast, honest, low-pressure replies set you apart. Automation can keep that standard at three in the afternoon on day two, when your office is worn out.

The first text in five questions

The first reply, by text or voice, collects only what you need to book an inspection. Keep it short. A homeowner in the middle of storm cleanup will not fill in a long form.

  1. Confirm the property address and the best number to reach the homeowner.
  2. Ask what they saw: missing shingles, granules in the gutters, a leak inside, or nothing yet.
  3. Ask whether water is coming in right now, which flags an active leak for a person.
  4. Ask for the roof's rough age and type if they know it, and whether a claim is filed.
  5. Offer two real inspection windows from your calendar and book the one they pick.

That is the whole conversation. The answers land on the lead record, and any photos the homeowner texts back attach to it. The confirmation names the estimator, the window and what the visit involves, so the homeowner knows what to expect. The estimator opens one page with everything needed before the visit.

Three details make this work. The assistant says plainly that it is automated and gives a number a person answers. It accepts photos but never requires them to book. And it stops the moment the homeowner asks for a person or says stop.

Text suits the first reply because homeowners are busy and their phones are in hand. For calls, a voice assistant can ask the same five questions, so a caller who prefers talking gets the same screening.

Score and route every lead

Scoring turns those answers into an order of work. The table shows one way to sort a surge. Change the rows to fit your market, your crews and your own definition of a priority.

A sample scoring and routing table
Lead typeSignalsNext stepOwner
Active leakWater coming in right nowPriority call and an offer of emergency tarpingOffice lead
Past customer in the storm pathIn your records, in a hit zip codeCheck-in text and a first-day inspection offerEstimator
Visible damage, claim filed or plannedMissing shingles, a leak stain or a claim numberInspection booked within the daily capEstimator
Possible damage, no claim yetHomeowner unsure, roof age knownInspection offered on the next open dateAutomation, then estimator
Commercial or multi-buildingProperty manager, several addressesA call from a person the same dayOwner or sales lead
Price shopper or outside your areaAsks only for a number, or the address is outside your territoryA polite reply, a waitlist spot or a referral noteAutomation

Keep the scoring simple. Four signals are enough to start: damage reported, active leak, claim status and distance to your service area. Add points for a past customer or a referral, and subtract for an address outside your territory. A simple score you can explain beats a clever one nobody trusts.

The score is only an order of work. It never decides who deserves a roof, and anyone who asks for a person gets one. Your office lead reviews the scoring rules before launch and again after the first storm, when real leads show where the rules are off.

Past customers deserve a note of their own. A text that says you served their home and can check it after the storm lands differently from a cold message. The system finds them by address in your records, and you approve the wording. The storm response workflow shows how that outreach and the inbound surge fit together.

What a voicemail costs after a storm

Say a hailstorm brings 90 inquiries in four days. Your office answers 40 live, and the other 50 reach voicemail. Say you win one signed job for every four inspections you book, and the average roof job is worth $12,000.

Now suppose an instant text-back reaches those 50 callers and books 20 of them for inspection. Twenty inspections at one signed job in four is five jobs. Five times $12,000 is $60,000 in work that voicemail was sending to other roofers.

Those numbers are assumptions, so test them against your last storm. Count the calls that went to voicemail, how many called back and how many signed with someone else. If only four of the 50 would have booked, that is one signed job and $12,000 in revenue. Apply your own margin to see how fast a build in the $1,000 to $5,000 range pays back.

Weak leads cost time too. Say each visit costs an estimator an hour including the drive. Ten visits to price shoppers and out-of-area addresses is ten hours, more than a full day of one estimator's time. Scoring and the waitlist point those hours at leads with real damage.

Speed matters inside the surge too. A homeowner who gets a text within a minute and a booked window soon after has less reason to keep calling around. Say that lifts bookings by two inspections among your 40 live callers. Two inspections is half a signed job on these numbers, or $6,000.

Set an inspection cap and give honest dates

A surge can book more inspections than your estimators can run. Say you have two estimators who can each inspect six roofs a day, which is 12 a day. If 60 inspections are booked, the last homeowner waits five days. A promise of tomorrow would have been false.

Set a daily cap in the calendar and let the system offer only the dates that exist. When the calendar fills, it tells the homeowner the next open date and offers a spot on the waitlist. Nobody is promised a slot that cannot be kept.

The waitlist is a list, not a promise. When a slot opens, the system texts the next homeowner first. Anyone who has waited more than two days gets a personal call from the office.

Honest dates protect your reputation in the weeks when every homeowner is comparing roofers. They also protect your crews. Production schedules real work, and nobody inherits a promise made in a rush. The crew scheduling workflow shows how inspection dates and install dates share one calendar.

Route by territory as well. The system assigns each lead to the estimator who covers that zip code, so drives stay short and nobody crosses the county for one inspection.

Raise the cap when you add inspectors or borrow help, and lower it when weather closes the roofs. One person owns the number each morning. The system reads it, and every offered date follows from it.

What automated messages must never say

Storm work comes with rules. What a contractor may say or do around an insurance claim differs by state, so build your messages to match the rules where you work. Have whoever advises your company read the wording before launch.

  • Never promise that insurance will pay for a roof, or call damage storm damage, before someone has inspected it.
  • Never quote a price or a payout in a text. Pricing comes after the inspection.
  • Never pressure a homeowner to sign or to file a claim. The message offers an inspection and leaves it there.
  • Always say that an automated assistant is writing, and give a number a person answers.
  • Stop all messages the moment a homeowner says stop, and log that they did.

Photos need the same care. The system can accept photos and attach them to the lead. It should not label them as hail damage or wind damage, because that is the estimator's call after the inspection.

Respect quiet hours too. Storm texts at midnight read as pressure. Set sending hours that match your office, and tell homeowners who write after hours when to expect a reply.

Keep a log of every message. For each number, record the first text, the reply and any opt-out. If a homeowner ever disputes a message, the log shows what was sent and when.

Build it before the next storm

A storm leaves no time to build. The work happens in the quiet weeks before it, and a storm switch turns the surge flow on when the weather arrives.

  1. Pull the inquiries from your last storm and note which ones booked, which stalled and which never got an answer.
  2. Write the scoring rules and the three message templates: first reply, booking confirmation and waitlist.
  3. Connect your phone line, text number and web form to one lead record in your CRM, with the calendar and the daily cap.
  4. Set the storm switch: a weather alert for your service area, or a button the office lead presses to turn the surge flow on.
  5. Test with a batch of last storm's real inquiries, and have your office lead read every reply.
  6. Run a drill with five test leads, including an active leak and a commercial roof, and check that each reaches the right person.

Decide who flips the switch and who turns it off. A surge flow that stays on after the rush ends keeps texting homeowners you can no longer inspect. The office lead owns both ends, and the system logs each change.

Name the people behind the flags too. The office lead takes active leaks, the sales lead takes commercial properties and the owner takes anything upset. Each flag arrives with the full thread, so nobody asks the homeowner to repeat the story.

Plan for failure too. If the calendar or CRM is unreachable, the system still answers and writes each lead to a backup list. It texts the office lead that the list needs attention. A surge is the worst time to find a silent failure.

The integrations are ordinary. The system reads your CRM and calendar, writes each lead and booking back to them and keeps the phone and text history on the record. If a tool has no clean connection point, the free walkthrough finds that out before anything is quoted.

What to do this week

Pull your last storm's inquiry list and count three things: calls that reached voicemail, texts that sat unanswered for a day and inspections you booked. The gap between the first two and the third is your surge leak.

Then write your scoring table in plain words, with a priority for each lead type and an owner for each. Show it to your office lead and your best estimator, and fix what they dislike. That page is the hardest part of the build, and it is yours to write.

If you have time left, draft the three messages in your own words: the first reply, the booking confirmation and the waitlist note. Read them aloud, and cut anything you would not say at a front door.

When you want it built, a free consultation and workflow walkthrough comes first. A written quote and statement of work follow. Automation of this kind typically takes a few days to a month and runs $1,000 to $5,000, flat rate or $50 an hour. The lead qualification workflow lists what a build covers, and the quote follow-up workflow picks up after the inspection.