Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
I'm sure this has probably been posted before, but it never fails to drive me nuts, and customers never stop doing it, so:
Why do end users think "it's broken" is all they have to put into the support ticket?
It's a web app, not a goddamn pretzel.
If the turn signal on your car stops working, do you drop your car off at the mechanic, hand them the keys, and say "its broken, fix it!"?
While I'm on the topic, "I tried to do {x} and it gave an error" is better than "its broken", but still: why do you think what the actual error says would be completely irrelevant, especially when we put in the effort to give you relatively meaningful error messages?
I mean, is "there was a problem sending the email" so utterly gibberish to you that it is indistinguishable from "error: 0x000351e6"?
If so, I'm sorry, but you're too stupid to use a goddamn computer!
undefined
stupid-customers