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 for the minimum: no rule fires more often than once every 30 minutes.
• Channels — where the notification goes. At least one is required, and at most 10. For Slack you need a webhook URL: see Slack integration.

A site can have at most 20 rules. A space's alerts send at most 100 emails and 200 other notifications (Slack, Telegram, SMS) a day; past that, a rule still fires and its firing is recorded, but nothing is sent.

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 still waits 30 minutes after each firing - the minimum for every rule.

Viewing firing history

Each time a rule fires, it creates a firing instance: the responses that matched (the newest 100 when more did — the count still covers them all), 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.

A response from a survey whose responses only certain teams can read shows its score, survey and time, but not its text, and can't be opened. The teams that can read it are listed under it, each with a button to request access.