Why Channel-Based Alerts Beat Email
Email alerts are easy to ignore. They get buried in inboxes, filtered into folders, and lost among hundreds of daily messages. When a critical service goes down, you need your team to see the alert immediately — and that means meeting them where they already are.
Slack, Microsoft Teams, and Discord are where engineering teams live. Outage alerts in these channels get instant visibility, trigger real-time discussion, and ensure the right people are looped in.
Setting Up Slack Alerts
Step 1: Create a Dedicated Channel
Create a channel specifically for outage alerts:
- Name:
#service-alertsor#outage-notifications - Purpose: "Real-time alerts from ServiceAlert.ai for cloud service status changes"
- Pin the channel so it stays visible in your sidebar
Step 2: Create a Slack Webhook
#service-alerts channelhttps://hooks.slack.com/services/T.../B.../xxx)Step 3: Configure in ServiceAlert.ai
Slack Alert Format
ServiceAlert.ai sends rich Slack messages with:
- Service name and current status
- Status change details (e.g., "Operational → Degraded")
- Direct link to the service's status page
- Timestamp of the status change
Setting Up Microsoft Teams Alerts
Step 1: Create an Alerts Channel
In your Teams workspace:
- Create a channel:
Service Alertsunder your engineering team - Set notifications to "All new posts" for team members who need immediate visibility
Step 2: Create a Teams Webhook
Step 3: Configure in ServiceAlert.ai
Teams Alert Format
Alerts appear as Adaptive Cards in Teams with:
- Color-coded status indicators
- Service name and status change
- Action button to view the full status page
Setting Up Discord Alerts
Step 1: Create a Dedicated Channel
In your Discord server:
- Create a text channel:
#service-alerts - Set permissions so only the webhook can post (optional but keeps the channel clean)
Step 2: Create a Discord Webhook
Step 3: Configure in ServiceAlert.ai
Discord Alert Format
Alerts appear as rich embeds with:
- Color-coded sidebar (green/yellow/orange/red based on severity)
- Service name and status details
- Clickable links to status pages
Best Practices for Alert Channels
1. Separate Alerts from Discussion
Keep your alert channel for alerts only. Create a separate #incident-response channel for discussion during active incidents.
2. Configure Alert Levels Wisely
Not every status change needs an alert:
- Always alert: Major outages, partial outages
- Consider alerting: Degraded performance
- Optional: Recovery notifications (useful for knowing when to stand down)
3. Use Multiple Channels
Send critical infrastructure alerts (AWS, Azure, Cloudflare) to a high-urgency channel. Send less critical service alerts to a lower-priority channel.
4. Set Up Redundancy
If Slack is your primary alert channel, what happens when Slack itself goes down? Configure at least two alert channels (e.g., Slack + email, or Teams + Discord).
Getting Started
ServiceAlert.ai supports all three platforms out of the box. Sign up for a team plan and have alerts flowing to your channels in under 5 minutes.