Horizon OxygenUser forgetpassword withinone businessweek of newpasswordClient calls inwith self-diagnosedsolution.Solution isincorrectAttempted toreach client,client claimsno attemptsmadeUser emailsnon-urgentissue, callsimmediatelyafterClient escalatesticket internally,blaming IT.Found to be atfault instead.Client mentoredin how toresolvereoccurringissue, calls inanywayTicketcompleted withabove expectedservice, clientcomplainsComplete ticketto client'swrittenspecifications,not mentalspecifications.User submitsticket but omitskey detailsexpecting IT toread mindsNew ticketfor new hirestartingnext dayClientschedules call,but isunavailable atscheduled timeUser fatfingerspassword,blames literallyanything elseAnyPrinterTicketClient attemptsIT projectwithout IT.Ticket based onmess, not onproject.Ticket urgent,butdocumentationmissingTicket isopened rightbeforeclient'svacationClient makesrequest, thenimmediatelymakes anotherrequest reversingthe initial requestClient ignorespreviouscommunication,new ticketcreatedClient complainsabout lack ofservice, attemptto resolve butdelayed due toclientClient asks help,then refuses helpoutside of slow,frustratingmethods. ITblamed for issuesClient told tocall, insteademails sayingthey'reavailable for acallTicket labeledASAP/Urgent,but clientunavailable.Client attemptsto use a featureoutside ofintendedpurpose,blames IT.Repeatedlyreach out toclient, noresponse untilticket closureClient needsto beremindedabout ADSyncHorizon OxygenUser forgetpassword withinone businessweek of newpasswordClient calls inwith self-diagnosedsolution.Solution isincorrectAttempted toreach client,client claimsno attemptsmadeUser emailsnon-urgentissue, callsimmediatelyafterClient escalatesticket internally,blaming IT.Found to be atfault instead.Client mentoredin how toresolvereoccurringissue, calls inanywayTicketcompleted withabove expectedservice, clientcomplainsComplete ticketto client'swrittenspecifications,not mentalspecifications.User submitsticket but omitskey detailsexpecting IT toread mindsNew ticketfor new hirestartingnext dayClientschedules call,but isunavailable atscheduled timeUser fatfingerspassword,blames literallyanything elseAnyPrinterTicketClient attemptsIT projectwithout IT.Ticket based onmess, not onproject.Ticket urgent,butdocumentationmissingTicket isopened rightbeforeclient'svacationClient makesrequest, thenimmediatelymakes anotherrequest reversingthe initial requestClient ignorespreviouscommunication,new ticketcreatedClient complainsabout lack ofservice, attemptto resolve butdelayed due toclientClient asks help,then refuses helpoutside of slow,frustratingmethods. ITblamed for issuesClient told tocall, insteademails sayingthey'reavailable for acallTicket labeledASAP/Urgent,but clientunavailable.Client attemptsto use a featureoutside ofintendedpurpose,blames IT.Repeatedlyreach out toclient, noresponse untilticket closureClient needsto beremindedabout ADSync

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