Discussion Locked

What questions should the helpdesk ask?

0 helpful
64 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I would like to hear from my peers about what they feel are the questions that the helpdesk should ask a caller or respond to in an email request on an initial request. I am at the second or third level support and the desk has no matrix to start with and I would like to get as much info from them as possible when I first look at the problem.

Thanks in advance,

Clindell

64 replies

by gralfus

I'm not trying to be rude, just trying to analyze what you are after. What kind of things are missing from the calls you already get, that you would like to have? What info do you get that you can't do without? I've done help desk for years and we always had a software package that has certain fields to fill in for each call.

*Caller's name and phone
*What is the issue, symptoms
*PC name (useful for internal company helpdesk, so we know which PC in the room we are dealing with. Put this info on a sticker so the user can tell you)
*Location of the computer
*What catagory of call is it (hardware, MS Office, email, niche software, etc)
*What priority call is it (does it require immediate attention or not, is the customer a VIP that gets special service)

by clindell

I know some of what should be asked, not all; you pointed out what our helpdesk and I know for the most part. I know our helpdesk does not have any specific questions that should be asked during an initial call, which may require additional questions later. The more info we get initially the better we can serve our staff, so I am just looking for something we might be forgetting and build a matrix that gets as much info as possible on the first round. The more people contribute to a list the more through it will be, and we might be missing a few good questions.

by mhorlandi99

The minimum information that I consider as necessary are:
* Caller?s name
* Location
* Problems
The phone number I get it because I see on the display of the phone. Depending on who the caller is the priority of the call will be.

by suwaiema

Second and third level support staff required the following information:

? Caller?s full name.
? Caller?s phone numbers.
? Caller?s location.
? Serial number of affected device.
? Category of the reported problem ( Hardware ? hard drive etc. it should be three tiers).
? Summary of the problem (description of the problem)
? Assets details (obsolete ? under warranty ? the device location).
? Priority of the case (urgent ? high ? medium ? low). Priority depends your service level agreement with the caller?s organization.

by heml0ck

1-Nature of Problem- ie -error message or behaviour
2-Is this a recurring problem, or is this the first time?
3-Have there been any changes to machine config at all (remember, most users are afraid as being seen to be messing about, so further probing is usually necessary)
4-specific details about event/error

Remember W5-who, what, when, where, why and how

by skidoggeruk

Aghhhhhhh !!!!

How often have you got to go find some desperate user, because the Helpdesk has not asked this simple basic question???? Angry, me? Never, frustrated maybe.

Priority, well it is ALWAYS an emergency, isn't it? Ha

by clindell

That's why I am asking these questions to others that understand. I have done a search and can't really find anything that states what you should initially ask.

When is an organization so large that you cannot comfortably remember where the callers are calling from? We have around 180 employees at 18 locations. They assume we should be able to remember who and where they are when we are called. This was good when this company was first founded and was a more intimate workplace. It is my understanding that you could remember everyone at that time but times have changed and this company keeps growing and increasing in size.

Where do you draw the line? Should we be required to look it up for each caller or require everyone to provide their location and call back number? I feel that at some time you would be spending too much time looking up user and hardware info, which the user can provide, letting the helpdesk more quickly address the problem.

by chipper

I usually ask things like what applications were open when the issue occured? What were you doing before this issue happened? did you try re-booting your system? Did you get a screenshot of any error messages? things like that. I am a hand holder in a small company so I usually respond in person and within 1 minute so I can sit and fix the issue as they point things out to me. Do you have any remote ability?

by keiths

Each Call will require different inforamtion to be obtained. However, there is a standard set (name, contact number, asset details etc..) that should be obtained (and recoreded) each time.

I have found that the use of applications that prompt the analyst to ask questions depending on problem are very useful and either results in more 1st line resolutions or ensures that all required information is obtained prior to escalating the call.

by dkeith

Something that I ask my help desk staff to ask our users is what part of your job are you unable to do because of this issue. Users will often think that their issue is a Priority 1 to everyone because it is to them but as often they will underestimate the priority of the issue thinking that it is only happening to them. The basics for every call are the who, what, where, when and why but other things they can ask, depending on their time availability and their skill level are: What were you doing on your system immediately prior to the problem? Have there been any software or hardware updates or upgrades recently on your system. The first thing is usually to ask the user if they have performed a reboot of the system. Simple but very often all it takes to get things back on track.

Some users will give a lot of information and some either can't or won't. The more the help desk knows about the processes and what has been happening in the other areas of IT, the easier it is for them to get good information from the caller. Make sure that your help desk is aware of any network or server changes ahead of time.

