August 19, 2026
Your account has six kinds of alerts, not three. Five of them exist automatically the moment your account is created — you can turn each on or off, but they're not something you create from scratch. The sixth is a custom rule you set up yourself, available on Pro and above.
Fires when a device that has heartbeated at least once goes quiet for more than 24 hours. A device that's never heartbeated at all shows the Offline badge too, but — as covered in why a device shows Offline — it can't trigger this alert, since there's no "last seen" time for it to compare against. Cooldown is 24 hours per device.
Fires the moment a device registers with your account for the first time — this one's real-time, not something that waits for an hourly check. Its cooldown is only 5 minutes, since a device only ever registers once — the short window just guards against a rare duplicate-fire race, not a repeat sender.
Fires when a removed device's agent tries to check back in and gets refused. Covered in full in re-registering a device after you remove it. Its cooldown is 60 minutes, specifically because a crash-looping agent can retry every few seconds — without a cooldown that long here, you'd get flooded.
Every Sunday, one email summarizing the average score and last scan time for every active device on your account. If every device is paused or your fleet is empty that week, no digest goes out at all — it doesn't send an empty summary.
Fires the moment your subscription plan changes — real-time, not something that waits for an hourly check. It can be triggered two different ways for the same change: from the in-app Upgrade Plan modal when you switch plans yourself, or from Stripe confirming that same change moments later. Both paths are checked against each other so you only get one email per actual change, not two.
Nothing fires if your plan doesn't actually change — for example, if a billing detail updates but the plan itself stays the same.
A custom rule you create yourself: choose a percentage, and get alerted when a device's worst-scoring category — not its average — drops below that number. You can scope it to your whole fleet or a single device. Only scans from the last 72 hours count, so a device with no recent scan data won't trigger a stale alert. If your plan drops below Pro, an existing rule stops firing rather than getting deleted — it starts working again if you upgrade back.
No matter which of these six you're looking at, and no matter who on your team configures them, the email always goes to the account owner's address — never a custom address, and never a team member's own inbox. This is deliberate: the option to send alerts to a custom address is intentionally not available, specifically so this feature can't be used to relay email to an address that has nothing to do with your account.