Skip to content

Email alerts

When an incident opens, UpAll emails your team. When it resolves, UpAll emails your team again. There is nothing to configure — and nothing to misconfigure.

What triggers a message

Every incident, from every source, at every severity: check-driven Outages, certificate Info and Degraded incidents, and manual incidents written by staff. Each fires two messages over its life — one on open, one on resolve — so the inbox thread reads as a complete story: what broke, and when it was over. See how incidents open and close.

Who receives it

All active workspace staff: every admin and every engineer. Deactivated accounts get nothing. Client users never receive alert emails — their window into incidents is the portal and status pages.

Each recipient gets the message in their own interface language: your Arabic-first engineer and your English-first admin read the same alert, each in their language (switching language and theme).

What's in the message

Enough to triage from a phone without opening the console:

  • the client and site — who is affected;
  • the monitor — what is affected;
  • the start time, in the workspace timezone;
  • the last recorded error — what the check actually saw;
  • a link straight to the incident in the console.

The honest scope

Alerting today is email, and email only. There is no per-monitor recipient routing — every alert goes to the whole staff list — and there are no quiet hours or schedules. That shape has a real upside for a small monitoring team: no incident can fall into a routing gap, and nobody wonders whether they were on the right distribution list. The practical consequence: keep your staff roster to people who should be seeing alerts, and deactivate accounts that shouldn't — see invite your team.

WhatsApp and SMS alerts are planned but not yet available. If a channel isn't listed here, UpAll doesn't send on it.

One more email: the stale digest

Incidents aren't the only thing that reaches your inbox. When monitors stop producing fresh results, staff get a once-per-episode digest listing them — a different failure mode with its own article: stale monitors.