CompTIA A_ Certification All-In-One Exam Guide, Seventh Edition - Michael Meyers [21]
Generally, IT folks are there to support the people doing a company’s main business. You are there to serve their needs and, all things being equal, to do so at their convenience, not yours.
Don’t assume the world stops the moment you walk in the door and that you may immediately interrupt their work to do yours. Although most customers are thrilled and motivated to help you the moment you arrive, this may not always be the case. Ask the magic question, “May I start working on the problem now?” Give customers a chance to wrap up, shut down, or do anything else necessary to finish their business and make it safe for you to do yours.
Engage the user with the standard rules of civil conversation. Take the time to listen. Don’t interrupt customers as they describe a problem; just listen and take notes. You might hear something that leads to resolving the problem. Rephrase and repeat the problems back to the customer to verify you understand the issue (“So the computer is locking up three times a day?”). Use an even, nonaccusatory tone, and although it’s okay to try to explain a problem if the user asks, never condescend and never argue.
Remain positive in the face of adversity. Don’t get defensive if you can’t figure something out quickly and the user starts hassling you. Remember that an angry customer isn’t really angry with you—he’s just frustrated—so don’t take his anger personally. Take it in stride; smile, and assure him that computer troubleshooting sometimes takes a while.
Avoid letting outside interruptions take your focus away from the user and her computer problem. Things that break your concentration slow down the troubleshooting process immensely. Plus, customers will feel insulted if you start chatting on your cell phone with your significant other about a movie date later that night when you’re supposed to be fixing their computers! You’re not being paid to socialize, so turn those cell phones and pagers to vibrate. That’s why the technogods created voicemail. Never take any call except one that is potentially urgent. If a call is potentially urgent, explain the urgency to the customer, step away, and deal with the call as quickly as possible.
If you discover that the user caused the problem, either through ignorance or by accident, don’t minimize the importance of the problem, but don’t be judgmental or insulting about the cause. We all screw up sometimes, and these kinds of mistakes are your job security. You get paid because people make mistakes and machines break. Chances are you’ll be back at that workstation six months or a year later, fixing something else. By becoming the user’s advocate and go-to person, you create a better work environment. If a mistaken action caused the problem, explain in a positive and supportive way how to do the task correctly and then have the user go through the process while you are there to reinforce what you said.
Eliciting Answers
Your job as a tech is to get the computer fixed, and the best way to start that process is to determine what the computer is doing or not doing. You must start by talking to the customer. Allow the customer to explain the problem fully while you record the information. Once the person has described the situation, you must then ask questions. This process is called eliciting answers.
Although each person is different, most users with a malfunctioning computer or peripheral will be afraid and often defensive about the problem. To overcome this initial attitude, you need to ask the right questions and listen to the customer’s answers. Then ask the proper follow-up questions.
Always avoid accusatory questions, because they won’t help you in the least (Figure 2-4). “What did you do?” generally gets a confused or defensive “Nothing” in reply, which doesn’t get you closer to solving