5 ms·
At a previous company I had a very similar problem, and eventually converted an old SIM-less phone into my Slack device and mounted it in a stand on my desk. (S
by trynewideas 4y ago
At a previous company I had a very similar problem, and eventually converted an old SIM-less phone into my Slack device and mounted it in a stand on my desk. (Slack was not deemed a sensitive company app that had to run on company devices, which considering the access to customer channels and prod-affecting chatops features seemed stupid, but I'm not IT.)
I could physically turn Slack off by turning the phone off, and the only other way to get through to me was async, via email or in tickets.
A coworker I trusted had my personal cell number and texted me when something was actually urgent, which happened twice in 6 months.
- trynewideas 4y agoAlso I'd really strongly suggest that you push your company away from a team @ alias and toward a team channel. The only groups that should have an @ alias that punches through notification settings are on-call, and if your role IS on-call then no amount of Slack changes will reduce interrupts.
- throwaway91021 4y agoPeople create one @ alias per team and also many others for subteams or temporary project teams, etc. There is one for oncall too. Every time one of those aliases gets tagged, I get a notification, an orange counter or sometimes messages from Slackbot asks me to join the channels. *> punches through notification settings I'd like to specify which aliases should not be ignored but I can't in Slack, unless I'm missing something. Also, disabling the oragen counter is not possible (even for muted channels).
- Spivasart 4y ago[dead]