Alerts

Alerts watch your incoming responses and notify you (Telegram, Slack, or email) when a rule's condition is met — instead of you having to check the dashboard yourself. Create and manage them from Alerts.

Creating a rule

Each rule has:

• Name — shown in notifications and the firing history.
• Scope — either all surveys on the domain, or one specific survey.
• Time window — Hour, Day, or Week. This is how far back the rule looks each time it's evaluated (e.g. a Day window checks responses from the last 24 hours), not a fixed schedule.
• Condition — at least N responses within the time window (optionally filtered by an operator against the survey's main rating — e.g. "at least 3 responses with rating ≤ 2"). If you don't set an operator/value, it simply counts every response in the window.
• Throttle — an optional number of hours the rule must wait after firing before it's allowed to fire again, even if the condition is still met. Leave it empty to allow firing every time the condition is met.
• Channels — where the notification goes. At least one is required.

Throttle, precisely

Throttle prevents notification spam from a rule whose condition stays true for a while — once a rule fires, it won't fire again until throttleHours have passed since its last firing, even if new matching responses keep arriving in the meantime. Without a throttle, a rule can fire again on every single evaluation where its condition is met.

Viewing firing history

Each time a rule fires, it creates a firing instance: the exact responses that matched, the reason it fired, and a timestamp. Find these in the Alerts page's firing history — open one to see full details, jump to the matching responses, and acknowledge it once you've handled it.