Came to youas a P2 butshould be aP0 or P1Case from aclient inimplementationCase sentup with anangryclientDid not haveanytroubleshootingGot a100%CSATHelpedsomeone ona specificcaseSent to CoreApp when itwas reallySRCame toyou as aP1 but itain'tT1 tookover aweek toescalateT1attemptedadatapumpHad to tellSupe thatthis one maybring theboomDidn'tpin aBomgarSent casestraight toT2T1 said theyread KBs butdidn't actuallyapply the infoTroubleshootingsteps don'tmatch the caseTold clientT2 wouldfix it (outof scope)T1 didn'teven tryNo issuesby the timeyou got thecaseT1 shouldhave knownhow to fix itCase froman internalclient(anotherdepartment)Resolutionwasprovided butT1 escalatedanywayDidn't tellclient theywereescalatingCame toyou as aP0 but itain'tHad tophone afriend forhelp on acaseCame to youas a P2 butshould be aP0 or P1Case from aclient inimplementationCase sentup with anangryclientDid not haveanytroubleshootingGot a100%CSATHelpedsomeone ona specificcaseSent to CoreApp when itwas reallySRCame toyou as aP1 but itain'tT1 tookover aweek toescalateT1attemptedadatapumpHad to tellSupe thatthis one maybring theboomDidn'tpin aBomgarSent casestraight toT2T1 said theyread KBs butdidn't actuallyapply the infoTroubleshootingsteps don'tmatch the caseTold clientT2 wouldfix it (outof scope)T1 didn'teven tryNo issuesby the timeyou got thecaseT1 shouldhave knownhow to fix itCase froman internalclient(anotherdepartment)Resolutionwasprovided butT1 escalatedanywayDidn't tellclient theywereescalatingCame toyou as aP0 but itain'tHad tophone afriend forhelp on acase

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