Good incident management is about good communications. Sharing updates regularly to keep your customers (and team!) updated is a great practice to get into.
There are 2 ways you can send updates to your customers in incident.io:
If you use a public Statuspage, you can connect it to incident.io to update it in 2 clicks
Send updates using incident.io Workflows: you can send customised email updates to customers
💡We're working on our own Statuspage replacement - get in touch to tell us your wishlist!
📢 Broadcasting via Statuspage
Many organisations use Statuspage to create a public webpage that customers can refer and subscribe to to stay informed about incidents.
Once you add Statuspage to incident.io, just hit
/incident statuspage to keep your Statuspage updated with the latest information!
⛔️ Automatic Statuspage updates are on our roadmap but not available yet 😩
In the meantime, on top of our built-in nudges (see video), you could also set up a Workflow like the one below to remind your team to update Statuspage! 👇🏼
🪘 Targeted updates via incident.io
If you do not have Statuspage, or simply wish to do conditional updates, Workflows is what you're looking for! Workflows will let you, for example:
Send a customised message (email, SMS, Slack message etc.) to a specific customer when an incident affecting them is declared, updated or closed
Send an email to all your customers when an incident's severity crosses a certain threshold
Send an incident update to a Slack Connect channel with your customer
Building a Workflow is very simple! Let's use the first case above as an example 🙂
1️⃣ Pick the communication trigger
Do you want the customer communication (email, Slack message etc.) to be sent when:
An incident is created, or its details (severity, status etc.) are updated; or
When a teammate shares a status update message?
Note: you can of course use the other 2 triggers, though those tend to be for more internal uses.
In this example, we'll pick 'When an incident is created or changed', as we want to inform our customer when someone creates an incident affecting them.
2️⃣ Select some conditions that need to be met for the comms to go out
For example, you might want customers to only be informed of Critical incidents. Or you might have a Custom Field that tracks affected customers, systems or customer journeys - so you can pick a condition that fires comms only when specific values of those fields are met.
For our example, we'll use our Custom Field 'Customer' to alert our customer Globex Corporation that an incident affected them has arisen. We'll also add an extra condition to only update them if the incident is Major or Critical, so we don't make them hit the panic button for small issues.
3️⃣ Add your communication channel and personalise your message
You can now add the communication channel (or channels - you can add multiple Steps!) you'd like to use for your customer communication, and use our editor to customise your message with the right information.
For this example, we'll choose to send an email to our example client. We'll use handy variables to automatically fill out the right Affected Component and Incident Lead values
Create and you're all set 🎉
Check out the end result for our example!
If you need any help setting those up or are looking for triggers, conditions or steps you can't see, get in touch! 👋