Angry_Autist (he/him)

IED(EDS) sufferer and spectrum surfer. You probably won’t like what I have to say.

  • 0 Posts
  • 18 Comments
Joined 2 months ago
cake
Cake day: July 20th, 2024

help-circle


  • This is incorrect. On your first call to nearly any customer service you are getting a script reading grunt that literally will lose their job if they go off script.

    You will need to go through the script regardless.

    What the ACTUAL trick is convincing the script reading grunt that this is critical enough to escalate to a tier2 helpdesk rep.

    THAT’S when the real actual problem solving happens.

    Not yelling at all is a good step, an even better step is to open immediately with “Hey I know it’s not your fault, and you just work there, but I’ve been tearing my hair out over this for blah blah blah.”






  • There are probably less than 5 emails in our internal helpdesk queue this month that WEREN’T marked as urgent.

    Urgent problems this month include: ‘The glare from my kitchen window washes out my laptop screen’, ‘How do I change the color of my folders icon?’ and ‘Client reports hearing faint mumbling from their org’s landing page’

    I handled the last one personally, she had a forgotten tab with a looping podcast playing on very low for the last few days.

    When EVERYTHING is urgent, NOTHING is urgent.








  • You really don’t understand how many millions of hours of human effort force updates have destroyed.

    Yes, there should always be, ESPECIALLY IN CORPORATE ENVIRONMENTS, a point where the client can vet and approve the update.

    This recent Crowdstrike problem is proof of it. You LITERALLY witnessed proof as 1/4 of the world basically shut down for the day. This would have been avoided in many cases if the update was vetted by the local IT teams.