Has earnedat leastdoubleranger onTrailheadComplainsabout trafficbut wouldnever leaveChicagoHas Googledthe sameSalesforceerror morethan onceIdentifiesas aDeveloperHas morethan 1SalesforcecertificationHas been toDreamforceHasattended thisuser groupbeforeIs beingmoreextrovertedthan usualLives inthesuburbsHasalreadyregisteredfor TDXHas a petthat’sbeen on aZoom callUses emojisprofessionally🧡Has said“it worksin thesandbox”Came “justfor thefood/swag”Knows what“dibs” means—and hasopinionsPlans toattend aDreamin’event thisyearBelongs to atleast 5 Slackworkspaces(and canprove it)Has strongopinions aboutmeetings thatcould’ve beenemails/SlackmessagesHas everbrokenproduction😅Hasautomationthey’re afraidto touchIs activelyjobhuntingMentors (orhasmentored)someone inSalesforceWorks foraSalesforcepartnerHas alreadyexchangedLinkedInprofilestonightForgotsomeone’snameimmediatelyafter hearing itIs asoloadminIs hiringrightnowKnows thefastest wayto avoidLowerWackerHas adedicateddisplay spacefor SalesforceswagHas used aformula theydon’t fullyunderstandanymoreIs herebecausesomeoneelse madethem comeTook theCTA toget hereHas blamedSalesforcewhen it wasactually usererror 😇Hasweather-relatedtrust issuesHasrenamed afield tosomething“temporary”HasdebatedMalört (andsurvived)Has clickedActivatewhile holdingtheir breathIs open tonetworkingcoffeechatsHas strongopinions ondeep-dishvs thin crustIntentionallyavoids openingcases withSalesforceSupportHas said“that’sstandardSalesforcebehavior”Regularlysays “itdepends” onmeetingsHascreated afield just forreportingHas madea careerpivot intoSalesforceIdentifiesas anAdminFound aSalesforcejob throughthecommunityHas inheritedan org withlittle to nodocumentationHas used aworkaroundthey’re “notproud of”Has rebuiltthe sameFlow morethan onceFirst time ata SalesforcecommunityeventHas given aSalesforcepresentationLives inthe city ofChicagoIs anAgentblazerLegendHasmultipletabs open“for later”Has strongfeelingsabout multi-selectpicklistsHas aSalesforcesticker ontheir laptop orwater bottleHas chaseddown apermissionissuePrefersdarkmodeHascleaned uplegacyautomationHas said“that’s nothow it wasdesigned”HasattendedSalesforceSaturdaysChicagoHas been toa ChicagoSalesforceevent beforeHas talkedwhile onmute at leastonce thisweekOwns morethan oneSalesforcehoodieHasGoogledthemselvesrecentlyHas eversaid “whyis thisslow?”Hasrenamed afield… andregretted itHas earnedat leastdoubleranger onTrailheadComplainsabout trafficbut wouldnever leaveChicagoHas Googledthe sameSalesforceerror morethan onceIdentifiesas aDeveloperHas morethan 1SalesforcecertificationHas been toDreamforceHasattended thisuser groupbeforeIs beingmoreextrovertedthan usualLives inthesuburbsHasalreadyregisteredfor TDXHas a petthat’sbeen on aZoom callUses emojisprofessionally🧡Has said“it worksin thesandbox”Came “justfor thefood/swag”Knows what“dibs” means—and hasopinionsPlans toattend aDreamin’event thisyearBelongs to atleast 5 Slackworkspaces(and canprove it)Has strongopinions aboutmeetings thatcould’ve beenemails/SlackmessagesHas everbrokenproduction😅Hasautomationthey’re afraidto touchIs activelyjobhuntingMentors (orhasmentored)someone inSalesforceWorks foraSalesforcepartnerHas alreadyexchangedLinkedInprofilestonightForgotsomeone’snameimmediatelyafter hearing itIs asoloadminIs hiringrightnowKnows thefastest wayto avoidLowerWackerHas adedicateddisplay spacefor SalesforceswagHas used aformula theydon’t fullyunderstandanymoreIs herebecausesomeoneelse madethem comeTook theCTA toget hereHas blamedSalesforcewhen it wasactually usererror 😇Hasweather-relatedtrust issuesHasrenamed afield tosomething“temporary”HasdebatedMalört (andsurvived)Has clickedActivatewhile holdingtheir breathIs open tonetworkingcoffeechatsHas strongopinions ondeep-dishvs thin crustIntentionallyavoids openingcases withSalesforceSupportHas said“that’sstandardSalesforcebehavior”Regularlysays “itdepends” onmeetingsHascreated afield just forreportingHas madea careerpivot intoSalesforceIdentifiesas anAdminFound aSalesforcejob throughthecommunityHas inheritedan org withlittle to nodocumentationHas used aworkaroundthey’re “notproud of”Has rebuiltthe sameFlow morethan onceFirst time ata SalesforcecommunityeventHas given aSalesforcepresentationLives inthe city ofChicagoIs anAgentblazerLegendHasmultipletabs open“for later”Has strongfeelingsabout multi-selectpicklistsHas aSalesforcesticker ontheir laptop orwater bottleHas chaseddown apermissionissuePrefersdarkmodeHascleaned uplegacyautomationHas said“that’s nothow it wasdesigned”HasattendedSalesforceSaturdaysChicagoHas been toa ChicagoSalesforceevent beforeHas talkedwhile onmute at leastonce thisweekOwns morethan oneSalesforcehoodieHasGoogledthemselvesrecentlyHas eversaid “whyis thisslow?”Hasrenamed afield… andregretted it

