better-stack-on-calllisted

# Better Stack On-Call Management ## Overview Better Stack Uptime includes integrated on-call scheduling that determines who gets paged when a monitor fails. Schedules define rotation patterns, and notification/escalation policies define how and when responders are alerted (via phone, SMS, email, or push). For MSPs, on-call is commonly configured per customer team, with separate schedules for each client's SLA requirements. ## Key Concepts ### Schedule Structure Better Stack schedules define: - **Members** - Responders in the rotation - **Rotation** - Daily, weekly, or custom patterns - **Time zone** - Critical for follow-the-sun setups - **Start date** - When the rotation begins ### Notification (Escalation) Policies Policies define the alert cascade when a monitor goes down: | Step | Description | |------|-------------| | 1 | Page the on-call schedule via phone, SMS, email, push | | 2 (after timeout) | Escalate to a secondary schedule or individual | | 3 (after timeout) | Escalate to team manager or broader group | Better Stack calls these "notification policies" rather than "escalation policies", but they serve the same purpose. ### Notification Methods - **Phone call** - Voice call for critical alerts - **SMS** - Text message notification - **Email** - Email alert with incident details - **Push notification** - Mobile app notification - **Slack/Teams** - Integration-based notifications ### Integration with Monitors Monitors are linked to notification policies