My first fucking thought. I’m still waiting on helpdesk to respond to an issue I’ve already chased down to a registry key because I’m not allowed workstation admin privileges. 🙄. Which I’m fine with but more than a week to respond to a ticket? Come the fuck on
Comment on IT support work be like
LemmyIsFantastic@lemmy.world 10 months ago
For every “I’m the bottom 10% of tech users” there is another 70% of the user base bitching about inept prioritization and service desk people who couldn’t troubleshoot process issues if their life were dependent on it.
Different people different skills.
netwren@lemmy.world 10 months ago
c0mbatbag3l@lemmy.world 10 months ago
How many seats are they responsible for? Could be understaffing.
Lesrid@lemm.ee 10 months ago
It’s always understaffing.
c0mbatbag3l@lemmy.world 10 months ago
That’s because IT management theory currently holds that the more processes/workflows you standardize and consolidate the fewer things there are that break. Which means you can hire fewer help desk personnel.
Unfortunately the people usually tasked with performing this standardization is the help desk, so they don’t have the time to decrease their own workflow through standardization when they’re already filled to the brim with a backlog. At that point you’re just giving them more of a backlog.
SocialMediaRefugee@lemmy.world 10 months ago
Googling problems with Windows I find the majority of the results are MS support telling them to reset the OS. No attempt to debug the issue just nuke it and see if that fixes it. Then you read the next comments and inevitably they say “Nope, didn’t fix it”. I really dislike scripted responses like this.
Buddahriffic@lemmy.world 10 months ago
Yeah the MS support forums are very hit or miss. And even the hit ones usually start with a response that doesn’t appear to understand the question very deeply, followed by a “that didn’t work”, “I said in my post that I tried that and it didn’t work”, or maybe a “that’s not what I’m trying to do, I want to do x”, and then a reply with useful links.
Though to be fair, problems can come from software the user installed or fuck ups they’ve made to settings along the way. Or quiet sabotage from another user.
Once upon a time I provided phone support for Comcast and had a caller call in unable to access Facebook. I did the usual script and found her internet was otherwise working. Narrowed it down to a dns issue. I was aware of the hosts file because I was using it for ad blocking at the time so had her open that up on a whim (which I would have gotten in trouble for since it was off script). Sure enough, it was there. Someone didn’t want her accessing it.
Who knows what kinds of methods people have used to discourage other things on shared PCs. Is edge really broken or did the user’s kid get tired of everyone clicking “make it the default browser” when it begged each time it was opened so they wrote a small program that kills it as soon as it starts?
MystikIncarnate@lemmy.ca 10 months ago
As someone who works in IT support, I have yet to find any significant number of support people who can’t troubleshoot process issues. What I have found in spades is management making it impossible to make any meaningful process improvements.
There’s a nontrivial number of management type folks that just want it done a specific way, regardless of how that impacts worker performance or how difficult it makes my job.
The number of times I’ve suggested improvements only to be told that the existing methodology works, is too damn high.