As for location and contact information, it takes only a minute for the agent to ask for the information for verification and it should be done every single time the user calls in. The information in the database should be corrected as needed at the same time. No one can be expected to remember where someone sits in a company with more than 20 users. Most call tracking systems have places for that information.

by richard h

We only have 150 employees at 7 locations.

You need to talk to you programming/Web development group. We have created a small web interface to a database where we log helpdesk calls. On the opening of a ticket, we query our LDAP server and the helpdesk agent selects the persons name from a drop down list or an auto fill input box. All of the caller's information is then automatically populated. We then have additional dropdowns for other classification areas (hardware [printers, monitors, etc.], Telephone [voicemail, dialtone, etc.], Software [word, excel, proprietary app, desktop, email, etc.])

In a few clicks we have all the user information and have classified the call. Now all the agent has to do is to fill in exactly what the trouble is all about. THIS is where we have a problem. Agents have simply reported "His printer is missing", we refered the call to security. Then there is the ever popular "It's broke". The best way we have found to deal with this is to have all contact with the user go through the helpdesk agent. We ask the agent for the information we need and have them contact the caller. So far it is working in that tickets are finally starting to come to us with a little more detail about what the problem is.

by urzica1

See if you can develop an intranet type of call tracking where users can input all the information possible, i.e. location, cube, phone number, problem with the computer, operating system, etc. Also try to have some type of inventory system of the hardware and software. if they work different shift, when they are available. Just some thoughts.

by heml0ck

I addressed the looking up part by automating a data feed from our corporate database in our helpdesk database. That way when a call comes in, you ask who's calling, pull them up in the helpdesk s/w, and start filling in problem details.
We support @450 users here, from manufacturing to engineering. We have also incorporated plant operations into the helpdesk.
Most helpdesk solutions will allow you to track all sorts of extra fields, including inventory.
I have found using the inventory functions really helpful in distinguishing between a problem user and a problem machine.

by expert-in-spe

1) validate user
2) get user information (who, where, which pc etc)
3) why does the user need it (business or private - if not business kill this issue...)
4) problem description...
When did this happen,
did you talk to/contact anyone else from IT/support about it,
do you have an issue number,
did this happen before, if so do you still have the issue number from that incident? was it resolved....,
is this stopping you from completing a task,
if so by when do you absolutely have to have the task finished,
is there a computer nearby on which you can complete the task or a colleague who can do it whilst we solve your issue
(if you have multiple setups) what setup does the user have
what applications are you using
did you attach something new to the machine today or download any programmes, toolbars, pop-up blockers etc...
are you available for fixes (today, in the next days etc)
have you ever been able to sucessfully perform the operation you are now unable to perform.
and then let the user babble on for 2-3 mins as this usually gives a load of interesting extra information e.g. "my puppy was lying below the table when I lost my network connection" (dog chewed up the cable), "I wouldn't worry normally but today I have to work on XY's computer" (didn't take the roaming profile with her.) etc...
Try the book IT problem management author:Gary Walker for more information about how to streamline Helpdesk calls...

by clindell

There doesn't seem to be much feedback here. I would have thought there might be some questions that some people ask that are not what we would call standard questions "boiler plate" and would share some of their favorite ones with us???

by g.lauwers

We always ask our users to send e-mail to the helpdesk when they call us and they can do that using a form we created in lotus notes.
The user clicks on a button, the form opens and his name, phone number, location and PC registration number is filled in automatically. There are only 3 fields the user has to fill in:

- Name of the application or hardware number
- Problem description
- Action taken this far
For remote control we use Novel Console One

I don't see anything else u can ask and if the user isn't very clear u can always call him.

by ahe

Have you rebooted?
Have you moved your pc recently (or anyone near you done it)
Is anyone else affected
Can you reproduce the problem on another machine/software account
Have you installed any new software recently

At that point you then go into the specifics of the call with questions as other people have said.

by cmb from omaha

I would ask, in a very neutral, "non-prosecutorial" way, if the user knew of any recent changes to the problem PC. For example: "To your knowledge, has there been any new software installed on the machine recently?" If the answer is "no"--"How about updates from Microsoft or Norton, for example"...if still "no"..."By any chance, do you know whether someone might have downloaded any free trial software or anything like that? Or some helper software like Shockwave Flash or Adobe Reader? Maybe Kazaa, or Grokster? Anything like that?" I think this line of questioning--again if done casually, like a skilled police officer interrogating a suspect--might reveal some valuable information.

Also, I wouldn't "report" a naughty user the first time beyond a verbal or possibly written warning. You don't want your users to be afraid of you so that they won't tell you the truth. (Unless we're talking about literally illegal user activity, of course!)

by g.lauwers

