41 replies
by sean reed
Well, here's how it plays out where I was working, this summer. I came onboard the Information Resources Management team at a large Health Care Center. Now, although certain or your peers may not want to hear this, most of the other workers in IRMhere would go that extra mile and in the process build good relations between IRM and other divisions.
Before I came to work there, in the 70's and 80's, IRM was apparently run by "ticket takers" type IS people, who would handlewhat they could and pass on what they couldn't (without telling the users). But now, every delay is explained to the users, and as a consequence, we're finally starting to live that bad reputation down.
So, yes, I feel that help desks generally should provide extra service to the users. Also, if you explain what you're doing and what it took to correct the problem to the user, then you're less likely to get another call like that again, or at least you'll get less calls like that in the future.
by prmohr
by netty_m
I suppose that you need to find out what your user community expects from the support staff and where you fit into that model. If you are a member of a "call center" than you are a "ticket taker" that does not return calls and research resolution methods. If you are a "Help Desk" than your job is a little different. You are responsible for resolving issues and call backs. Really, it's that simple.
The problem is when your department has no SLA, and your "call center" is called a "help desk" Beg and plea that the management develop SLA's for your team.
by al macintyre
I serve IT needs of 50 users & always have some irons in the fire & periodically check back with them for which is highest priority in their eyes.
I get Same Question / Request from time to time, sometimes from same people. I politely reply thatthis is not impossible but rather we do not have certain key resources essential to the resolution of your need & I have zero indication that management is interested in reviewing their decision not to have these resources. You need to make your case to upper management how important this need is to you, so that they can address why I not have these resources with respect to importance of your needs ... I also tell management that here is another user need dependent on what situation you decided against, that may be worth a review some time.
A few months later history repeats - exact same question request.
There are certain problems that repeat but different players, in which the problem could be avoided in my view if new hires got a modicum of relevant training in the computer infrastructure they are to use. I walk the player through how to deal with their situation & I periodically inform management how much resource being wasted because of people who do not get proper training - that is all I can do.
Occasionally I give upper management a list of recurring scenarios & problem areas I think we collectively could do a better job of avoiding but the causes are out of my control.
I also provide progress reports on the software that is under development but not yet completed, and make announcements of deployment of new features as they come available.
by soozi13
Previous to the position I currently have I worked for a company that provided Help Desk Services to many companies , they would outsource the help Desks to our company and we would set up a separate desk for every company, and the desk that I was on provided services to the largest film and camera maker in the U.S., our desk of 10 people supported 45 thousand plus of their employees, and unfortunatley the company that I worked for was paid by the tkt. So for every tkt created the company was paid a set fee , And I had a supervisor with no Technical knowledge whatsoever, who's main goal for the desk was pump those tkts out make lots of dollars but do not spend any time with your customers , I had a real problem with that theroy , I need tofollow thru with every customer to make sure that the problem was fixed and they have a clear understanding of their resolutions, and for the 2 years I was on that desk I managed to juggle thru my day taking an average of 60-75 calls a day and follow thru with the customers (but it was very tiring),Which Brings up a very good point for another disscusion Is Outsourcing a good thing to do ? (Not) The company that I work for now has theier own in house help desk which I am on and I enjoy the ability to follow thru with every customer with praise from my supervisor for my commitment to the customer , instead of having to work extra hours without extra pay and hide my follow ups from my previous company\supervisor.
Suzi
by al macintyre
You see variations of this in the insurance industry ... resolve claims, get minimum $ paid, do not holistically look at the needs of the customer, so the quality of medicine suffers, and there is a disconnect between what is advertised & what is delivered.
We need some ratings from the customers ... I happen in my career to have used many different tech support places & from my perspective they are as different as night & day in the delivery of quality.
Some places you call - give company identity, serial # of equipment we calling about & they look up data base & know that equipment is covered & who we are & access to prior calls, so we do not have to go through extensive identification of our reality.
Other places you have to repeat a bunch of identification material with every call to follow-up on something that was not resolved with the last call.
Some places can dial into your computer & run diagnostics, or you dial into theirs & authorize diagnostics, so that they have very powerful software designed for diagnostics that ordinarily no need for on customer machine, so they automate much of the process of playing detective.
Other places you end up with end user who is ignorant on many technicalities talking to person who needs to know those technicalities.
Some places have learned how to walk total know nothing computer users through a variety of tests & be totally diplomatic the whole way such that the tests narrow down what the problems are.
by wayne m.
Nothing tarnishes the reputation of the help desk faster than lack of information and follow up.
It is a common complaint that the help desk serves as a big black hole for problem reports. A second complaint is corrections that don't solve the problem. Be sure to let users know when someone is likely to address their problems and be sure to follow up to make sure their problems were resolved.
There are two possible approaches. The help desk can take the initiative and keep users informed or the help desk can expect users to periodically call back to find out what's going on. I don't think anyone favors the latter approach.
by jaley
It's a really intersting question, and something that we struggled with at my former employer. My former company was based in Chicago, but had offices scattered all over the country. Therefore, most support done was over the phone. Obviously, some fixes took 30 minutes, while others could takes days, or sometimes weeks. It just depended on the situation. However, the biggest complaint that I heard when I came onboard as Help Desk Manager was that there was little-to-no followup on the current status of the issue. The end-users had no idea where their issue stood, and/or what was being done to remedy it.
I took a look at what some of the big computer companies do, and chose Gateway as a good example. Every time I deal with Gateway, they DO provide that "extra touch" that you mention in your message. They are professional, courteous, and their follow-up is excellent. That's the way I tried to model our local help desk.
In other words, yes, I believe that the help desk does have the obligation to followup, touch base, etc... There is a lot more to that job than just being a ticket taker. Good question!
JPA
*Maybe your company needs me to come manage your help desk?????? :)
by sheilau
It is nice to know that other large companies have more service-oriented help desks. The same thing happened here, where the help desk had a horrible reputation until new management took over and started pushing for better customer service. It's hard to convince some old-school techs of that, though. They don't feel the need to provide that follow up, or even stay on the phone to make sure their fix worked for the user. It's not really something that can be taught, it seems - people have to have an inclination towards customer service for it to be effective. Anyway, it's good to know that others have fought this battle as well.
BTW - thanks for the management offer, but we just got a new one who is working out rather well!!
by clair
by o/siris
When an end user calls about a problem, and that call needs to be referred to someone else. Even then, do you think the user is thinking about that next level when they're in the dark?
Nope. They think "Help Desk." Others have already spoken about efficiency and the need for centralized management of users' calls. I'm thinking a little bit differently here. The Help Desk is the primary point of contact. It is "The Place" to which users turn when something goes awry.
I've had upset users when the Help Desk could not answer their question. But I've had BALLISTIC users when that Help Desk could not inform them of call status. And it's almost never the other way around. In fact, my own experience has been that users that go ballistic right away are almost always ones that have run into this failing of the Help Desk before.
Who is on their mind when they think about the problems they face? That is almost always the Help Desk. Doesn't it make sense to meet that expectation?
R?? Vargas
by mal4462
by dpennell
by rich_zei
by jerryb
by jerryb
by cajundon
My help desk is flooded with calls and you can only have a certain number of help desk representatives to stay in business.
If you combine that with customer service, the customer will have a longer wait time for the answer to their problem.
Customer service follow up should be done by the sales representative, who sold the computer system to the customer, and to keep the customer happy.
Don Thibodaux, Don's Computer Systems.
by jrowland
Your job is not to be some robotic solving machine. It has been proven again and again that the first IT face or voice someone hears is your help desk. Want to set the mood as a uncaring IT company or department. Brusquely answer calls and just provide what you have to. Be like Packard Bell who blew it on customer service. Or GNN who did the same as well.
Customer Service is not defined by a customer service rep. Everybody in your company is in Customer service. Unless you don't have customers then you must understand that you need to help each customer as they need it. Anybody can do the service, it just has to be everybody doing it.
Don, consider this. If you need your car repaired you go to the mechanic. The mechanic just fixes the problem speaks one or two words with you and is only concerned with getting the next customer in and out. You would be a little ticked perhaps? Might take your business elsewhere, hmmm?
I know that the rude techs at Dell are very seriously threatening their contract with us. We may pull out because they have gone from being very customer service oriented to more tech oriented.
Jon Rowland
Client Services Supervisor
by al macintyre
Depending on the size of your business, staffing, tech support, infrastructure, corporate culture, management style, etc
You can have a standard form summarizing status on work in progress that will take more than a day to resolve.
Statement of the Problem.
Business Case to Solve it ... consequences if it is not solved.
Urgency ... is the end user DOWN ... is work not getting done ... is it taking excessively long to do the work ... is cash flow impaired ... have some codes relating to nature of urgency
What KIND of problem is it ... i.e. needs to be solved via programming, bug hunt, end user training, sounds like a hardware problem ... tentative diagnosis
Who is working on this, periodically give a progress report
Each time the form is updated ... copy access to it to interested parties
Also have a report with 1-3 lines per active form ... open issues status, what got closed resolved.
by al macintyre
A company can also maintain a knowledge data base of similar issues.
I have one relating to things that often go wrong & how to repair the damage & what if anything we can be doing to lead to that problem happening less often & what sometimes goes wrong when we fixing the thing that went wrong & how to verify this incident is now resolved. Then each time we have an incident that was not without further incidents, I refine the how to cope document to help with the next time.
Now the customer sales person has access to our history of service issues with that customer, so that when they have their next contact they know ALL the open issues, including the fact they have not paid some bills from 6 months ago & that we are working on fixing this & that problem & they had an engineering change request & we sent out samples of it but they never approved it so what should we do with these new buy orders for the new version that they have not yet approved or given any reason it is not Ok.
In other words, size of business can mean many contacts between our people & their people on multitude of specialities, but system of paperwork records needs to be such that it all can be correlated & right people updated on timely basis.
by sheilau
by reggie
by rbonahue
by hardhead
Really I think it is a 2 way street. I currently work for a software developer who has international resellers spread around the world. A lot of the time, a problem will come to us from a reseller, a response will go back with a request for feedbackon the result of the fix. 9 out of 10 times this feedback does not occur and we then have to chase the reseller for the information.
I have also been on the other end of the stick, working for an international reseller who sent problems to the developers for resolutions and bug fixes. In this case, 9 out of 10 times we had to chase these developers for the status of a request. In both cases I have implemented a weekly reporting schedule that outlined the status of currently open tickets. This has helped to clear up a lot of confussion and also get a more accurate picture of the current open ticket situation. It has also served to open up a clearer line of communication between all parties involved. Everyone now knows what is expected of them when a problem comes in an also when it goes out.
by boonchung
Yes. But they must be properly trained and motivated to handle the task at hand.Customer service is basically the core of the company. Many organization assumes that only the customer service department handle the client/customer. They are mistaken.
Front desk staff are your frontliners. Customer sees them first and last. A good impression therefore is essential.
Customer service, even on a small scale is important! I work on internal support desk for about 150 users, myself and one other, and we have a workflow, the call is logged, e-mailed to the relevant user informing them of the ticket number and the engineer has been assigned. The access database also informs the user when the ticket has been closed. In between, I try and keep the user informed every other day as to my progress, out of courtesy.
All of this customer service is just good manners and a good control system in place.
Be nice and play well with others
Of course they should, I know when dealing with some of our vendors and their help desks I am thankful for their help but sometimes I have some questions that come up after getting off the phone. If the questions seem trivial or are just curiosity Idon't want to take the time with the call. Also after being on eternal hold for help, or being told that I have called the wrong number, or being told it isn't their problem it would be nice for someone to just touch base and act as if they care if my problem was taken care of or that I might be satisfied with the results of my solution.
Because of my experiences with a lot of the rude companies (Symantec) I make sure that I always touch base with a contact within the week and reconnect with them the following week. It may be a pain sometimes for me and the client, but if it makes one in a hundred happy then it is worth it. I have found though, the majority of clients appreciate it and remember it.
by rvmc
by al macintyre
There are a lot of expenses associated with getting a new customer, but once you have that customer, it is cheaper to service the new customer, than the work that must continue to get more customers.
Word of mouth from happy satisfied customers to new potential customers is the cheapest & best form of advertising.
Keeping customers happy is perhaps more than the purpose of this discussion group, but it is at the core of policies that dictate what constitutes good quality customer service.
by identcc
by lodi44
I would have to agree that help desk should provide follow-up calls and the like. This is very true as I am help desk, customer service, researcher, and problem solver in a small library. People bring computer problems in because they do not trustthe help center sometimes and that they want a person to look at the computer. Also, I help in refernece follow-ups to ensure that the person finds the materials that will do the job.
My 2 cents
Michaelibrarian@hotbot.com
by rich_zei
While I have found your scenario to be true. Calls need to go to the Service Center/Help Desk ar what ever you need to call it so that there is a record of the issue. With out that record, it is impossible to track trends. This plays right into the whole issue of CS. If the techs are following up with customers on fixes,procedures et.al, then training/hardware/software issues and trends can be addressed by the IT/IS dept. Which in the end makes our jobs that much easier. It also makes the users less likley to show up at your desk and say, " My machine is doing (fill in issue), could you take a quick look? " In my experience this usualy means that there is a major time consuming issue that has been going on for months, on all the machines in a department and never addressed.
rich
by kasperilio
by hlp8620
I think it depends on the structure & the mentality of the organization. If the help desk has enough qualified people to answer the questions and the tools, then the help desk would be able to provide a necessary service.
However, very few companies provide adquate tools to the people that work in a job control "ticket taker office" or the tools to provide the extra mile service.
I come from the TV repair business that kept a record of EVERY product repaired. Something like the doctor's office. If the help desk office has kept a record of every problem that is called into the office and each help desk employee can quickly access these records and the employee that works in that office has the mental skills, then they have a foundation to build the extra mile service.
I used to work in what was called Job Control. The most people we had at one time working were two. Some days I would open & close 80 jobs in an eight hour shift.
We were ticket takers. We did not have time for many questions.
by rsmith
by conniea
by al macintyre
Some places will not help you unless you do their work analysing their software to locate their bugs ... then still want to give you an arguement.
Here I am in which I know the purpose of the software, I have identified the specific program that is spitting out bad data under what circumstances, well documented examples, I have dug into the source code & identified the lines of code that are causing this, and they still want to give me an arguement.
I go on the internet discussion group &learn of many other programs that other customers have gone through the same process with them.
I am talking about the reality where I am the IT person serving the needs of 50 users at a company sharing an ERP in which the source code is like millions of lines of code. I can fix things, but I also have a shared responsibility with other customers of the package to get the vendor to fix things that we find wrong, so that other customers in future releases will also get better software thanksto all of our input.
by al macintyre
Help Desk Personnel need Training of Different Kinds ... Diplomacy, Tact, Technical Issues, Paperwork Tracking to Log what they did for larger Management Perspectives.
There are different kinds of help desks.
A company that is servicing the needs of outside customers. A desk that is servicing its own personnel. Outsourcing that.
Are the people being served in the same building city you are in so easier to visit them, or are you talking to folks in another city.
Do you have software such that you can see on your screen what they are doing on their screen.
I have a deal where I start the copy function & the user at far end can say yes or no on the copying. I do not see the keystrokes the person made, but I do see what showsup on their screen so I am on the phone with them & I say STOP ... you see that error message on bottom of screen ... please move cursor so it is over top & then press F1 which is the help key ... I want to see more detail on that error message.
Without tools like that, it can make work of help desk so much more unproductive.
This discussion is closed to new replies.
Trending Community archive posts
Sort by Trending