We started with Response to help with coordination and communication, then we launched Status Pages to keep internal and external stakeholders up to date. Today, we’re delighted to announce the final piece of the puzzle: On-call.

This is on-call as it should be. The secret's out. The world can finally know. incident.io On-call is here. Naturally, a lot of you may be wondering: why and why now. So to help answer those questions, we sat down with Chris and Pete, two of our co-founders here at incident.io to get a bit of background on this project: This episode will not only get you excited about this huge week, it'll get you pumped for what's ahead for on-call.

In this snippet, we explain what a software bug is. You can read more about this in our blog post—Incident vs bug.

In this snippet, Rob explains exactly what our latest Suggested Follow-ups feature is all about.

In this snippet, Rob explains why product spec sheets for AI builds are very different from everyday projects.

Noting follow-up actions is really important at the end of the incident response process. The problem is that it can be really easy to overlook certain actions or forget to do them entirely. With Suggested Follow-ups, this is now a thing of the past. In this episode, you'll hear from Rob, the project lead for our latest Suggested Follow-ups feature, to get a peek behind the curtain.

For a lot of teams, incident management can be a bit of a headache. It's stressful. It's not optimized. The whole process can feel like it's being held together with tape. Worst of all? Responders are the ones feeling the brunt of it. But in reality, your customers are, too. Think about it: But honestly, the situation doesn't even have to be so dire. Things can be, generally speaking, totally fine. But you recognize that there are some things that you can do to make incident response really shine at your organization.