this post was submitted on 06 Sep 2025
378 points (99.5% liked)

Fuck AI

3977 readers
912 users here now

"We did it, Patrick! We made a technological breakthrough!"

A place for all those who loathe AI to discuss things, post articles, and ridicule the AI hype. Proud supporter of working people. And proud booer of SXSW 2024.

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] jqubed@lemmy.world 25 points 2 days ago (1 children)

I think I once or twice gave a customer to an engineer and it was at the engineer’s suggestion each time, typically because this was having a call so they could try to resolve the issue faster and not have the delay of me relaying info between each party. It was always at the engineer’s suggestion and always obvious that the customer was technical enough to speak to the engineer.

But there are also cases where I think it’s good to rotate engineers and other staff through support roles. It can be a way of preventing different parts of the company from getting too distant from the customer’s actual experience. Kind of a related concept to dogfooding your product. Sometimes it’s easier to ignore a problem when you can set an arbitrary threshold and say you need a certain number of complaints before you’ll investigate. It can also be good to get your support people out to events where they will encounter happy customers. When all you’re dealing with is people having problems it can start to give you a negative view of your own products and the people making them, even if the problems are actually pretty rare and only affecting <5% of customers. The company where I worked support used to rotate sending a support person to the trade shows partly for that reason. Generally in our industry the products were beloved. Unfortunately the company was bought by a conglomerate shortly before I started and they put an end to that by the time I could’ve gone.

[–] visnae@lemmy.world 13 points 2 days ago (1 children)

Sounded like a lovely company

Engineers at customer support might also make tooling after understanding the process flows and struggles which might in turn make support more productive/happy.

[–] Aceticon@lemmy.dbzer0.com 4 points 2 days ago (1 children)

In the companies I worked it, engineers were at most at 3rd level support (mainly in places where the users were business experts and advanced computer users) or even the people 3rd level support calls when they can't sort the problem out.

Either way, the vast majority of support calls are filtered by lower support levels out before it gets to them.

Putting engineers as first line support sounds like a spectacularly bad idea, at multiple levels: they're far too expensive to waste doing that job, they generally tend to use expert terms rather than common terms so the users don't get them, what they see as "baseline computing know-how" that they expect users have is still well beyond the computing expertise of most people so all in all they tend to detest doing it.

[–] visnae@lemmy.world 2 points 2 days ago (1 children)

Sure, I agree with you on that, but I'm more talking about listening in on customer support or just joining their stand-up every once in a while. I think it's bad when people are working in silos and don't understand the different obstacles other parts of the organisation are struggling with.

[–] Aceticon@lemmy.dbzer0.com 2 points 2 days ago* (last edited 2 days ago)

Well, I've worked directly with end-users often enough, both on the side of getting requirements from them for new features and supporting them for the existing application features (these were expert users) and think it's important for engineers to get that kind of exposure.

However working with a limited number of users who are experts in their domain and have high skills in computing is something very different from manning phone lines to provide first line support for a mass marketed product or service whose users are just average people who don't work on any organized thinking area (so their thinking and ability to express themselves clearly is all over the place) and whose computing abilities are usually pretty low, especially compared to an engineer - the mismatch is so broad that it tends to be an exercise in frustration from which the average engineer will learn very little even if they are open minded and understanding.