Alert routing

/dashboard/alerts/routing is the matrix editor that decides where alerts are sent. Rows are alert types (Instance Down, License Expiry, etc.); columns are channels (Mobile push, Email, PSA, Slack, Teams, Webhook, AI voice call).

Each cell is a checkbox: when checked, alerts of that type and severity are pushed to that channel.

Channels

• Mobile push — sends to anyone with the mobile app + push notifications enabled. Free on every plan.
• Email — to the owner + anyone in the email recipient list.
• PSA ticket — creates a ticket in your configured PSA (ConnectWise, Autotask, HaloPSA, Syncro). Pro+.
• Slack / Teams / Webhook — outbound webhook to your configured endpoint. Pro+.
• AI voice call (Pro+) — Dialora-powered phone call to the on-call user. Used for the most-critical events (Instance Down, Service Down).

Per-severity rules

Most types let you set rules differently for Critical vs Warning vs Info. Example: send Instance Down to every channel, but License Threshold only to email + Slack.

Quiet hours

Below the matrix, you can configure quiet hours where pushes are suppressed (8 PM → 8 AM in your tenant's timezone, for example). PSA tickets and emails always fire — the suppression is just for intrusive channels.

Per-instance overrides

Beyond the global matrix, each instance can override routing in its own settings. Use this when one customer wants different escalation than the rest of the fleet.

Recipient list

Email and AI voice channels need recipients. Configure who in Settings → Team → Notification recipients.

Test it

The fastest way to verify routing is to fire a simulated alert from an instance's quick-actions card. Fires through the full routing chain. See First alert.