You’ve created a status page that reflects your brand’s look and feel, now let it shine through subscriber emails, too! Email customization is one of our most requested features, so we’re thrilled to announce that it’s now live for all Statuspage customers.
We caught up with three Statuspage customers to learn how their teams come together for awesome incident response. Want to learn from more incident response teams or submit your own tips and stories for us to feature? Head over to our new HugOps hub.
Downtime happens. While it can certainly be chaotic and stressful, if handled properly, it can also be a chance to build customer trust and loyalty. The way you respond to and communicate around incidents and downtime tells customers a lot about what you value. Therefore, it’s essential to show customers you value them by communicating early, often, and candidly during an incident.
You’ve just resolved an incident – congrats! High-fives and #HugOps all around.
Every company depends on tools that help them do their jobs. HR tools, CRMs, chat & collaboration tools, business intelligence tools, marketing automation tools… the list goes on. Bringing another tool into the mix involves approval processes, buy-in from execs, and the occasional boss-nudging for her credit card.
Last month, Atlassian attended SITS 2018, The Service Desk and IT Show. We staffed a busy booth, demoing our software and learning about challenges facing the support managers, analysts, IT directors, and CTOs in attendance. Our own Principal Solutions Engineer, Paul Buffington, also spoke to an overflowing crowd about best practices for incident management. We sat down with Paul to get his thoughts on some of the most noteworthy ITSM trends.
Over the years here at Statuspage we’ve probably heard every version of the open source vs. paid status page argument. While we’re obviously fans of the SaaS model, we also know there are a lot of advantages to an open source status page for a lot of teams. We’ve even recommended that route to some potential customers we thought would have a better experience hosting their own open source page.
An incident postmortem is an excellent framework for learning from incidents and turning problems into progress. It also builds trust with customers, colleagues, and end users (basically the folks affected by the incident) and lets them know your team is working to minimize future incidents and impact.
Nothing puts a drag on IT service teams and customer support teams like answering the same question across multiple tickets. Outages and incidents have a way of sending these teams an avalanche of duplicate tickets. During a service interruption, tickets start flying in, the team can’t keep up, and end users have a bad experience made even worse.
We’ve talked about the increasingly-interconnected nature of cloud tools and the domino-goes-crashing-down effect thatcan happen when just one critical service has downtime. Web uptime is more important than ever, and it’s critical that these services we all rely on are up and running as often as possible.
