Can a Slack bot do more than notify — can it run an engaging, multi-week social game for a whole company?
Octobet started as an internal tipster league at nomtek back in 2014 and grew into a Slack bot for betting during the 2022 World Cup. We released it free to any team — and used it to probe how much engagement, state, and workflow a Slack bot can actually carry.
Octobet
2022
nomtek had run a football tipster league internally since 2014. By 2022 we wanted to see whether that shared ritual could become a Slack bot, hosting a stateful, multi-week, multi-user experience rather than just push notifications.
A Slack bot that ran a full World Cup betting game: bets on matches, top scorer, and tournament winner, private and channel notifications; a points and ranking system, and reminders.
The problem space
Slack is where distributed teams live, but most bots are thin — they post alerts and little else. The interesting question is how much further the platform stretches: can a bot hold state across weeks, manage scoring for hundreds of users, run scheduled events, and stay engaging? And separately — does a shared, low-stakes game actually strengthen the culture that keeps teams together? Octobet let us test both at once, on a real event with real users.
users across those teams, in 40 installations worldwide
bets placed through Octobet during the tournament
organisations that installed it — with zero marketing spend
Technology choices
What we evaluated, what we chose, and why.
Meets users where distributed teams already work — no new app to install or adopt. The platform's events, scheduled messages, and interactive components were enough to run a stateful, multi-week game.
Rejected for this use case. A separate app would have added an adoption barrier and defeated the "live where the team already is" premise. Slack-native kept friction near zero.
Rejected. The scoring logic, scheduled match events, and per-user state needed real control; off-the-shelf builders would have constrained the game design.
The POC in action
The working thing — capabilities, not a scope list.
Users bet on match results, the tournament top scorer, and the best team — all from within Slack.
A transparent points system (e.g., 8 pts for an exact result, 3 pts for the right outcome but wrong score, 24 pts for top scorer, 12 pts for tournament winner) with channel-posted standings.
DMs for upcoming matches and points earned; channel posts for rankings, per-match results, and reminders — keeping the game alive without manual admin.
The same foundation maps onto other team workflows: anonymous feedback collection, automated standup status gathering, system/event notifications, message analysis, and ChatGPT-backed Q&A over a team's own Slack knowledge.
Results & takeaways
Honest findings from a self-released experiment.
16,461 bets across the tournament shows the platform handles real scoring, scheduling, and per-user state — not just alerts.
400 users across 35 organisations and 40 installations worldwide, with no promotion, signalling real demand for lightweight team-bonding tooling.
The game's pull was tied to the World Cup. Sustained, year-round use needs a recurring hook (ongoing leagues, other events) or a pivot to utility (standups, feedback) rather than novelty.
The durable value isn't betting but the proven bot framework for anonymous feedback, automated standups, event notifications, and ChatGPT-over-Slack-knowledge — a natural fit for HR and people-ops teams in remote-first tech companies and agencies that already run their culture inside Slack.
