Teams vs. On-Call Schedules vs. Direct Escalation: Which Should You Use?

Three Ways to Route Incident Notifications

When an incident fires in Alert24, your escalation policy decides who gets notified and in what order. Each step in an escalation policy targets one of three types: a team, an on-call schedule, or an individual user. Choosing the right one depends on how your organization handles incidents.

Direct User Escalation

The simplest option. You pick a specific person and they get notified.

When to use it:

• Solo founders or very small teams where one person handles everything
• Escalation steps that should always reach a specific decision-maker (e.g., "if nobody responds after 15 minutes, notify the CTO")
• Services with a single subject-matter expert

Limitations:

• That person is always on the hook — no rotation, no relief
• If they're on vacation or asleep, the alert sits unanswered
• Doesn't scale past a handful of services

On-Call Schedules

A schedule rotates responsibility among team members on a defined cadence — daily, weekly, or custom. At any given moment, exactly one person is on-call.

When to use it:

• You want 24/7 coverage without burning out a single person
• Your team is large enough to rotate (typically 3+ engineers)
• You need a clear, predictable "who's responsible right now?" answer

How it works in Alert24:

1. Create a schedule and add members
2. Set the rotation interval (e.g., weekly starting Monday 9am)
3. Add the schedule as a target in your escalation policy
4. When an incident triggers, only the current on-call person is notified

Example: A weekly rotation across 4 engineers means each person is on-call one week per month. If an incident fires on Tuesday at 2am, only that week's on-call engineer gets paged.

Teams

A team is a group of people who all get notified at the same time. There's no rotation — everyone in the team receives the alert simultaneously.

When to use it:

• Critical escalation steps where you need all hands on deck
• Cross-functional groups that should all be aware of certain incidents (e.g., a "Platform Team" or "Database Admins" group)
• As a final escalation step when the on-call person hasn't responded
• Incidents where multiple people need to coordinate a response

How it works in Alert24:

1. Create a team and add members
2. Add the team as a target in your escalation policy
3. When an incident triggers that step, every active member gets notified

Example: Your "Backend Engineers" team has 6 members. If an incident escalates to this team, all 6 people get notified at once.

Combining All Three in One Escalation Policy

The real power comes from layering these together. Here's a common pattern for a production API:

This gives you:

• Fast initial response from the person who's expecting to be paged
• Broader coverage if that person is unavailable
• Executive visibility if the incident isn't being handled

Another Pattern: Different Severity Levels

You can also create separate escalation policies for different severity levels:

Low severity (e.g., elevated error rate):

1. Notify the on-call engineer
2. No further escalation

High severity (e.g., full outage):

1. Notify the on-call engineer
2. After 3 minutes, notify the entire team
3. After 10 minutes, notify the engineering director

Which One Should You Start With?

• Just you or 1-2 people? Start with direct user escalation. You can always add schedules later.
• 3+ engineers sharing on-call? Set up an on-call schedule with weekly rotation.
• Need an "all hands" fallback? Create a team and add it as a later step in your escalation policy.

Most growing teams end up using all three. Start simple, then layer in complexity as your team and services grow.

Setting It Up in Alert24

1. Go to Incidents > Teams to create teams and add members
2. Go to Incidents > On-Call Schedules to set up rotations
3. Go to Incidents > Escalation Policies to build multi-step policies using any combination of users, teams, and schedules

The goal is simple: make sure the right people are notified at the right time, every time. Whether that's one on-call engineer at 2am or your entire platform team during a major outage, Alert24 gives you the flexibility to handle both.