Ticketcompleted withabove expectedservice, clientcomplainsAttempted toreach client,client claimsno attemptsmadeClient ignorespreviouscommunication,new ticketcreatedTicket labeledASAP/Urgent,but clientunavailable.Client makesrequest, thenimmediatelymakes anotherrequest reversingthe initial requestAnyPrinterTicketClient escalatesticket internally,blaming IT.Found to be atfault instead.User submitsticket but omitskey detailsexpecting IT toread mindsUser fatfingerspassword,blames literallyanything elseClientschedules call,but isunavailable atscheduled timeTicket urgent,butdocumentationmissingClient told tocall, insteademails sayingthey'reavailable for acallNew ticketfor new hirestartingnext dayComplete ticketto client'swrittenspecifications,not mentalspecifications.Client complainsabout lack ofservice, attemptto resolve butdelayed due toclientClient attemptsIT projectwithout IT.Ticket based onmess, not onproject.Ticket isopened rightbeforeclient'svacationClient mentoredin how toresolvereoccurringissue, calls inanywayClient needsto beremindedabout ADSyncUser emailsnon-urgentissue, callsimmediatelyafterClient attemptsto use a featureoutside ofintendedpurpose,blames IT.Repeatedlyreach out toclient, noresponse untilticket closureHorizon OxygenUser forgetpassword withinone businessweek of newpasswordClient calls inwith self-diagnosedsolution.Solution isincorrectClient asks help,then refuses helpoutside of slow,frustratingmethods. ITblamed for issuesTicketcompleted withabove expectedservice, clientcomplainsAttempted toreach client,client claimsno attemptsmadeClient ignorespreviouscommunication,new ticketcreatedTicket labeledASAP/Urgent,but clientunavailable.Client makesrequest, thenimmediatelymakes anotherrequest reversingthe initial requestAnyPrinterTicketClient escalatesticket internally,blaming IT.Found to be atfault instead.User submitsticket but omitskey detailsexpecting IT toread mindsUser fatfingerspassword,blames literallyanything elseClientschedules call,but isunavailable atscheduled timeTicket urgent,butdocumentationmissingClient told tocall, insteademails sayingthey'reavailable for acallNew ticketfor new hirestartingnext dayComplete ticketto client'swrittenspecifications,not mentalspecifications.Client complainsabout lack ofservice, attemptto resolve butdelayed due toclientClient attemptsIT projectwithout IT.Ticket based onmess, not onproject.Ticket isopened rightbeforeclient'svacationClient mentoredin how toresolvereoccurringissue, calls inanywayClient needsto beremindedabout ADSyncUser emailsnon-urgentissue, callsimmediatelyafterClient attemptsto use a featureoutside ofintendedpurpose,blames IT.Repeatedlyreach out toclient, noresponse untilticket closureHorizon OxygenUser forgetpassword withinone businessweek of newpasswordClient calls inwith self-diagnosedsolution.Solution isincorrectClient asks help,then refuses helpoutside of slow,frustratingmethods. ITblamed for issues

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