When a month of work arrives before lunch
A storm comes through — high winds, a hard freeze, a power outage, a downpour — and within hours the phone is a wall of calls. Every one is urgent, every one is a customer in distress, and there are ten times more of them than you have techs to send. This isn't the gradual swing of seasonal demand, which you can staff and schedule against because you see it coming for weeks. A surge is a wall: a month of demand compressed into a day, arriving all at once, with no runway. Handled well, it's the best reputation-building stretch your business will have all year, the moment customers remember you showed up when everyone else couldn't. Handled badly, it's a self-inflicted disaster of broken promises, no-shows, and one-star reviews that outlast the weather by months.
The difference between those two outcomes isn't how many techs you have — in a real surge you'll never have enough. It's whether you triage deliberately or just let the chaos dispatch itself.
The surge breaks the thing that worked yesterday
The reason a surge is so dangerous is that your normal dispatch logic inverts. On an ordinary day you absorb the occasional same-day emergency without wrecking the schedule — one or two urgent calls slot into a board that mostly holds. In a surge there is no normal board to protect; the emergencies are the board, and the failure mode flips from "the emergency disrupts the plan" to "there's no plan and everything is an emergency." Three things break at once:
- First-come dispatch becomes wrong. Answering calls in the order they ring means a minor inconvenience booked at 8am gets a tech before a genuinely dangerous situation that called at 8:20. Order-of-arrival is fine on a normal day and actively harmful in a surge.
- Promises outrun capacity. Whoever's answering phones, desperate to reassure panicked customers, promises arrival times the field can't possibly hit. Every one of those promises becomes a broken one a few hours later, and a broken promise in a crisis is the review that haunts you.
- Your existing customers get buried. The flood of new emergency callers swamps the people who were already on your board for today — the customers who'll still be here long after the storm-chasers are gone.
You can't out-staff this. You can only out-triage it.
Triage by severity, not by sequence
The core discipline of surge dispatch is sorting by how bad it is, not by who called first. Before anyone gets dispatched, every incoming call gets sorted into rough tiers:
- Genuine danger or major damage — anything threatening safety or causing active, worsening damage. These jump the line regardless of when they called. This is where your trucks go first.
- Real urgency, no immediate danger — a serious problem that needs same-day attention but isn't getting worse by the minute. The bulk of the surge usually lands here.
- Can honestly wait — uncomfortable or annoying, but safe to schedule for tomorrow or the day after. Booking these out is a kindness when it's honest, because it frees your trucks for the people in real trouble.
The tool that makes this survivable is a shared, live board. In Hosting Field, dispatch shows the whole day's jobs and every tech's status in real time, so as the surge lands you can see the entire picture — who's free, who's mid-job, where everyone is — and assign the next genuine emergency to the right tech instead of guessing. When you sort the queue by priority on a board everyone can see, the worst situations rise to the top and the trucks follow them. Without that shared view, dispatch fragments into whoever shouted loudest on the phone, and severity stops driving anything.
The promise you keep beats the promise you wish you could make
The single most reputation-saving move in a surge is to stop promising arrival times you can't keep. A panicked customer wants to hear "we'll be there in an hour," and the worst thing you can do is say it when you can't. An honest "we have you on the list; given the storm volume, realistically it's tomorrow morning, and we'll keep you posted" beats a comforting lie that becomes a no-show by nightfall, because the no-show is what gets written up, not the honest wait.
This is where keeping customers informed earns its keep at maximum stakes. The same customer-communication discipline that prevents ordinary surprises becomes survival in a surge: a customer who's been told the truth about the wait and gets an honest update will forgive a long delay, while one who was promised an hour and waited a day will torch you in a review no matter how good the eventual repair was. And don't abandon the people who were already on your board — the customers scheduled before the storm hit. Surfacing a where-is-my-tech status for them keeps the existing relationships intact while the new flood gets triaged, so you don't win ten storm-chasers and lose the regular who's been with you five years.
After the wall: capture what just happened
A surge doesn't end when the calls stop — it leaves a debris field of half-finished work, parts ordered, and customers waiting on a callback. The shops that come out ahead are the ones that captured the chaos as it happened instead of trying to reconstruct it afterward. Jobs created on the fly during the surge, with their real status on the board, mean nothing falls through the cracks once the dust settles: the multi-visit jobs blocked on parts are tracked, the customers you promised a return to are on the list, and the callbacks from work done fast under pressure are caught early. A surge handled with no record is a surge that generates its own second wave of dropped balls a week later: the work you did under pressure becoming the complaints you field next.
What to measure
- Promise-keeping rate during the surge — the share of arrival commitments you actually hit. In a surge, an honest "tomorrow" you keep is worth more than an "in an hour" you miss; this is the number that protects your reviews.
- Existing-customer disruption — how many already-scheduled jobs got bumped or dropped while you chased the flood. Winning storm-chasers while losing your base is a bad trade you won't see unless you watch for it.
- Surge backlog clearance time — how long after the storm before the board is back to normal. A long tail of unfinished surge work is where callbacks and dropped follow-ups breed.
A storm surge is the rare moment when demand exceeds anything you could have staffed for, and that's exactly why the operations that handle it well win so decisively. You can't send a truck to everyone at once, but you can send them to the right people first, tell everyone the truth about the wait, and capture the chaos so nothing rots in the aftermath. Triage by severity on a board everyone can see, keep the promises you actually make, protect the customers who were already yours, and the worst day of the year becomes the one your customers remember you for.