Alerts

Alerts are under System > Alerts — a rule that watches a measurement (call quality, volume, a threshold on some object) and fires an action when it crosses a line. Who actually receives it is configured on three linked pages: Contacts, Groups and Schedules.

The Alerts list

Open System > Alerts to see every rule, its type, what it checks, the object it watches and whether it is enabled — with links to Contacts, Groups and Schedules at the top.

Alerts: the list, empty on this test system.

Creating an alert

New alert opens one form with three parts: what to measure, the thresholds that trigger and clear it, and what happens when it does.

New alert: what is measured, the thresholds, and the actions.
FieldMeaning
Alert typeWhat is measured — e.g. ASR (answer-seizure ratio), ACD (average call duration), PDD (post-dial delay), total/answered calls, a price sum, simultaneous calls, HGC (channel-group usage), a provider registration, or a group alert that combines other alerts.
Check typeWhat kind of object this watches: user, provider, device, destination, destination group, or the system as a whole.
Object (check_data)Which one — an ID for a device/provider/user, a dialling prefix for a destination, or all.
Alert if ≥ / Alert if ≤The value that triggers the alert.
Clear if ≤ / Clear if ≥ / Clear after (min.)What brings it back to normal, and how long it must hold before the alert clears.
Count period (min.)The rolling window the measurement is taken over.
Ignore if calls < / >Skip the alert when there is too little (or too much) call volume to make the ratio meaningful.
Email on alert/clear, SMS on alert/clearSend a notification through the object's Email/SMS group (below) when the alert fires, and again when it clears.
Disable object on alert / Enable object on clearAutomatically disable the watched device/provider/user while the alert is active, and re-enable it once it clears.
Notify the userFor a user or device alert, also notify that customer, not just staff.
Email/SMS groupWhich alert group (below) receives the email/SMS actions above.

Who gets notified: contacts, groups, schedules

An alert's email/SMS actions do not name a person directly — they point at a group, which bundles contacts and gates delivery through a schedule:

Alert groups: a name, an email schedule, an SMS schedule, and monthly caps.
Alert contacts: the people, with their own hourly/daily email caps.
Alert schedules: named time windows a group can attach to its email or SMS side.

Opening a schedule lets you add periods — a day type (all days, workdays, weekend, or one named day), a time range, and ON/OFF. Opening a group lets you add existing contacts to it. The chain is: Alert → picks an Email/SMS group → the group lists its contacts and, separately, an email schedule and an SMS schedule that decide when those contacts may be messaged.

Note

This is separate from Notifications under Settings, which reports a fixed catalogue of system events (Asterisk down, database unreachable, and so on) to ntfy.sh channels. Alerts here are user-defined rules on calls, users, providers and devices, delivered by email or SMS.

Warning

This test system had no alerts, contacts, groups or schedules configured — every screenshot above shows an empty list or a blank new-item form. No alert, contact, group or schedule was created or saved to write this page.

Check

Open System > Alerts and confirm the Status column reads Enabled for a rule that should be active; open the group it points at and confirm it has at least one contact and, if quiet hours matter, a schedule.