Underestimating how important your incident communication is can cause major problems for your business, and huge damage to your brand.
When you're faced with incidents in your organisation, it's sometimes difficult to know exactly how to respond or communicate issues. For many businesses, this results in a lack of communication altogether - only sending out a quick 'send to all' email once the issue been resolved.
If you don't know what's happening just yet, you should still communicate that a service is down and make them aware you're investigating the issue. Telling users when to expect the next update also helps to build trust during an incident. → Click to Tweet.
Pre-configuring templates for sending out communication makes it much easier to get the message out to your team in a hurry. Rather than worrying about the wording of your message, you can edit out a template and hit send in a matter of seconds.
Ensure that every member of your team knows what their role is when an incident arises. → Click to Tweet. Who's responsibility is it to send out communication to the right people? Is there someone who approves incidents notifications before they're sent?
Ensure that members of your team take ownership - without it, incident communications becomes an afterthought.
Tailor your incident planning towards your users, try to allow them to receive notifications that work for them, on the channels they use. → Click to Tweet. This will help to increase engagement from users, and keep productivity up.
When sending out communications, the most important aspect is that you let users know what's happening fast. Brevity is cruicial when you send notifications to avoid information overload - keep it simple with the key points they need to know.
If you're currently using email to send out incident notifications, do you have a backup communication channel if your email experiences downtime? When responding to incidents, ensure that you've thought of possible situations that might impact on your ability to carry out your incident plan. → Click to Tweet.
Having a centralised tool for viewing all active incidents is key for transparancy across the organisation. Plus, it empowers users to be able to check on the incidents themselves without needing to raise tickets with service desk.
A cloud-based incident communication tool means that you don't need to rely on having access to systems that might experience downtime. This means you can continue to communicate on any channel, whenever you need to, which is one less thing to worry about when an incident arises.
A cloud-based incident communication tool means that you don't need to rely on having access to systems that might experience downtime.
When a major incident happens make sure that you review your process, how many users viewed their notification? Did you update users when you said you would do? Spend a little bit of time to make a detailed review of what went well and what could be improved.
After you've reviewed an incident, it's crucial you update your incident management plan to reflect the lessons learned from the previous events. → Click to Tweet. After these amendments are made it's also a good idea to test out your plan again.
Be proactive in your incident responses, ensure that there is a clear communication plan in place that can be executed effectively when an incident arises. With clear ownership and responsibilities set out, your incident communications can create a positive experience from those within your organisation, ultimately boosting confidence and internal brand image.
Want to learn more? Check out this collection of incident planning articles.
Klaxon is an intuitive, simple platform to provide fast and powerful communications when you're faced with major incidents. Schedule your personalised demo today and try it free for 30 days.More Posts