Those are questions you should ask a home user. Our company policy prohibits users to download and/or install software not provided by us. If we find out, we just put a new standard image on it.

by sberends

As I start to talk with the user, I ask this question: "What happened to the PC just before it quit working?"

Then and here's the trick - I don't say another word.

The user will immediately say "Nothing", but after just about 30 seconds of silence, say something that will be key to the problem resolution.

Example: Nothing .... but I got this funny email earlier today.

Try it!

by wdickerson

You may have recieved part of my response. In the middle of a nice piece I was kicked out... Here ya go (again)...You have a lot of H.D. experience coming at you. I will teach you in 5 minutes. You will teach me in 10 minutes.

I have vast experience in the IT repair/fix it/ customer service environment. I started in the military with a "Job Control" function. Radar, radio, navigation, weather, computer, communications. If electrons ran through it we fixed and tracked the item. If you are starting a helpdesk it evolves very quickly and you need a system for tracking things.

Not to scare you it gets better if you fellow some guidelines. Once you become comfortable you can taylor the system for efficiency. Are you going to be the H.D. Manager? Will your H.D. opreration be 24/7 or quit at 5pm? What happens on the weekend when critical sys1 (The Mr. Coffee pc)breaks and will not have coffee waiting for the boss on Monday?

You will need H.D. policy and procedure for the company/users so you can serve them at max efficiency. Some policy is users can only be served via a H.D. (We do this.) request. No request, no fix. Will you have H.D. Reps to take caller information and/or be first line tech support over the phone? H.D. Reps dispatch techs?

Joetech, Sallyjo has a blue screen at site 1 and Ralph is toasting marshmellows at the South cupcake site on his monitor. It seems a little warm. Can you take a look?" I can not stress the one entity that can save or break you. "CUSTOMER SERVICE." If one of your H.D. Reps (seem) to be rude or the user is not satisfied believe me you will here (Experience speaking.) it from the top and not just the IT Manager.

A user's computer breaks after 5 hours worth of work. Only thing the user wants to hear is when will pc work again. There are users that appreciate the H.D. and for you will make the Tech Dept and H.D. shine.

If you really want to make your H.D. life easy, I suggest using H.D. software. I have worked with Remedy, Magic and CORES in the military. Currently, where I work we use HelpStar. H.S. does it all. On the H.D. Admin side, H.S. initiates requests, alerts techs when new request comes in, gives user status via email, request tracking, response time, Request analysis, trends, time in suspense/fix. I may have missed some things but I believe you have the basics

Of course when you and any of your I.H.D.F. (Impossible Help Desk Force) make it we will
clap for you. Good Luck.

Will

by trmcsam59

