Ticket urgent,butdocumentationmissingClient makesrequest, thenimmediatelymakes anotherrequest reversingthe initial requestClient escalatesticket internally,blaming IT.Found to be atfault instead.User emailsnon-urgentissue, callsimmediatelyafterClient ignorespreviouscommunication,new ticketcreatedClient calls inwith self-diagnosedsolution.Solution isincorrectTicketcompleted withabove expectedservice, clientcomplainsClient told tocall, insteademails sayingthey'reavailable for acallAnyPrinterTicketClient asks help,then refuses helpoutside of slow,frustratingmethods. ITblamed for issuesUser submitsticket but omitskey detailsexpecting IT toread mindsClient attemptsto use a featureoutside ofintendedpurpose,blames IT.Client needsto beremindedabout ADSyncClient complainsabout lack ofservice, attemptto resolve butdelayed due toclientComplete ticketto client'swrittenspecifications,not mentalspecifications.User fatfingerspassword,blames literallyanything elseNew ticketfor new hirestartingnext dayHorizon OxygenUser forgetpassword withinone businessweek of newpasswordTicket isopened rightbeforeclient'svacationAttempted toreach client,client claimsno attemptsmadeClient attemptsIT projectwithout IT.Ticket based onmess, not onproject.Clientschedules call,but isunavailable atscheduled timeClient mentoredin how toresolvereoccurringissue, calls inanywayTicket labeledASAP/Urgent,but clientunavailable.Repeatedlyreach out toclient, noresponse untilticket closureTicket urgent,butdocumentationmissingClient makesrequest, thenimmediatelymakes anotherrequest reversingthe initial requestClient escalatesticket internally,blaming IT.Found to be atfault instead.User emailsnon-urgentissue, callsimmediatelyafterClient ignorespreviouscommunication,new ticketcreatedClient calls inwith self-diagnosedsolution.Solution isincorrectTicketcompleted withabove expectedservice, clientcomplainsClient told tocall, insteademails sayingthey'reavailable for acallAnyPrinterTicketClient asks help,then refuses helpoutside of slow,frustratingmethods. ITblamed for issuesUser submitsticket but omitskey detailsexpecting IT toread mindsClient attemptsto use a featureoutside ofintendedpurpose,blames IT.Client needsto beremindedabout ADSyncClient complainsabout lack ofservice, attemptto resolve butdelayed due toclientComplete ticketto client'swrittenspecifications,not mentalspecifications.User fatfingerspassword,blames literallyanything elseNew ticketfor new hirestartingnext dayHorizon OxygenUser forgetpassword withinone businessweek of newpasswordTicket isopened rightbeforeclient'svacationAttempted toreach client,client claimsno attemptsmadeClient attemptsIT projectwithout IT.Ticket based onmess, not onproject.Clientschedules call,but isunavailable atscheduled timeClient mentoredin how toresolvereoccurringissue, calls inanywayTicket labeledASAP/Urgent,but clientunavailable.Repeatedlyreach out toclient, noresponse untilticket closure

IT Bingo - Call List

(Print) Use this randomly generated list as your call list when playing the game. There is no need to say the BINGO column name. Place some kind of mark (like an X, a checkmark, a dot, tally mark, etc) on each cell as you announce it, to keep track. You can also cut out each item, place them in a bag and pull words from the bag.


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
  1. Ticket urgent, but documentation missing
  2. Client makes request, then immediately makes another request reversing the initial request
  3. Client escalates ticket internally, blaming IT. Found to be at fault instead.
  4. User emails non-urgent issue, calls immediately after
  5. Client ignores previous communication, new ticket created
  6. Client calls in with self-diagnosed solution. Solution is incorrect
  7. Ticket completed with above expected service, client complains
  8. Client told to call, instead emails saying they're available for a call
  9. Any Printer Ticket
  10. Client asks help, then refuses help outside of slow, frustrating methods. IT blamed for issues
  11. User submits ticket but omits key details expecting IT to read minds
  12. Client attempts to use a feature outside of intended purpose, blames IT.
  13. Client needs to be reminded about AD Sync
  14. Client complains about lack of service, attempt to resolve but delayed due to client
  15. Complete ticket to client's written specifications, not mental specifications.
  16. User fat fingers password, blames literally anything else
  17. New ticket for new hire starting next day
  18. Horizon Oxygen User forget password within one business week of new password
  19. Ticket is opened right before client's vacation
  20. Attempted to reach client, client claims no attempts made
  21. Client attempts IT project without IT. Ticket based on mess, not on project.
  22. Client schedules call, but is unavailable at scheduled time
  23. Client mentored in how to resolve reoccurring issue, calls in anyway
  24. Ticket labeled ASAP/Urgent, but client unavailable.
  25. Repeatedly reach out to client, no response until ticket closure