I have a perfect example of a pet peeve I have as a CS rep so to speak. When a client calls in, there are certain pieces of information I need before I can begin anything at all.
I ask for the person's name first. Then I ask for their account number. (Our company policy says to ask for account number, then name, but I think that's just rude, so I refuse to do that.) Most of my clients know what theirs is, but some don't. It's not that big of a deal at the beginning if they don't know it off hand. We can usually figure that out later.
But then I have to know what software package they're calling about. We develop and support numerous, numerous software packages as a company, and I don't support all of them. So I ask, "What software are you calling regarding today?" And a good portion of the time, they completely ignore my question and move right on to what their problem is. Sometimes I can tell from context what software they are using, but not very often. I politely let them finish their two minute spiel. Then I ask again. Often enough they come back with "your tax software"... well, just about all we have is tax software. So they could still be talking about one of well over two dozen different packages. They might get a bit more specific, but not quite enough. "Ok, what is the exact name of the software you are calling about?" I mean, these people use this software every day. The splash screen they see every day tells them the specific name. The title bar tells them the specific name... come on, throw me a bone here.
It's sort of like if you call a general Microsoft support line and when asked what app you're calling about, just saying "D'uh, well, Microsoft of course!"
Is it too much to ask that a person know who they're calling and what they're calling about?