How do alerts work in SuperLedger?

Alerts tell you when something needs attention — a spam surge, a location that's gone quiet, a drop in call volume, or a critical transferred call. Open Alerts in the sidebar to see them. SuperLedger checks for alerts automatically every 15 minutes, and you choose who gets emailed for each rule. Alerts resolve on their own when the issue clears, or you can acknowledge or snooze them.

Before you start:

The Alerts page at a glance

The page has these tabs:

TabWhat's there
Active AlertsEverything currently needing attention, with a count badge.
HistoryResolved alerts.
Flagged CallersYour watchlist of suspicious numbers (details).
Alert RulesCreate and edit rules, including who gets emailed (details).
Alert ReplayAn advanced testing view for re-running detectors.

On Active Alerts you can switch the audience between Operations (system health — outages, capture failures, quality regressions, abuse) and Client Health (churn signals — volume, engagement, and value drops). Use Group to collapse repeated alerts of the same type, and Search alerts... to filter.

What you can do with an alert

  • Acknowledge — mark that you've seen it.
  • Snooze — silence it for a set window; it re-surfaces automatically if the issue is still happening when the window passes.
  • Mark as false positive — silences that exact alert for 30 days for everyone in your org. Use this only when the alert is wrong — if it was real and you fixed it, let it auto-resolve or Acknowledge it instead.

What happens next

Most alerts auto-resolve once the condition clears (spike-type alerts within about 15 minutes; slower trend alerts within 24 hours), and move to History. New and recovered alerts can email the recipients you set on the rule, and post to Slack if you've connected it.

How it works

Checks run automatically every 15 minutes against rolling time windows. To cut noise, SuperLedger rate-limits repeat alerts of the same type and honors your false-positive feedback for 30 days. Muting a location's monitoring stops its alerts entirely.

← Back to Help Center