“Wouldn't it be nice to use the Slack client in a Teams environment (or vice versa if that's your thing) ? This would produce more competition because companies would have to develop the client software to be compelling itself, rather than relying on the pull of installed deployments with captive victims^wusers.”
“Same with CS2, Fortnite, Vallorant, etc.I’m fine with Google Workspace owning the client and the service, same with Zoom, Slack, Teams, Box, Dropbox, etc.I don’t think we’d have better games (pretty much for certain), and I don’t know that we’d have as good online productivity tools either.”
“I’ve worked on enough internal and third-party SOA to know that documentation could be in an email, a slack chat, or a hallway conversation. The public docs go through writers and reviews.”
“Slack’s new Surfaces feature will let users describe what they need and have Slackbot build interactive dashboards, reports, and other tools without leaving the chat. The feature can also pull permitted data from apps like Google Drive and Salesforce.”
“I tried signing up using an alias with the 'main' tld (simplelogin dot com). When signing up, I made a mistake with something so I thought I'd try to signup again, error.”
“i work at ClearFeed, and the bit i'd want agreed internally is who gets that Slack conversation into the service desk. "I've opened a ticket for this, you don't need to repost it" feels much better than sending them away halfway through explaining the issue.”
“Anyone who has used Slack or Zoom knows Teams is a superior product. Once you are in the microsoft ecosystem, it's hard to beat that user experience outside in the competing products.”
“**•** Have you tried any tools for this already (shared prompt libraries, Notion pages, Slack channels, whatever)? Did it stick, or did people stop using it?”
“We have Slack enabled/connected in Salesforce, and everything functionally works — Slackbot can interact with Salesforce and an Opp flow can successfully create a Salesforce Channel.”
“Our agent (Smith) is coming along nicely, and today we opened up access for our team to be able to interact with him - Slack is our messaging interface of choice for the moment.”
“Most people are excited about Slack agents because they do the work and have a lot of context. This is great, but it misses a huge side effect for an organization that I think is even more compelling: Using AI openly in Slack drives your entire team to become AI native.”
“Slack lists is a terribly designed feature. I want a better way to organize collaborative tables or mini databases for key information, projects, ideas,”
“My company was acquired and our Slack workspace is being merged into the acquirer's Slack Enterprise Grid as an additional workspace. We use Slack heavily.”
“No; why would you loose history of the ticket or create slack channels for each one? At that point they’re better off as threads within a channel, or if it’s anything bigger it goes on the roadmap.”
“Put a recording proxy in front of gmail, slack and whatsapp so every tool call is captured and replayed on later runs, then let only a small nightly slice hit a real sandbox workspace with disposable channels and a per run label prefix, so cleanup is a delete instead of a diff.”
“Runable connecting into Gmail/Slack/Sheets/Notion is what made this feel less theoretical to me. Once an AI agent is inside the places the business actually runs, permissions probably matter more than another benchmark score.”
“Discord and Slack map better onto what you described: Slack is keyed by thread, Discord by channel, so a second thread/channel is a second session without extra commands. Telegram is one session per chat unless you \`/new\`.”
“I liked slack because it enables an allowed users list, so not only do they have to be in the channel, it’s deny by default until I add them to the allowed users list for that profile.”
“WhatsApp is not the right app, switch to Buzz ! Mobile and desktop, groups of humans and agents, in same channel, in various channels, like slack by way better and free!”
“All the other suggestions about turning off Slack, work phone, etc. after hours are great. If you’ve been responding over a period of time, though, I’d manage your coworker’s expectations.”
“Most workflow tests should never touch Gmail or Slack at all. Put each provider behind a small adapter, then run the workflow against a deterministic local implementation that records exactly what would have been sent.”
“For Gmail or Slack that means minting real-looking ids that later reads actually return, and keeping a message store the agent can query back. Reset in CI becomes constructing a new one, which kills the dirty-test-account problem outright.”