(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
Lives in the city of Chicago
Has already registered for TDX
Complains about traffic but would never leave Chicago
Has blamed Salesforce when it was actually user error 😇
Has renamed a field to something “temporary”
Has strong feelings about multi-select picklists
Is open to networking coffee chats
Lives in the suburbs
Has created a field just for reporting
Has cleaned up legacy automation
Intentionally avoids opening cases with Salesforce Support
Belongs to at least 5 Slack workspaces (and can prove it)
Is an Agentblazer Legend
Has a pet that’s been on a Zoom call
Has used a formula they don’t fully understand anymore
Has already exchanged LinkedIn profiles tonight
Has renamed a field… and regretted it
Took the CTA to get here
Plans to attend a Dreamin’ event this year
Regularly says “it depends” on meetings
Has chased down a permission issue
Has made a career pivot into Salesforce
Has a Salesforce sticker on their laptop or water bottle
Has been to Dreamforce
Has used a workaround they’re “not proud of”
Is hiring right now
Has earned at least double ranger on Trailhead
Has said “it works in the sandbox”
Has talked while on mute at least once this week
Has automation they’re afraid to touch
Has said “that’s standard Salesforce behavior”
Is a solo admin
Has attended Salesforce Saturdays Chicago
Came “just for the food/swag”
Owns more than one Salesforce hoodie
Has clicked Activate while holding their breath
Has debated Malört (and survived)
Has inherited an org with little to no documentation
Forgot someone’s name immediately after hearing it
Has rebuilt the same Flow more than once
Knows the fastest way to avoid Lower Wacker
Is actively job hunting
Identifies as a Developer
Works for a Salesforce partner
Has said “that’s not how it was designed”
Identifies as an Admin
Prefers dark mode
Knows what “dibs” means—and has opinions
Has been to a Chicago Salesforce event before
Has multiple tabs open “for later”
Has ever broken production 😅
Has Googled themselves recently
Has strong opinions about meetings that could’ve been emails/Slack messages
Has Googled the same Salesforce error more than once