Channel types
Slack incoming webhooks
Microsoft Teams incoming webhooks
In-product alerts and dashboard indicators
Operations
Notifications & Alerting
Route savings, anomaly and action events to the teams that can approve work or verify the result.
Alert sources
New high-value savings actions
Receipt verification or regression events
Budget threshold events
Action lifecycle events
Operational anomalies
Region policy exceptions
Recommended routing model
Savings channel
New high-value opportunities, approval requests, receipt checkpoints and regressions.
Risk channel
Critical exposure context, unauthorized regions, public access changes and policy exceptions.
Platform channel
Scan failures, integration health changes, queue delays and action execution failures.
Finance channel
Verified savings receipts, export job failures, budget variance and monthly evidence handoff.
Severity guidance
Critical
Route immediately to the owning team and keep the alert visible until acknowledged.
High
Route during business hours unless the event affects production, identity or internet exposure.
Medium
Batch into daily triage where possible to avoid alert fatigue.
Low
Keep in product dashboards unless a team explicitly asks for notifications.
Next: configure routing in How to configure alerts routing and validate prerequisites in Integrations.
Get started
Find recoverable spend before the next invoice lands.
Connect one AWS, Azure or GCP scope, approve the safest savings actions, and give finance a receipt when the savings verify.
Read-only scan first. Approval gates before remediation.