Tune severity & noise
minThe single biggest determinant of whether your team will love or hate Intello after week one. Get this right and the product fades into the background. Get it wrong and people start ignoring alerts — which is worse than not having alerts at all.
The rule
Page on Breaking. Notify on Risky. Digest Safe.
That's the whole thing. Three tiers, three different volumes. You'll spend the rest of this page understanding why.
Why a single channel for everything fails
When you set up your first integration, every change goes to one place. After week one you'll notice the breaking-change alert is buried under fourteen safe additions. After week two your team mutes the channel.
Severity routing is how you separate "wake the on-call engineer" from "FYI on Friday."
How to set it
Open Settings → Alert preferences. You'll see a matrix of severity tiers and channels. Default it like this:
| Severity | Slack | PagerDuty | Email digest |
|---|---|---|---|
| Breaking | ✓ | ✓ | ✓ |
| Risky | ✓ | — | ✓ |
| Safe | — | — | ✓ |
That gives breaking changes a human in real time, risky changes a heads-up where work happens, and safe additions a once-a-week record.
Per-integration overrides
Sometimes a single integration needs different rules — your payments API gets escalated treatment, your analytics API gets relaxed treatment. Override at the integration level: Integration → Alert preferences. Org defaults still apply to everything else.
What counts as breaking, exactly
Intello calls a change Breaking when it would break code that worked yesterday. Concretely:
- An endpoint or operation removed.
- A required request field added (existing callers now fail validation).
- A response field removed that callers might depend on.
- A type narrowed in a way old payloads can't satisfy.
- An auth requirement tightened (e.g. a new required scope).
If the vendor explicitly versions the change away (e.g. /v3 introduces it but /v2 is unchanged), Intello tags it for the new version only.
Quiet hours and silence windows
You can suppress non-breaking alerts during defined quiet hours per channel — useful for teams with global on-call. Settings → Alert preferences → Quiet hours. Breaking changes always get through.