• stoy@lemmy.zip
    link
    fedilink
    arrow-up
    6
    ·
    4 months ago

    “That’s fine, when you have the time, run the tool I sent you, it takes 30 seconds and should solve your issue!”

    • BCsven@lemmy.ca
      link
      fedilink
      arrow-up
      4
      ·
      4 months ago

      I wish that worked. Rather than spend an hour diagnosing which file is causing the error, they would rather struggle with it crashing for a week.

      • stoy@lemmy.zip
        link
        fedilink
        arrow-up
        7
        ·
        4 months ago

        Yep, but that is their problem, I have it logged that I gave them the tool with instructions on how to use it, with them dismissing it, even when I followed up on it.

        I won’t work myself up over a user who is not interested in solving their issue.

        Now obviously in real life I would remote in and run the tool for them, but there have been time when they have been unwilling to do that due to some pointless reason, that’s fine, I have logs showing that I tried.

        • BCsven@lemmy.ca
          link
          fedilink
          arrow-up
          1
          ·
          4 months ago

          Yeah, sometimes we can’t remote in due to IT policy or ITAR data. And I was just being dramatic with the comment, it just boggles my mind that they will just keep calling back without even trying to help themselves. Even scheduling a call…“I don’t have time for a call I just want it fixed” LOL