Has talkedwhile onmute at leastonce thisweekHasweather-relatedtrust issuesHas eversaid “whyis thisslow?”Lives inthe city ofChicagoHas clickedActivatewhile holdingtheir breathHas used aworkaroundthey’re “notproud of”Regularlysays “itdepends” onmeetingsLives inthesuburbsHascleaned uplegacyautomationHas aSalesforcesticker ontheir laptop orwater bottleHas strongopinions ondeep-dishvs thin crustHas rebuiltthe sameFlow morethan onceOwns morethan oneSalesforcehoodieHasGoogledthemselvesrecentlyIs open tonetworkingcoffeechatsCame “justfor thefood/swag”Hasautomationthey’re afraidto touchHas said“it worksin thesandbox”Is beingmoreextrovertedthan usualHas said“that’sstandardSalesforcebehavior”Has been toa ChicagoSalesforceevent beforeHas inheritedan org withlittle to nodocumentationHas morethan 1SalesforcecertificationMentors (orhasmentored)someone inSalesforceKnows what“dibs” means—and hasopinionsIdentifiesas aDeveloperHas chaseddown apermissionissueHasattended thisuser groupbeforeForgotsomeone’snameimmediatelyafter hearing itKnows thefastest wayto avoidLowerWackerTook theCTA toget hereIntentionallyavoids openingcases withSalesforceSupportHas everbrokenproduction😅Works foraSalesforcepartnerHas a petthat’sbeen on aZoom callIs anAgentblazerLegendHas earnedat leastdoubleranger onTrailheadHasrenamed afield… andregretted itUses emojisprofessionally🧡Plans toattend aDreamin’event thisyearHas given aSalesforcepresentationHas alreadyexchangedLinkedInprofilestonightIs hiringrightnowHas adedicateddisplay spacefor SalesforceswagHas been toDreamforceHas used aformula theydon’t fullyunderstandanymoreHascreated afield just forreportingIs asoloadminFirst time ata SalesforcecommunityeventHas strongopinions aboutmeetings thatcould’ve beenemails/SlackmessagesHasrenamed afield tosomething“temporary”Complainsabout trafficbut wouldnever leaveChicagoHasdebatedMalört (andsurvived)Found aSalesforcejob throughthecommunityPrefersdarkmodeBelongs to atleast 5 Slackworkspaces(and canprove it)Has Googledthe sameSalesforceerror morethan onceHas said“that’s nothow it wasdesigned”Has madea careerpivot intoSalesforceHasattendedSalesforceSaturdaysChicagoHasalreadyregisteredfor TDXHasmultipletabs open“for later”Is activelyjobhuntingIdentifiesas anAdminHas blamedSalesforcewhen it wasactually usererror 😇Has strongfeelingsabout multi-selectpicklistsIs herebecausesomeoneelse madethem comeHas talkedwhile onmute at leastonce thisweekHasweather-relatedtrust issuesHas eversaid “whyis thisslow?”Lives inthe city ofChicagoHas clickedActivatewhile holdingtheir breathHas used aworkaroundthey’re “notproud of”Regularlysays “itdepends” onmeetingsLives inthesuburbsHascleaned uplegacyautomationHas aSalesforcesticker ontheir laptop orwater bottleHas strongopinions ondeep-dishvs thin crustHas rebuiltthe sameFlow morethan onceOwns morethan oneSalesforcehoodieHasGoogledthemselvesrecentlyIs open tonetworkingcoffeechatsCame “justfor thefood/swag”Hasautomationthey’re afraidto touchHas said“it worksin thesandbox”Is beingmoreextrovertedthan usualHas said“that’sstandardSalesforcebehavior”Has been toa ChicagoSalesforceevent beforeHas inheritedan org withlittle to nodocumentationHas morethan 1SalesforcecertificationMentors (orhasmentored)someone inSalesforceKnows what“dibs” means—and hasopinionsIdentifiesas aDeveloperHas chaseddown apermissionissueHasattended thisuser groupbeforeForgotsomeone’snameimmediatelyafter hearing itKnows thefastest wayto avoidLowerWackerTook theCTA toget hereIntentionallyavoids openingcases withSalesforceSupportHas everbrokenproduction😅Works foraSalesforcepartnerHas a petthat’sbeen on aZoom callIs anAgentblazerLegendHas earnedat leastdoubleranger onTrailheadHasrenamed afield… andregretted itUses emojisprofessionally🧡Plans toattend aDreamin’event thisyearHas given aSalesforcepresentationHas alreadyexchangedLinkedInprofilestonightIs hiringrightnowHas adedicateddisplay spacefor SalesforceswagHas been toDreamforceHas used aformula theydon’t fullyunderstandanymoreHascreated afield just forreportingIs asoloadminFirst time ata SalesforcecommunityeventHas strongopinions aboutmeetings thatcould’ve beenemails/SlackmessagesHasrenamed afield tosomething“temporary”Complainsabout trafficbut wouldnever leaveChicagoHasdebatedMalört (andsurvived)Found aSalesforcejob throughthecommunityPrefersdarkmodeBelongs to atleast 5 Slackworkspaces(and canprove it)Has Googledthe sameSalesforceerror morethan onceHas said“that’s nothow it wasdesigned”Has madea careerpivot intoSalesforceHasattendedSalesforceSaturdaysChicagoHasalreadyregisteredfor TDXHasmultipletabs open“for later”Is activelyjobhuntingIdentifiesas anAdminHas blamedSalesforcewhen it wasactually usererror 😇Has strongfeelingsabout multi-selectpicklistsIs herebecausesomeoneelse madethem come

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