Current News

Everyday I get someone who asks me to make a recommendation on what they should do with their software. They don't like making their own choices. Basically they want the program to do everything they need it to do out of the box or they want to call up and have us tell them exactly what to click.

This is a lot like going to a store and expecting the cashier to tell you what you should buy. Especially after all you've told them is that you have a three-bedroom house and a car. So, ok, the cashier figures you should buy some wool carpets, and maybe a couch? So you the customer dutifully go off and put those things in your cart and take them home.

... when you get home you realize that you already have a couch! And upon carrying in the rug you find that you are allergic to wool and now you're itching all over.

Now, you are an unhappy customer and you go back to the store and complain to the cashier's manager that you bought these things, one you didn't need and the other that caused you problems, and it's the cashier's fault for telling you to buy these things.

Yeah, right.

Don't get me wrong. I have no problem guiding someone in how to use the program. I also am happy to tell them how to do a specific action they want, when they don't know how. Using my previous example, in which I am the cashier...

Customer: I want to be able to put drinks and my tv remote on something in my living room.
Me: Ok, the purchase you need to make for what you are asking for would typically be a coffee table. Do you have room for a coffee table?
Customer: I think I do.
Me: Ok, you go to department 5 to get the coffee table. When you get it home, make sure you set it on it's legs.
Customer: Thanks, that's all I needed.

See? See how easy that is? The customer told me what he wanted and I told him how to get it!

The things you as a customer need to know before you ask me these kinds of questions:

1. What is my environment like? (In the case of computers this means... how much RAM do I have? What kind of CPU do I have? Do I have other software running on this machine?)
2. What do I want this software to do?
3. Am I prepared to work? (Meaning, at the computer and without other distractions)

So, Mr. Admin, call support! But don't ask them to make up your policies for you or do all your work! That's what you get paid for!!

Labels: admin, advice, phone, phone support, question, questions, ram, requirements, software, support, system, technical, technical support

I got feedback today, for a customer I'd talked to that took issue with my answer to her question.

She originally called, saying that she'd recently installed some new MS patches, and since then she'd been having trouble with her system. Things were flowing slowly.

She had stopped our services, and suddenly the problem went away - but let's get this straight - she recently installed a ton of new patches.

I had asked her what patches she installed, but mentioned that this was most likely something she'd have to ask MS about. She didn't know what patches she'd gotten. There were too many of them. I told her that I would be happy to see if there were any issues with our software and her patches, but I needed to know what they were. She just didn't know.

I said, ok, well maybe something we're dependent on was changed while we were installed. A big no-no with our software. I offered up a couple things that would have made my program go haywire and do weird stuff.

She pin pointed one and said that she had indeed done an update to it. So I suggested that she reinstall our product so that we could reassociate with the latest changes.

I offered some other things we could do to troubleshoot, but she said that she couldn't do them right now, as she needed permission to do them.

So, uh, no troubleshooting? You're saying you called and expected me to press the magic button?? Lady, I can't pull an answer out of my butt with the information you gave me. You gave me nothing!

So I have her go off and do the uninstall/reinstall and suggested that if that doesn't work, she can get back in touch with me via email.

...

A few days pass and she calls back in, and gets the next guy in line. She lets him troubleshoot. They go back and forth a bit till he figures out what's wrong.

...

She then emailed a supervisor here, and said that she'd called MS and they charged her $500 bucks and it's all my fault because I was not listening to her.

...

No lady, I don't have the magic button. It's not my fault that I gave you that answer, seeing as you gave me the information I used to give you that answer. You don't want to troubleshoot? Then don't complain when I give you a lame answer and your issue is not resolved.

Labels: microsoft, MS, phone, phone support, question, questions, stupid, support, technical, technical support, vague, windows

I'll preface this by saying, I would love to work from home. It's always been my dream to be a freelance "something" like a web developer or something. I would love to set my own schedule and not have to deal with office politics or put on pants. You know, the fun stuff. I would like to advise any Admins out there who want to work from home, do so! We admire you for having that ability.

That being said... get an office (that locks) in your home or send the kids to daycare. If I hear screaming kids in the background and your phone gets cut off in the middle of our conversation I will not attempt to help you. I will tell you whatever you want to hear to get you off the damn phone.

Be reasonable will you? I can't troubleshoot with you if I have to call you back ten times, or if your computer gets turned off by a rambunctious 2 year old. I don't appreciate having to yell to be heard, and let's face it, what person wants to sit by and listen to some poor kid get yelled at or spanked on a BUSINESS phone call?

Keep home separate from work PLEASE.

Labels: advice, baby, call centers, calling, kids, phone, phone support, stupid, support, tech, technical, technical support

Todays lesson is: Don't ask a question if you're not ready for the answer.

