Notification Throttling
Notification Throttling is designed to help prevent unnecessary alert fatigue while ensuring that active events continue to receive the attention they require. With this enhancement, Stat Temp now delivers a more controlled, predictable, and efficient flow of notifications for events that remain active over multiple days.
This improvement supports operational clarity, reduces repeated messages, and keeps important information visible without overwhelming end users.
Why This Matters
Long-running alerts can result in high-volume, repeated messaging across multiple channels. Notification Throttling ensures that alerts remain meaningful and actionable by:
- Reducing excessive and redundant notifications
- Providing a predictable communication rhythm
- Keeping awareness high throughout the entire duration of an event
- Ensuring all users remain informed on extended-duration events
How Notification Throttling Works
Notification delivery is based on the number of days an alert remains active. The alert continues to function normally — only the frequency of communication changes.
|
Days Active |
Notification Behavior |
Recipients |
Delivery Timing |
|---|---|---|---|
| Day 1–5 | Normal notification frequency and channel delivery | All users in the notification chain | As triggered |
| Day 6–10 | One notification per day, per user, per channel | All users in the notification chain | Sent at 1:00 PM EST |
| Day 11+ | One email per day, per user | All users in the notification chain | Sent at 1:00 PM EST |
Channels included: email, SMS text message, and phone call (where applicable)
What’s Included in Throttled Emails
Each throttling-stage email contains:
- Notification name
- Duration (how long the alert has been active)
- Direct link to the affected sensor
- Explanation of throttling stage
- Option to acknowledge the alert
Acknowledging an alert will continue to function as expected and will prevent further notifications for that user