Client needsto beremindedabout ADSyncClient calls inwith self-diagnosedsolution.Solution isincorrectUser emailsnon-urgentissue, callsimmediatelyafterClientschedules call,but isunavailable atscheduled timeComplete ticketto client'swrittenspecifications,not mentalspecifications.Attempted toreach client,client claimsno attemptsmadeUser fatfingerspassword,blames literallyanything elseClient attemptsto use a featureoutside ofintendedpurpose,blames IT.Client escalatesticket internally,blaming IT.Found to be atfault instead.Ticket labeledASAP/Urgent,but clientunavailable.Client complainsabout lack ofservice, attemptto resolve butdelayed due toclientClient ignorespreviouscommunication,new ticketcreatedClient mentoredin how toresolvereoccurringissue, calls inanywayTicket urgent,butdocumentationmissingRepeatedlyreach out toclient, noresponse untilticket closureClient told tocall, insteademails sayingthey'reavailable for acallHorizon OxygenUser forgetpassword withinone businessweek of newpasswordAnyPrinterTicketClient asks help,then refuses helpoutside of slow,frustratingmethods. ITblamed for issuesTicket isopened rightbeforeclient'svacationClient attemptsIT projectwithout IT.Ticket based onmess, not onproject.New ticketfor new hirestartingnext dayTicketcompleted withabove expectedservice, clientcomplainsClient makesrequest, thenimmediatelymakes anotherrequest reversingthe initial requestUser submitsticket but omitskey detailsexpecting IT toread mindsClient needsto beremindedabout ADSyncClient calls inwith self-diagnosedsolution.Solution isincorrectUser emailsnon-urgentissue, callsimmediatelyafterClientschedules call,but isunavailable atscheduled timeComplete ticketto client'swrittenspecifications,not mentalspecifications.Attempted toreach client,client claimsno attemptsmadeUser fatfingerspassword,blames literallyanything elseClient attemptsto use a featureoutside ofintendedpurpose,blames IT.Client escalatesticket internally,blaming IT.Found to be atfault instead.Ticket labeledASAP/Urgent,but clientunavailable.Client complainsabout lack ofservice, attemptto resolve butdelayed due toclientClient ignorespreviouscommunication,new ticketcreatedClient mentoredin how toresolvereoccurringissue, calls inanywayTicket urgent,butdocumentationmissingRepeatedlyreach out toclient, noresponse untilticket closureClient told tocall, insteademails sayingthey'reavailable for acallHorizon OxygenUser forgetpassword withinone businessweek of newpasswordAnyPrinterTicketClient asks help,then refuses helpoutside of slow,frustratingmethods. ITblamed for issuesTicket isopened rightbeforeclient'svacationClient attemptsIT projectwithout IT.Ticket based onmess, not onproject.New ticketfor new hirestartingnext dayTicketcompleted withabove expectedservice, clientcomplainsClient makesrequest, thenimmediatelymakes anotherrequest reversingthe initial requestUser submitsticket but omitskey detailsexpecting IT toread minds

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