This applies in two ways. One, if you ask a question, pause your talking long enough to hear an answer. Two, if you ask a question that requires I give you information to write down or type, have your keyboard/paper ... READY.

That's all for today.

Labels: be ready, call centers, calling, instructions, listen, listening, phone, phone support, question, support, tech, technical, technical support

You don't have the most current version. Why do you say that if you don't really know?


Ok, so today... today I'm talking to a customer. It's way too early in the morning. I have a headache and the customer didn't help. So I ask him: "What version of -this product- do you have on your system?"


He answers, "I have the latest version. Version 5.0.5.366...." Then he proceeds to talk and talk and talk. It takes him 5 minutes to pause long enough for me to say anything. Come on!


So finally, I can say something, but it's not important right now to tell him that he's an idiot and has like, 4 versions back. No sir. You do not have the most current version. Not by a long shot.


The worst part about this is that this is a common issue. Many many people do exactly the same thing. I can't believe they have the gall to call and not have the information they need ready. Or in the very least, be willing to say they don't know.
I much prefer to hear..."I don't know" and have the customer be willing and ready to find out then the "I have the latest version..." while not actually knowing they do for sure, without even knowing what version they actually have!!

Labels: call centers, calling, calling back, listen, listening, phone, phone support, question, questions, support, tech, technical, technical support, wrong product

A friend of mine pointed this out from Craigslist, Best of, and it fit so well with my theme here I had to post it. This is awesome funny. Kudos to whoever wrote it.
((Note: this is an exact copy, it includes the links back to craigslist.com and the posting number))


best of craigslist > pittsburgh > Things to consider when calling Tech Support...

Originally Posted: Fri, 27 Apr 23:38 EDT

Things to consider when calling Tech Support...
Date: 2007-04-27, 11:38PM EDT


Hi! I'm your Technical Support Rep. I have a considerable amount of control over one or more important aspects of your daily life: television, telephone, and internet. Sometimes one, sometimes all three. Before we interact, I'd like to share some thoughts with you:



* I am here, simply put, to fix your shit. My job is not complete until said shit is fixed. Please just help me fix this shit.

* With that out of the way, know that I hate you exactly as much as you hate me. No more, no less. If you are at least relatively pleasant, I'm happy to help you- even to make small talk as I attend to the issue at hand. Conversely, if you are a total and complete jackass, I will make this the worst 10 minutes of your week.

* Neither I, nor any of my coworkers, are out to fuck you. We are not idiots. We are college graduates in technical disciplines, the vast majority of whom are here to work their way up the IT ladder to more fulfilling positions. Sometimes we have off days, sure, but we know EXACTLY what we are doing. Note that this does not apply to anyone outside of our department. They are, in all reality, idiots who are out to fuck you.

* So you've already unplugged the "internet box" and plugged it back in? Brace yourself, you're going to do it again. Most of the time I do this for a reason...unless you're a dick. Then I do it to see how mad it makes you.

* Don't lie to me- I can tell you have a router. It isn't illegal.

* To those who think they are "computer illiterate": The vast majority of the time, you are lovely customers: Patient, willing to learn, and most importantly, willing to listen. Thank you!

* To those who think they are CompSci PHD's: The vast majority of the time, you are retarded: If you already cycled your equipment and it didn't work, why did it work when I made you do it again? If you are so well educated, stay the hell out of the queue so that people who need help can get it.

* Supervisors don't have a magic wand that they can wave to make everything better. They are governed by the same protocol and use the same utilities as I do. In fact, supervisors are more likely to tell you to fuck off- believe it or not, they have other pressing issues to attend to. If a node goes down, they WILL put those 200 subscribers before you in Priorityland.

* Threatening to cancel does not intimidate us. We have an entire department that is paid to care about that, which means that I don't have to. Harsh? Sure, but I have more than enough work to do fixing shit, yelling at field techs, following up on cases, and explaining the concept of email to your grandmother that it won't cause me to lose any sleep.

* It worked fine yesterday? Oh, then I must be wrong. Let me reconsider the 40 minutes I spent troubleshooting your Win98 box. Check it out: Shit breaks (see point 1); If shit did not break, I would be mowing your lawn instead of sitting in this office.

* Speakerphone? Turn it the fuck off.

* Don't call back and have another rep troubleshoot the same problem. He will read the notes I left about how you spilled coke into your cable box. Even if he didn't, he would come to the same conclusion, and more people with undiagnosed problems would be stuck listening to that god-awful hold music.

* I am not blowing smoke when I say that I understand how frustrating it is to wait on hold, get transferred, and deal with bad agents. I too have called Dell's tech support line. The difference is that I actually DO care about your problem, so please just calm down before I kill your family.

