Complete ticketto client'swrittenspecifications,not mentalspecifications.Ticket labeledASAP/Urgent,but clientunavailable.Client mentoredin how toresolvereoccurringissue, calls inanywayClient attemptsIT projectwithout IT.Ticket based onmess, not onproject.Client needsto beremindedabout ADSyncTicket isopened rightbeforeclient'svacationUser fatfingerspassword,blames literallyanything elseUser emailsnon-urgentissue, callsimmediatelyafterClient attemptsto use a featureoutside ofintendedpurpose,blames IT.Client makesrequest, thenimmediatelymakes anotherrequest reversingthe initial requestNew ticketfor new hirestartingnext dayClient calls inwith self-diagnosedsolution.Solution isincorrectClientschedules call,but isunavailable atscheduled timeClient escalatesticket internally,blaming IT.Found to be atfault instead.Ticket urgent,butdocumentationmissingHorizon OxygenUser forgetpassword withinone businessweek of newpasswordClient ignorespreviouscommunication,new ticketcreatedClient told tocall, insteademails sayingthey'reavailable for acallClient complainsabout lack ofservice, attemptto resolve butdelayed due toclientUser submitsticket but omitskey detailsexpecting IT toread mindsRepeatedlyreach out toclient, noresponse untilticket closureAnyPrinterTicketClient asks help,then refuses helpoutside of slow,frustratingmethods. ITblamed for issuesAttempted toreach client,client claimsno attemptsmadeTicketcompleted withabove expectedservice, clientcomplainsComplete ticketto client'swrittenspecifications,not mentalspecifications.Ticket labeledASAP/Urgent,but clientunavailable.Client mentoredin how toresolvereoccurringissue, calls inanywayClient attemptsIT projectwithout IT.Ticket based onmess, not onproject.Client needsto beremindedabout ADSyncTicket isopened rightbeforeclient'svacationUser fatfingerspassword,blames literallyanything elseUser emailsnon-urgentissue, callsimmediatelyafterClient attemptsto use a featureoutside ofintendedpurpose,blames IT.Client makesrequest, thenimmediatelymakes anotherrequest reversingthe initial requestNew ticketfor new hirestartingnext dayClient calls inwith self-diagnosedsolution.Solution isincorrectClientschedules call,but isunavailable atscheduled timeClient escalatesticket internally,blaming IT.Found to be atfault instead.Ticket urgent,butdocumentationmissingHorizon OxygenUser forgetpassword withinone businessweek of newpasswordClient ignorespreviouscommunication,new ticketcreatedClient told tocall, insteademails sayingthey'reavailable for acallClient complainsabout lack ofservice, attemptto resolve butdelayed due toclientUser submitsticket but omitskey detailsexpecting IT toread mindsRepeatedlyreach out toclient, noresponse untilticket closureAnyPrinterTicketClient asks help,then refuses helpoutside of slow,frustratingmethods. ITblamed for issuesAttempted toreach client,client claimsno attemptsmadeTicketcompleted withabove expectedservice, clientcomplains

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