That was the only thing that popped into my mind when I thoughtlessly gave in to the annoying “Windows has updated, please restart computer” message that kept on popping up at the corner of my workstation’s remote desktop. Since I knew (by experience at home) that the darned thing would keep on bugging me every fifteen minutes for a restart, I thought of forestalling the annoyance and allowed it to reboot.
Then I remembered that what it was rebooting wasn’t the computer we were using in the office, but a system somewhere in the US remotely accessed by our networks.
Needless to say, it turned what might have been another normal (if slow) day at work into what some people could consider a waste of a morning. Since the remote system rebooted, I could no longer access the programs needed to even answer calls during the shift. What’s worse, I wasn’t the only one affected; the guy I was sharing my network profile with, who came on earlier than me and had by that time been in for several hours, also couldn’t access his remote desktop anymore, and had to stop taking calls. In a flash, workforce lost two of its active agents for the day, and I’d imagine that they weren’t happy about that fact, even if the shift could be considered a “slow day”.
Naturally, I kept my mouth shut that it was my fault.
Although the problem was reported to technical support, and a ticket eventually filed, there was no resolution forthcoming for the rest of the day. As for us, the two affected agents, we spent the morning literally catching some shut-eye, which wasn’t all that uncomfortable given the large assortment of seat pillows scattered about our area. By eleven o’clock, workforce decided to let us off early, since we weren’t doing anything anyway.
Ugh. I’d be lying if I didn’t feel guilty about the whole affair, regardless of the unexpected bonus (not taking in calls at all for the day) that resulted from it.