Right! We'll get *right* on that!!!
Jan. 6th, 2007 08:56 pmI used to work for a temp company for an IT services company at a large aerospace company in town. (and frankly I'm surprised I was not forced to do my own taxes and get classed as a "sub-contractor", which would have made me a sub-sub-contractor. But that's a bit of humor.)
Anyway, My job there was to take tickets that the national help desk would get from the local users, look them over, and assign them to the various departments: Server calls got sent to the server group's bucket, network issues to the network group, deskside calls to the desk monkeys, etc.
One thing we did *not* do was deal with building maintenance. They had their own number to call for support, apparently. The national helpdesk knew this, and knew it well. Almost ten years after the fact, I'm *still* trying to figure out just how the hell we got this ticket in our work queue. It was put in as a 'sev 2' which means that the user is unable to work and needs it resolved ASAP. Riiiight. There is a level above it, sev 1, that is reserved for down servers and outages affecting more then one person.
We already had a few months worth of crap tickets from the national help desk, and management didn't seem to be doing a thing about it, so we decided to make a statement. Hence, the lead dispatcher called our person at the national desk and had this ticket opened up.
very shortly thereafter the national helpdesk started making better quality tickets. The persons who touched the ticket (including Yours Truly) got talked to. Well, just the people in our group. I imagine that the Aerospace Co. employees who touched the ticket were more amused at it then anything. I never found out what happened to them.
(The reason the tickets look like crap is because they sat for the longest time in my paper archive, so they got a bit mangled. and I munged obvious names for my protection. Except for Entex, whom I don't think is still kicking around. They got bought in 2000 by Siemens, and lord only knows what happened afterwards.
Anyway, My job there was to take tickets that the national help desk would get from the local users, look them over, and assign them to the various departments: Server calls got sent to the server group's bucket, network issues to the network group, deskside calls to the desk monkeys, etc.
One thing we did *not* do was deal with building maintenance. They had their own number to call for support, apparently. The national helpdesk knew this, and knew it well. Almost ten years after the fact, I'm *still* trying to figure out just how the hell we got this ticket in our work queue. It was put in as a 'sev 2' which means that the user is unable to work and needs it resolved ASAP. Riiiight. There is a level above it, sev 1, that is reserved for down servers and outages affecting more then one person.
We already had a few months worth of crap tickets from the national help desk, and management didn't seem to be doing a thing about it, so we decided to make a statement. Hence, the lead dispatcher called our person at the national desk and had this ticket opened up.
very shortly thereafter the national helpdesk started making better quality tickets. The persons who touched the ticket (including Yours Truly) got talked to. Well, just the people in our group. I imagine that the Aerospace Co. employees who touched the ticket were more amused at it then anything. I never found out what happened to them.
(The reason the tickets look like crap is because they sat for the longest time in my paper archive, so they got a bit mangled. and I munged obvious names for my protection. Except for Entex, whom I don't think is still kicking around. They got bought in 2000 by Siemens, and lord only knows what happened afterwards.
no subject
Date: 2007-01-07 04:48 am (UTC)ummm... yeah... be RIGHT there...
no subject
Date: 2007-01-07 04:55 am (UTC)no subject
Date: 2007-01-07 06:15 am (UTC)no subject
Date: 2007-01-07 07:35 am (UTC)Of course, sometimes I would get replies to it from those less quick on the uptake. In which case I would just send the datadump again, with the appropriate team and contact number changed to 72 point bright red.
On the extremely few times I got a reply to that, I'd just forward it on to the manager of their office with a cut-n-pasted line asking them to please have a word with their staff.
no subject
Date: 2007-01-07 07:49 am (UTC)In the end the manager had to promise this guy (who was probably on the other side of the country) that he would get his pizzas...
no subject
Date: 2007-01-07 01:26 pm (UTC)no subject
Date: 2007-01-07 06:29 pm (UTC)I once got a ticket for power plugs in a conference room... now this wasnt found out till we had been out to the site 2 or 3 time and had checked every network port in the room... I finally got the idea to ask if it was a power outlet after noticing the number on the ticket for the jack was in a electrical format rather than the fomat commonly used for network jacks at said company...
Another common misrouted ticket I would get is for deskphones.
And once, we, deskside support, got a ticket for a problem with a SQL Server... I just told the guy, "Your supposed to know more about this than me, at any rate, you lost the data, gone, fini, since your a software engineer, try writing an app to fill the database with fake data... it would be really helpfull in the future."
no subject
Date: 2007-01-08 04:02 am (UTC)no subject
Date: 2007-01-08 05:05 am (UTC)Fortunatly, I've run across anything goofy like that at the current place... yet.
no subject
Date: 2007-01-11 12:45 am (UTC)