Client ignorespreviouscommunication,new ticketcreatedUser fatfingerspassword,blames literallyanything elseTicket labeledASAP/Urgent,but clientunavailable.Ticket isopened rightbeforeclient'svacationClient attemptsto use a featureoutside ofintendedpurpose,blames IT.Client mentoredin how toresolvereoccurringissue, calls inanywayClient calls inwith self-diagnosedsolution.Solution isincorrectComplete ticketto client'swrittenspecifications,not mentalspecifications.Attempted toreach client,client claimsno attemptsmadeTicket urgent,butdocumentationmissingClient complainsabout lack ofservice, attemptto resolve butdelayed due toclientRepeatedlyreach out toclient, noresponse untilticket closureClient attemptsIT projectwithout IT.Ticket based onmess, not onproject.Horizon OxygenUser forgetpassword withinone businessweek of newpasswordClient told tocall, insteademails sayingthey'reavailable for acallClient escalatesticket internally,blaming IT.Found to be atfault instead.Client asks help,then refuses helpoutside of slow,frustratingmethods. ITblamed for issuesClient needsto beremindedabout ADSyncClientschedules call,but isunavailable atscheduled timeUser submitsticket but omitskey detailsexpecting IT toread mindsUser emailsnon-urgentissue, callsimmediatelyafterAnyPrinterTicketClient makesrequest, thenimmediatelymakes anotherrequest reversingthe initial requestTicketcompleted withabove expectedservice, clientcomplainsNew ticketfor new hirestartingnext dayClient ignorespreviouscommunication,new ticketcreatedUser fatfingerspassword,blames literallyanything elseTicket labeledASAP/Urgent,but clientunavailable.Ticket isopened rightbeforeclient'svacationClient attemptsto use a featureoutside ofintendedpurpose,blames IT.Client mentoredin how toresolvereoccurringissue, calls inanywayClient calls inwith self-diagnosedsolution.Solution isincorrectComplete ticketto client'swrittenspecifications,not mentalspecifications.Attempted toreach client,client claimsno attemptsmadeTicket urgent,butdocumentationmissingClient complainsabout lack ofservice, attemptto resolve butdelayed due toclientRepeatedlyreach out toclient, noresponse untilticket closureClient attemptsIT projectwithout IT.Ticket based onmess, not onproject.Horizon OxygenUser forgetpassword withinone businessweek of newpasswordClient told tocall, insteademails sayingthey'reavailable for acallClient escalatesticket internally,blaming IT.Found to be atfault instead.Client asks help,then refuses helpoutside of slow,frustratingmethods. ITblamed for issuesClient needsto beremindedabout ADSyncClientschedules call,but isunavailable atscheduled timeUser submitsticket but omitskey detailsexpecting IT toread mindsUser emailsnon-urgentissue, callsimmediatelyafterAnyPrinterTicketClient makesrequest, thenimmediatelymakes anotherrequest reversingthe initial requestTicketcompleted withabove expectedservice, clientcomplainsNew ticketfor new hirestartingnext day

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