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