Slack, Teams and ADHD: Notification Settings That Protect Focus
The Slack and Teams settings that cut interruptions without going dark, how to batch replies, and response-time norms your team will actually accept.
You open the document at 9:12. At 9:14 a channel you muted months ago lights up anyway because someone used an at-here. At 9:20 a direct message arrives that could have been an email. By 9:40 you have answered eleven things and started none of your own work, and the document is exactly where you left it.
ADHD notifications at work are not a willpower problem. Chat tools are built to pull attention, and ADHD attention is easier to pull than most. The settings that fix this exist in both Slack and Microsoft Teams. They are buried, and the defaults are the worst possible ones for you.
Here is how to set both tools up, how to reply in batches without looking unresponsive, and how to get your team to agree on response times so you are not the only one playing by different rules.
Why chat apps hit ADHD attention harder than email
Email waits. Chat arrives with a sound, a badge and a social expectation of speed, and each one of those lands directly on the parts of attention that ADHD makes hardest to govern: the pull toward novelty, the difficulty re-entering a task after a break, and the sense that an unanswered message is a small emergency.
The cost is not the thirty seconds it takes to reply. It is the ten to twenty minutes it takes to get back to where you were, multiplied by every ping. Many people with ADHD find that a chat-heavy day feels busy and produces almost nothing, which is a fair description of what happened. The post on why ADHD brains struggle with noise and distractions covers the mechanism; this one is about the settings.
Channel muting, keyword alerts and notification schedules
The goal is to make the tool notify you about work that is yours and nothing else. Three layers do most of it.
- Global default to mentions only. In Slack, set notifications to direct messages, mentions and keywords rather than all new messages. In Teams, open notification settings and turn channel activity down to mentions and replies to your own posts.
- Mute or hide channels you only need to search. Both tools let you mute a channel so it never badges, and hide it so it leaves the sidebar. If you have not posted in a channel in a month, mute it. You can still search it.
- Keywords. Slack has a keyword list in notification preferences: add your project names, your clients' names and the system you own. You are then notified when those appear, even in a muted channel. Teams does not have a direct equivalent; the workaround is to ask teammates to tag you rather than rely on you reading everything.
- A notification schedule. Slack lets you set the hours and days notifications are allowed at all. Teams mobile has quiet hours and quiet days. Set both to your working hours and stop apologising for the gap.
Expect to feel exposed for a week. The feeling that you will miss something important is strong and mostly wrong, and the keyword list is what makes it wrong.
Focus blocks your team can see
Going quiet without warning makes people chase you harder. Going quiet with a visible reason makes them wait. The tools support this directly.
- In Slack, set a status such as Heads down until 11 with an expiry time, and pause notifications for the same window. The status answers the question before it is asked.
- In Teams, a Do Not Disturb status silences everything except people on your priority access list. Add your manager and one teammate so a real emergency can still reach you.
- If your organisation uses Outlook, book focus time in your calendar. Teams reads it, switches your status to Focusing and quiets notifications for the block.
- Make the block the same time every day where possible. A predictable 9 to 11 silence is something colleagues learn; a random one is something they test.
Two blocks of ninety minutes a day is a realistic target. Start with one and keep it for a fortnight before adding the second.
Answering in batches without looking rude
The fear is that batching looks like ignoring. It does not, if the batches are predictable and the first reply in each batch is a fast acknowledgement. Try three chat windows a day: the start of the morning, just after lunch, and the last half hour. In each one, work the list from the top.
- Anything that needs a one-line answer gets it now.
- Anything that needs real work gets an acknowledgement and a time: Seen, will have this to you by 3. Then it goes on your task list, not left in chat.
- Anything that should have been a meeting or a document gets moved there: This needs more than chat, I will set up fifteen minutes.
- Use the save-for-later or mark-unread feature on anything you cannot deal with in the window, so it survives the scroll.
The acknowledgement with a time is the whole trick. It converts an open loop in someone else's head into a closed one, and it converts an open loop in your head into a task with a deadline.
Phone versus desktop: where chat should and should not live
The strongest single setting is a decision rather than a toggle: work chat lives on the computer, not the phone. A phone notification arrives during dinner, in the car, at 11 p.m., and each one restarts the work day in your head.
- Delete the mobile app if your role allows it. Most do, and the honest test is whether anyone has ever needed you by chat outside hours for something that could not wait until morning.
- If you must keep it, turn mobile notifications fully off and open the app on purpose. Slack can also send mobile notifications only when you are inactive on the desktop, which is a reasonable middle setting for on-call days.
- Never let chat badges sit on the home screen. A red number is a small, constant tax on attention.
If your job genuinely requires after-hours reach, ask for a separate channel for that purpose, with its own notification sound, and silence everything else.
Proposing team norms for response times, and this week
Individual settings get you most of the way. A team agreement gets you the rest, and it protects you from being the one person who seems slow. Propose it as a team question, not an ADHD one.
- Expected response time in chat is a few hours, not minutes. Anything urgent gets a call or a mention with the word urgent.
- At-channel and at-here are for outages and deadlines only.
- Decisions go in a document or a ticket, never only in a thread.
- No expectation of replies outside working hours unless on call.
Most teams accept something like this readily, because everyone is drowning. If you want help building the habits around the settings, our answer on whether CBT can help with ADHD at work explains how structured skills work applies to this. For this week: set the global default to mentions only, mute every channel you have not posted in for a month, add five keywords, book one ninety-minute focus block, and take the chat app off your phone.
This article is for educational purposes only and is not medical advice, diagnosis, or treatment. Always consult a licensed healthcare professional about your individual situation. If you are in crisis or thinking about self-harm, call or text 9-8-8, Canada’s Suicide Crisis Helpline, at any time.
Finding Focus uses AI tools to help research and draft some articles. Every article is edited and fact-checked by the Finding Focus team before publication. See our editorial and medical review policy.