ChicagOhana BINGO - 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
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
  1. Has earned at least double ranger on Trailhead
  2. Complains about traffic but would never leave Chicago
  3. Has Googled the same Salesforce error more than once
  4. Identifies as a Developer
  5. Has more than 1 Salesforce certification
  6. Has been to Dreamforce
  7. Has attended this user group before
  8. Is being more extroverted than usual
  9. Lives in the suburbs
  10. Has already registered for TDX
  11. Has a pet that’s been on a Zoom call
  12. Uses emojis professionally 🧡
  13. Has said “it works in the sandbox”
  14. Came “just for the food/swag”
  15. Knows what “dibs” means—and has opinions
  16. Plans to attend a Dreamin’ event this year
  17. Belongs to at least 5 Slack workspaces (and can prove it)
  18. Has strong opinions about meetings that could’ve been emails/Slack messages
  19. Has ever broken production 😅
  20. Has automation they’re afraid to touch
  21. Is actively job hunting
  22. Mentors (or has mentored) someone in Salesforce
  23. Works for a Salesforce partner
  24. Has already exchanged LinkedIn profiles tonight
  25. Forgot someone’s name immediately after hearing it
  26. Is a solo admin
  27. Is hiring right now
  28. Knows the fastest way to avoid Lower Wacker
  29. Has a dedicated display space for Salesforce swag
  30. Has used a formula they don’t fully understand anymore
  31. Is here because someone else made them come
  32. Took the CTA to get here
  33. Has blamed Salesforce when it was actually user error 😇
  34. Has weather-related trust issues
  35. Has renamed a field to something “temporary”
  36. Has debated Malört (and survived)
  37. Has clicked Activate while holding their breath
  38. Is open to networking coffee chats
  39. Has strong opinions on deep-dish vs thin crust
  40. Intentionally avoids opening cases with Salesforce Support
  41. Has said “that’s standard Salesforce behavior”
  42. Regularly says “it depends” on meetings
  43. Has created a field just for reporting
  44. Has made a career pivot into Salesforce
  45. Identifies as an Admin
  46. Found a Salesforce job through the community
  47. Has inherited an org with little to no documentation
  48. Has used a workaround they’re “not proud of”
  49. Has rebuilt the same Flow more than once
  50. First time at a Salesforce community event
  51. Has given a Salesforce presentation
  52. Lives in the city of Chicago
  53. Is an Agentblazer Legend
  54. Has multiple tabs open “for later”
  55. Has strong feelings about multi-select picklists
  56. Has a Salesforce sticker on their laptop or water bottle
  57. Has chased down a permission issue
  58. Prefers dark mode
  59. Has cleaned up legacy automation
  60. Has said “that’s not how it was designed”
  61. Has attended Salesforce Saturdays Chicago
  62. Has been to a Chicago Salesforce event before
  63. Has talked while on mute at least once this week
  64. Owns more than one Salesforce hoodie
  65. Has Googled themselves recently
  66. Has ever said “why is this slow?”
  67. Has renamed a field… and regretted it