I have a cool job. For about a year now I've been a Technical Support Representative. The program I support is newer to the company I work for, as they made their name on a really powerful program that is still considered the standard to do what it does, and then created this smaller program that really hasn't done much until about a year ago when they changed to a service model instead of a product model. (Yes I'm being dodgy because I like my job and want to keep it. This article does not have their approval so no names only descriptions
One of the things that I find so hard about this job is cynicism. The Dictionary.com definition of cynicism I'm talking about is: An attitude of scornful or jaded negativity, especially a general distrust of the integrity or professed motives of others. Primarily the issue in Technical Support is the distrust of the integrity of others because they profess an insanely debilitating case of Technophobia. You can't help but become cynical when you receive a call and all they can say is that they don't know what their doing. To fix a problem over the phone requires nothing more than 3rd grade reading skills and the ability to follow directions. You obviously found our phone number and you used the phone to call us, so you just confirmed you meet this criteria. To fix a problem, you may need to describe what is going wrong. In some cases this does require some communication skills (again a 3rd grade level will do nicely) which is fine even if some people need their teeth pulled to provide an actual description with pronouns and everything. In most cases however what is going wrong is that an error message has appeared. Why would an error message be considered unimportant if you are calling for technical support? On average over 70% of the calls I receive are because of an error message, and the person calling has no idea what it said. Error messages are not uncommon with computers, and in most cases if it appears once, your eyes glaze over, you press OK and hope it doesn't appear again. But if the message is appearing every time you are trying to do something, perhaps it is trying to tell you that you have a problem. Maybe you should read it. If it doesn't make since to you, well call technical support and let them know the error you are receiving, and I bet you they can help. But why would you think that just saying your getting an error that they are going to be able to help? And Why is it such a problem that if the error message is the result of another piece of software, that it's so hard to accept that you may need to seek help from someone else too?
This is not to say that all error messages are created equal. The program I support has a good set of error messages that explain the problem and offer solutions if it's an application problem. In addition to the application though we provide a subscription service too, and the error messages generated by the components managing the subscription are literately cryptic in the form of numbered error codes that are completely meaningless to anyone besides me, our QA, and the programmer. (Yes this is a very bad design, but I only support it, I didn't build it) But does that mean you don't read it, or that you don't expect that you will need the exact error you are seeing to get a solution?
I don't know where the trend started, but the assumption that computers are toasters was a great exaggeration. The toaster is simple, you press the button and it makes toast. Simple, elegant, effective, and completely utilitarian. For some reason people cling to the belief that you press a button and the computer does what it is suppose to and they can't fathom the idea that computers are not utilitarian at all, they rely on criterion. There is not a software program available that does not have system requirements that are listed as criteria of the hardware that should work with the software. But even if you meet the criteria, it does not guarantee the program will work flawlessly. If you have background programs, old (in computer terms) or exotic hardware that is poorly supported, this can affect your success of using the software. These are the gambles you take with computers, but expecting to just click a button to fix the problem is an absurd expectation.
To sum up, I love my job, because I get paid to be a mad scientist and fix things for people. The problem is that I find my self everyday in situations that I want to write a person off as just too dumb to be helped, and I have to fight with every word I say to not be this cynical and provide the help the person needs. Hopefully with a little less cynicism on my part, I can get a little more patience and understanding on my callers part.