The first sign is a reasonable expectation, the second sign removes a little agency but is still decent customer service, the third sign reads like a parody of overbearing corporate attitudes, and the fourth is just abusive
I have no problem with the second one. If a customer asks you something and you can't help them, you don't just dismiss them. You might try to find the answer yourself, or find someone else who could help (the opposite of "not my department"). In the end you may not be albe to help them, but you should make an effort as an employee. Like you said, it's the basis of good customer service, something that I don't think is taught very much anymore (for reasons that delve into capitalism and other problems).
People who haven't worked retail, sales, or customer service don't realize how staggeringly much of any soft-skills role comprises JUST figuring out what the fuck someone even wants or needs in the first place because they are so bad at articulating it themselves.
But, to be fair, everyone has their expertise in different areas and things that are common sense to me in my specialized role is completely unknown and novel to people who have entirely different sets of circumstances to deal with on a daily basis.
So yes they're contextually stupid AND they're also all too often socially stupid too because they are, via failures of rhetorical conditioning, primed to look down on "the help". Their extant frustration in the face of unmet needs is, when filtered through an attitude of misguided narcissism, thus transformed into sheer distilled repugnance. The faux "status" posturing of capitalism makes fools of everyone interacting with it.
At the end of the day, the solution comes down to:
taking in the full breadth of the client's situation,
distilling it down to its actionable components,
mapping out the vector of the conflict wherein needs are going unmet,
generating a set of actions that could each individually OR collectively address the conflict,
convincing them that this actually WILL solve their issue,
and then, most importantly, and finally: obtaining their willingness to PAY for it.
it's a far more involved process than most salaried administrative-level keyboard punchers will EVER comprehend...
Client: I clicked every link that said "hot singles in your area" and all I got was every trojan known to man, plus some guy named "James" from Bangladesh remoted into my computer and stole all of my banking information, and now I'm destitute.
GSA: that is all completely my fault, sorry I didn't show up or message you for a sexy night. Please move in with me until you're back on my feet, as Best Buy says it's my fault that you're a complete moron.
A different context, but I think this is actually a pretty good rule for software engineering. A number of times I was sure a problem was someone elses fault, only for them to find my own silly mistake that I was overlooking. Sometimes the opposite also happens to me. Now I really make sure and typically find the actual root cause of problems before I suggest someone else caused it.
Wow. This place sounds more toxic than extremist politics. If I go to an interview and see this on the walls, I will point to it, say [loud enough for all to hear, but without yelling] "this view is exploitative, toxic, and unacceptably offensive, and I won't work here", turn around, and walk off.
The problem is that's great for them you are not what they want. I started seeing these as like with spelling mistakes in scam emails they act as a filter for people that are not desperate or people that have enough self respect to not put up with it. That way they get the people they want that they can exploit to hell and back.
I agree. But that's why I say it loud enough for other employees to hear. It plants a seed. Maybe it'll grow, maybe it won't. But if it does, it'll be fruitful in that (soon to be former) employee, and maybe fruitful enough to cause an exodus.
In Firefox, I had to middle click the actual text/link itself to open the photo in a new tab, then it loaded the full resolution version. When I clicked the actual photo, I got an unreadable low-res version.
Zooming into a blurry picture just gives to a closer look at the blur. There is some kind of disparity in what some people are seeing and what others are cause when I pull this up I get basically white lines on black backgrounds no matter how much I "enhance".
Edit: Looks like it's an issue with Lemmy's interface with Firefox. Clicking the link gives you the clear picture while clicking the image gives you a rather large (and blurry) thumbnail.