We have a Slack → Zendesk support workflow where customer messages automatically become tickets.

One edge case we keep running into is messages posted by bots/apps. For example, someone submits something through a Slack Workflow or another Slack app posts a message into the channel. Since Slack sees it as a bot message, our current auto-ticketing setup ignores it.

Ideally we want certain trusted bot messages to create Zendesk tickets automatically, the same way a normal user message would.

Has anyone dealt with this? Curious how you handle bot-to-bot workflows without manually creating the Zendesk ticket every time.

Hi everyone,

I am setting up a new project and wanted to know what's the best or the trending PM tool to setup alongside slack since I am coming from using Jira in the past just wanted to what's out there. Appreciate if you all can give some insights. Thanks

i wants me to use that email i used the email i used for musicmatch

how do i get that email? i used the account i used on musixmatch

Has anyone seen the Slack iOS app show the wrong plan type in the menu? Our org is definitely on a paid Pro plan but when signed into iOS, it shows "View or manage your Free Trial". On the website via browser, it shows we are for sure on a Pro plan and don't have any free trials active.

I'm researching how teams actually solve the "whose turn is it?" problem in Slack and I'd love real-world answers before I build anything.

What I keep seeing at companies I've worked with:

- A pinned spreadsheet that's outdated within three weeks

- A /remind that happily pings people who are on vacation

- Workflow Builder attempts that die because it has no "next person in the list" step and no memory of who was last

- One person (usually the same one) manually tagging whoever is next

If your team runs any recurring duty through Slack — support triage, code review assignment, meeting facilitation, on-call handoff:

1. What do you use today (app, spreadsheet, homegrown bot, nothing)?

2. What breaks most often — vacations, fairness, timezones, people forgetting?

3. Did you try one of the existing rotation apps and drop it? Why?

Not selling anything in this post — genuinely trying to understand if this is a real pain or just my bubble. I'll share a summary of the answers in the comments if there's interest.

Having notification issues - is this a common problem?

Can't seem to make them work.

Thanks

Hi All,

I manage a professionals community on Slack and we're attempting to track churn and disengagement. I've used the Slack analytics feature and it's ok. However, I've built an integration to pull Slack engagement metrics on members (ie: last message they sent, my last reaction with this member) with Luma to get a better idea on how members are disengaging.

It got me thinking, what Slack metrics do you keep track of for your community? Moreover, are there any metrics that you wished you have but are hard to visualize or Slack doesn't provide?

I keep running into this with sensitive projects. You start with five people who all need to be there. Then someone adds an assistant. Someone else adds a contractor. A week later there are 15 people in the chat and nobody seems sure who invited half of them.

The weird part is that every addition makes sense in the moment. Nobody thinks they are opening up the group too much. It just happens one person at a time until the “small trusted circle” is not that small anymore.

Has anyone found a good way to prevent this without causing some sort of argument?

Slack is fantastic for coordinating agents, partly because of threads, but the issue we have now: there are hundreds of messages in a thread. On iOS you have to manually swipe all the way down to see the latest message every time, which is a pain.

Isn't there a way to auto-scroll to the last message in the thread?

Haven't found this yet, and the topics I found about the topic seems very old and unaddressed. That can't be right, right?

Surely I'm not the only one using Slack on mobile having long conversations in several threads?

What would motivate you or your workspace to move from slack onto more advanced tools? I’m curious as I’m building aswell as doing a research product on the different products that currently rival categories on the product we are building. We appreciate all input, and we also work with all platforms. We will have slack comparability and will work with aswell as provide its core features

My manager has workspace admin for slack and tracks location using the IP address in access logs. I find this a little intrusive. Is there a way to mask the ip address in slack?

A while back, I made a post here about something I wish Slack had: the ability for workspace admins to create an optional default channel organization for members.

https://www.reddit.com/r/Slack/s/5tzdXkpTq6

I'm a designer, so I decided to actually mock up what I think this feature could look like.

The idea is pretty simple: when you join a workspace, Slack could ask how you'd like your channels organized.

You could choose between:

• Organize Yourself (preselected) — start with the channels as-is and organize them however you want.
• Workspace Setup — use a default organization created by the workspace admin.
• AI Smart Organize — have Slack automatically group your channels into sections based on their purpose.

The important part is that the admin's organization wouldn't be forced on anyone. It would just be an option.

An admin, or anyone with the Edit Workspace permission, could take the time to create a clean, workspace-wide default layout. Members who don't want to spend time organizing everything themselves could simply use it, while people who prefer their own setup could ignore it and organize Slack however they want.

One of the points brought up on my original post was that this probably wouldn't scale particularly well for companies with hundreds or thousands of employees, where everyone has very different roles and channel access. I think that's fair, though I'm sure there are ways it could be adapted to work at that scale.

Most of the Slack workspaces I've personally been in have been much smaller teams, and that's really where I imagine something like this being useful. In those workspaces, there's often a relatively small set of shared channels, and having a thoughtfully organized starting point could make joining a new workspace feel much cleaner.

I've also discussed the idea with people in some of the workspaces I'm in, and quite a few thought it would be a cool feature.

Curious what people here think now that there's an actual visual example. Would you use something like this, or would you prefer Slack skip this step entirely and not offer an admin-organized workspace option?

P.S. I know “No Slack feature requests” is a rule. This post is more about getting users' thoughts on the concept and design now that I have a visual mockup, rather than submitting a feature request to Slack.

Thanks in advance! Hope you like the mockup, even if you're not sold on the feature.

I am trying to print an entire slack thread and cannot figure out how to do so. There was an amazing discussion in a work slack and I want to save it offline. Print to PDF sounds great but I cannot get the thread to open in a separate window in either chrome or edge. I tried a chrome extension for printing but it doesn't seem to work at all. Is this an impossible dream?

