OK–I’ll go ahead and add my $0.02 worth, even though everyone (especially Biggirl) may fell like they were gypped.
I’ve worked in IT since the early 90s. First selling computers to home consumers and businesses (and occasionally doing trouble-shooting and training), then a stint in Desktop support that included manning a help desk phone one day a week, then graduating to 2nd/3rd level support and server management. I have had experiences with users similar to those related in the previous posts in this thread by IT people.
I’ve never called a user a liar (and hope I’ve never implied that!), but there are certainly situations where I was incredulous at the problem being reported and said as much. If I was handling the call described in the OP, my reaction might very well have been “Well, that’s freakin’ weird!” or something similar. IMO, Biggirl has gotten a very poor IT service person who should be (at least) reprimanded. And if the organization has disabled screen-shots, they all ought to be taken to a remedial trouble-shooting course…I absolutely rely on that as a trouble-shooting tool.
That having been said, I’ve found that there are different types of users out there:
[ol]
[li]Clueless users[/li][li]Users who want to get the problem solved[/li][li]Users who want me to solve the problem for them[/li][li]Users who know enough to be dangerous.[/li][/ol]
In my expereince, all users suffer from a problem that prevents them from taking down, in detail, everything associated with the error condition they are experiencing. Error messages are not noted or written down (yes, I need to know exactly what the message said!), time of the error isn’t known, what steps were being taken when the error occurred isn’t known, etc. The more information I have up front, the quicker I’ll be able to resolve the issue for you. However, it may take a couple of iterations (or more) in some cases even if everything goes perfectly.
The problem with Clueless Users is they have a hard time comprehending the technology, and so can’t help me do my job. They can be difficult to work with at times because of this, but just require a little more attention and time to work things out. As long as they can follow directions, I’m OK with these folks.
Users who want to get the problem solved are my favorites. They usually have at least half of a clue, can navigate around the screen OK, and understand most of what I’m talking about. They may not have gotten the information I need the first time the error occurs but, by golly, they’ll make sure I have it the next time! When I ask them to try something, I feel confident that they will, and will report back accurately what difference any changes we made have had on the issue.
Users who want me to solve the problem are pretty bad. They won’t make the effort to note the error message or take a screen shot. They seem annoyed when I contact them for more information. Often, these are the folks that, when asked for more info via phone or e-mail, will ignore the request until the problem recurs, then will send a nast note to me (or worse, my manager) asking why the problem isn’t fixed yet. Often when I do contact them, they tell me they’re busy and don’t have time. Well, sorry…if you don’t have time for me, I don’t have time for you, either!
Users who know enough to be dangerous are the worst kind. All the IT folks in this thread know the type: they think they know about computers, but usually don’t. They try to anticipate what I am going to say, and race ahead without listening to my instructions. As mentioned up-thread a couple of times, they’ve often mucked with their computers in some way, and caused their own problems, then expect me to bail them out. Except that when I try to do that, they don’t admit to what they’ve done and it takes 5 times longer than it should.
Anyone in IT should recognize these user types, and can generally identify them on the other end of the phone within the first 3 or 4 sentences of the conversation. A good IT person will do just that, and work to the level at the other end, not be condescending or rude (until after the caller has hung up!
), and try in good faith to identify and correct the problem as quickly as possible. Yes, sometimes even after identifying the user type it’s still necessary to ask the obligatory “Did you reboot?” or “Are you sure the printer is turned on?” or “Please check to make sure the cable connections are tight” because the obvious is sometimes over looked. Hell–I’ve done it before and needed to be reminded!
I don’t know if any of this helps, Biggirl. You’ve got a bad egg there in my opinion, and you should let management know.
ETA–Holy crap! That got a LOT longer than I intended!!
Mike