Operations | Monitoring | ITSM | DevOps | Cloud

When your team shares one support number, someone has to decide who gets the calls when customers need help after hours. And if your team rotates on-call responsibilities weekly, which is common in IT (SRE, DevOps, ITOps, etc), clinical and field engineering teams, you’ve probably relied on manual call forwarding at some point. On paper, it seems straightforward: update the forwarding number each week to point to the person who’s on call. In practice? It often turns into a scramble.

OpsGenie is shutting down. And Atlassian recommends migrating to Jira Service Management (JSM). But if you’re not sure JSM is the right fit for your team’s on-call management needs, this review will help you decide. I signed up for JSM and put it through real-world testing. I created on-call schedules, rotations, and overrides. Then, I reviewed JSM’s on-call management across 4 key criteria. For each criterion, I shared what I liked and what I didn’t.

When your company has multiple offices or operational sites – whether that’s across the U.S. or around the world – getting alerts to the right team isn’t as easy as just checking who’s on duty. Events can come from a wide range of sources tied to different physical locations, time zones, or even separate departments, and not every alert is meant for every team. Let’s say your company has operations in New York, Dallas, and San Francisco.

Being on-call is one of the toughest responsibilities in IT. Engineers must be ready to respond at any hour, often balancing the stress of urgent incidents with everyday operations. But nothing drains energy faster than duplicate alerts. When one problem triggers dozens of notifications across different devices or monitoring tools, on-call teams spend valuable time sifting through noise instead of resolving the real issue.

Providing continuous, high-quality care takes more than clinical expertise—it depends on well-designed physician on call schedules that balance patient safety, physician wellness, and operational efficiency. Whether you manage a residency program or a multi-specialty group, creating an effective physician call schedule—or a broader provider on call schedule—is critical for 24/7 coverage and clinician well-being.

Being “on call” sounds simple: you’re not actively working, but you need to be available if something goes wrong. The real question many employees ask is: do you actually get paid for being on call? The short answer is: it depends. Your pay may hinge on labor laws, company policies, and how restricted your time really is.

At incident.io, we are building a product that our users rely on 24/7, all year round. This means it is crucial that it is always working, and that is where our on-call rotation comes in. We believe that everyone should be on-call because it tightens the feedback loop between shipping new features and maintaining what we have, leading to more pragmatic engineering decisions.

Managing developer on-call rotations and escalations isn't just about who gets woken up at 2 a.m. — it's about ensuring reliability, minimizing downtime, and scaling operational excellence. With so many tools out there, choosing the right on-call solution can be tough. We've analyzed 10 of the most trusted on-call scheduling platforms in 2025 — comparing usability, pricing, integrations, automation, and support — to help you choose the best tool for your engineering or DevOps team.

You’re likely here because you heard the news: Atlassian ended new sales for OpsGenie on June 4, 2025, with a complete shutdown scheduled for April 2027. For years, OpsGenie has been the backbone of on-call management for countless teams. It might have been your team’s trusted solution too. But now, that chapter is closing. The pressure to find an OpsGenie alternative for on-call is real. However, you can’t just pick any tool and hope it works for your team.