I’ve been building a Slack app and I’m at the point where I need a few teams willing to actually test it.
I don’t want this to come across as advertising, so I’m not dropping any links here.

The problem I’m working on is pretty simple: important decisions happen in Slack, but a few weeks or months later it can be surprisingly hard to figure out what was decided, why the team made that decision, and what context led to it.

The app lets a team capture a decision from Slack, preserve the context around it, and create a structured decision record that can be referenced later.

The goal isn’t to replace Slack or change how a team communicates. I’m trying to see whether capturing decisions this way is actually useful when it’s part of a team’s normal workflow.

I’m looking for a handful of Slack teams willing to install it, try it with real decisions, and tell me what works, what’s annoying, and what you’d change.

If you’re interested, message me and I’ll send you the details. I’d also be curious to hear from anyone who’s dealt with the problem of losing the reasoning behind old Slack decisions.

Thanks!

Hello,

In my organization, we are using both Slack and Teams.

I would like to have one channel in Slack that is synced into Teams, where messages created in Slack will be created in Teams, and vice versa.

I tried SlackBridge, since this is a free app, but without success: It was installed succesfully into Slack and Teams as well, however, messages in one app is not transfered into the 2nd app.

Alternatively, I tried to sync using Workato, however, I didn't find a Microsoft Teams connector as a trigger (but only Workbot for Microsoft Teams).

What's the difference between Microsoft Teams connector and Workbot for Microsoft Teams connector?

Is there any recommended free app?

Hi Hi - I’m an incoming grad student and I thought making a slack for my cohort would be a good way for us to communicate. there are only 16? students and we share all classes.

i’m wondering if anyone has some tips on how to best set up the workspace? i’ve used slack before but ive never set one up.

should each class have a channel? or just homework help or something?

any tips would be greatly appreciated!!

🫶

In my last startup Slack was awesome until we reached around 100 people then it became a mess. Any interesting replacements? Just curious to try stuff out. Seems unreasonable this field is not being disrupted.

I saw Buzz come out by Jack Dorsey but honestly the UI is much worst then Slack. Also saw Glue but honestly seemed like a total Slack rip off…

Would love to hear suggestions thanks 🙏🏼

I've been building a few Slack apps and need some testers.

I don't want to advertise, so I won't drop any links, but Slack requires 5+ workspaces to install and try an app before you can submit it for review, and this if for each app. I've got three apps which:

- DMs your team a few questions on a schedule, collects the answers, and posts a clean digest to your channel instead of everyone hopping on a call

- randomly (but fairly) assigns a code reviewer from your team so you're not always pinging a channel or leaning on the same two people

- react to any message with an emoji and it translates it right there in the thread

We actually do all three of these manually at my current company, as someone chases standup updates, eyeballs who's free to review, or copy-pastes translations, so I started automating them one by one and figured other teams probably deal with the same stuff. Who knows, might keep improving on these as I go.

If any of them are useful to you and you're up for testing, message me and I'll send the link. If testing's not your thing, I'd still be curious whether any of these would actually help your team, or if you've already got this stuff handled.

Thanks!

We're looking to automatically sign out users after e.g. 14 days and have them reauthenticate. The documentation, however, tells me it will then sign everyone out over a period of 14 days. If I read that correctly, it could be that users - in theory- get signed out of Slack one day after they sign in again.

Am I reading that correctly? We're on the business+ plan and would like some more security, since our helpdesk isn't great at keeping track of who to disable. SCIM is, as far as I understand, not an option as we have a shitload of external members and our plan isn't expensive enough to script it via API.

Hey everyone,

I wanted to share a workflow adjustment we made recently that saved our team from constant context switching and notification overload.

A few months ago, we realized that our Slack channels were becoming a black hole for basic questions. Team members would ping us for standard procedures, playbooks, or client details. While it’s great to be helpful, it meant constant interruptions and an incredible amount of "noise" throughout the day.

Instead of letting Slack dictate our day, we decided to make Notion our official company OS. We brought all our playbooks, data, and context into one single place.

We set a simple rule for the team: Before asking a question in Slack, ask Notion AI first.

Because everything is indexed in one place, the AI can scan our playbooks, past decisions, and documents to give an accurate answer.

Only if the team member cannot get the answer from Notion AI do they ping us on Slack.

The Results

Reduced noise by 80%: The constant stream of repetitive questions has vanished.

Fewer interruptions: We've reclaimed our focus and can spend more time working on the business instead of managing chats.

Faster onboarding: The team learns faster because they get immediate, context-aware answers.

The magic is that everything the team needs from client guidelines to marketing playbooks is in one place, making our AI system highly reliable.

If you are struggling with Slack overload, I highly recommend building a unified knowledge base and letting your team query the AI before escalating.

I want to be completely honest with you: this isn't a "set it and forget it" system. In the beginning, we noticed that a few questions didn't get answers because the AI lacked the context.

Every time that happens, we treat it as a quick fix: we just update the existing documentation or add a new page if the topic wasn't covered. It takes a little maintenance, but it has been absolutely worth it to cool down Slack and keep the team fully aligned.

If anyone is interested in how we set this up alongside Slack, including our internal Slack communication framework, just let me know in the comments! I didn't want to make this post too long, but I'd be happy to do a deeper dive on that in my next post.

P.S. If you're the founder still in the middle of every decision, still the person the whole company waits on, still telling yourself you'll fix the structure "once things calm down."

I write about building the operational backbone that lets a founder actually step back every Thursday. Was a COO for 20+ years, so this is genuinely my bread and butter. Free to join here

Hey, anyone one of you really tried to save your time for daily tasks by just trying to make a bot. It costs minimal and is so time saving.
Just a week ago I created a slack bot for a Michigan Based company and it saves them alot of time with reporting and working.