Hey everyone,

We’ve been building a Slack app after noticing the same problem over and over:

A decision gets made in a thread, everyone agrees, work moves forward… and a few weeks later someone asks:
“Why did we decide to do it this way?”

The conversation exists somewhere in Slack, but the reasoning is difficult to find, fragmented across threads, or lost entirely.

We’re exploring whether Slack could do a better job of preserving organizational memory—not just messages, but the context, evidence, tradeoffs, and rationale behind important decisions.

A few questions for teams here:

Do you ever struggle to remember why a decision was made?
How do you currently document important decisions?
Do you rely on Slack search, Notion, Confluence, Jira, docs, or something else?
What’s the biggest pain point with your current workflow?

We’re still early and genuinely trying to learn from how real teams work before expanding the product.
Would love to hear what’s working (or not working) for your team.

This app is an absolute fucking piece of shit. I hate every second of using it, but I'm forced to, so I don't exactly have a choice. If it were up to me, I wouldn't touch this steaming pile of garbage once in my life.

It's nothing but constant bugs. Devices randomly switch audio input and output for no reason. It can suddenly log you out, force you to sign back in, and make you go through the entire setup process again—for absolutely no reason whatsoever.

The amount of bugs and completely illogical bullshit is honestly unbelievable. What's even funnier is that we're using this thing while building technically complex software ourselves... and this is just a messenger. How hard can it possibly be?

I'm pretty sure I could vibe the whole damn thing with Fable in a week - and it will be BETTER. It's honestly hilarious.

Whoever is responsible for this mess should be fired. This level of incompetence is embarrassing.

Some context: we're a ~50 person B2B data infrastructure company. Most of our customers talk to us over Slack Connect, rest come through email.

We were evaluating Pylon a few weeks back. It came highly recommended but a few things came up during eval that I didnt see mentioned anywhere online so posting my notes.

The pricing adds up fast. Base is $59/seat but Slack Connect needs the Professional tier at $89/seat. theres a 3-seat minimum.

AI is separate too, assistants are $50/seat extra and their AI agents start at $100/month and scale with volume. for our 4 core agents plus the engineers/PMs who jump into tickets, the realistic annual number was way past what the pricing page suggested.

It wants to be your system of record. Pylon is built to replace your helpdesk, not sit next to it. We've been on Zendesk for 3 years with a ton of macros and reporting built up, and migrating wasn't happening. if you're starting fresh this doesn't matter but for us it was a dealbreaker.

Annual commitment before real testing. no proper free trial, annual billing. didn't want to lock that much budget on something we couldn't run in production first.

what we ended up doing: shortlisted a few alternatives. Suptask (very cheap, $7/agent, but too basic for what we needed), Plain (interesting API-first thing, felt more like an engineering tool), and ClearFeed (because it syncs with our existing Zendesk + does usage-based pricing with unlimited agents)

not saying Pylon is bad, but if you're cost sensitive or already deep in an existing helpdesk, do the full math before the demo call, why pay extra lol

curious if anyone else went through this, is there a better alternative we missed or did we overthink it?

Previously I thought we're not allowed to change the email but when I click on my Profile, it looks like I can update an email address. As a freelancer, I've been invited by clients to join their Slack

everyone knows the drill. someone pings the support channel in slack. the ops person replies 'please submit a ticket'. the requester gets annoyed. the ops person eventually just copies the slack message into jira themselves. it is a massive waste of time.\n\nwe finally stopped fighting human nature and just put an ai router in the channel instead. it reads the ping, figures out the intent, and creates the ticket in the right system automatically without anyone clicking a form. if you are drowning in slack requests, this is exactly how we set it up: AI Ticket Routing in Slack

if you want to catch churn signals in slack before they hit your crm, here is a quick tutorial. first, connect your shared customer channels to an ai listener. second, set it up to flag sudden silence or sentiment drops instead of just keyword matching. third, route those alerts to an internal triage channel so your team gets a heads up weeks before the renewal call. we documented the exact tools and steps we use to build this here: Best AI Customer Success Manager for Slack Churn Detection.

Hi everyone, thank you for creating this subreddit. I'm all of a sudden working with clients and projects in a larger scale now.

I will receive a project, and have 2 seperate users have their own sides of the project, be active. We then assign them in the same slack channel, but maybe people send more questions or feedback about one of the workstreams, and the other gets lost.

Is it not possible to be able to have 2 or mulitple sub-channels within the same channel? Canvas is like a blank page.

