The 48 Hours That Decide Your Storm Season: A Call-Capacity Diagnostic for Restoration Companies

The first hard freeze hits on a Thursday night. By 6 a.m. Friday your phone has rung nineteen times. You are standing in a flooded basement in Northglenn with your own phone buzzing in your pocket while you talk a homeowner through what her insurance will and won't cover.

You have three crews. You take the calls you can, you write names on the back of an estimate pad, and you tell yourself you'll circle back Saturday. By Saturday, eleven of those nineteen homeowners have already signed with somebody else — and you never learned who six of them were.

The Leak: Your Season Is Capped by Answering, Not by Producing

Ask a restoration owner what limits their revenue during a catastrophe week and almost everyone says the same things: trucks, air movers, techs, subs.

Those are real constraints, but they're rarely the binding one. During a freeze event or a regional storm, demand arrives in a 48-hour spike and the homeowner calling you at 5:40 a.m. is calling four companies off the same Google search. The question isn't whether you could have handled the job. It's whether you were the voice that picked up.

The scale of what falls outside your reach is easy to underestimate: across service businesses, 40-60% of inbound leads arrive outside business hours, and in restoration that share climbs during exactly the events that make your year — because pipes break at 2 a.m. and roofs fail during the storm, not during the workday after it.

Why It Happens

The on-call rotation was designed for a normal Tuesday, and a catastrophe week is not a normal Tuesday.

On a normal night, one person with a forwarded phone can absorb two or three calls. During a freeze event, that same person is fielding calls while driving to a job, while inside a crawlspace, while already on another line. Calls stack. The overflow doesn't go to a second person — it goes to voicemail, and voicemail during an emergency is functionally a hang-up.

There's a second, quieter cause: the owner becomes the bottleneck by choice. In most restoration companies the owner is the best salesperson, so during a spike everything routes to them. That works at ten calls a day and collapses at fifty, and it collapses on precisely the days when the owner is also the person the crews need on site.

The last cause is invisible until you look for it. Nobody is logging the calls that were missed. There is no record of the six homeowners you never identified, so the loss never shows up in any report you review on Monday.

The Diagnostic: Six Questions to Run on Your Last Storm

This takes an afternoon and costs nothing. Run it on your most recent spike week while the records still exist.

1. Pull the raw call log for the 72 hours around the event

Not your CRM — your carrier's log or your phone system's report. You want every inbound call, answered and unanswered, with timestamps.

Now count three things: total inbound, total answered, and total that rang out or went to voicemail. The gap between column one and column two is the number nobody in your company has ever seen. Write it on a whiteboard. It is the single most useful figure you will produce this quarter.

2. Match calls against jobs

Take the answered calls and mark which ones became jobs. Then take the unanswered ones and check whether that number ever called back or ever appears in your system at all.

The callback rate is the number that tends to change owners' minds. Most assume a homeowner in an emergency will try again. In practice, a large share never do — they were already dialing the next result before your voicemail greeting finished.

3. Time-stamp your first human response

For every lead that did convert, calculate minutes from first contact to first live human conversation. Then sort that list and look at the slowest quarter.

You're checking one thing: is your response time during a spike meaningfully worse than on a normal week? If it is, you've found the constraint, and it isn't trucks.

Be honest about what counts as a response. An auto-reply text that says "we got your message" is not a human conversation, and homeowners don't treat it as one. The clock stops when somebody answers the question they actually asked, which during a loss is almost always some version of "how fast can you get here and what does this cost me."

4. Count how many calls hit one person

Pull the on-call phone's log for the peak 12 hours. How many calls did a single human handle, and what was the longest stretch where two calls arrived within five minutes of each other?

Any time two emergency calls overlap, one of them was waiting. Count those overlaps. That's your true simultaneous-capacity number, and it's almost always one.

One is a fine number on a Tuesday in September. It is a catastrophic number during the 48 hours that produce a disproportionate share of your annual revenue, and no hiring plan fixes it — you cannot staff a second and third after-hours body for events that happen four times a year.

5. Separate the emergency from the reconstruction conversation

Mitigation calls get answered because they're loud and obvious. The follow-on conversation — the rebuild, the contents, the scope expansion — happens on a normal weekday when everyone is buried digging out from the event.

Look at your last spike and calculate what share of mitigation jobs converted to reconstruction. If that number sagged after a busy week, the spike didn't just cost you the missed calls. It cost you margin on the jobs you did win.

6. Ask your crews what they turned away

Field techs field calls too, and they make judgment calls about capacity that never reach you. Ask three techs what they told homeowners during the peak. You'll usually find at least one who was quietly triaging your pipeline on your behalf without knowing the economics. A tech who tells a homeowner "we're slammed, try us next week" is making a revenue decision with none of the information required to make it.

The Proof

If those six answers point the same direction, the underlying dynamic is not unique to your market.

Roughly 78% of sales go to whoever responds first, and leads contacted within five minutes are 21x more likely to qualify than those contacted after thirty minutes. In a catastrophe week the effect compresses further, because the homeowner's decision window isn't days — it's however long it takes them to reach a company that answers. The competitor who won those eleven jobs did not out-sell you. They out-answered you while you were in a crawlspace in Northglenn.

Where This Goes Next

The diagnostic above is yours to run, and it's worth running whether or not you ever change anything, because it converts a vague sense of "that week was chaos" into a countable number of lost jobs.

If the number turns out to be large, the fix isn't a bigger on-call rotation — you already know how that performs at 50 calls a day. It's giving yourself unlimited simultaneous answering capacity. That's what James does inside Tykon's system: it picks up every call and form fill in under 60-90 seconds no matter how many arrive at once, qualifies the loss type and urgency, books the inspection, escalates true emergencies to your on-call tech with the details already captured, and follows up on the reconstruction conversation your team is too buried to have. Afterward, it asks for the review.

Start with step one. Pull the 72-hour call log from your last freeze or storm event and find the gap between calls received and calls answered. If that gap is small, you're already winning your spikes. If it isn't, you just found the number that caps your season.