A pager that knows what's a real problem and what isn't.

The problem

Alert fatigue is the #1 reason critical alarms get missed. When every flicker pages someone, people stop reading. When the same event fires fifty messages because it touched fifty devices, the inbox is useless before the issue is even understood.

How WaterTwin solves it

• Multi-condition rules. Trigger when pH drops below 6.5 and turbidity rises above 5 NTU for more than 10 minutes. Combine telemetry, weather, satellite, and time windows in a single rule.
• Severity-aware routing. Critical alerts page on-call immediately. Warnings batch into a 5-minute digest. Informational events just log.
• Root-cause grouping. When a pump station goes down, you get one alert with the cause — not fifty per-device messages.
• Inhibition. A MongoDown event silences every downstream "can't reach data" alarm until it's resolved.
• Branded email with deep links straight to the relevant dashboard. Plus optional webhook to Slack, Teams, Discord, or PagerDuty.
• Per-user notification preferences. Each user controls what reaches their inbox.

How it works

1. Build rules in the UI from the telemetry, weather, and satellite signals already in your platform.
2. Set severity. Pick the routing.
3. WaterTwin evaluates rules continuously. When a rule fires, the right people get told the right way.

What changes for the on-call team

• Pages they actually need to act on.
• Inboxes that stay readable on a busy week.
• A clear root cause in every notification — no "WaterTwin pump #47 just flagged ‘unknown'".