I got a ticket for a remote site that said "there's an error message and the computer doesn't start" . there was no clarification what the error message actually said.

I spent about 20 minutes driving out there, turn the computer on:

"System battery voltage low. Press F2 to continue"

I did not have a battery with me. If they just said what the error was, I would have brought a battery with me. Now they have to wait for another tech to be scheduled to drive out to this location which could be a week later.

It's been over 20 years since I did phones, but I don't imagine it has changed that much. The "techie" callers fall into two categories: Those who actually know what they're doing and those who think they know what they're doing. The latter group are the worst of all callers. I'd rather be on the phone to an 80-year-old who has trouble finding the start menu than with a caller who thinks they know more than they actually do.

If you honestly do know what you are talking about, the way to get this to tech support is to tell them what prompted you to call. An actual competent caller will open the call with something like:

"Hi, this is Cile. I'm calling from ______. My UserID/AccountNo etc is _______. I'm having a problem with ___________. The error message is [EXACT MESSAGE]. I have done a, b, c, but that resolved it."

For your example where it's an access matter, adapt the above accordingly. Something like "I need to do ________, but I lack the access to [steps you would take if you did have access]".

Finally:
Unless you are experiencing something super weird, the tech support people have probably seen this problem before and know how to solve it. Follow their instructions even if it's something you wouldn't have done. Even if their way seems less efficient. There will be a reason why they're doing it that way, and it won't always be apparent to you.