Emergency
Frozen lateral, main line split, controller dead after a storm
- Short triage: address, water shutoff status, zone count if known
- Click-to-call with tracking swap when numbers publish
- SMS bridge to on-call tech when you wire the integration
Licensed · Backflow-certified · Medfield & neighbors
This Growth-template scaffold shows how we split emergency dispatch from seasonal routing—so controllers see intent before they call the customer back, with quote paths that work one-handed from a truck cab.
Stock photography stands in for your install gallery—on a real build we wire your project photos, truck shots, and HOA-friendly proof.
Events stay labeled per path in analytics—so once PostHog (or your stack) is live, owners can see which line fills the schedule without blending gusher calls with tune-up season.
Emergency
Seasonal routing
01
Homeowners self-select urgency so your tech knows if they need a shovel or a controller swap kit.
02
License, insurance, and backflow partners sit above the fold—especially for townships with strict reuse rules.
03
Events are named per path so reporting compares apples to apples once campaigns spin up.
Booked a blowout without describing every zone twice. The form asked what mattered for my townhouse loop.
Emergency path made it obvious we were not calling a pool company. Tech texted before he turned onto our street.
Photos on the seasonal page matched what showed up—felt like the crew my neighbor referred.
Ready for your trucks?
This page is a scaffold. Your logos, towns, controller lines, and CRM hooks replace every placeholder once scope is locked. Colors above come from a token map—swap the map, keep the layout.