We've added the ability to escalate to other people and teams during an incident

In an incident, at the boundaries of your knowledge and need help to figure something out? We've all been there.

Fear no more. You can use incident.io to directly page users in Slack via /incident escalate — no need to log in to PagerDuty, search around and find the right place. You can page:

• An escalation policy: a way to notify on-call users about an incident that relates to a service or system, and have the right people notified at the right time.
• Any user on PagerDuty: sometimes, you know that special someone that can help you out when you get stuck. Escalate to them directly, and bring them in to help.

<aside> ❓ Use VictorOps? Don't you worry — we'll have you covered soon. We've started with a single provider to get ourselves happy with the flow. We'll add other integrations over the next few weeks.

</aside>

Getting it set up 🤝

You can add PagerDuty to incident.io in just a few clicks. To get started, head over to the Integrations section of your account settings page.

Pressing "Add PagerDuty" will start an OAuth flow, which will give incident.io permission to create incidents on your behalf.

Press Authorize to connect PagerDuty to incident.io. Unfortunately, PagerDuty doesn't give us the option to request any more granular permissions than these.

If that was successful, you're all set up with PagerDuty! Try it in an incident channel with /incident escalate 🎉

Things to know 💭

All escalations will originate from the email of the user that connected PagerDuty to your incident.io account. This is unfortunately a limitation of the PagerDuty API. When you create an incident, it must always be associated with the email of a valid PagerDuty user, as bots (i.e., us) are not allowed to create incidents on their own. If you'd rather not have incidents attached to a user's email, you could create a dedicated account in PagerDuty and connect that to incident.io. However, be aware PagerDuty will charge you for the extra seat.