In my opinion it's not only the things you - as a helpdesker - want to know, but also the things the 2nd- or 3rd-line helpers want to know:
= Which OS is in use?
= Which version of the software are you using?
= Contact info (name, contact#, phone#, email)
When you are serviceing company clients the caller must have an registration#.
= How many people are affected (priority)?
= Are there more collegea's using the same softeware? And are they having the same problem?
= When did the problem occurre? Did it work before? (Did it ever work?)
= What where you doing when the problem occurred?

(I hope you forgive me my poor english and the spelling mistakes)
My point is: ask those questions that people 'after you' (2-nd a/o 3rd-line) might need to solve the problem, in case you can't help the customer on the phone.

Kind regards, Simon.

by d.durke

Not all helpdesks are for internal problems and this response relates directly to such helpdesks as those affecting after sales, broadband and the like. For those working on such helpdesks the same rules apply with some additional points:

* Data Protection policies need to be adhered to as they apply to the nature of callers query.
* There are many templates now being used which will highlight the essentials and still allow for further 'open questionning' for further diagnostics.
* Many 1st line staff have to adhere to such systems as matter of course. Only use questions within these templates that actually help and do not just add unnecessary pressures to the work of 1st line support staff as this can lead to 'boilerplate' responses in order to cut handling time etc. This also leads to ill will between different levels - help all lower levels do the job you 'actually need' done and no more.
* Look for the extra undisclosed items such as home networks, non-standard OS(for that particular case)
* During questionning build a profile of user competence/experience and ability so that 2nd level etc. are better able to work subsequent callback
* Has caller used all help tools that have been supplied to them and acted on any previous instructions
* Determine if this is in fact the correct department for this query and ensure that all calls/transfers mistakenly escalated are advised of correct process to avoid further such calls

I apologise to Clindell as this does not in itself add to her own awareness but hope it has some benefit for those who work on publicly available helpdesks. Clindell you could as already mentioned in another response basically reverse the logic of the information you get. This can allow you to develop accurate questions to be asked prior to the call reaching you.
Example.
Information you need = Internet Explorer Version
Level 1 question/request = In Internet Explorer please click on Help/About Internet Explorer. Under version what does it say?

All information needs can be reversed to their point of origin to arrive at the correct question. The question above can be amended to ask for update version instead of IE version, which depending on your own knowledge gives you several answers at once including IE version.

Get what you want by determining the questions you would ask and then get the level 1 agent to ask this. You can build a flowchart to determine these and their order. As stated above though only get what you need from lower levels, don't alienate them by asking them to do what is essentially part of your own job, but do get them to give you everything you can legitimately ask of them. This can be a fine line but complaints from below will let you know if you cross it.

Cheers,
Denzil

by expert-in-spe

true,
we're an internal helpdesk, I know my customers well (about 400 people) and that really helps on categorization and prioritization. also the cooperation between us and them is generally really good so it's easier to agree on things. I can even translate some people's It's not working type messages as I know them and their job well. that's lucky for me. Nevertheless my second level has none of these advantages as they only get around 15% of the calls. What I'm driving at is that the helpdesk needs to provide information as if nobody knows the customer so that assumptions of what we know don't cause errors. therefore many things are going to be universal.

by d.durke

I have updated my original post and hope it gives a better indicator of just a single way of getting the relevant information. I have no idea of your individual needs but the original starting point of this thread started by Clindell is working out what questions to ask. You can determine these questions by looking at the information ultimately needed. A case of layering questions with the easiest and most generally applicable information requested through questions asked by level 1s with expanded questionning from level 2s etc. This is not dependent on type of helpdesk at all. There need be no missed or assumed information issues if such an approach is used. However, rule-of-thumb analysis by all levels can come into play and cause problems.

Sorry if this doesnt help.
Cheers,
Denzil

by heml0ck

2nd or 3rd level support is rarely a stock issue.That is why first level or whoever takes the initial call is CRITICAL.
The information gathered during initial contact determines if this is a known issue, or if we've hit on a new one. If it is a known issue, then the 1st level techs reference the KB (in the helpdesk- we use issuetrak), find the solution and fix the problem.
If it is a new issue, 1st level collates all the info and passes it on to level 2.
Level 2 then starts asking questions like :"What's different between Bob's PC (with the prob) and June's (without.)"
"Have there been any systematic config changes" (I work for a large multinational; things change without notice on a regular basis.)
"steps to reproduce error"
Once further info gathering is done, then level 2 support looks for an answer. If they still come up dry, then it gets handed to level 3 support- senior people who approach the issue as a one off, but with potential KB application.

by d.durke

Apologies for any female reference. Not meant to offend. However, when asking for assistance a bit less attitude might be a good idea. Too easy to criticise before much of the info was put on this post because info didn't come quick enough for you. I'm off. Learn or don't learn. Your choice.

by misskris

Yeah, those are questions to ask asssuming that someone is following company policy, which as we all know is NEVER the reality.

Whenever users call me, the first thing I do is look them up in our helpdesk software - we use Intuit TrackIT! to track users because we have 200+ users in five locations, their PC hardware and software configs at the last audit, and ask them to explain the situation. It's helpful to compare what is currently on the system compared to what was there at the last audit to see if anything had been changed without our knowledge.

When someone calls and says "My PC won't work," that isn't going to cut it in helping you to resolve the situation quickly and easily. Asking if they have moved their desk recently, if they have checked to see if everything is plugged in, was there a power failure, are there any lights blinking? Those are some of the first questions to ask. Sometimes, it turns out to be the monitor.

There are a lot of questions to ask someone, but each situation differs so we don't have "boiler plate" type questions to ask because of the variable types of calls we receive. Getting their contact information is critical - when we have people call the on-call staff after hours, we get messages like, "Hi, this is Keith. The system is down. Call me." Where? At the psychic friend's hotline, maybe? We have an SOP for after-hours calls that outlines the types of calls that are considered "emergencies."

The more questions you ask a user, sometimes in a volatile situation where they are under pressure and need something done and their PCs aren't up to snuff just exacerbates the situation. Tread lightly, don't sound accusatory, and like someone else said, when asking a question about if something was installed, ask them "To your knowledge" because there could be a multitude of people who have access to that PC and may have been creative one night.

by keiths

SupportWorks Heldpesk From Hornbill Systems (www.hornbill.com) provides the administrator to set questions against a given Problem Profile. An example of which may be the MS Windows Print trouble shooter with all questions and answers automatically being entered into the call ticket

by andypiesse9

Apart from the obvious. If the user base is getting to be too big to remember, one question that may be important is if this is the first time the problem has occured/reported. If not what actions have already been taken.

by ibm5081

1. Has this ever worked before?
2. When was the last time this worked properly?

For escalation purposes:
a. Document contact information
b. Document which application and which system experienced the problem (if there is more than one system where the application resides)

by dsnethen

Ask the basics, but be sure to drive the conversation. I have seen were support staff answer calls with either, "Help Desk" or "Help Desk, how can I help you?" and this leads into responses that sometimes get you to the root of the problem or have you listening to someone's story about their bad drive in to work that day.
Our approach is to answer, "Help Desk, this Joe, can I have your name? phone number? Location? and so on. From that point, I would recommend you have set scripts and try to have them lead the call down a certain path and if possible the script of questions you ask can be tied to a knowledgebase with the appropriate answers.
Our scripts ask the basics and based on certain responses, we move to various sections on the script with links to possible answers in our still being developed knowledgbase.

by computer luser

Clindell,

It sounds like you actually have two questions: What caller information should I gather? and What technical questions should I ask?

I'd be curious why the help desk manager isn't asking these questions and if the answer is because there isn't one then kudos to you for your efforts.

You have several options to answer the first question. There are many software packages which will aid the help desk person in gathering the needed contact information. We use HEAT (though I will be the first to admit we do not use all of it's features) and it seems to work well for our 85 field offices and central office of 1000+ users. It is possible to tie this software to a human resources database so that you have all the caller information present. This is accessed by entering any one of several user defined (at initial setup) key fields (like username) which then does a lookup and populates the rest of the fields (location, first/Last name, extension, etc.) For our use, the software pulls from a SQL database with all of the information about every user in our company. However, the downside is that this all has to be setup and maintained and my be beyond your scope. But, with a little creativity you may find time and money saving shortcuts.

Your implied second question is a bit perplexing. Creating a matrix of all possible calls and possible issues might be a good way to change career paths. Just reading the posts to this thread brings up 11 technical issues let alone the amount of possibilites found in a company. My point is, your first level support should have enough training and skills to know what questions to ask without needing a matrix. However, the valitidy of my statement depends on the amount of turnover you have at this level to justify costs of training and skill maintenance. If you truly need the ability to pull anyone off the street, hand them a call matrix, and have them take phone calls on technical issues, then you may want to take the time to use the suggestions in this thread of what kinds of questions to ask. Again, the task of creating a technical call matrix for first level support who has the potential to get calls on hundreds of different issues may not be the most direct way to help your customers and yourself. If you decide to do this then keep in mind you are not trying to make your first level support techs second or third level support techs (this goes back to my previous statement about turnover and training) so you questions should be based on information which would be helpful at this level.

Not knowing details of your exact situation I really can't offer more specific information or advice. Keep in mind, my perspective is from a mid size company with 9 or 10 help desk staff whose skills fall between the upper 2nd level to lower 3rd level support range.

I hope you are able to gleen some helpful informaiton from my ramblings!

by clindell

Yes, two questions, I would say you are right. The coordinator though trying does not have standardized questions and seems to shoot from the hip and does OK at it. Part of this is due to the fact the company was small at one time and everyone knew everyone else. Now that it has grown not all employees know everyone else or where they are. We are using DK helpdesk for our tickets and I am learning the application quickly but I want to improve the customer satisfaction without making it seem like a "big" company and somehow retain a little of the more personal approach.

When the coordinator is out I back her up and I am the guy off the street who doesn't know a lot of what they do here yet so that matrix is important, I feel very important. What would happen if the coordinator were to leave or unable to work for some reason? IMO any company need to have a contingency plan to handle the what "ifs" and though our coordinator does OK without a matrix to follow there still is a need for the person that might come off the street or be new to the way this company operates.

by heml0ck

This is a very important distinction which gets over-looked far to often (by me included).
It begins the triage process b y gathering first -the user info, and second by gathering initial technical info.

by clindell

OK you counted 11 of them, how about listing those 11? The reson I am asking is because our HD coordinator is new to computers (two years) and does not have the depth and is learning from trial by fire.

by ag0044

First, having made a serious mistake many years ago, I always ask who I am talking to!

Other questions include:
* what happens if you do "it" right after a re-boot?;
* what EXACTLY did you do?;
* what EXACTLY did you expect to happen?;
* what EXACTLY did happen?;
* what messages did you get (screendumps)?;
* what happens if you try to do it on another PC?;
* is it happening to other people?

We have around 300 users, all on either Win2k or XP; from politicians to mechanics; remote (radio and dial-up) and local.

Being able to access their PCs remotely, trying to get the user to go through the same steps to reproduce the problem, is a great help. BUT, it is amazing how many times "it" works when we (IT) are watching!

by andypiesse9

As a start point, I am the sole Help desk(er) I have a personal coding system that categorizes the user. Some of the descriptions, I wouldn't want published but It does help me ask the right questions.
Sometimes to gauge the abilities of the user I ask them to do a standard task like a defrag and depending on how much assistance they need I can judge their abilities and their personality.
Apart from that, how about making the list up as you answer your calls. Any questions that appear on your list regularly you can discuss with your first liners as to the apropriateness of asking during first contact.
It occurs to me that depending on how heavy each levels work load is and the percentage of referrals upward. If for arguments sake you have a 10 percent escalation rate then any question asked by level 1 staff that they don't need for themselves costs ten times as much in time to the company as they will be asking nine people non essential information. I hope this makes sense.

by northern star

Google or Yahoo on 'help desk software' and you'll get a list of lots of choices. Research what will work for you, the packages are out there.

We researched several packages and chose Intuit's TrackIt several years ago. As a previous comment mentioned, this software lets you compare the computer's last hardware and software status with the current state. It allows you to keep track of inventory, training a user has taken, problems by your own defined categories, history of problems, and solutions, time spent, etc. There are many customizable features and we still don't use everything. Now we are working on building a knowledge base in the package, as we can't depend on our memories to track it all.

Hope you find what you are looking for, it made our job easier and we provide better service.

by skarva

Why?

Why are you asking? Are you trying to fix something? Are you trying to limit the second level support calls? What is it that you are trying to do and why.
As soon as you answer these question you will come up with your matrix. Aside from the basic question name, problem and actions taking by user there isn't anything else.

The detail that you will need on any of the three basic areas depends on the systems you have in place and type of problem.
If your systems are automated and are able to pull-up information on your users and issue this will limit the amount of useless questions that are asked.
And allow your first level support team to deal with the user's problem.

My advise to you is not what questions should be asked but what questions should not be asked, meaning you should have the answers already.

by clindell

Why build a widget if someone else already has? I will look at your widget and see if I can improve on it. If I look at everyone else's widgets I will take the best from them all and make them mine and in turn someone will take that and improve on it and make it their's.

by heml0ck

I think what skarva meant was if you answer the questions about your needs specifically, not as Joe off the street, then you will have gone a long way to getting the direction your matrix should take.
For example; In my situation they "why do we use a helpdesk" is to improve response time to client requests. So, what questions do I need to ask to improve response times?
W5 for user info, then w5 for tech info.
Is this mission critical -ie- we're going to lose money
Is the user the only one with access to given machine /app whatever?
If answer is yes to either of the above questions, move issue to top of list and assign first and/or seond level tech.
If answer is no to both above, ask about possible workarounds -ie- using someone elses machine, provide temporary machine until resolution.
Lastly, assign tech (level 1)
Next issue.

As you can see, the questions and response are geared to address the given Why.

Something to keep in mind is to publish your SLA (service level agreement) so that callers understand what time frames they are dealing with.

Hope this is useful.

by mj512003

I probably have repeated several questions that you may have received already. Over the course of many years within the helpdesk industry these are questions that have been asked in most of the internal helpdesks that I have encountered. Some of these seem to be standard across several desks. It is lengthy and I apologize but hopefully some of these will help you. Good Luck

Correct Spelling of name
Location or Site (if several locations)
Building(if employee-based HD & several bldgs)
Floor (if employee-based HD & several floors)
Callback number
Best time to contact (keeping Time Zones in mind)
Login or UserName
Email address
Exact Problem
The following is mostly customized to the actual desk but this might give you some ideas that you can use
Hardware Problem
Internal Desk
Depending on the piece of hardware
- Type of Equipment(Make, Model, etc-some
companies may not have standard equip)
- PC Identifier(some companies use asset tags
for their equipment)
- Printer Identifer (asset tag???)
- Is this a new piece of equipment
- Error Message if any
- When error message or problem occured (on
bootup, while in a certain app, etc)
- When did problem start
- Did anything change between the last time
it worked and now
- Troubleshooting steps HelpDesk used,
(including rebooting if necessary)
Software Problem
Internal Desk
- Application
- Error Message if any
- What were you trying to do within app
- When did problem start
- Where you ever able to do this function
- Did anything change between the last time
it worked and now
- Troubleshooting steps HelpDesk used,
(including rebooting if necessary)
Installation Requests
Internal Desk - Software
- Application needed
- Version (if no standard)
- Reason for request
- Usually this type of request can be a form
which requires managerial approval and has
the relevant questions(bigger corps)
Internal Desk - Hardware
- Type of equipment needed
- Person's name who needs it
- If it is a PC, then what type of PC
(desktop, laptop, etc) apps are needed
besides standard config
- Location or Site(if different than
requestor)
- Building (if different than requestor)
- Floor(if different than requestor)
- Room or Cube/Desk
- Usually this type of request can be a form
which requires managerial approval and has
the relevant questions(bigger corps)
Physical Relocations (Internal Desk)
- Type of equipment (PC and/or Phone)
- Person's name who needs it
- If changing locations, from xxx to xxx
- If changing buildings, from xxx to xxx)
- If changing floors, from xxx to xxx)
- If changing room/cube/desk,from xxx to xxx
- Jack #s (from xxx to xxx)
- Usually this type of request can be a form
which requires managerial approval and has
the relevant questions(bigger corps)

