How to stop walk-ins at the helpdesk
Hey all,
I was wondering what were some ways to stop people from dropping by the helpdesk, and have them just give us a call instead?
Thanks,
Ryan
Junk
Hey all,
I was wondering what were some ways to stop people from dropping by the helpdesk, and have them just give us a call instead?
Thanks,
Ryan
by cleaverx
Ryan, strap on your helmet, fix your bayonet and prepare to repeal! Seriously, short of locking yourself in, there is no real way to do it, however I have found a way that is distasteful to all but the most determined trespasser. You must understand, that most people do not travel from their station to the Help Desk just to report trouble; usually they are just in the area on unrelated business, so they figure:"Hey I am here already, might as well just walk in". Sure you can sit there and explain the policy and how it is supposed to work, but really, how many times do you want to have that argument? What I did was this: I created a form for them to fill out, I made sure to make it a real pain too, with lots of fields. I made a lot of copies and clipped them on a board by my desk (he he he). It went like this:
(Big smile)"Welcome to the Help Desk, what can I do for you?..bla, bla; What? Trouble you say? Well you know, the policy is that you should call this in, but hey, since you are already here, go ahead and fill out this here form!!". Once the word got out, the number of drop-ins went down to single digits for any given month! Also, this kind of written records can be used for all sorts of things..it turns out that supervisors do not care for people spending time away from their work station filling out forms, when they SHOULD BE USING THE PHONE!!! he he he.
Talk to your supervisor, and let us know how it turn out.
Dismissed soldier!!!
Brigadier General CleaverX
by absolutely
by jdclyde
I don't understand why someone walking up to the "help desk" can't be helped?
Is there something magical about getting them on the phone that enables them to be helped better?
Is this a case of people forgetting the reason they have a job in the first place? To help the users?
A techs job is to enable the end-user to do their job more efficiently. Period. As soon as people remember that the users are our customers and we don't have a job without them, the better off everyone is.
Users will a lot of times believe that if they show up in person it will give them priority then you lose productivity time by stopping what you are working on.
So IT is there to give user support and to provide the best service. To do that are the very reasons helpdesk policies are created.
by aka.dunby
Well I think I noticed you were 3rd level support so would confirm you may work in a more reactionary environment.
As for service desks, the main issue with walk in traffic is expiring SLA's currently in the system. A client from a remote site should not be disadvantaged by staff who can access their service desk on foot.
Simply log the call into the system by email, web or telephone and based on priority, business impact and then logged time a call will be resolved, not based on accessibility.
that would be my stance on walk in traffic
Paul
At least when I'm at the desk I can log the call, and I have references available to research the problem.
When they stop me in the hall, I'm usually responding to someone else's call. When I tell them to leave a voice mail or send an e-mail as a reminder, some of them act put out. Apparently it's a big hassle to spend two minutes sending me a reminder for a problem they forgot they had until they spotted me en route.
by jdclyde
My coworkers have. B-)
When we have to go to a remote location, there are all the people that have "problems" they need help with. Of course they weren't big enough problems to CALL or email about them.
My coworkers would not know how to say "no" and would get re-directed to handle these problems and never get to what they went on location for in the first place. So the person that followed procedures got punished and the people that don't get the reward. Not a good lesson for user to learn!
When I ran into people trying this same thing, I would politely show them my orderly checklist of what I am on-site for, and I write them in at the BOTTOM of the list with the clear understanding that I might not have enough time in the day to get to them on that trip and to make sure to contact me before hand to get them further up the list.
If I have a full days work planned, I make a point to only take the tools I need to do THAT job, so I can just tell the rest I CAN'T work on it because they didn't say anything about it before hand, so I was not prepared to handle that problem and don't have the tools I need. Bottom of the list.
Because when I go on-site I DO get my assigned job completed, I now am sent more often than the counter-parts. Good thing I like to go for joy rides.
I WAS suppose to go down to Grand Rapids today, but with the ice and snow storms, I vetoed that and will go later in the week.
by darinhamer
You're talking about a hijacking now. You can't log a ticket or track the incident. Shoot, if enough people do this to you on your way to and from the bathroom, you may not even be able to remember the incident. You should refuse to help people in this instance, because in the long run it is doing more harm than good.
In this instance, tell them that you are going to have to have them give you a call/send you an e-mail when they get back to their desk. But that protects you and ensures that their issue gets the proper attention. This is not the same thing as saying that you don't want to have to wait on people in person when you are at the helpdesk.
by atcollege
by dmambo
But you should use helpdesk software and tell them that you can only respond to requests logged thru the system. I know that it's our job to provide excellent support with a minimum of red tape, but it's really not fair to you if users drop by because it doesn't give you a chance to do any type of research or put in any thought into the problem since drop-bys often expect an immediate answer.
It's also not fair to those people who play by the rules and access the help system thru the accepted channels.
I think the biggest hurdle you'll face is the arguement that "I know this will only take you a minute...."
by absolutely
isn't to be confrontational.
You seem to have some specific knowledge about this professional's work environment that I didn't see posted.
"It's also not fair to those people who play by the rules and access the help system thru the accepted channels."
I just didn't read anywhwere that he said that approaching the desk in person is [i]not[/i] an accepted channel, and in my job at a helpdesk, it most definitely [i]was[/i] an accepted channel. For very basic software & equipment support of a very small academic computer lab, but my point is that the job offered to me included the expectation of both taking calls, and walk-up requests. The fact that there [i]is[/i] a 'desk' to which users can walk, also suggests to me that this is legitimately a part of his job, just a part that he dislikes.
by dmambo
I often find that walk-ins to my office just happen to hit when I'm into deep concentration mode. By dropping what I'm doing, which can often be what they expect, I find that I lose my momentum on the project that I'm focused on. If that's the situation when the phone rings or when I'm alerted to a new system help request, I at least have the choice to make whatever notes I need so that I will have a mental bookmark before I respond to them.
Just seems to work out best for me. And we do have a system that users are supposed to follow. All that being said, I also agree with Palmetto's post below. Sometimes the requests can be pretty far off the mark as compared to the nature of the problem.
BTW - It's sad that one can't have an intellectual discussion around here without others getting confrontational... ;)
We have a system for the user to enter their calls, but I prefer to enter them myself.
If they enter the call, the description is usually way out in left field. Often a user-diagnosed problem is wrong and I lose time working on a false lead.
If I'm going to get any benefit from the call's solution in the future, I have to rewrite the whole to eliminate the false "diagnose". It's easier to do it myself from scratch.
Finally, if they submit it, I have to keep checking the call list. I've already got to check e-mail and voice mail. I don't need another communications method to keep up with. If I enter the calls, I don't get surprised when something new pops up.
The users in our other facility submit their own calls, but there are more users and more techs. The call goes into a queue for the next tech.
by jdclyde
My favorite thing is when people call and tell me their PC is dead. I tell them to send me an email on it and I will get right on it!
After a short stunned silence, I tell them I am joking and will get right on it. B-)
I don't know why, but I prefer getting up and going to the user as opposed to working remotely.
Perhaps its because the "face time" gives the user the idea I care (even when I don't ;-) ) Perhaps its because I look for excuses to get off my donkey and burn a few calories. Perhaps it's just because I hate holding a phone to my ear. Fortunately, my help desk is located pretty much in the middle of the facility and no user is more than a hundred yards away.
I reserve remote access for those occasions when the help desk at our other facility is understaffed or overloaded and I have to pick up the slack.
by w2ktechman
Unless the person is off-site, I get off the phone quickly with a "I'll be right there", and head to their desk.
Usually, when they call on the phone (on-site people at least) they are mostly incoherent and I cannot figure out what they want anyway. when I walk up they talk much differently and usually I can figure out the problem in mere seconds.
by atcollege
by cleaverx
by mjd420nova
by pgm554
You'll be amazed how quickly those annoying (L)USERS will quit showing up at the help desk.
Leaving a dirty hypodermic and a heroin cooking spoon laying around sometimes works too(but not very well in NYC or Philly,they'll just want to borrow your works).
by bschaettle
Just have some really awful, bizarre food to share with them. And don't take "no" for an answer -- just dish it up and hand them a plateful and a plastic fork. And make sure to wear a shirt with plenty of food stains on it.
Also, being overly friendly, talking their ear off, and inquiring endlessly about their family ("and how did your mother's colonoscopy go?") will help drive them away, as well.
If they get what they want when they drop by your office then they will do it again. If they don't get what they want then they may eventually stop. I have, on many occasions, explained to people that I was busy when they interrupted me and that they will have to call the help desk or send an email to me explaining their question or problem. Then you just return to working on whatever you were working on before you were interrupted.
It's really just that simple. You may think that the sky is going to fall or that you will lose your job. I've handled office drop by's like this for many years and I did not lose my job or whatever as a result of telling people, politely but firmly, that they have to call the help desk or send an email and that I cannot be interrupted when I am working on something. It really works.
Or, when that fails, I use a lamp cord plugged into the wall socket and touch the bare ends to the person's naughty bits. Electricity can be very persuasive. Either they will get the message or their heart will stop beating. The problem is solved either way.
by willjamr
Don't like walk in clients? Lock the door! Seriously, what's all this whining about not logging the incident if the user walks in? Any good help desk software will allow the help desk personnel to make entries!
Help desk where I work has gadgets at each desk which light red leds in a circle sequentially when the help desk person is on the phone. Helps the walk in to avoid talking to someone who is currently on the phone.
by gsg
by w2ktechman
by mr.wiz
by saihib
by sasha
First I created a helpdesk email address, then a helpdesk form. Then added the helpdesk procedures into our computer use policy. Folks are to email thier request, or submit a hard copy request. We then will triage all helpdesk requests, and respond to them in order of urgency/importance.
Now, for the most part folks use the system correctly. When they ask any of us directly, we do the following: First, We ask the individual to go ahead and send in thier request via the helpdesk email system, and explain that it helps us track our work. We will then either take care of thier problem right then, or we tell them that as soon as it hits the helpdesk email it will be triaged. It all depends on thier urgency, and our current work load. I also send out occasional email reminding folks of the procedures for the helpdesk. You will always have people stopping you in the hall, the bathroom, coming by the computer room, etc. But if you have a system and policy set up like what we have done, more often than not, people will follow the rules. It has helped us out greatly. We have been much more effective in our help desk support, and by using a central helpdesk email for folks to submit thier problems/questions, we have been able to proactively assess reoccuring issues and Questions.
by 50kilroy
The whole idea of being in the service industry is ....service. You should be viewing your users as the reason for your existance and then treat them as such.
Many people like the face-to-face approach, some feel that they can better explain their problem in person, some are just in the area and drop by to ask for a service call.
Rebuffing the user community will result in your Helpdesk becoming known as the title of this reply....
by ctmcswain
I tend to disagree with the statement, "You should be viewing your users as the reason for your existence and then treat them as such." I feel that is a God Complex just waiting to happen. I mean let's be honest, If we all did that, ALL users would be getting new computers/monitors every 6-12 weeks. I agree that the Help Desk should be service oriented but you have to manage resources so that you aren't spread too thin and so that issues don't "backup". I think there ideal system has a set policy for logging incidents, prioritizing them, and then correcting the issue. Once a "tech" has been assigned an incident the customer service portion of the job now becomes his responsibility. Good communication between the tech and the "customer" is an absolute necessity. 99% of the time, I've found the user doesn't care how back up you are, or how it takes for you to get to them as long as you make contact and clue them into the situation and let them know that you HAVEN'T forgotten about them and that you are in fact on your way as soon as possible.
*Steps off soap box*
by absolutely
[i]I tend to disagree with the statement, "You should be viewing your users as the reason for your existence and then treat them as such." I feel that is a God Complex just waiting to happen. I mean let's be honest, If we all did that, ALL users would be getting new computers/monitors every 6-12 weeks.[/i]
It is possible to decline a request while being accessible. Maybe you aren't at a 'help desk' at all, and this doesn't apply? If you are, though, having "a set policy for logging incidents, prioritizing them, and then correcting the issue" shouldn't prevent you from being available to assist and to answer questions, even if the answer sometimes is "I don't have time for that." Like I said, if you're in IT but [i]not[/i] at a Help Desk, none of this applies. But if you do have a desk that is supposed to be available for drop-in questions, get used to working for a living, and doing the tasks delineated in your job description.
by darinhamer
You post says "I think there ideal system has a set policy for logging incidents, prioritizing them, and then correcting the issue."
You are right. But set up your process so that it can accommodate walk-ins as well as phone calls and e-mails. You can manage resources even with a customer standing at your desk. No, they shouldn't move to the front of the line just because they showed up in person. But, you should still help them. And your process should accommodate that.
by atcollege
by dancinkatieh
by willjamr
"That's a cute answer but some places don't have doors."
I meant it to be cute.
Just this morning a coworker wandered in to my cubicle and asked for help. Help with an area supported by two people down the hall from me. And I helped them. And, no, I don't work at the help desk.
by ron_007
(lots of clever ideas posted so far that cover most of the points I wanted to make)
What is your corporate policy about the issue (walk up help desk requests)?
Everything you do should be controled by official published corporate policy. If there is no current Help Desk policy, then ask your manager to get one created, and published so that everyone knows what it is.
But regardless of the policy, or actually as part of the policy, if you have a help desk application that is used to track and schedule help requests, part of your response has be be along the lines of "... yes I can help you, but your request (no matter how apparently trivial) has to logged in the help request system. This is very important because we use it to assign priority to all of the requests. AND ..., at the end of the year statistics taken from the help desk system are used to create next year's help desk budget. If we have a lot of calls logged that have unacceptably (by corporate policy) long waits before action is take, we stand a better chance of getting more resources (ie money &/or people) assigned to working solve problems in future." That way you are not simply an IT "Policy Parrot" saying no! You are saying, "yes but" and giving them a good reason why the "but" is worth while for them.
You have to make it clear to them, verbally and by your subsequent actions, that walkup requests do NOT automatically get priority response. Walk-ups get added to the queue of all other requests, its action order depends on the standard pre-defined priority criteria.
PS: My (least) favorite help desk policy response is "oh, our policy for ALL software problems is to simply re-install windoze and all of your applications. By the way, I started the process 5 minutes ago, I hope you have already saved everything you want to keep from your HD to the LAN ... . You haven't, gee sorry, I thought you knew (snicker snicker)".
by ron_007
You can also check out this link:
http://downloads.techrepublic.com.com/download.aspx?docid=173363
10 ways to decline a request for free tech support
It is only obliquely related to your question, but you might get a useable idea or two. Or at least a chuckle.
This discussion is closed to new replies.
Sort by Trending