Didn'tpin aBomgarTold clientT2 wouldfix it (outof scope)T1 shouldhave knownhow to fix itDidn't tellclient theywereescalatingTroubleshootingsteps don'tmatch the caseResolutionwasprovided butT1 escalatedanywayGot a100%CSATHad tophone afriend forhelp on acaseT1 tookover aweek toescalateSent casestraight toT2Had to tellSupe thatthis one maybring theboomT1attemptedadatapumpDid not haveanytroubleshootingCame toyou as aP1 but itain'tCame to youas a P2 butshould be aP0 or P1T1 said theyread KBs butdidn't actuallyapply the infoNo issuesby the timeyou got thecaseCame toyou as aP0 but itain'tT1 didn'teven trySent to CoreApp when itwas reallySRCase sentup with anangryclientCase froman internalclient(anotherdepartment)Helpedsomeone ona specificcaseCase from aclient inimplementationDidn'tpin aBomgarTold clientT2 wouldfix it (outof scope)T1 shouldhave knownhow to fix itDidn't tellclient theywereescalatingTroubleshootingsteps don'tmatch the caseResolutionwasprovided butT1 escalatedanywayGot a100%CSATHad tophone afriend forhelp on acaseT1 tookover aweek toescalateSent casestraight toT2Had to tellSupe thatthis one maybring theboomT1attemptedadatapumpDid not haveanytroubleshootingCame toyou as aP1 but itain'tCame to youas a P2 butshould be aP0 or P1T1 said theyread KBs butdidn't actuallyapply the infoNo issuesby the timeyou got thecaseCame toyou as aP0 but itain'tT1 didn'teven trySent to CoreApp when itwas reallySRCase sentup with anangryclientCase froman internalclient(anotherdepartment)Helpedsomeone ona specificcaseCase from aclient inimplementation

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