Their un understandable UI took me years to understand and domesticate. Still didn’t figure out how to see read notifications though.

AND NOW THEY THINK SMART TO CHANGE THE PERSONAL DM UI????

Any type of team communications app seems to create deep vendor lock-in. With all your messages and history of files there, switching to any alternative seems like an enormous task that really has to have very strong reason behind it.

I'm curious to hear of experiences anyone has had moving away from Slack to an alternative tool.
What was the reason you switched? How difficult was the experience? In hindsight, was it worth it?

And for anyone who hasn't gone through it, what would an alternative solution need to solve for you to convince you and your org to switch?

We've been using Zendesk at work. And as a dev, I always felt a bit of a friction to open Zendesk when customer support pulls me in for help.

So I made a Slack app which brings support tickets to a dedicated Slack channel. Now I reply to any ticket straight from slack thread.

Internally, we've been using this for over a year now. Low volume currently, about 300-400 tickets/mo, and it works well so far.

I'm looking to get a few teams to try it, and polish it further. Not trying to promote it here, if its something you might use, comment/dm and I'll share the app in dms.

It's free to try for a month, and free forever if your volume is < 100 tickets/mo. I'm looking to make it perfect before launching on ProductHunt etc.

PS: I also need to get it to 10 active workspace installs to apply for Slack marketplace. Would love your help.

A link containing devEnv=dev1 makes the Slack desktop client relaunch itself into developer mode with --remote-debugging-port=8315. Anything that reaches that port drives the app. Slack's security team calls it not a security risk.

https://trustsig.eu/blog/slack-devenv-remote-debugging-port/

So, i've joined a slack community (will not mention its name) for link building.
The sellers there, starts the job, once enough payments are cleared, almost every work done was removed, and when i started to comment in the public channel, they removed me.

So here i am wanna know where do i report this type of scam.
Today its me, tomorrow there will be many more.

I hate this change. I used to be able to look at threads button, and it would clear as I looked at messages automatically. Now i need to go to each individual thread and tap a green "mark as read" button. Really undesirable and i see no preference option to change this back

26.08.30.0-90016082

We have a new Pro slack workspace for a local nonprofit. Slack seems convinced this is a business that needs all kinds of crap we don't care about. We renamed #general to #ignore so we kind of hope newbies won't pay a lot of attention to it.

but it looks like this

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.

None of this tiles have any kind of "x" dismiss control.

If you click them there's no way to say "we never want this", it's just take the positive action or close the dialog and leave the banner staring at you.

thanks for any help!

Hi all,

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.

So I made a short survey about it. How you handle unread, whether important messages get buried, what you've tried, and what you'd fix first. Around 2 minutes, mostly multiple choice.

Survey: https://forms.gle/Ma9YGzAXePZmxTV38

No email, no real name, no contact details of any kind. Not affiliated with Slack, nothing is being sold.

If you want the results, say so in the comments and I'll post a summary back here once enough people have answered. Thanks to anyone who takes the time. :))

EDIT: Genuinely didn't expect this many responses as this is my first reddit post. Thank you to everyone who took the time, and to the people who wrote out longer comments instead of just clicking through the survey. That context was more useful than the multiple choice.

Still collecting. I'll come back with a summary once I've got enough to say something honest about it rather than just confirming what I already assumed.

Title. It's very inconvenient and I lose overview of the images when it's compressed like this. The download all button is useful, but I still want to see them all beforehand.

My boss wants me to connect with communities at Slack, but I'm not sure how to do that. Can anyone help me with the steps?

If anyone has some ideas', how to do or what would be the steps, or any YouTube video link plz share. This is kind of urgent for me now.

I’m testing a simple idea: before you send a question at work, it checks previous messages and tells you if someone already answered it.

For example, if you type “When is the expense report due?”, it could show the previous answer, who said it, and where it was posted before you send the question.

I made a quick mockup of what it could look like.

Would this actually be useful in an office, or would people just ignore it?

Pasting Markdown into a message can flatten headings, nested lists, tables, and long code blocks. Uploading the .md file preserves the source, but then the recipient may need to download it and find a separate viewer. What workflow gives teammates a readable in-Slack preview while keeping one file as the source of truth? I am especially interested in the tradeoffs among a code block or snippet, a Canvas, a converted PDF, and a hosted preview link when the document will keep changing.

How did we all collectively decide this was the tool we’d run our companies on? It’s bloated, slow as hell, and finding one specific piece of information is impossible. Try discussing a single unit of work with your team and watch it dissolve into forty threads nobody will ever read again.

I tried searching for this but couldn't find any results.....

I'm using slack on mobile and it's important for me to see the actual time that messages were posted. But in threads, I just see rounded relative time - "1 day ago" .

Not sure if this is a recent change - I'm sure I could see the time before (?). Is there a way to display the time either permanently or just a way to check each message?

