The more people using incident.io in your organisation, the better it gets. A key part of that is letting your colleagues know what incident.io is, and how they should use it. We've prepared some communications below to make your life easier.

If you don't manage to let your colleagues know, we'll introduce ourselves the first time they interact with incident.io — such as joining an incident channel or creating their first incident — so you'll still be covered.

Introducing incident.io

Copy and paste the below into Slack, and edit as you like!

👋🏼 Hello!

We're now using incident.io to help us respond, review and learn from our incidents.

What is incident.io and why are we using it? It brings our incident response process directly into Slack, making it easier to communicate and collaborate. You can use it to:

• Run an incident: assign roles, post updates, escalate to others, track actions
• Prepare a postmortem: it automatically exports a postmortem to save you time
• Track follow-up actions to ensure they get done: it exports actions from incidents to our issue tracker

The end result is that our incidents run more smoothly. We can spend more time focusing on the problem, rather than the process.

What should I do next? Here's the key things to know:

• To stay up to date with all of the incidents that are being created, join #incidents.
• To kick off an incident when you see something going wrong, just type /incident and incident.io will guide you through the rest of the process.
• If you'd like to practice with an incident, you can create your own sandbox incident by typing /incident test.

Where should I go to learn more? If you want to learn more, head over to their Help Centre.

If you ever need support on using the product, you can send them a message using Intercom on the incident.io dashboard (press the bubble in the bottom right of the screen), or email [email protected] and they'll get straight back to you!