The message that mentioned finance and tagged nobody

A Slack user asked in a product channel if finance could be included in the discussion. No finance team members tagged in the thread, and it went on for three weeks before a contract was signed without their input. This isn't a tooling problem, but a lack of proper communication. Slack works fine, but there's an issue in how it handles mentioning teams versus involving them. Keyword searching for finance would generate irrelevant results, as the word appears in unrelated sentences.

The real signal lies in the structure of Slack messages. When someone references a channel, it appears like this: Can we loop in #C01ABCDEF|finance before this goes out? That's a channel reference, not a mention. Even if no one reads the finance channel, the workspace already knows about it. The bot parses references, not words, and looks for specific structures indicating a message pointing to a governance channel. This context is already present in the event payload, but it's being discarded.

To ensure complete coverage, the bot doesn't join channels manually. Instead, it listens for channel_created events and joins new ones automatically. This covers over a hundred channels by default, without relying on anyone remembering to add the bot to each one. The bot uses Socket Mode, which opens an outbound connection instead of receiving inbound webhooks. This approach eliminates the need to expose a public HTTPS endpoint, reducing security risks.

However, there's a catch. Because Socket Mode doesn't allow inbound connections, the bot must bind to a port. If it fails to start, the platform hosting it won't consider it healthy and will shut it down. To avoid this, the bot runs a sidecar HTTP server that responds to a health check. This ten-line snippet ensures the bot appears healthy to the platform, keeping it running without needing to configure anything else.