* My company has over 20 million subscribers. I handle a region of about 2 million. To this day, none of them have ever called in to say "I just wanted you to know that my shit is working correctly." Maybe someday?



So what can I help you with today?

* Location: Internet
* it's NOT ok to contact this poster with services or other commercial interests


PostingID: 320304562

Copyright © 2007 craigslist, inc. terms of use privacy policy feedback forum

Labels: call centers, calling, calling back, e-mail, guilt, instructions, listen, listening, method, microsoft, phone, phone support, question, questions, support, technical, technical support

Asking the same question twice doesn't change the answer. Asking it in a new and different way, does NOT change the answer. Here's an example:

1. My dog Fluffy went to the dog barber. When he comes back can his hair be cut differently?
2. When my dog Fluffy goes to the dog barber will he come back with a different hair cut if I ask him to cut it differently?
3. Next time I send Fluffy to the dog hair cut guy I would like his hair to be styled differently with a cutting implement. Is that an option?
4. If dog barbers cut dogs' hair does that mean Fluffy will have a new hair cut when I send him there?

The answer to all of these is:

If you request for your dog's hair to be cut differently from the dog barber, it will be.

So please, if you call me for support, don't think you're so smart that you can change the question to get a different answer.
If you want a different answer..... ask a DIFFERENT QUESTION.

Labels: dog barber, phone, phone support, question, questions, technical, technical support

Ok, I work in a call center-like environment. I get calls from people who've been on hold for an hour. They are upset because of the amount of time that they were on hold, so in retribution they hold you up asking lists of dumb, time-consuming questions or insisting that you hold their hand through the simplest of procedures.
They never seem to understand that our hold times would be shorter if they didn't create a laundry list and expect every whim to be fulfilled just because they had to sit for an extra 10 minutes on hold.
We understand you've been waiting a long time and we would love to help you as fast as possible, but if you take your time and stall for no real reason, you will be the reason that someone else will do the same thing. If you want faster service be kind to those behind you in line and limit your call to the issue at hand. Save the laundry list of items for your user guide or online/email support.
If you absolutely must call in for support, in the case of the documentation not fulfilling your needs, try to call very early in the morning. Morning hours are the best times to get support - every place I've ever worked in support was always dead during the first hour. If you choose to call at lunch time, expect to be on hold for 30 - 60 minutes at least. This is especially the case within the first month after a new version of your software is released, or right after a national holiday.
If you're looking for a good day to call in, the day before Christmas, Thanksgiving, and Easter. Also, if your support center is open on weekends or other travel holidays, call in on those days.

Have a great day and enjoy calling!

Labels: call centers, calling, holidays, phone, phone support, tech, technical, technical support

Today is the day that I address the problem of being vague.



I'm going to try to use examples, but because I don't want to reveal actual people, I'm going to replace parts of the examples with something else. For this one I'm going to use a VCR and TV.


Customer: "I would like to configure my TV, my remote, and my VCR."
Me: "Ok Mr. Customer, what would you like to configure it to do?"
Customer: "Well, I currently have my remote in my hand, and my TV is on."
Me: "Well, Mr. Customer, did you have a question regarding the remote? "
Customer: "I've turned my tv on, and I want to change my settings on my VCR to make my TV blink. I also want my recordings to be taped on certain days. I'd like my TV to do that."
Me: "Mr. Customer, these two items are not related in that way. You are able to change settings on the TV if you would like to make it blink. The settings for the tapings need to be changed on the VCR."
Customer: "But that's not what the VCR tech told me!"
Me: "I'm sorry Mr. Customer, but the VCR is what determines the times that tapings get done."
The customer, irate at this point requests to talk to another person. He doesn't feel that I've given him the correct information, and swears the programs are related to eachother.
Me: "Ok, I can transfer you back into the queue if you'd like, but there's a possiblity that you may get me again."
Customer: "Fine. I just don't think you're understanding me."
So I transferred him.

--end--


So, this customer didn't really know what he wanted or what to ask for. This is an example of being vague. This is also an example of not-knowing-what-you-want-itis. On a side note, the calls I take are from network administrators. These folks should already know how frustrating it is to get a call or email from someone asking for something that means nothing, or calling for help and never saying what they want.

I've had at least three people call me with vague-itis today. When you don't know what you want, you frustrate the person you're calling to for help. You won't get anything taken care of. If you want to talk to a technician, make a list. Make a list before you call! Decide what questions you'd like to ask. Determine what direction you'd like to go. Read the documentation that comes with your item and use that as a spring board to get what you want.

Just remember, we really do want to help you get what you want if its within our power to achieve. We just want to know what it is!

Labels: listen, phone, phone support, question, questions, stupid, support, tech, technical, technical support, vague