4 ms·
Same here. I'm on support duty and have my own outage to attend to, and that's really really hard when you cannot communicate with your experts.
by majewsky 7y ago
Same here. I'm on support duty and have my own outage to attend to, and that's really really hard when you cannot communicate with your experts.
- jt2190 7y agoForgive me, but just to clarify... There is no “fallback” communication channel for your team to use?
- wil421 7y agoThere’s email, phone, whats app, group SMS, some form of WebEx or Zoom, or even a shared google doc spreadsheet with tasks for each outage. If Slack is your only forum of communication with your team it’s time to rethink your support structure and DR plans. Edit: It’s very unhelpful if I point out issues and don’t provide solutions. PagerDuty has a great article about Incident Response[1]. [1]https://response.pagerduty.com/ https://response.pagerduty.com/
- wastedhours 7y agoI don't want to sound snarky by questioning what's probably an org mandated tool usage, but I can't quite believe companies where there's only one accepted way to get in contact. Ideal would be a live conference call (phone, Skype, Hangouts etc...), but you've got SMS, email, heck, I once solved a pressing issue with my team in a Sharepoint Word document where all our comments were just new paragraphs being edited live (which actually had the handy benefit of being savable without needing to pay extra for the privilege...).
- matwood 7y agoI know it's 'old school', but we would all just get on a conference call before the fancy chat tools.