by rkg

The information should be grouped by when it is appropriate to ask.
1) Name, preferred contact method, and primary complaint should be asked at the beginning of the call. Other information may be included.
2) Platform, environment, OS version, service pack status, etc. should be asked in the process of troubleshooting. The same information the tech uses to make their assessment should be included in the report. This should also include the exact steps required to reproduce the problem (keystroke by keystroke if necessary).
3) If it is unresolvable by first tier, they should then summarize steps taken, repeatability info (can the tech reproduce?), and any other appropriate information. At this time, you should probably use your bug tracking tool as a template; make certain that information is collected for all the required fields in your database.

by clindell

Thanks for the feedback so far, there is great sharing of info going on! Our Helpdesk coordinator does pretty well but since we are in the business of customer service we can try to do better, which is the reason for my questions. Where I work we have close to 200 employees 18 locations and soon there will be more as we expand and it becomes more difficult managing the expanding users, some of whom are used to first name treatment and direct call in to a voice they know. Soon we will need to send out a memo that officially announces we need EVERYONE to use the same method of contact for Helpdesk as it is to difficult to keep up with changing users and a growing company.

by clindell

There was no attitude, actually it was with humor, but you couldn't hear that in the message. One thing I have learned is try to diffuse the stress with humor :)

by d.durke

