Obviously it depends on the specific kind of support and the hotline I am calling, but if it's a complex issue, and the support hotline is a national toll free number that's clearly outsourced to whatever crummy T1 support call center, I don't even bother with details. It just confuses them, and I know they have a script that management will fillet them over not following even if they know what to do. Just mash A through the script and save the effort for T2 and higher.

Who knows. Sometimes that T1 script catches things you missed. It's designed to weed out the simple stuff, after all. When you directly leapt to more advanced troubleshooting, sometimes you leave an obvious step behind.

My time is just as important as theirs. I have a busted product that I paid good money for, but now, in order to get useful support I have to slog through the basics which is frustrating and useless since 99% of the time I've already tried everything that they're suggesting.

I worked for Disney+ as a System Administrator and later an Engineer, we'd have servers die all the time (with thousands of servers, we'd easily have 10-20 support tickets open at a time) that would need to be replaced. We pay for top tier support and get stupid suggestions from them like "did you try and clear the CMOS?", "Try and flash this new firmware" even though nothing changed hardware wise in years and it was working fine for years, "try this and send us logs", etc... This type of shit costs businesses a lot of money in downtime. It's a disservice to the customer to not support them at the level that they require. In the end the product would just end up being RMA'd after a week or two of back and forth.

If you went to a doctor for a problem and they suggested all the things you already tried, and then sent you home, would you be happy?

Since when is "let's skip the basics" asshole vibes? It's a waste of time for them and myself to cover all the basics, which I've already gone through.

"did you check the power cord?", " did you reboot it?", "Is it actually on?"

Yes, I'm not tech illiterate. We don't need 5 back and forth emails over the course of a few days to get down to something helpful. Give me the helpful stuff up front. Sometimes this stuff is time sensitive and these support people are costing companies a lot of money due to unnecessary downtime. I used to work for Disney+ and we had servers that died all the time, we'd email Dell or SuperMicro and tell them what the issue was, and then we would spend days or weeks of back and forth doing things we already tried, or things we know wouldn't fix the issue before they finally decide "ok let's replace it". A few times their suggestions even bricked our servers and made the problem worse! We'd say that there was a CPU issue on a server that started crashing and the IPMI logs and Linux itself would point to a faulty CPU or RAM. They told us to flash a new EFI, we would do so, and great now the server doesn't power on at all instead of just crashing occasionally.

So do I, but that becomes very difficult and frustrating when they have zero clue what you're talking about, like in my above example of the IPMI and BMC. It sounds like you're talking about the Dingle Arm and Reticulated Splines on your Rockford Retro Encabulator.