No talk, only fix
No talk, only fix
13 comments
-
Out of office message already set, they'll be back to work in about two weeks.
-
More like:
- You file a ticket
- crickets
- IT replies at 2am asking more info.
- IT closes the ticket at 4am because you didn’t respond in 2 hours.
- 9am, you try to reopen the ticket, but the ticket workflow doesn’t allow the ticket to be reopened
- You file a second ticket
- rinse and repeat
-
- My boss sees that I’ve closed 2 priority tickets in a timely manner thus meeting quarterly goals
- He gets executed during the next quarterly staff “restructuring”
- The king is dead, long live the king
- I see our new goals are for even faster close time
- Babylon falls, the wheel turns
Should’ve just dug ditches for the army at least I’d be staying fit.
-
Well at least I'm not the only one who's been through this.
-
Also like:
You open a ticket with all the information you can provide. The ticketing system sends you an email confirming what you've sent.
IT: "What is thing.file?"
????
Send them exactly what you put in the ticket body again.
-
I've decided that's a stall tactic. It's like asking you to pull forward so they can get you fresh fries.
They don't want or need to know if you have version 2.13.45 or 2.13.52 installed, they're bouncing it back to you to game the metrics. The faster you answer their stupid question, the dumber said questions get because they have all of the relevant information already.
Ever notice how they only ask one question at a time? Why not ask all 4 or 5 at once?
-
-
The user failed to respond to repeated contact attempts at X, Y, and Z times using Teams, Slack, Zoom, Whatsapp, and SMS. As such I will be lowering this ticket priority to Low and closing the case with User Not Responding (or if you want to be cheeky, User resolved the issue themselves)
-
"I came back from my vacation, why isn't my issue fixed?"
-
That's why I always appoint someone else as my contact person in these cases.
-
-
13 comments