Alerts
Slack and email alerts the moment a theme spikes, regresses, or a user turns at-risk.
Sentriment watches every theme's baseline and every user's health 24/7. Alerts are how it taps you on the shoulder — in Slack or by email — the moment something needs a human. Set them up under Settings → Alerts: add a channel, then toggle which events it receives.
What you can be alerted on
#| Parameter | In | Description |
|---|---|---|
Spikes | event | A theme suddenly surges past its own baseline — you hear about a breaking issue while it's minutes old, not after tickets pile up. |
Regressions | event | A resolved theme starts collecting fresh reports — the fix didn't stick, or a release broke it again. |
At-risk users | event | An identified user's health drops into at-risk or critical. The alert links to their full history so CS can reach out. |
Verdict changes | event | A tracked Ask question flips its answer — e.g. pricing sentiment moving from mixed to negative. |
Channels & testing
#Add a Slack incoming webhook or an email address, then use the green per-event chips on each channel row to control exactly which alerts it gets. A Send test button fires a sample alert through the real delivery path so you can confirm setup end-to-end. A channel that fails repeatedly is auto-disabled with a one-click re-enable.
Tip
Route spikes and regressions to your engineering channel, at-risk users to your CS channel. At-risk alerts need identified users with a health score; verdict changes need a tracked question.