The wind worked all night, and by the time you're up on your first roof of the morning the phone's already gone off four times in your pocket. You can't grab it. You're two stories up with a bundle of shingles and both hands full, and the caller waits maybe fifteen seconds before hanging up and dialing the next roofer on the list.
That's the ugly math of a nor'easter. One storm can hand you a week's worth of work in a single afternoon, and most of it goes to whoever picks up. The jobs you miss don't leave a polite voicemail and wait around. They call the next guy, and the next, until somebody answers.
Here's what nobody mentions: you don't have to choose between the customer on the ground and the dozen people trying to reach you. A little setup, done before the season turns, lets a system catch every call, ask a couple of smart questions, and text people back while you keep working. It won't climb the ladder for you. It buys you time, which during a storm is the one thing you're short on.
Why a missed call during a storm costs more
On a normal Tuesday, a missed call is no big deal. The person leaves a message or tries again after lunch. During a storm, that same caller has water coming through a ceiling and a phone full of roofers to try. They aren't leaving a voicemail. They're working down a list, and the first calm voice that answers usually gets the job.
So the real cost of a ring-out isn't one lost call. It's the whole job, plus the referral that job would've sent your way come spring. Figure a handful of those in one bad afternoon and you can see why the phone matters more than almost anything else you own.
The two or three questions that sort a real emergency
Not every storm call is an emergency, and treating them all the same is how you end up driving across three towns for a loose gutter while someone's kitchen floods. The fix is a short script, the same one you'd run in your own head, handed to something that never gets rattled.
Keep it to three questions, no more. Something like this:
- Is water coming into the house right now, or is it damage you can see while the inside stays dry?
- Where's it getting in, and how big is the area (a drip in one spot, or a ceiling starting to sag)?
- What's the address, and is anyone there now?
An AI phone assistant (a voice system that answers, listens, and talks back in plain language) can run those questions, jot the answers, and sort the caller into get there today or book for later this week. It doesn't diagnose anything. It sorts, which is exactly what you'd be doing in the truck if you had a free hand.
How text-back catches the callers you still can't take
Even with something answering, a real crush can still stack up calls faster than one line can handle. That's where missed-call text-back earns its keep. The instant a call goes unanswered, an automatic text goes out, in your name, within seconds.
Your text reads like you actually wrote it: "Hi, this is Dave's Roofing. We're slammed after the storm and out on jobs. Reply with your address and what's happening and we'll get you in line. If water's coming in right now, text the word URGENT."
This does two jobs at once. It keeps the caller from dialing the next roofer, because they've already heard back from a real-sounding business. And it turns a frantic phone call into a text thread you can handle between jobs, at a stoplight, or over coffee, on your schedule instead of theirs.
Holding a fair line for the job you already promised
A storm surge carries one real danger: you chase the loudest new caller and quietly abandon the customer who booked you last week. That's how you win one job and burn two. The way out is simple, set your line rules before the wind picks up, so nobody's making promises in a panic.
Spelled out, the rules might look like this:
- Active interior water or a safety issue: same day, worked in as capacity allows.
- Visible damage, nothing coming in: booked for the next open slot, usually within the week.
- Jobs already on the schedule: honored, not bumped, unless the customer reschedules themselves.
Write that once and the system follows it every single time, which is more than any of us manage at 4 PM on the worst day of the month. The customer already on your calendar keeps their spot. The genuine emergency jumps the line. Everyone else gets a fair, honest place in the queue.
Be honest about what it can't do
None of this fixes a roof. The assistant can't look at a photo and tell you the flashing's shot, it can't promise a homeowner you'll be there by two, and it sure can't climb the ladder. It answers, asks, sorts, books, and texts. That's the whole of it.
It'll get things wrong now and then, too. A caller mumbles the address, or phrases something in a way that trips it up. That's why every urgent flag should land on your phone as a text or a call, not sit quietly in a system waiting for you to notice. Treat it like a sharp new dispatcher on their first storm, great at the routine, still needs you for the judgment calls.
Worth doing this week
You don't need all of this wired up before the next front rolls through. Start with the pieces that catch the most calls.
- Turn on missed-call text-back. Most phone systems and answering services offer it, and this one change alone catches the callers you'd otherwise lose.
- Write your three triage questions on an index card. If you can't sort a call with them yourself, no software can either.
- Set your line rules, one plain sentence per tier, so the system knows what jumps ahead and what waits.
- Record a short, real greeting so storm callers hear an actual business, not a robot reading a menu.
- Test it on yourself. Call your own number, don't answer, and see what a stranded homeowner would get. Fix whatever sounds off.
If wiring it together yourself sounds like one more thing you don't have time for, that's the sort of setup we handle at Massachusetts AI Agency, and it's usually live in a day or two, often for under a couple hundred a month. Either way, get something answering before the first real blow. Come January, you'll be glad the phone kept working while you couldn't.