Appreciate your response! It is sometimes difficult when you have only words on a screen and I took it the wrong way.

You can find a lot of info on the web and you may like to visit this site.

http://www.helpdesksurvival.com/sitemap.html

No idea of quality of this site but there just may be something which strikes a chord with you.
You may also like to sign up free of charge and access some of these white papers.

http://www.itpapers.com/search.aspx?scid=85

Could be worth checking out the results you get when you enter "ask better questions" on a search engine.

If you have any salespeople in your organisation it may be worth asking them the information they need to make each sale. Then ask them how they develop the questions which lead them to this information. Much of this will always be the same but the best salespeople will never follow the mainstream all the way. The correct answers only come from the correct questions, no matter if in helpdesk, sales, investigative work - know what you need to know and then direct the questions to deliver it.

I do apologise for taking your reply wrongly and hope you get the answers you require.

All the best

by alfred e. neuman

believe it or not, our helpdesk has even had problems getting the user's name a couple of times!!!! In today's multi-network environments, we should ask a simple question which can help determine a network issue "Is anyone else having the same problem ? "

by twyllie

This information is crucial. Many customers will try to do something to solve their problems first and will call the Help Desk only when they can't solve the problem by themselves.

by windy city 2k

An old technique that I learned while doing field service in "Big Blue." At the surface the question implies that the caller is either doing other work, came up with a work around, tried to fix the problem themselves or is dead in the water until their issue is resolved.

