We need it now

So, we had a new business unit opening up beginning of December last year.  They needed an MFP.  Wasn't the top of the list, but it was on the list.  So, end of December I order the machine.  They've already been open for a while, and haven't mentioned anything about it.

Machine gets delivered middle of January, I store it in my office and I ask the business unit leader where they want it.  She says she'll get back to me.  A week later I follow up by e-mail to see if she has decided.  No response.  So, I let it go.

Two months later, work ticket comes in asking that it be put in a location where it won't work.  I respond to that ticket with that information and ask for a different location.

Two months after that, a work ticket comes in saying exactly what the first work ticket said.  So, I say "This is exactly what you already put in with ticket number ####".  And I copy and paste the whole old work ticket into the new one.  She comes back with "I don't know how to pick a spot, can you help?"  I respond that I can.  I suggest a couple of dates.  Those dates come and go, with no communication.

A week after the last date, she contacts me and suggests a date.  I accept.

That's where we're at now.

The point:  I cannot believe that a business unit leader couldn't even communicate about a need she had.

It's broken!

So, I've had a low-priority item on my to do list.  It was a small piece of technology that was "broken".  So, I put it off for quite a while.

Finally, due to the length of time it had been on the list, it moved to the top of the list.  So, we ordered a $500 replacement / upgrade for the broken part.  I received it and installed it today.  Then, I removed the "broken" piece of technology, brought it back to my desk and tried it out.

Guess what happened.

It worked.

I know you must be shocked that a user would complain for months about something being "broken" when it actually works.

But, I ask myself about their actions, "Was it worth it?"

Really?

Found this on another site...

It rings pretty true...

First Post

Today we received an e-mail from a supervisor passing along an angry e-mail from a staff member.  Apparently, that staff member's name was spelled incorrectly in our e-mail system.  Some things jumped out to me.

First, that staff member's account was created over 7 months ago.  This person's name has been wrong for 7 months!  What would possess someone to wait 7 months to get the problem resolved?

Second, during that time there were exactly 0 work tickets placed in our system, 0 phone calls, 0 e-mails and 0 times talking to a technician in person.  After exactly 0 attempts to use any of the communication methods supplied to contact us about the problem, the first contact we have is from an angry employee's supervisor.

Finally, upon doing research, we discover that the way the name is spelled currently is exactly the way Human Resources sent us the name.

So we get an angry person who should have contacted us months ago angrily communicating with us through their supervisor (who now also has a bad opinion of us) about something that could have been easily resolved (again many months ago) if only they had told us sooner.  On top of all that, the error isn't even our fault. 

Welcome to the Helpdesk.

Welcome

Welcome to the Really? Technology Blog.  At this site, we will publish stories related to disbelief and technology.

We look forward to the laughter.  Hope you do too.