What urgent outages are you having that can't be circulated with a quick "hey is ___ down for you" in a shared org channel? Also, you still have to get up and walk over to the hubbub to find out what's happening, then walk back before digging into the issue - in that time you could have just read the slack message and been fixing.
You're inventing solutions to a problem that actually worsen the issue.
edit: also, automated alerting solves literally all your problems here - and that should be an investment even if you're at a company with 100% RTO. Your first line of alert will still be digital in that case. If you're waiting to hear panicked seatmates to solve issues you're sure not worried about immediacy.
It would be nice to know every failure mode or possible reason for intervention in advance, but not always the case.
I find it interesting that there is this strong belief that how people organize and work together in certain businesses is generally done wrong. How would you know? A lot of critical interactions might not be tech-tech, but tech-business, for example.
You're inventing solutions to a problem that actually worsen the issue.
edit: also, automated alerting solves literally all your problems here - and that should be an investment even if you're at a company with 100% RTO. Your first line of alert will still be digital in that case. If you're waiting to hear panicked seatmates to solve issues you're sure not worried about immediacy.