Came toyou as aP1 but itain'tCase sentup with anangryclientTroubleshootingsteps don'tmatch the caseCame toyou as aP0 but itain'tSent to CoreApp when itwas reallySRHad tophone afriend forhelp on acaseSent casestraight toT2Resolutionwasprovided butT1 escalatedanywayT1 shouldhave knownhow to fix itDidn'tpin aBomgarHad to tellSupe thatthis one maybring theboomT1attemptedadatapumpCase froman internalclient(anotherdepartment)T1 tookover aweek toescalateGot a100%CSATCase from aclient inimplementationHelpedsomeone ona specificcaseCame to youas a P2 butshould be aP0 or P1T1 didn'teven tryT1 said theyread KBs butdidn't actuallyapply the infoDidn't tellclient theywereescalatingTold clientT2 wouldfix it (outof scope)Did not haveanytroubleshootingNo issuesby the timeyou got thecaseCame toyou as aP1 but itain'tCase sentup with anangryclientTroubleshootingsteps don'tmatch the caseCame toyou as aP0 but itain'tSent to CoreApp when itwas reallySRHad tophone afriend forhelp on acaseSent casestraight toT2Resolutionwasprovided butT1 escalatedanywayT1 shouldhave knownhow to fix itDidn'tpin aBomgarHad to tellSupe thatthis one maybring theboomT1attemptedadatapumpCase froman internalclient(anotherdepartment)T1 tookover aweek toescalateGot a100%CSATCase from aclient inimplementationHelpedsomeone ona specificcaseCame to youas a P2 butshould be aP0 or P1T1 didn'teven tryT1 said theyread KBs butdidn't actuallyapply the infoDidn't tellclient theywereescalatingTold clientT2 wouldfix it (outof scope)Did not haveanytroubleshootingNo issuesby the timeyou got thecase

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