“Slack falls over because a message has no state. It's not pending or expired, it's just an old message, and the only person who knows whether it got dealt with is whoever happened to scroll past it.”
“One Slack channel centralizes the noise, not the approval. The thing to centralize is the decision record: exact action, payload hash, requester, approver, expiry, and result.”
“The workaround I've seen most often is "just pipe everything into one Slack channel" which sort of works until the channel becomes noise and people stop reading it.”
“If you’re not good at computing and prefer stagnant software that you update once every 3 years… I can imagine you’d not like Slack (or really any modern software).”
“It would be great if I can give a thread a topic or one or more tags, acknowledging the use case of a thread being a sub "channel". With this, when I'm scrolling through a few unread threads, the context of each unread is anchored by the topic/tag of the thread.”
“Teams and Slack handle things differently but threads, replies, posts, emoji's, and file sharing work fine. Theres no DM's but for bridging channels it works well and does what it says.”
“we moved to teams a couple years back because the cto got a bundle deal with office 365. it was a nightmare, search is still garbage and half the integrations we relied on in slack just don't exist. the migration tool basically just dumped everything into a single channel and called it a day, so we lost all context.”
“Slack kicked some of my users off of the platform without any communication or explanation. So, to convince me to switch, don't have policies that are opaque that you get to enforce without giving the people paying you some insight into the way things work.”
“I’ve been using Unthread and in a previous company Plain, these both allow me to both respond directly in the Slack channel but also from a traditional ticketing system view in a browser. Great integrations with most of our platforms as well.”
“On top of that, if you add all the other risks around confidential customer data buried under those thousands of Slack messages then it suddenly becomes too high risk.”
“I think the Slack channel is not active anymore. If you get invited to a project, there will be a chat specific to that project in your dashboard sidebar panel.”
“i run the same private slack channel pattern, the pain is whether the agent can spend a tool without me, without a yes/no gate i still end up opening the laptop for anything that writes”
“So a way that I do this (doesn’t necessarily have to be this exactly) is I setup a personal slack channel. I think ping the slack channel from my phone with various asks (setup this, do this, add this to my to-do, etc…) then I have a Claude routine running and scraping that channel, taking action on it and resolving it with a checkmark and feedback once complete.”
“Slack can read your messages; they aren't encrypted. Free-tier history vanishes behind a paywall. And Slack's privacy policy has said your messages may train its ML models unless you opt out by email.”
“It’s not that it’s a bad feature, but Slack has little structure beyond “channel”, which leaves it to human convention to retain order. And humans *suck* at that.”
“@zachperret The biggest one for me is monitor all channels (slack, email, WhatsApp, iMessage, etc) and can basically do search across them all when I ask for what I’ve left unattended or unanswered. But also.”
“The first thing that i use agents for is summarization across many plugins and channels. Notion, Email and Slack... I have 3 editor teams, a management team, all”
“If a customer asked me to get teams messages and store them in a different product slack or any other, i'd tell them.they need to find someone else to handle that nightmare. Just use an AI note taker like anyone else does or drop slack and merge into teams, or just have the data in your own stand alone 365 environment.”
“but tbh as someone who's had to juggle slack internally while clients demand teams, this is a real pain point. the zapier/make bandaids always break at the worst possible moment”
“most “agent in slack” tools stop at chat. the bit i keep re-reading here is that a run can also start from an issue, a pull request, a webhook, or a schedule.”
“It’s very likely employees have shared customer information, support issues, screenshots, contracts, credentials, code, or other confidential information in Slack and email. Removing employee PII doesn’t solve that.”
“I’ve found live API keys, customer contracts, candidate notes, and pasted customer data in supposedly boring Slack exports. Stripping names does not remove the confidentiality or IP problem, so I’d say no unless every agreement permits model training and the lab accepts the liability, which they probably won’t.”
“app.slack.com/client only opens workspaces you already belong to. slack communities are separate, invite-based workspaces, so start from each community’s official signup page and confirm its topic and rules before trying to connect.”
“Can we clear out those stupid header or banner tiles? most of our members are new to slack so they will be confused by this without us getting any benefits from it.”
“If you mean joining Slack communities, you’ll generally need an invite link or a community’s signup page. If your boss means connecting with people/communities *through Slack*, ask whether they already have specific communities in mind—there isn’t one universal “Slack communities” directory or connection process.”
“I'm a product manager doing a self-directed teardown of Slack, and I'm stuck on one part: I keep reading that notification overload is the big pain, but I don't actually know if that's true or just loud people on the internet.”
“Executives are increasingly encouraging employees to use public #Slack channels instead of private DMs so #AI agents can access more context, analyze conversations, summarize meetings, build presentations and even help make”