Keep in mind that the service lines also deal with customers who can’t distinguish a CPU from a modem from a monitor. Hence the basic troubleshooting in the beginning.
Yeah, I know they have to follow their script, so I just play along. And honestly, it’s not as if I’ve never made a stupid mistake before, like accidentally leaving something unplugged.
I always start off by telling them “I know what I’m talking about, I work in IT, let’s skip the basics, I’ve tried it all already.” but they sometimes still don’t listen.
Years back, I bought an Asus workstation motherboard with IPMI, the stupid BMC would reliably crash every 12 hours rendering the IPMI absolutely useless since it would hang upon login. I emailed support and told them that the BMC sucked and asked if they had an internal build I could try… They directed me to the downloads page and told me to download the UEFI firmware 🤦♂️ It took about SIX back and forth emails over the course of a week or so to get them to understand that I was talking about the BMC and not motherboard itself. Their tier one and two support had ZERO clue what a BMC or IPMI was. After begging them to forward me to an engineer who actually knew what I was talking about, they agreed and that engineer sent me an updated build…which still crashes every 12 hours 🤦♂️. In the end my solution was to set a cron job (I run Linux) to execute every 11 hours that logged into the IPMI from the running OS and did a cold reset on the BMC. That worked like a charm as long as Linux was running.
I always start off by telling them “I know what I’m talking about, I work in IT, let’s skip the basics, I’ve tried it all already.” but they sometimes still don’t listen.
They don’t listen because, unfortunately, for every one person telling the truth, there’s probably at least three people who don’t have an iota of a clue about their system but lie about it because they think claiming they’re an expert is a cheat code to getting better support. Ruins it for the rest of us.
I also think it comes off as a bit snotty. Nobody’s perfect and asking through the basics is the tech covering themselves, too. And who says that your basics and their basics are identical?
I usually start by giving a detailed description of the problem and of what I already tried in particular.
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.
Keep in mind that the service lines also deal with customers who can’t distinguish a CPU from a modem from a monitor. Hence the basic troubleshooting in the beginning.
Yeah, I know they have to follow their script, so I just play along. And honestly, it’s not as if I’ve never made a stupid mistake before, like accidentally leaving something unplugged.
I always start off by telling them “I know what I’m talking about, I work in IT, let’s skip the basics, I’ve tried it all already.” but they sometimes still don’t listen.
Years back, I bought an Asus workstation motherboard with IPMI, the stupid BMC would reliably crash every 12 hours rendering the IPMI absolutely useless since it would hang upon login. I emailed support and told them that the BMC sucked and asked if they had an internal build I could try… They directed me to the downloads page and told me to download the UEFI firmware 🤦♂️ It took about SIX back and forth emails over the course of a week or so to get them to understand that I was talking about the BMC and not motherboard itself. Their tier one and two support had ZERO clue what a BMC or IPMI was. After begging them to forward me to an engineer who actually knew what I was talking about, they agreed and that engineer sent me an updated build…which still crashes every 12 hours 🤦♂️. In the end my solution was to set a cron job (I run Linux) to execute every 11 hours that logged into the IPMI from the running OS and did a cold reset on the BMC. That worked like a charm as long as Linux was running.
They don’t listen because, unfortunately, for every one person telling the truth, there’s probably at least three people who don’t have an iota of a clue about their system but lie about it because they think claiming they’re an expert is a cheat code to getting better support. Ruins it for the rest of us.
I also think it comes off as a bit snotty. Nobody’s perfect and asking through the basics is the tech covering themselves, too. And who says that your basics and their basics are identical?
I usually start by giving a detailed description of the problem and of what I already tried in particular.
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.
I agree that “I work in IT” gives off “I want to talk to the manager” vibes.
I list off everything I did so far, and explain the problem. That usually gets me the best results.
You likely could have followed their script in less time.