Notifications
Configure alerts and notification preferences to keep your team and customers informed about service status changes and incidents.
Notification Types
UpReport provides multiple notification channels to ensure the right people get the right information at the right time.
👥 Team Notifications
Comprehensive internal alerts for your team regarding all system activity.
- • Incidents & Maintenance (Full lifecycle)
- • Includes reminders and status updates
- • Covers both Public and Internal events
- • Component status changes (Public & Internal)
📧 Customer Notifications
Public notifications sent to status page subscribers.
- • Public Incident updates
- • Public Maintenance announcements
- • Service restoration confirmations
- • Subscribe to specific components/groups
Notification Channels
Standard notification method for all plans.
- • Team member alerts
- • Subscriber notifications
- • Incident summaries
Slack
Collaborate with your team directly in Slack.
- • Channel notifications
- • Custom alert rules
- • Interactive updates
SMS
Urgent alerts for critical updates.
- • Critical incident alerts
- • High-priority status changes
- • Team notifications only
Get notifications directly in WhatsApp.
- • Instant delivery
- • Secure messaging
- • Global reach
PagerDuty
Enterprise incident response integration.
- • Trigger incidents
- • On-call routing
- • Incident mapping
Setting Up Notifications
1 Organization Integrations
Configure shared notification channels for your entire team (Slack, PagerDuty).
- Go to Dashboard → Notifications
- Select the Channels tab
- Click Connect on your desired platform (e.g., Slack) or Add Configuration for PagerDuty
- Follow the prompts to authorize or configure the integration
- Once connected, you can configure specific alert rules (e.g., only critical incidents in #general)
2 Personal Preferences
Manage your own email and personal notification settings.
- Go to Account Settings (click your avatar)
- Select the Notifications tab
- Toggle email notifications for Incidents and Maintenance updates
- These settings apply only to you, not the rest of the team
💡 Granular Alert Rules
For each integration channel, you can configure exactly which events trigger a notification:
- Incident created / updated / resolved
- Maintenance scheduled / in progress
- Component status changes
- Check failures (up/down)
Customer Notification Management
Manage your status page subscribers and their preferences.
Subscriber Management
✅ Subscription Options
Subscribers receive notifications for Public Incidents and Maintenance only.
- • Subscribe to all updates
- • Select specific components or groups
- • Receive incident & maintenance alerts for selected items
- Note: Direct component status changes (e.g. Up/Down) do not trigger subscriber alerts unless associated with an incident.
🔧 Admin Controls
As an admin, you can manage the subscriber list:
- • View list of active subscribers
- • Remove subscribers from the list
- • Export subscriber data
Notification Limits by Plan
| Plan | Email Notifications | Slack & PagerDuty | SMS & WhatsApp |
|---|---|---|---|
| Launch | 100 / month | Slack Only | ✗ |
| Professional | 1,000 / month | Unlimited | 50 / month |
| Business | 4,000 / month | Unlimited | 200 / month |
| Enterprise | Custom Volume | Unlimited | Custom Volume |
📊 Understanding Notification Counts
"Notifications" in the plan limits refers primarily to emails sent to subscribers. If you have 50 subscribers and send an incident update, that counts as 50 email notifications. SMS and WhatsApp messages have their own separate monthly quotas as shown above.
Need more notifications? You can increase your monthly quotas with paid add-ons available in your billing settings.
Notification Best Practices
✅ Do
- • Route Alerts Strategically: Send critical incidents to PagerDuty/SMS and general updates to Slack #channels to reduce noise.
- • Use Components: Encourage subscribers to select specific components so they only get relevant email updates.
- • Automate Status Updates: Configure UpReport's built-in monitoring checks to automatically update component status when services go down.
- • Keep Teams Aligned: Use internal notes in incidents to keep your team informed via Slack without emailing all customers.
❌ Don't
- • Alert Everyone for Everything: Avoid sending "All Components" notifications for minor issues affecting only one service.
- • Duplicate Alerts: Don't enable both Email AND Slack/SMS for every single event unless it's a critical outage.
- • Ignore Internal Channels: Don't rely solely on public status page updates for internal team communication.
- • Overload SMS: Save SMS/WhatsApp quotas for true emergencies to avoid hitting monthly limits too quickly.