Manage Slack Notifications Without Distractions
A founder-tested Slack notification setup, plus a free Google Sheet to audit your channels, keywords, and DND windows in one sitting.
Slack fragments the workday. Every context switch takes real minutes to recover from, so the fix is not more discipline, it is fewer eligible pings. This guide walks through the five Slack settings I change first, a batching schedule that survives a real team, and a free Google Sheet that turns the audit into a 20 minute exercise.
I built the first version of Mursa in between Slack pings, which is to say I did not build very much. Every notification looked urgent for the two seconds it took me to open it. Most were not. The pattern that finally worked was boring: audit every channel, kill every notification I could not defend, and then batch what was left into windows I picked instead of windows Slack picked for me.
Below is the exact setup, plus a Google Sheet I now hand to every founder who tells me Slack is eating their day. Copy the sheet, spend 20 minutes filling it in, and you will leave with a defensible answer for every channel in your sidebar.
Copy the Slack Notification Audit Worksheet
A one-sitting audit of your Slack notifications. List every channel and DM, decide keep or mute or leave, build your DND schedule and keyword allowlist, and pick the two or three windows a day you will actually check Slack. Comes prefilled with the defaults I use.
Why Slack notifications are so hard to ignore
The core problem is not willpower. It is recovery time. Gloria Mark's team at UC Irvine measured what happens after an interruption in real office work and found that people took, on average, 23 minutes and 15 seconds to return to the original task ([Mark, UC Irvine publications](https://www.gloriamark.com/publications)). Every ping that pulls you into Slack for 30 seconds is quietly costing you a full recovery cycle.
Communication tools also compound. RescueTime's ongoing analysis of knowledge worker behavior in its [State of Communication](https://www.rescuetime.com/state-of-communication) work shows how often people flip to chat apps during a normal day. It is not a scheduled behavior, it is a reflex, and Slack is designed to reward it.
Slack's own engineering team has written about the same design pressure from their side, including how mobile push, desktop, and email notifications interact ([Slack Engineering](https://slack.engineering/)). The takeaway I keep coming back to: if you do not remove notifications explicitly, Slack will keep sending them, and your brain will keep answering.
The five Slack settings I change first
These are the settings I open on day one of every audit. None of them require a paid plan. Each one has a place in the Google Sheet so you can track what you changed and why.
Mute every channel you did not opt into
Open your sidebar, right click each channel, and pick Mute channel unless you can name the reason you need live pings. This is the highest ROI change. Most people have 15 to 40 channels and need real time notifications for maybe 3.
Set a Notification schedule
Preferences, then Notifications, then Notification schedule. Pick your actual working hours and, inside those hours, add a focus window like 9am to noon where DND is on. Slack respects it automatically, and you stop toggling DND by hand.
Trim your keyword highlights
Preferences, then Notifications, then My keywords. Every keyword here fires a notification across every channel you are in. Keep only your name, your handle, and one or two project codenames. Delete everything else.
Turn off email and mobile duplicates
Preferences, then Notifications, and turn off Send me email notifications for mentions and DMs when I am inactive. Then, on the Slack mobile app, set Notifications to Direct messages, mentions and keywords only. This kills the ping-then-ping-again loop.
Follow threads on purpose, not by default
In Preferences, set Threads notifications to Notify me about replies to threads I am involved in and turn off Automatically follow threads I create. Otherwise every thread you start becomes a permanent notification source.
Batch Slack into windows, not a live stream
Once notifications are trimmed, the second lever is when you look at Slack at all. The setup I use is two long windows and one short one: 30 minutes at the start of the day, 30 minutes after lunch, and a 15 minute closeout before I stop working. Everything else stays in DND.
The Google Sheet has a tab for this. You write down your three windows, the channels you will scan in each one, and the response time you are promising your team. That last part matters. Batching only works if the people around you know when to expect an answer.
Sync your Slack status with Google Calendar using the built in integration. It writes In a meeting automatically and blocks notifications during the event. Pair it with a recurring calendar block called Focus and Slack behaves as if you were in a real meeting.
Team level fixes when personal DND is not enough
If you are on a team, personal settings only go so far. The next layer is agreeing on norms so nobody feels ignored when you batch. Three that have held up for us:
First, replace live standups with an async post in a #standup channel by 10am local time. This drops the pressure to be online early and gives everyone a written record. Second, define a response time expectation, for example DMs answered within four working hours, @channel within one. Write it into your team README. Third, reserve one channel, usually #incidents or #urgent, as the only place that is allowed to override DND, and set that override in Preferences under Notifications, Channel specific notifications.
These are not novel ideas, but they are the ones that actually let a person on your team turn on DND without guilt.
How to run the audit in 20 minutes
Open the Slack Notification Audit Worksheet and go tab by tab. On the Channels tab, paste your channel list from Slack's Browse channels view and mark each one Keep, Mute, or Leave. On the Keywords tab, list every keyword highlight you have and delete anything that is not your name or a live project. On the DND tab, write your Notification schedule and your daily focus window. On the Windows tab, write the two or three times you will actually check Slack, and what you will do in each window.
The Weekly review tab is the one that keeps this from decaying. Once a week, spend five minutes answering three questions: which channel pinged me most, which ping was worth it, and which one should I mute before Monday. If you skip nothing else, do that.
When this setup is the wrong answer
Some roles legitimately need to be reachable in near real time. On call engineers during a shift, sales teams working live inbound, support agents on a queue, and founders in an active incident all fall into this category. For those hours, DND is the wrong tool. What still works is trimming keyword highlights, muting non-critical channels, and using channel specific notification overrides so only the queue channel breaks through.
The rest of your week, though, is not on call. Treat it that way.
If you only do one thing after reading this, copy the [Slack Notification Audit Worksheet](https://docs.google.com/spreadsheets/d/1SB_cLZEGwQUleS8e0XEOB_ENg5F7wa3VSK2vTUJPKuQ/copy) and mute every channel you cannot defend. The rest of the setup is easier once your sidebar stops shouting.
Frequently Asked Questions
What are the most important Slack notification settings to change first?
Mute every channel you did not opt into, set a Notification schedule with a daily focus window, trim keyword highlights to just your name and active projects, turn off email and mobile duplicates, and stop auto-following threads you create. Those five changes handle most of the noise before you tune anything else.
How do I use Do Not Disturb on Slack without missing urgent messages?
Set your Notification schedule to your real working hours and a focus window inside those hours, then use channel specific notification overrides to let one channel, usually #incidents or #urgent, break through DND. Everything else waits.
How often should I check Slack during the workday?
Two or three windows a day works for most non on-call roles: a longer window at the start, one after lunch, and a short closeout before you stop. Write these windows down and share your response time with your team so batching does not feel like silence.
What if my team expects instant Slack replies?
Agree on a written response time norm, for example DMs within four working hours and @channel within one, and reserve one channel for anything that truly cannot wait. Async standups and a shared team README make it easier for everyone to defend focus time.