Before, during, and after a storm

The storm from the customer's chair

Here's what a customer actually experiences across one event — how the pieces fit into a single, calm journey.

Before

The customer's world is quiet, and that's the point. Their properties, settings, and history sit in the portal, and their alert preferences are set. Nothing needs their attention until snow starts.

During

As the storm runs, the experience comes alive:

• A status alert lets them know a pass has started on their event.
• They open the portal — or the live tracking embed — and watch the fleet working, machines moving in real time.
• A live ETA tells them when their property is likely to be cleared, updating as the swarm actually unfolds.
• An en-route alert with an ETA lands when a machine is on its way.
• A service-complete alert confirms their property is done.

After

When the storm's over, the record is already there:

• Service-visit history shows exactly what was done, with materials and photos.
• The run-log embed gives a per-property timeline they can revisit or show a tenant.

The honest bottom line

None of these individual pieces is unique to Snowmass — competitors have tracking, history, and alerts. What ties them together is the live dispatch engine underneath: the ETA moves because the fleet really is self-dispatching, and the whole journey runs on real data instead of a dispatcher's best guess.