New ticketfor new hirestartingnext dayTicketcompleted withabove expectedservice, clientcomplainsClientschedules call,but isunavailable atscheduled timeClient ignorespreviouscommunication,new ticketcreatedClient attemptsIT projectwithout IT.Ticket based onmess, not onproject.Client calls inwith self-diagnosedsolution.Solution isincorrectClient complainsabout lack ofservice, attemptto resolve butdelayed due toclientComplete ticketto client'swrittenspecifications,not mentalspecifications.Client asks help,then refuses helpoutside of slow,frustratingmethods. ITblamed for issuesClient mentoredin how toresolvereoccurringissue, calls inanywayUser fatfingerspassword,blames literallyanything elseRepeatedlyreach out toclient, noresponse untilticket closureTicket labeledASAP/Urgent,but clientunavailable.Attempted toreach client,client claimsno attemptsmadeUser emailsnon-urgentissue, callsimmediatelyafterTicket isopened rightbeforeclient'svacationClient makesrequest, thenimmediatelymakes anotherrequest reversingthe initial requestClient escalatesticket internally,blaming IT.Found to be atfault instead.Client attemptsto use a featureoutside ofintendedpurpose,blames IT.User submitsticket but omitskey detailsexpecting IT toread mindsClient needsto beremindedabout ADSyncTicket urgent,butdocumentationmissingAnyPrinterTicketClient told tocall, insteademails sayingthey'reavailable for acallHorizon OxygenUser forgetpassword withinone businessweek of newpasswordNew ticketfor new hirestartingnext dayTicketcompleted withabove expectedservice, clientcomplainsClientschedules call,but isunavailable atscheduled timeClient ignorespreviouscommunication,new ticketcreatedClient attemptsIT projectwithout IT.Ticket based onmess, not onproject.Client calls inwith self-diagnosedsolution.Solution isincorrectClient complainsabout lack ofservice, attemptto resolve butdelayed due toclientComplete ticketto client'swrittenspecifications,not mentalspecifications.Client asks help,then refuses helpoutside of slow,frustratingmethods. ITblamed for issuesClient mentoredin how toresolvereoccurringissue, calls inanywayUser fatfingerspassword,blames literallyanything elseRepeatedlyreach out toclient, noresponse untilticket closureTicket labeledASAP/Urgent,but clientunavailable.Attempted toreach client,client claimsno attemptsmadeUser emailsnon-urgentissue, callsimmediatelyafterTicket isopened rightbeforeclient'svacationClient makesrequest, thenimmediatelymakes anotherrequest reversingthe initial requestClient escalatesticket internally,blaming IT.Found to be atfault instead.Client attemptsto use a featureoutside ofintendedpurpose,blames IT.User submitsticket but omitskey detailsexpecting IT toread mindsClient needsto beremindedabout ADSyncTicket urgent,butdocumentationmissingAnyPrinterTicketClient told tocall, insteademails sayingthey'reavailable for acallHorizon 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. New ticket for new hire starting next day
  2. Ticket completed with above expected service, client complains
  3. Client schedules call, but is unavailable at scheduled time
  4. Client ignores previous communication, new ticket created
  5. Client attempts IT project without IT. Ticket based on mess, not on project.
  6. Client calls in with self-diagnosed solution. Solution is incorrect
  7. Client complains about lack of service, attempt to resolve but delayed due to client
  8. Complete ticket to client's written specifications, not mental specifications.
  9. Client asks help, then refuses help outside of slow, frustrating methods. IT blamed for issues
  10. Client mentored in how to resolve reoccurring issue, calls in anyway
  11. User fat fingers password, blames literally anything else
  12. Repeatedly reach out to client, no response until ticket closure
  13. Ticket labeled ASAP/Urgent, but client unavailable.
  14. Attempted to reach client, client claims no attempts made
  15. User emails non-urgent issue, calls immediately after
  16. Ticket is opened right before client's vacation
  17. Client makes request, then immediately makes another request reversing the initial request
  18. Client escalates ticket internally, blaming IT. Found to be at fault instead.
  19. Client attempts to use a feature outside of intended purpose, blames IT.
  20. User submits ticket but omits key details expecting IT to read minds
  21. Client needs to be reminded about AD Sync
  22. Ticket urgent, but documentation missing
  23. Any Printer Ticket
  24. Client told to call, instead emails saying they're available for a call
  25. Horizon Oxygen User forget password within one business week of new password