Client attemptsIT projectwithout IT.Ticket based onmess, not onproject.Client needsto beremindedabout ADSyncComplete ticketto client'swrittenspecifications,not mentalspecifications.Client ignorespreviouscommunication,new ticketcreatedTicket labeledASAP/Urgent,but clientunavailable.Client makesrequest, thenimmediatelymakes anotherrequest reversingthe initial requestClient attemptsto use a featureoutside ofintendedpurpose,blames IT.Ticketcompleted withabove expectedservice, clientcomplainsClientschedules call,but isunavailable atscheduled timeClient asks help,then refuses helpoutside of slow,frustratingmethods. ITblamed for issuesClient told tocall, insteademails sayingthey'reavailable for acallUser fatfingerspassword,blames literallyanything elseUser emailsnon-urgentissue, callsimmediatelyafterNew ticketfor new hirestartingnext dayAttempted toreach client,client claimsno attemptsmadeRepeatedlyreach out toclient, noresponse untilticket closureClient calls inwith self-diagnosedsolution.Solution isincorrectUser submitsticket but omitskey detailsexpecting IT toread mindsAnyPrinterTicketClient mentoredin how toresolvereoccurringissue, calls inanywayClient complainsabout lack ofservice, attemptto resolve butdelayed due toclientClient escalatesticket internally,blaming IT.Found to be atfault instead.Ticket isopened rightbeforeclient'svacationHorizon OxygenUser forgetpassword withinone businessweek of newpasswordTicket urgent,butdocumentationmissingClient attemptsIT projectwithout IT.Ticket based onmess, not onproject.Client needsto beremindedabout ADSyncComplete ticketto client'swrittenspecifications,not mentalspecifications.Client ignorespreviouscommunication,new ticketcreatedTicket labeledASAP/Urgent,but clientunavailable.Client makesrequest, thenimmediatelymakes anotherrequest reversingthe initial requestClient attemptsto use a featureoutside ofintendedpurpose,blames IT.Ticketcompleted withabove expectedservice, clientcomplainsClientschedules call,but isunavailable atscheduled timeClient asks help,then refuses helpoutside of slow,frustratingmethods. ITblamed for issuesClient told tocall, insteademails sayingthey'reavailable for acallUser fatfingerspassword,blames literallyanything elseUser emailsnon-urgentissue, callsimmediatelyafterNew ticketfor new hirestartingnext dayAttempted toreach client,client claimsno attemptsmadeRepeatedlyreach out toclient, noresponse untilticket closureClient calls inwith self-diagnosedsolution.Solution isincorrectUser submitsticket but omitskey detailsexpecting IT toread mindsAnyPrinterTicketClient mentoredin how toresolvereoccurringissue, calls inanywayClient complainsabout lack ofservice, attemptto resolve butdelayed due toclientClient escalatesticket internally,blaming IT.Found to be atfault instead.Ticket isopened rightbeforeclient'svacationHorizon OxygenUser forgetpassword withinone businessweek of newpasswordTicket urgent,butdocumentationmissing

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