this post was submitted on 26 Jul 2024
491 points (97.5% liked)
People Twitter
5277 readers
315 users here now
People tweeting stuff. We allow tweets from anyone.
RULES:
- Mark NSFW content.
- No doxxing people.
- Must be a tweet or similar
- No bullying or international politcs
- Be excellent to each other.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
You'd hate me then. I'm a software developer who did IT support for a couple years, so if I'm calling, it's because I've exhausted all of the common problems.
BTW, shibboleet.
My internet goes out a few times per year. I run entry-level enterprise hardware (Ubiquiti APs + Mikrotik router), and I'll do a full power cycle (power off, wait 30s, plug back in, etc) before calling in. I'll have detailed diagnostics (e.g. can I ping the gateway, but not 1.1.1.1? traceroute logs saying exactly where my connection is failing, etc), and I'll submit them through their online form entry before calling.
I've only gotten through their phone support once or twice. I think they recognize the number and just dispatch a team pre-emptively, because my internet is usually fixed within 10 min of sending that in (and I've waited up to an hour before). It's a small ISP that only serves my small town (30-40k people), and they don't have a monopoly, so I'm one of probably a few thousand customers and they probably only have one or two phone support people.
I've had one time when it was something I could fix (was a faulty cable), but every other time it's been some kind of service disruption on their end.
No, I'd love that too. Cause I could instantly escalate your ticket away from my desk.
:)
No offense, but I want to talk to you about as much as you want to talk to me. I get through so many first level tech support calls by just overwhelming the person with information. I'm not trying to show off, I just want to save your time and mine.