What the question is really getting at is an assessment of Urgency.

If they say "I'm dead in the water and I have this deadline by 5 PM tonight..." you know that the situation is urgent.

If they say "I switched to other work and can get back to this application later" you know that the situation is not urgent (not yet anyway).

The question also helps get the caller on the solution side of the fence. Sometimes they think up a creative way to keep their overall workload going while talking with me on the phone or in person.

by figmo

After some years of answering lots of questions on lots of subjects about lots of problems, I decided to strip the process down to the "things" which comprise all problems and their solution(s).

But first, remember this truth: THE OBSERVER IS RESPONSIBLE FOR SOLVING THE PROBLEM. If they cannot solve it themselves then they should attempt to recruit or direct other resources to help THEM solve it. The fact that they call you does NOT make it your problem, unless you accept the role of observer. The, guess what, it becomes your problem.

Note that this is almost always an unpopular point to make because observers assume (and many will say) that once YOU are told about it, it is YOUR problem.

They are wrong because only the observer can test the solution.

So, I offer the following:

A problem is the observer's perception or anticipation of an unacceptable variance between an expected and an experienced outcome after a predetermined event has occurred or period of time has elapsed.

1. Identify the observer.
2. Identify the experienced outcome.
3. Identify the expected outcome.
4. Identify either the predetermined event or the elapsed period of time.
5. Derive the variance between the experienced and expected outcomes.
6. Verify the unacceptability of the issue.
7. Estimate the timing of the next occurence of the problem
8. Assign a priority to the problem solving effort based upon the severity and the estimated amount of time remaining until the next occurrence of the problem.
9. Understand what causes the experienced outcome.
10. Understand what causes the expected outcome.
11. Eliminate the variance between the expected and experienced outcomes, or make the variance acceptable, by changing one or both of the outcomes, selecting a different event and/or adjusting the period of elapsed time.