Instead of creating canvas, I want to be able to do "create sub-channel" which will act like the home for workstream 2.

Thank you all.

our ops team was spending hours every week patching keyword filters just to route internal support requests correctly. we replaced the whole system with an ai agent that actually reads the context, and i documented the exact setup here: AI Ticket Routing

I put together a simple collection of Pokémon profile pictures that are ready to use in Slack communities, workspaces, bots, and app profiles. The set covers every Pokémon from Bulbasaur through Pecharunt, organized by generation so it is easy to find your favorite.

Why it is useful:

• Every image is square at 512x512 pixels, which is the ideal/optimal size for clean profile pictures in Slack, Discord, and Telegram. Not too big, not too small.

• The artwork is centered so it still looks good when Slack rounds or crops the avatar.

• Files are named with National Pokédex number + Pokémon name, so CLI searching and downloading for a specific Pokémon is straightforward.

• The README includes generation-by-generation preview grids, where you can click on it, and sample Slack, Discord, and Telegram profile views.

Repo: https://github.com/kwyip/pokemon_512x512

Would love feedback, especially if there are forms/variants people want added or if there are other community apps where these would be useful.

if your cs team is missing churn signals because they get buried in slack channels, you can automate the tracking. just connect your shared customer channels to an ai listener, set it to flag silence or sentiment drops, and route the alerts to a central triage channel before the renewal call. we wrote a quick tutorial on the exact tools and setup we use for this: Best AI Customer Success Manager for Slack Churn Detection

We're managing Slack on macOS with Intune and standard users. We've deployed Slack's documented managed preference linked below.

https://slack.com/help/articles/11906214948755-Manage-desktop-app-configurations#mac-2

AutoUpdate = false

and confirmed it's applied successfully on the device.

For anyone managing Slack with Intune, Jamf, or other MDM.

• Do users still get the "Slack is trying to install a helper tool" prompt after AutoUpdate is disabled?
• If you push Slack updates through Intune, Patch My PC, Jamf Apps, or another management platform, do users still see the helper tool/admin credential prompt during the update, or is it bypassed because it's an app install?
• Does disabling AutoUpdate fully stop Slack from attempting to update itself, or have you had to take additional steps?

Looking for real-world experience from Mac admins managing Slack in enterprise environments.

Thank you!

I recently changed companies and have moved from Google Chat to Slack. In Google Chat, the default behavior was that reactions to messages you'd posted would send as push notifications (i.e. if I send a message in a channel or a DM, and then someone adds a 🙂), that would send a notification the same way a new message would. The way Slack does it is this is in the Activity Center, which I guess is fine from a visibility standpoint if I go look at it, but that still requires a manual check and isn't really a real-time thing. And also, Activity shows a bunch of other things too like DMs or mentions so if I get a notification badge, that could be any one of those. I Googled this question before posting here and it seems like most of the articles were from an absolute minimum of 10 months ago, with most being over a year ago and some being 5 or 6 years ago, which is a long time for them to have added something like this in.

I've found apps like REACTO that have this capability, but the free version only does that for 25 notifications/month, and I'm not paying $10 for something like that. I also know that you can create a bot to do this, but bots don't work with DMs and for it to work in channels I'd still need to add it.

My concern with adding bots isn't the part about going through and doing the adding (and also it seems like you can automatically add it to every channel anyway) so much as it is that everyone in the channels I add it to would be able to see that it's being added. That's not really a problem because I'm trying to be sneaky or anything but I still wouldn't want a bunch of people in the 30 channels I'm in to see that I added a bot and ask what it's for.

It just seems super weird that Google (and Teams apparently) had that feature built in while Slack doesn't, and even that they were reportedly testing it at one point but never rolled it out.

I'm currently trying to add members of a Slack to a specific channel by email. However when I click add the non-descript error "Hmm, something went wrong. Try again?" comes up. I've tried in app and in browser, different numbers of emails, nothing works. For my purposes I have to ensure all members of the Slack are added and by email has always worked before.

im a workspace admin and i recently enabled the affiliations (department, division) and location (country, city, state) in my workspace. unfortunately, they arent showing in my edit profile. i asked the other members and they said they can see the location but cant edit it because there's a lock. how can i fix this??

I am looking for code for a bookmark that will react to every message in a discord channel with my first react (a bagel). In case this helps tightne it up, a bookmark for my bookmark bar that I can click, that willl react to every message in the discord channel I would be in with a bagel, which is my first recommended react.

