Follow-Up To My Last Post...

[fragbert.livejournal.com]

So Mister "What-Are-My-Initials" calls back, and cannot connect to the network via remote login.

Being the hot-shit analyst that I am, with a memory for these types of (l)users, I solved the case quickly and efficiently.

What follows is an exact c&p of my entire worklog:

Cannot log in to network.
User misspelling his name.
User able to log in with correct spelling.
Closing case.

Comments

[fatesplaything.livejournal.com]

Is your icon from "Internet Killed the Video Star"? I love that video.

[fragbert.livejournal.com]

It sure is! Screencapped it myself, yes I did.

You got some good eyes on you.

Off-topic

[ace-brickman.livejournal.com]

Wonderful parody, that song is!! I pulled out some screencaps mahself for my icon as well. ImageReady is a wonderful thing.

[nightsinger.livejournal.com]

Oh, for the love of everything pretty. The man doesn't know his own name???

There are definitive days when I loathe and despise the human race.

[the-s-guy.livejournal.com]

Had one of those a couple of years ago.

User could not log in to email program.

User was too dopey to make any kind of sense over the phone.

User was unable to give coherent directions to her own desk in the building.

Tracked user down and discovered she had forgotten how to spell her own name, which is needed for logging on to email.

Advised user to get brain scan.

[the-s-guy.livejournal.com]

Reminds me of my own worklogs. The only reason I use four lines on the stupider cases (User getting error X when doing Y; Rebooted PC; No further errors; Gave ticket number) is because the local manager doesn't like it when I use three lines or less.

Personally, I think the problem tracking application should have a checkbox for "Rebooted, no further problems, gave ticket number", so I could have one-line logs.

Or, to be more accurate, end-users should not be calling us without consulting a site tech first, who should ALWAYS try a reboot.