You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi there, I'm Jake and I'm a Customer Success Manager on the Statuspage team. We're posting a series of blogs and prompts to help you improve your incident communication process, learn from other folks in the community, and answer any questions you may have on the topics we've chosen...follow the #incident-comms-tips tag to see them all!
---
Incidents (hopefully) don’t happen often, but when they do, you need to be ready. This involves defining what an incident means to your organization, identifying which channels you'll use to communicate, defining an owner for the communication process, and creating pre-written templates.
What has your team done to prepare for incidents?
Jake Bartlett
Atlassian TeamCustomer Success Manager
14 accepted answers
2 comments