by jeff

Thats what every help desk needs. On-site service with a cost of 55.oo per call. End users like it better.

by heml0ck

Our corporate policy also forbids installing unauthorized s/w and we could put a new image on any machine not in compliance.
I will NOT, however, nuke the Plant Manager's or senior managers PCs without trying corrective action first, along with a detailed explanation as to what happened on their PC.

by andrew.lawton

Having worked in high level tech support - I got the questions down to the basics:

Who - find out who the caller is and how they can be contacted if contact is lost.

What - what is the problem or complaint.

Where - where do they see this problem occur.

When - when did this first start, when do they see the error.

How - Is there a reproduction scenario to follow in order to reproduce the error or problem. How often does this occur.

Why - if this is a bug - then a companies application staff can answer the why -

Hope this helps.

by nat18466

When client request help via email they should first select a category first, then prioritize your questions with each category
For Example:
1.Software
a.What application?
b.What error message? _________
c.What operating system are you using?________
d.What screen were you in when the error occurred.________

2.Hardware
a.Laptop,Desktop,Handheld? _________
b.Printer,Scanner,Mouse? __________
c.Modem,Router,Cable Modem,DSL ?_________
d.Error message? ___________
c.Symptoms ? ___________

In a live call I always ask these questions -

Software: What is it that you CAN NOT do that you were attempting to do?

Hardware: Have you attempted to reset the equipment - if so what have you done so far?

Categories are much more useful and user friendly because it makes the client feel that they will be able to get faster results because they can choose the specific target issue.
Category choices also teach the client how to distinguish between various aspects of the problem.

by rrosca

Given my latest bouts, I'd say 90% of the time, the problem ends up being malware the likes of Alexa, Dyfuca and VX2. So kindly ask - do you have AdAware installed?

It won't solve everything but in this day and age it will solve a lot of things :)

by litninrod1

Perhaps the most overlooked question in basic troubleshooting..."Have you ever been able to do this process on this machine?" If no, start diving into the specs of the product and find out if the product is designed to do what the user is attempting. If yes, find out what changed -- different machine, signed on to network differently, installed/uninstalled software or hardware. This really helps identify the REAL issue, as opposed to the symptom the user tries (and usually fails) to describe.

And of course, everyone's favorite:
"Is it plugged in?"

Seriously, all of us have stumbled by rushing to what we assumed was the answer and missing the basics.

by clindell

Answer the phone with "Help Desk, this *********, can I have your name (item 1A)? Phone number (Item 1B)? Location (Item 1C) Below?

1. Identify caller
a. Caller?s full name.
b. Caller?s phone numbers.
c. Caller?s location.

2. Identify the nature of the problem or complaint
a. Network
i. What is the error message or behavior?
ii. Is this a recurring problem, or is this the first time?
iii. Have there been any changes to the machine configuration that you know of?
iv. Have you tried rebooting?
v. Is anyone else affected

b. Hardware
i. What is the error message or behavior?
ii. Is this a recurring problem, or is this the first time?
iii. Have there been any changes to the machine configuration that you know of?
iv. Have you tried rebooting?
v. Has anything been moved recently?

c. Software
i. What is the error message or behavior?
ii. Is this a recurring problem, or is this the first time?
iii. Have there been any changes to any software that you know of?
iv. Have you tried using the computer or applications Help?

d. Phone system
i. What is the error message or behavior?
ii. Is this a recurring problem, or is this the first time?
iii. Have there been any changes that you know of?

3. Summary of the problem (description of the problem)
a. Has user done anything to try to solve the problem?

4. Can the caller give specific details about event/error and send them by email and with screen captures if possible?

5. Ask if the caller has a work around (so they are not waiting)
a. Priority of the case (urgent ? high ? medium ? low). Priority depends what the service level agreement says.

by mllwyd

I don't know about your company, but at ours people can access the system multiple ways, and each method requires a different trouble-shooting path. For example, we need to know: is the user on a PC/laptop, using Citrix via a Wyse terminal, using Citrix NFuse from a Macintosh, coming in from home on VPN, or coming in from home via Citrix NFuse?

This discussion is closed to new replies.