Ticketcompleted withabove expectedservice, clientcomplainsUser emailsnon-urgentissue, callsimmediatelyafterClient needsto beremindedabout ADSyncClient makesrequest, thenimmediatelymakes anotherrequest reversingthe initial requestUser submitsticket but omitskey detailsexpecting IT toread mindsClient mentoredin how toresolvereoccurringissue, calls inanywayClient asks help,then refuses helpoutside of slow,frustratingmethods. ITblamed for issuesClientschedules call,but isunavailable atscheduled timeTicket isopened rightbeforeclient'svacationRepeatedlyreach out toclient, noresponse untilticket closureClient ignorespreviouscommunication,new ticketcreatedNew ticketfor new hirestartingnext dayClient attemptsIT projectwithout IT.Ticket based onmess, not onproject.Client escalatesticket internally,blaming IT.Found to be atfault instead.Ticket labeledASAP/Urgent,but clientunavailable.Ticket urgent,butdocumentationmissingClient complainsabout lack ofservice, attemptto resolve butdelayed due toclientClient attemptsto use a featureoutside ofintendedpurpose,blames IT.User fatfingerspassword,blames literallyanything elseHorizon OxygenUser forgetpassword withinone businessweek of newpasswordComplete ticketto client'swrittenspecifications,not mentalspecifications.Attempted toreach client,client claimsno attemptsmadeClient told tocall, insteademails sayingthey'reavailable for acallAnyPrinterTicketClient calls inwith self-diagnosedsolution.Solution isincorrectTicketcompleted withabove expectedservice, clientcomplainsUser emailsnon-urgentissue, callsimmediatelyafterClient needsto beremindedabout ADSyncClient makesrequest, thenimmediatelymakes anotherrequest reversingthe initial requestUser submitsticket but omitskey detailsexpecting IT toread mindsClient mentoredin how toresolvereoccurringissue, calls inanywayClient asks help,then refuses helpoutside of slow,frustratingmethods. ITblamed for issuesClientschedules call,but isunavailable atscheduled timeTicket isopened rightbeforeclient'svacationRepeatedlyreach out toclient, noresponse untilticket closureClient ignorespreviouscommunication,new ticketcreatedNew ticketfor new hirestartingnext dayClient attemptsIT projectwithout IT.Ticket based onmess, not onproject.Client escalatesticket internally,blaming IT.Found to be atfault instead.Ticket labeledASAP/Urgent,but clientunavailable.Ticket urgent,butdocumentationmissingClient complainsabout lack ofservice, attemptto resolve butdelayed due toclientClient attemptsto use a featureoutside ofintendedpurpose,blames IT.User fatfingerspassword,blames literallyanything elseHorizon OxygenUser forgetpassword withinone businessweek of newpasswordComplete ticketto client'swrittenspecifications,not mentalspecifications.Attempted toreach client,client claimsno attemptsmadeClient told tocall, insteademails sayingthey'reavailable for acallAnyPrinterTicketClient calls inwith self-diagnosedsolution.Solution isincorrect

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