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