Primary on-call schedule
The on-call person in the schedule marked as Primary is notified about new incidents. You can escalate to any schedule using custom escalation policies.
When your product is critical to users, downtime isn’t an option. On-call is how you make sure the right person is always ready to respond. In an on-call schedule, on-call engineers or support specialists take turns being available to act when incidents need human attention.
When an incident happens, Better Stack notifies the current on-call person. Here's how it works in practice:
The on-call person in the schedule marked as Primary is notified about new incidents. You can escalate to any schedule using custom escalation policies.
Customize every step of the incident escalation flow using advanced escalation policies.
Configure which schedule or specific person should be notified and how to notify them. Add fallback steps, time delays, time-based rules, conditional metadata steps, and more.
Start by inviting all team members who’ll take part in on-call.
After applying changes, the calendar shows all assigned shifts.
You can:
Overrides are perfect for quickly stepping in and taking over someone's shift.
Click Create override to change who's on-call without modifying the schedule.
For more complex on-call setups, you can create multiple schedules and combine them in an escalation policy. This allows you to build advanced workflows like:
Please let us know at hello@betterstack.com.
We're happy to help! 🙏
We use cookies to authenticate users, improve the product user experience, and for personalized ads. Learn more.