What to tell customers before, during, and after a storm

Ask a residential snow contractor about their worst client relationships and you will rarely hear about a property that went unserviced. You will hear about a property that was serviced, on time, correctly — and the client called anyway, angry, because they did not know it had happened. Most snow-removal complaints are not service failures. They are communication failures wearing a service failure's clothes.

The good news is that communication is far more controllable than weather. Three messages, sent at the right moments, prevent the large majority of storm-time friction.

The three messages that matter

Before: the start notice

The moment service begins at a property, tell the client. Not "we are aware of the storm" — that is noise. A specific "a crew has started service at your property" message does something psychological: it converts the client from an anxious spectator into someone who knows they are handled. It also sets the clock in their mind honestly, which matters for the next message.

During: the moving ETA

This is the message most operations get wrong, because they send a static one. "Service sometime today" tells the client nothing and invites a follow-up call. A projected arrival time — one that actually moves as the fleet moves — is fundamentally more credible. The distinction is not cosmetic. An ETA sourced from your real dispatcher reflects where vehicles actually are and what they are claiming next, so when it says forty minutes and then updates to twenty-five, the client learns to trust it. A guessed ETA that never changes teaches them to ignore it.

After: the completion record

When a property is done, send a completion notice with a timestamp — and where relevant, what was applied. This is the highest-value message of the three. It closes the loop, it answers the "did you actually service us" question before the client asks it, and it quietly becomes your evidence months later if a claim ever surfaces. A per-property completion record is customer service and legal protection in the same message.

Event-driven messages beat a clock-driven cadence. Each one tells the client something actionable; hourly updates just add noise they learn to tune out.

Automate the sending, source the truth

Nobody has time to hand-send hundreds of messages during a storm, so all three have to be automated. But automation is only as good as what it is built on. A start notice fired off a route plan is a lie the moment the plan diverges. The same three messages become trustworthy when they are triggered by real events — service actually started, this vehicle is actually en route, this property is actually complete — rather than by a schedule that assumes everything went as planned.

Respect the quiet hours and the opt-outs

Aggressive communication can backfire. A completion text at 3 a.m. is not reassuring — it is annoying, and depending on the channel and jurisdiction it can be a compliance problem. Good storm communication honors quiet hours in the client's own timezone, respects per-channel opt-outs, and sends in the contact's language. The goal is to make the client feel informed, not surveilled.

Key takeaways

• Most complaints are communication failures, not service failures — and communication is far more controllable than weather.
• Send three event-driven messages: a start notice, a moving ETA, and a completion record with a timestamp.
• ETAs must come from the real dispatcher so they move as the fleet moves; a static "sometime today" teaches clients to ignore you.
• Automate the sending but source it from real events, and honor quiet hours, opt-outs, and language.