T1 said theyread KBs butdidn't actuallyapply the infoCame toyou as aP1 but itain'tTroubleshootingsteps don'tmatch the caseNo issuesby the timeyou got thecaseT1 shouldhave knownhow to fix itHelpedsomeone ona specificcaseCame to youas a P2 butshould be aP0 or P1Didn't tellclient theywereescalatingResolutionwasprovided butT1 escalatedanywayTold clientT2 wouldfix it (outof scope)Case from aclient inimplementationDidn'tpin aBomgarSent to CoreApp when itwas reallySRT1 tookover aweek toescalateT1attemptedadatapumpCase froman internalclient(anotherdepartment)Did not haveanytroubleshootingCame toyou as aP0 but itain'tCase sentup with anangryclientSent casestraight toT2T1 didn'teven tryHad to tellSupe thatthis one maybring theboomHad tophone afriend forhelp on acaseGot a100%CSATT1 said theyread KBs butdidn't actuallyapply the infoCame toyou as aP1 but itain'tTroubleshootingsteps don'tmatch the caseNo issuesby the timeyou got thecaseT1 shouldhave knownhow to fix itHelpedsomeone ona specificcaseCame to youas a P2 butshould be aP0 or P1Didn't tellclient theywereescalatingResolutionwasprovided butT1 escalatedanywayTold clientT2 wouldfix it (outof scope)Case from aclient inimplementationDidn'tpin aBomgarSent to CoreApp when itwas reallySRT1 tookover aweek toescalateT1attemptedadatapumpCase froman internalclient(anotherdepartment)Did not haveanytroubleshootingCame toyou as aP0 but itain'tCase sentup with anangryclientSent casestraight toT2T1 didn'teven tryHad to tellSupe thatthis one maybring theboomHad tophone afriend forhelp on acaseGot a100%CSAT

Crazy Case Friday - 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
  1. T1 said they read KBs but didn't actually apply the info
  2. Came to you as a P1 but it ain't
  3. Troubleshooting steps don't match the case
  4. No issues by the time you got the case
  5. T1 should have known how to fix it
  6. Helped someone on a specific case
  7. Came to you as a P2 but should be a P0 or P1
  8. Didn't tell client they were escalating
  9. Resolution was provided but T1 escalated anyway
  10. Told client T2 would fix it (out of scope)
  11. Case from a client in implementation
  12. Didn't pin a Bomgar
  13. Sent to Core App when it was really SR
  14. T1 took over a week to escalate
  15. T1 attempted a datapump
  16. Case from an internal client (another department)
  17. Did not have any troubleshooting
  18. Came to you as a P0 but it ain't
  19. Case sent up with an angry client
  20. Sent case straight to T2
  21. T1 didn't even try
  22. Had to tell Supe that this one may bring the boom
  23. Had to phone a friend for help on a case
  24. Got a 100% CSAT