All ideas

Make "VALUE" field more self-explanatory. Depending on the selected metric, there should be some kind of explicit hint what and in what format should be entered in the input. Add an example inside of the field, tooltip, etc.

Improve the naming and/or explanation.

List of devices - add user name to the extension

Provide an example or tool tip that setting 0 in Value field for poor calls would enable this type of alert.

Change "# of poor calls" to "Number of poor calls" and "% of poor calls" to "Percent of poor calls"

When user sets up an alert, there should not be a default alert severity, user should set that as part of the alert setup.

There are some options that become irrelevant under certain conditions, e.g. timeframe and alert frequency for >0 poor calls, call volume exception for number of poor calls or legs, target value for company wide target, etc.

The names of some of the endpoints aren't clear to the user. Consider a way to help the user understand what each endpoint is.

I want to be able to click on the link in the notification and be taken directly to the right page in the corresponding dashboard (and the right page of the dashboard) with the filters already pre-selected so that I can look at the data that cause...

Call volume exception is a confusing notion that becomes meaningful for only several triggers. Overall alerts functionality will benefit a lot if this advanced rule become more explained in the form of a tooltip or a notification, and a clear exam...