Client makesrequest, thenimmediatelymakes anotherrequest reversingthe initial requestAttempted toreach client,client claimsno attemptsmadeTicket isopened rightbeforeclient'svacationRepeatedlyreach out toclient, noresponse untilticket closureAnyPrinterTicketTicket urgent,butdocumentationmissingTicket labeledASAP/Urgent,but clientunavailable.User fatfingerspassword,blames literallyanything elseClient attemptsto use a featureoutside ofintendedpurpose,blames IT.Client complainsabout lack ofservice, attemptto resolve butdelayed due toclientComplete ticketto client'swrittenspecifications,not mentalspecifications.Client ignorespreviouscommunication,new ticketcreatedClient needsto beremindedabout ADSyncClientschedules call,but isunavailable atscheduled timeHorizon OxygenUser forgetpassword withinone businessweek of newpasswordClient calls inwith self-diagnosedsolution.Solution isincorrectClient told tocall, insteademails sayingthey'reavailable for acallNew ticketfor new hirestartingnext dayClient asks help,then refuses helpoutside of slow,frustratingmethods. ITblamed for issuesUser emailsnon-urgentissue, callsimmediatelyafterClient escalatesticket internally,blaming IT.Found to be atfault instead.Client attemptsIT projectwithout IT.Ticket based onmess, not onproject.User submitsticket but omitskey detailsexpecting IT toread mindsTicketcompleted withabove expectedservice, clientcomplainsClient mentoredin how toresolvereoccurringissue, calls inanywayClient makesrequest, thenimmediatelymakes anotherrequest reversingthe initial requestAttempted toreach client,client claimsno attemptsmadeTicket isopened rightbeforeclient'svacationRepeatedlyreach out toclient, noresponse untilticket closureAnyPrinterTicketTicket urgent,butdocumentationmissingTicket labeledASAP/Urgent,but clientunavailable.User fatfingerspassword,blames literallyanything elseClient attemptsto use a featureoutside ofintendedpurpose,blames IT.Client complainsabout lack ofservice, attemptto resolve butdelayed due toclientComplete ticketto client'swrittenspecifications,not mentalspecifications.Client ignorespreviouscommunication,new ticketcreatedClient needsto beremindedabout ADSyncClientschedules call,but isunavailable atscheduled timeHorizon OxygenUser forgetpassword withinone businessweek of newpasswordClient calls inwith self-diagnosedsolution.Solution isincorrectClient told tocall, insteademails sayingthey'reavailable for acallNew ticketfor new hirestartingnext dayClient asks help,then refuses helpoutside of slow,frustratingmethods. ITblamed for issuesUser emailsnon-urgentissue, callsimmediatelyafterClient escalatesticket internally,blaming IT.Found to be atfault instead.Client attemptsIT projectwithout IT.Ticket based onmess, not onproject.User submitsticket but omitskey detailsexpecting IT toread mindsTicketcompleted withabove expectedservice, clientcomplainsClient mentoredin how toresolvereoccurringissue, calls inanyway

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