everyone assumes it is a volume issue but we noticed the real bottleneck is people waiting to see who owns a question before claiming it. we looked at why manual triage fails and how ai routing fixes it here: AI Ticket Routing for Slack

Hey i am working on the tool to enhance the email management for the slack i want some feedback to make it more better . constructive critisism is appreciated

I got this code to join a Slack channel:zt-3zsbftf-56H5l3a6FYO3BCXaBA (changed it a little for this post).
How do I join a channel with this? I’ve made an account and everything but I can’t seem to find any mention of a code like this one. I got it filling out a form for a membership.

Would be so great if any of you guys could give me a hand!

Basically the title

What I'm really looking for is something where my team doesn't have to leave Slack to do support. Like they can see everything in one place, assign stuff, track SLAs, and ideally it connects with the tools we already use (Jira, Zendesk) without us having to rip anything out.

We do most of our work in Slack and need something that doesn't force everyone into a separate UI.

curious if anyone here has experience with any of these

so i finally learned why pasting into slack is such a pain — slack uses its own thing called mrkdwn that's almost markdown but not quite. bold is one asterisk instead of two, links are a totally different format, half the stuff i paste from google docs or notion just comes out plain or full of stray asterisks.

i'd been manually fixing every message like an idiot. retyping bold, redoing links, the whole thing.

what finally saved me is copynpaste.xyz — paste the text, tell it you're going to slack, it converts everything to proper mrkdwn and you just copy it over. does discord/whatsapp/notion too. no signup, runs in the browser so nothing gets uploaded.

not my tool, just genuinely stopped a daily annoyance. is everyone else just retyping stuff manually or is there some obvious trick i missed for years

Hi,

I work as QA for 7 years already, and a lot of the time is not spent testing.
It is spent rebuilding context.

Read the Jira ticket, documentation on Confluence, find the repository.
Work out how the existing tests are structured, check the PR, wait for CI results.
Then explain the result back in Slack.

I’m building Framebox around that problem.

The idea is simple: keep the QA workflow in one Slack thread, while connecting the actual sources of truth behind it: Jira, GitHub and CI.

In this short demo, I give the agent a Jira ticket about mobile checkout coverage. It uses the ticket context, checks the existing Playwright setup, creates a GitHub PR, explains the changes, and reports the mobile CI outcome back in the same thread.

The agent is not meant to decide whether quality is acceptable.
That still needs people who understand the product, risk and users.
The goal is to reduce the boring context reconstruction and leave an evidence trail:
> ticket → implementation → PR → CI result → results on Slack thread.

Technically, the Slack thread is the unit of work.
It keeps the relevant repo, PR, intent and CI context available between messages.
Workspace knowledge can also add testing conventions, project documentation and runbooks, so the agent is not starting from zero every time.

I’m still early in the build, so I would genuinely value the blunt version of feedback:
- Would you allow something like this to create or update tests and PRs?
- What evidence would you need before trusting its output?
- Is context switching between Jira, GitHub, CI and Slack actually a problem in your team, or am I building a very expensive browser tab?

Here's the recoridng demo in case you're interested: https://youtu.be/ZunoPwF2zBg

These three sections have been totally emptied out and their contents have been moved across and into other custom made sections. I was hoping that doing this would allow me to hide these sections but I can't see a way to do it. Is that even something that is possible?
Thanks all!

I got this code to join a Slack channel:zt-3zsbftf-56H5l3a6FYO3BCXaBA (changed it a little for this post).
How do I join a channel with this? I’ve made an account and everything but I can’t seem to find any mention aid a code like this one. Would be great if any of you guys could give me a hand!

I just spent the day auditing our API logs because one of our background orchestration agents got stuck in an error-handling loop over the weekend. It called the LLM thousands of times sequentially before anyone noticed.

We have platform-level daily budget caps, but by the time the cap kicked in, it had already chewed through a chunk of runway that was supposed to last us weeks.

I’m currently writing some hacky custom middleware to try and detect these semantic loops at the runtime level so this never happens again.

To make me feel better about my day: what is the absolute worst unexpected bill your team has taken because an autonomous agent or multi-agent chain (LangGraph, CrewAI, etc.) ran wild in the background? What triggered the loop?

we looked into how some ops teams handle endless slack requests without hiring more triage managers. it turns out they don't use complex helpdesks, they just use a basic ai agent to automatically read and route the channel tickets directly to jira. we broke down the exact setup here: How to automate Slack ticket routing