Sent to CoreApp when itwas reallySRDid not haveanytroubleshootingGot a100%CSATHad to tellSupe thatthis one maybring theboomT1 said theyread KBs butdidn't actuallyapply the infoSent casestraight toT2Didn't tellclient theywereescalatingTold clientT2 wouldfix it (outof scope)Helpedsomeone ona specificcaseTroubleshootingsteps don'tmatch the caseCase sentup with anangryclientHad tophone afriend forhelp on acaseCame toyou as aP1 but itain'tT1 tookover aweek toescalateNo issuesby the timeyou got thecaseT1attemptedadatapumpDidn'tpin aBomgarResolutionwasprovided butT1 escalatedanywayCase from aclient inimplementationCame toyou as aP0 but itain'tCase froman internalclient(anotherdepartment)T1 didn'teven tryCame to youas a P2 butshould be aP0 or P1T1 shouldhave knownhow to fix itSent to CoreApp when itwas reallySRDid not haveanytroubleshootingGot a100%CSATHad to tellSupe thatthis one maybring theboomT1 said theyread KBs butdidn't actuallyapply the infoSent casestraight toT2Didn't tellclient theywereescalatingTold clientT2 wouldfix it (outof scope)Helpedsomeone ona specificcaseTroubleshootingsteps don'tmatch the caseCase sentup with anangryclientHad tophone afriend forhelp on acaseCame toyou as aP1 but itain'tT1 tookover aweek toescalateNo issuesby the timeyou got thecaseT1attemptedadatapumpDidn'tpin aBomgarResolutionwasprovided butT1 escalatedanywayCase from aclient inimplementationCame toyou as aP0 but itain'tCase froman internalclient(anotherdepartment)T1 didn'teven tryCame to youas a P2 butshould be aP0 or P1T1 shouldhave knownhow to fix it

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