Complete ticketto client'swrittenspecifications,not mentalspecifications.Attempted toreach client,client claimsno attemptsmadeClient attemptsto use a featureoutside ofintendedpurpose,blames IT.Repeatedlyreach out toclient, noresponse untilticket closureTicket labeledASAP/Urgent,but clientunavailable.Client makesrequest, thenimmediatelymakes anotherrequest reversingthe initial requestClientschedules call,but isunavailable atscheduled timeClient mentoredin how toresolvereoccurringissue, calls inanywayUser emailsnon-urgentissue, callsimmediatelyafterClient escalatesticket internally,blaming IT.Found to be atfault instead.Ticket isopened rightbeforeclient'svacationClient needsto beremindedabout ADSyncClient told tocall, insteademails sayingthey'reavailable for acallClient complainsabout lack ofservice, attemptto resolve butdelayed due toclientUser submitsticket but omitskey detailsexpecting IT toread mindsTicket urgent,butdocumentationmissingUser fatfingerspassword,blames literallyanything elseTicketcompleted withabove expectedservice, clientcomplainsClient calls inwith self-diagnosedsolution.Solution isincorrectClient ignorespreviouscommunication,new ticketcreatedClient asks help,then refuses helpoutside of slow,frustratingmethods. ITblamed for issuesNew ticketfor new hirestartingnext dayAnyPrinterTicketClient attemptsIT projectwithout IT.Ticket based onmess, not onproject.Horizon OxygenUser forgetpassword withinone businessweek of newpasswordComplete ticketto client'swrittenspecifications,not mentalspecifications.Attempted toreach client,client claimsno attemptsmadeClient attemptsto use a featureoutside ofintendedpurpose,blames IT.Repeatedlyreach out toclient, noresponse untilticket closureTicket labeledASAP/Urgent,but clientunavailable.Client makesrequest, thenimmediatelymakes anotherrequest reversingthe initial requestClientschedules call,but isunavailable atscheduled timeClient mentoredin how toresolvereoccurringissue, calls inanywayUser emailsnon-urgentissue, callsimmediatelyafterClient escalatesticket internally,blaming IT.Found to be atfault instead.Ticket isopened rightbeforeclient'svacationClient needsto beremindedabout ADSyncClient told tocall, insteademails sayingthey'reavailable for acallClient complainsabout lack ofservice, attemptto resolve butdelayed due toclientUser submitsticket but omitskey detailsexpecting IT toread mindsTicket urgent,butdocumentationmissingUser fatfingerspassword,blames literallyanything elseTicketcompleted withabove expectedservice, clientcomplainsClient calls inwith self-diagnosedsolution.Solution isincorrectClient ignorespreviouscommunication,new ticketcreatedClient asks help,then refuses helpoutside of slow,frustratingmethods. ITblamed for issuesNew ticketfor new hirestartingnext dayAnyPrinterTicketClient attemptsIT projectwithout IT.Ticket based onmess, not onproject.Horizon OxygenUser forgetpassword withinone businessweek of newpassword

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