Take Control of Your Slack Notifications

My phone lit up at 4:12am. Then again at 4:15. By the time I gave up and looked, there were nine notifications waiting, and not one of them had anything to do with me. A deploy thread in a channel I could have sworn I'd muted. Someone in Singapore three messages into their Tuesday. A bot announcing a build. I lay there in the dark reading about a staging rollback I had no part in, fully awake now, and did the arithmetic. It was the middle of the afternoon for half the company. Of course my phone was going off. Somebody, somewhere, was always mid-workday.

That's the thing nobody warns you about when you join a team spread across the planet. The workday doesn't end. It just moves. The sun comes up in Sydney about the time it goes down in San Francisco, and Slack keeps the conversation rolling the whole way around the globe. Left on its out-of-the-box settings, your phone treats a 4am message from a colleague eight hours ahead exactly like a 4am emergency. It buzzes. And you, trained by years of red badges, look.

The defaults assume everyone shares your clock

Slack's default notification settings were designed for a team in one office on one schedule. Everybody's awake between nine and five, everybody goes quiet at night, so notify-on-everything mostly works. The app pings you, you glance over, and by the time you're asleep the whole company is too.

Cross a few timezones and that quiet assumption falls apart. There is no shared night anymore. Every channel you belong to has people typing in it at hours you'd normally be unreachable, and the app has no idea which of those messages matters to you and which is just the ambient hum of a company that's always partly awake. So it forwards all of it, at full volume, forever. The settings aren't broken. They're answering a question about a world that no longer exists, which is a world where the people you work with are asleep when you are.

Most people respond to this by suffering through it. They keep notifications on, get pinged at odd hours, and slowly train themselves to check Slack the moment their eyes open and the last thing before bed, because who knows what happened while their half of the planet was down. That's not staying on top of things. That's letting five timezones decide when you're allowed to stop paying attention.

Turn off almost everything, and mean it

The single most useful change I've made to how I work remotely was making silence the default. Not notifications tuned down. Off. Then I let a short, deliberate list of exceptions back through.

This sounds reckless the first time you hear it, and it isn't. On a synchronous team, all-channel notifications are a rough proxy for "something might need me right now." On an async team that proxy is worthless, because most of what lands in a channel while you're offline was never meant to interrupt you in the first place. It was written to be read whenever you next surface. That is the entire premise of working async in the first place: the message waits for you, not the other way around. If your notification settings don't reflect that, you've adopted async in name and kept the interruption model of an open-plan office.

So go into your Slack preferences and set the baseline to nothing. No badge for every channel, no buzz for every thread you were once tagged in. Then rebuild a small allow-list on purpose. The goal is a phone that stays quiet by default and speaks up only for the handful of things you've genuinely decided are worth breaking your focus for.

Give your phone hours it will respect

Set a Do Not Disturb schedule, and set it to your working hours, not the company's. If you work 9 to 6 in Lisbon, your phone should go dark at 6pm Lisbon time no matter how loud the Americas get as they come online. Slack will hold the notifications and hand them to you in the morning, which is exactly when they became relevant to you anyway.

The reason people hesitate here is fear. Turn off notifications at night and won't something urgent slip through? On a healthy team, almost never, and the fix for the rare true emergency is a separate channel, not keeping every ping live around the clock. But this only works if your team has actually agreed on what counts as a reasonable response time. When the norm is written down, and everyone knows a message sent at your midnight will be answered at your 9am, muting your evenings stops feeling like dereliction and starts feeling like the plainly correct thing to do. If no such norm exists, that's a bigger problem, and no notification setting will paper over it.

A protected evening also protects the other end. Those uninterrupted blocks are where the deep work remote is supposed to enable actually happens. You cannot think hard about anything for ninety minutes if your pocket is buzzing every four, and on a team that's always partly awake, it will buzz every four unless you make it stop.

Decide what's allowed to interrupt you

With the firehose off, you get to choose what earns its way back in. Keep the list short and specific.

Direct messages and direct mentions of your name are the obvious ones. Those are somebody deliberately reaching for you, and letting them through is the price of being reachable at all. Beyond that, keyword alerts are the sharpest tool Slack gives you and the one almost nobody uses. Add your project's name, the service you own, the word your team uses when something is actually on fire. Now a message in a channel you've muted will still find you if it contains "checkout is down," and nothing else in that channel will. You've told the app what you care about instead of making it guess from raw activity.

Mute liberally. Muting a channel is not leaving it; the messages are still there, still searchable, waiting for you to read them on your schedule instead of theirs. I'm in maybe forty channels and get live notifications from four. The other thirty-six I read the way you read a newspaper, in a batch, when I choose to, caught up in ten minutes over coffee. When you ping other people, extend them the same courtesy the etiquette for global teams asks for: schedule the message to land in their morning rather than firing it into their night and trusting their settings to catch it.

Quiet is not the same as gone

Here's the trade-off, because there is one and pretending otherwise would be dishonest. Go too dark and you pay for it. If you mute everything and surface only to dump your own work and vanish, you drift out of the team's peripheral vision, and isolation on a remote team is invisible right up until someone quits. There's a difference between controlling your notifications and disappearing, and the difference is whether you show up on purpose.

There's also a perception cost worth naming. A teammate whose phone is quiet at 4am can look, to a manager still reading the green presence dot, like someone who's checked out. That's the manager's mistake to fix, not yours to absorb by staying pingable all night. But you can meet it halfway by making your actual work visible in writing, so nobody has to infer your effort from how fast you react to a thread.

So batch-check the channels you muted a couple of times a day. Post in the watercooler. Answer the things that were waiting when you come online, promptly, so people learn that quiet-until-9am reliably becomes present-and-responsive after. Do that, and turning off the notifications doesn't read as absence. It reads as someone who's decided, deliberately, when the team gets to reach them.

That decision is the whole point. On a team that never fully sleeps, the choice was never whether to be interrupted less. It was whether you make that choice or hand it to whichever timezone happens to be awake at the moment your phone would otherwise buzz.

Let the Right Pings Through at the Right Time

Half the reason a late-night Slack message jolts you awake is that it arrived at the wrong hour for you and nobody meant it to. Timely converts every time mention in Slack to each reader's own timezone automatically, so "let's sync at 3" and "can you review this by 5" read correctly in every pocket they land in, and your teammates can time what they send around your day instead of ambushing it.

Add Timely to Slack — Free · See how it works