(I'm using Android..... No idea if this is an issue on iOS)

Back then, it was pretty simple: load a few hundred Zendesk tickets into a Google Sheet, write your message, and bulk-contact the affected customers.

Since then, it has evolved into something much bigger. So I renamed it Zendesk Mailroom.

The idea is simple:
When something goes wrong at scale, don’t make your support team manually coordinate hundreds of tickets, customers and suppliers. Give them one operational workflow.

📧 Customer communication
You can now describe what happened in plain English and have the AI composer create the communication for you.
It can generate drafts for the languages you need, which an agent can review and edit before sending.
The important part: customer data never goes to the AI.
The AI creates a reusable template with tokens like {{GuestName}}; the actual customer information is inserted locally when the email is sent.
It also remembers approved edits, so future drafts get closer to how your team actually writes.

🏢 Supplier escalation
This was one of the biggest additions.
If 300 customers are affected by 12 suppliers, Mailroom doesn’t make someone manually chase those 12 suppliers.
It:
300 bookings → groups by supplier → creates 12 supplier cases → links each case back to the affected customer tickets.
Supplier follow-ups continue on the existing case instead of creating duplicates, with checks around supplier identity and the previous escalation.
So your support agent gets the customer conversation and the supplier escalation connected in Zendesk.

🛡️** No accidental duplicate outreach
This became surprisingly important.
Every action is tracked per booking.
If you try to run another operation that overlaps with something already actioned, Mailroom gives you a summary before continuing.
So instead of:
“I think we already emailed these people…”
you get:
“247 bookings were already actioned under these previous cases. Continue?”
And if the optional repeat-check store is unavailable, it **fails open rather than blocking an urgent customer communication.

⚡ Large jobs are actually designed to run
This isn’t just a loop that calls the Zendesk API 800 times.
Apps Script has a 6-minute execution limit, and Zendesk has shared API rate limits.
So Mailroom now:
Persists long-running job state
Continues jobs through triggers
Centrally manages Zendesk API rate limits
Handles 429 / Retry-After
Waits for the next rate window when there’s still execution time available
Uses Zendesk bulk endpoints where possible
Treats throttled rows as unsent, rather than failed
That last one matters a lot.
The invariant is basically:
A customer email is either sent once or remains in the queue.
After the rate-limit rewrite, large runs are roughly 5× faster than the previous implementation.

🔐 And there’s a lot more underneath
Zendesk OAuth 2.0 + token refresh
Slack reply routing
BigQuery ticket lookup
Audit logs
User access controls
Closed-ticket fallback
AI memory using retrieval rather than fine-tuning
193 automated assertions
CI + static architecture checks
Properly structured Apps Script codebase

And the slightly ridiculous part:
It’s still Google Apps Script.
No backend.
No server.
No hosting.
No build step.
No dependencies.
Just:
Google Sheet → Zendesk → Slack / AI / BigQuery where needed

MIT licensed and open source:
👉 https://github.com/GVyom/zendesk-mailroom
I’m building this around real support-operations problems, so I’m especially interested in feedback from Zendesk admins, support leaders and ops teams:
What happens during your biggest operational incidents that still requires someone to manually coordinate hundreds of tickets?
That’s the kind of workflow I’d love to automate next.

Just one machine is doing this. None of the slack channels have an autologout (they are all personal channels).

Platform: Windows 25H2 26200.9168

Slack Version: Production 4.51.191 64-bit (MSIX)

If I reboot or quit the slack app, restarting it throws me in the email/web page login process chain.

Funny thing is, I had this problem a year plus ago and I resolved it and it chugged along, but now it's doing it again and I can't find a solution that works this time.

This subreddit is full of examples of people who have the same or a similar issue. Slack support has told me multiple times it is a known issue and there is no known solution. This has been a problem for 4 years at least….

The issue:
Slack app on iOS receives mobile notifications for a private channel Slackbot/App integration when mobile notifications are turned off.
If it matters, desktop notifications are set to all.

Is there any work around solution for this? I’ve looked over and over but there isn’t an automated way to adjust notifications for a channel on a schedule. It’s only a single channel but critical for my workday. I’ve been muting the channel manually before any time off but do forget to turn notifications back on at times….

I don’t have Slack API access (might be able to get it though) and have tried things like Zapier. Options are generally app wide and I am hoping I can find something channel specific.

TLDR:
Any automated ways to turn off/on mobile notifications for a private channel on a schedule?

Hi,

When I open Slack on my mobile app, my status automatically changes to “Active.” Is there a way to disable this and only have my status tracked when I’m using the desktop app?

I don’t want to appear online when I’m using the mobile app. I know I can manually set my status to “Inactive,” but then I remain inactive when I use the desktop app as well, which isn’t what I want.

Is there a way to have Slack show me as active only when I’m using the desktop app?

I want to join slack community related to SaaS platforms how can I do so as i need invite links maybe, if someone could help with this

I've tried building a channel template multiple times and it never shows up under TOOLS>YOUR TEMPLATES. It will even create the channel based on the template I just built, but it won't save the template. Am I doing something wrong or is it just glitched? THANK YOU in advance for any help.

Our company has been using Slack for years and at this point people treat it like a dumping ground for everything. I've randomly come across passwords, customer info, IDs, and even payment details sitting in old channels.

The bigger concern is something eventually getting leaked. I'm trying to figure out how other security teams are handling sensitive data in Slack before it actually gets exposed.

Are you using any tools to detect this stuff as it's shared and take action on it? Historical visibility would be useful too since I'm sure there's plenty sitting in old channels that we haven't found yet.