Client needsto beremindedabout ADSyncClient told tocall, insteademails sayingthey'reavailable for acallTicketcompleted withabove expectedservice, clientcomplainsClient attemptsto use a featureoutside ofintendedpurpose,blames IT.Ticket labeledASAP/Urgent,but clientunavailable.Complete ticketto client'swrittenspecifications,not mentalspecifications.Attempted toreach client,client claimsno attemptsmadeHorizon OxygenUser forgetpassword withinone businessweek of newpasswordClientschedules call,but isunavailable atscheduled timeClient escalatesticket internally,blaming IT.Found to be atfault instead.Client complainsabout lack ofservice, attemptto resolve butdelayed due toclientClient calls inwith self-diagnosedsolution.Solution isincorrectAnyPrinterTicketUser submitsticket but omitskey detailsexpecting IT toread mindsUser fatfingerspassword,blames literallyanything elseClient mentoredin how toresolvereoccurringissue, calls inanywayClient asks help,then refuses helpoutside of slow,frustratingmethods. ITblamed for issuesUser emailsnon-urgentissue, callsimmediatelyafterTicket urgent,butdocumentationmissingTicket isopened rightbeforeclient'svacationClient ignorespreviouscommunication,new ticketcreatedRepeatedlyreach out toclient, noresponse untilticket closureClient makesrequest, thenimmediatelymakes anotherrequest reversingthe initial requestClient attemptsIT projectwithout IT.Ticket based onmess, not onproject.New ticketfor new hirestartingnext dayClient needsto beremindedabout ADSyncClient told tocall, insteademails sayingthey'reavailable for acallTicketcompleted withabove expectedservice, clientcomplainsClient attemptsto use a featureoutside ofintendedpurpose,blames IT.Ticket labeledASAP/Urgent,but clientunavailable.Complete ticketto client'swrittenspecifications,not mentalspecifications.Attempted toreach client,client claimsno attemptsmadeHorizon OxygenUser forgetpassword withinone businessweek of newpasswordClientschedules call,but isunavailable atscheduled timeClient escalatesticket internally,blaming IT.Found to be atfault instead.Client complainsabout lack ofservice, attemptto resolve butdelayed due toclientClient calls inwith self-diagnosedsolution.Solution isincorrectAnyPrinterTicketUser submitsticket but omitskey detailsexpecting IT toread mindsUser fatfingerspassword,blames literallyanything elseClient mentoredin how toresolvereoccurringissue, calls inanywayClient asks help,then refuses helpoutside of slow,frustratingmethods. ITblamed for issuesUser emailsnon-urgentissue, callsimmediatelyafterTicket urgent,butdocumentationmissingTicket isopened rightbeforeclient'svacationClient ignorespreviouscommunication,new ticketcreatedRepeatedlyreach out toclient, noresponse untilticket closureClient makesrequest, thenimmediatelymakes anotherrequest reversingthe initial requestClient attemptsIT projectwithout IT.Ticket based onmess, not onproject.New ticketfor new hirestartingnext day

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