Repeatedlyreach out toclient, noresponse untilticket closureAnyPrinterTicketAttempted toreach client,client claimsno attemptsmadeClient calls inwith self-diagnosedsolution.Solution isincorrectTicket urgent,butdocumentationmissingClient needsto beremindedabout ADSyncClientschedules call,but isunavailable atscheduled timeHorizon OxygenUser forgetpassword withinone businessweek of newpasswordClient complainsabout lack ofservice, attemptto resolve butdelayed due toclientClient asks help,then refuses helpoutside of slow,frustratingmethods. ITblamed for issuesClient makesrequest, thenimmediatelymakes anotherrequest reversingthe initial requestTicketcompleted withabove expectedservice, clientcomplainsUser emailsnon-urgentissue, callsimmediatelyafterComplete ticketto client'swrittenspecifications,not mentalspecifications.Client told tocall, insteademails sayingthey'reavailable for acallTicket isopened rightbeforeclient'svacationNew ticketfor new hirestartingnext dayClient attemptsto use a featureoutside ofintendedpurpose,blames IT.User fatfingerspassword,blames literallyanything elseTicket labeledASAP/Urgent,but clientunavailable.User submitsticket but omitskey detailsexpecting IT toread mindsClient attemptsIT projectwithout IT.Ticket based onmess, not onproject.Client mentoredin how toresolvereoccurringissue, calls inanywayClient escalatesticket internally,blaming IT.Found to be atfault instead.Repeatedlyreach out toclient, noresponse untilticket closureAnyPrinterTicketAttempted toreach client,client claimsno attemptsmadeClient calls inwith self-diagnosedsolution.Solution isincorrectTicket urgent,butdocumentationmissingClient needsto beremindedabout ADSyncClientschedules call,but isunavailable atscheduled timeHorizon OxygenUser forgetpassword withinone businessweek of newpasswordClient complainsabout lack ofservice, attemptto resolve butdelayed due toclientClient asks help,then refuses helpoutside of slow,frustratingmethods. ITblamed for issuesClient makesrequest, thenimmediatelymakes anotherrequest reversingthe initial requestTicketcompleted withabove expectedservice, clientcomplainsUser emailsnon-urgentissue, callsimmediatelyafterComplete ticketto client'swrittenspecifications,not mentalspecifications.Client told tocall, insteademails sayingthey'reavailable for acallTicket isopened rightbeforeclient'svacationNew ticketfor new hirestartingnext dayClient attemptsto use a featureoutside ofintendedpurpose,blames IT.User fatfingerspassword,blames literallyanything elseTicket labeledASAP/Urgent,but clientunavailable.User submitsticket but omitskey detailsexpecting IT toread mindsClient attemptsIT projectwithout IT.Ticket based onmess, not onproject.Client mentoredin how toresolvereoccurringissue, calls inanywayClient escalatesticket internally,blaming IT.Found to be atfault instead.

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