Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,465,219
Community Members
 
Community Events
176
Community Groups

Service Desk Reflections: Outages and Downtime

I remember my days of working at a National IT Service Desk very clearly. Lots of fun was had with my team, and we provided excellent customer service. However on those days when a server crashed or a system went down it was challenging to receive call after call from discouraged, frustrated and sometimes angry clients when there was nothing we could do to fix their problem on the spot.

20144.jpgangry-customers-service-tips.jpg

We pulled together as a team, and were always empathetic with our clients. As a strategy to lower the queue volumes, we also asked that they pass on the outage message to others in their unit, so that we didn't receive multiple calls from the same unit. We also had our Service Desk Lead send out an outage message, unless of course email was also affected at the same time. 

We always got through it but ensured we regrouped as a team after the outage to boost morale and talk about the process and anything we could have done differently or that would help us for a future occurrence.

Wishing we had known about #HUGOPS back then, it definitely would have come in handy :)

hugops-blog-image@4x-1-1560x760.png

Having also been on the other side of the coin as the client, I was extremely patient with IT Service Desk staff, and took advantage of the downtime to work on things that were on the bottom of my pile (that didn't involve a computer), or having an impromptu team stand-up, or taking an earlier lunch. I also took the time to make phone calls and walked over to a colleague's desk to ask them something, rather than the new norm of sending emails to colleagues that are a cubicle away.

What are your stories of downtime? And secondly, do you have #HUGOPS in your organization?

 

2 comments

As a manager for multiple apps and websites - downtime happens. What makes the experience bearable is being proactive. I've witnessed a full server crash, had to wait to reboot and then recover/restore files. At the time, it helped to be upfront with our clients - actually emailing them a "heads up, our system is down and your site is currently affected". 

Our clients were upset but understood that with technology, things like this happen. They actually appreciated that we brought it to their attention - rather than finding out and then having to call/email us. 

Being proactive is a game-changer. Don't wait for the problem to come to you. 

Like Fernando Bordallo likes this

Thanks so much for sharing @carrie_eandm - being proactive makes a world of difference. I do like the under promise, over deliver approach as well, it has helped me manage expectations, and when things are back up and running sooner clients are much happier than if we say it will be back up at 2pm and it's not up for hours later. I haven't had to use that approach often, but it is helpful to have in the toolbox.

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events