How to set "do not disturb" hours for global teammates
If you work with global teammates, you'll get pings at all hours unless you actively manage your tools. Modern apps support Do Not Disturb (DND) hours that respect time zones — when set up correctly, they prevent late-night interruptions without making you unreachable in emergencies.
For checking colleagues' working hours, the world clock shows multiple zones at once. The rest of this post covers the actual settings.
Slack — the most common case
Slack supports DND hours per workspace and per user.
To set your DND schedule:
1. Click your profile picture in Slack
2. Click "Pause notifications" → "Set a schedule"
3. Set your daily DND start and end times (e.g., 6 PM-9 AM)
4. Pick which days (most people set Mon-Fri 6 PM-9 AM and weekends entirely)
During DND:
- Notifications are silenced
- Your status shows you're not available
- Direct messages still arrive but don't ping
- Channel mentions don't ping
Override exceptions:
- Mark someone as "VIP" to allow their messages through DND
- "@everyone" pings DO bypass DND by default (some workspaces limit this)
- Critical-priority pings (in workspaces with that feature) can override
To respect colleagues' DND:
- Slack shows their DND status in the conversation header
- Schedule sends ("Send later") to deliver during their working hours
- Don't override DND except for genuine emergencies
Microsoft Teams
Similar concept; the UI is different.
To set quiet hours:
1. Open Teams → click your profile picture
2. Settings → Notifications and activity → Quiet hours
3. Set daily quiet hours and quiet days
Behavior:
- Notifications silenced during quiet hours
- Status shows "Away" or your custom status
- Messages still received, just not notified
Teams' DND is less granular than Slack's but works similarly.
Google Workspace
Calendar:
- Settings → Working hours → set daily working hours per day of the week
- This is visible to other users when they try to schedule with you
Gmail:
- No native DND, but you can set scheduled send for outgoing messages and use Filters to mute non-urgent threads during specific hours
Google Chat:
- Auto-respect of working hours when integrated with Calendar; pings outside working hours show your status as away
Phone-level DND
Most phones (iOS and Android) have DND modes that silence all notifications:
iOS:
- Settings → Focus → Do Not Disturb
- Schedule: set daily times
- Allow exceptions for specific contacts (e.g., spouse, manager)
Android:
- Settings → Sound → Do Not Disturb
- Schedule: set daily times
- Allow exceptions for repeat callers, starred contacts
The phone-level DND is the last line of defense. Even if Slack's DND fails, your phone won't ring.
Working hours in productivity tools
Beyond DND, several tools support "working hours":
Notion / Linear / Jira / Asana: Mostly don't have native DND, but you can set notification preferences per project.
Loom: No built-in DND; just don't open the app outside your hours.
GitHub: Notification settings per repository; you can mute specific repos or silence for specific times via your phone's DND.
What to set DND to
Common configurations:
Conservative (recommended for most people):
- Mon-Fri 9 AM-6 PM your local time = working hours
- Mon-Fri 6 PM-9 AM = DND
- All weekend = DND
Liberal:
- Mon-Fri 8 AM-7 PM = working
- Some weekend availability
Strict:
- Mon-Fri 9 AM-5 PM = working
- All other hours = DND with no overrides
Variable for international teams:
- Mon-Fri morning (your local) = focused work, DND for non-essential
- Mon-Fri afternoon = collaboration window with US/EU colleagues
- Evenings and weekends = DND
The right answer depends on your role and team norms.
VIPs and emergency overrides
Most DND systems support exceptions. Common patterns:
Spouse/partner. Always reach you, regardless of DND. Some teams mark managers as VIP for true emergencies; this depends on trust.
On-call rotation. When you're on-call, your DND is suspended. Tools like PagerDuty integrate with this.
True emergencies only. Some teams have an explicit rule: only "production is broken" or "someone is hospitalized" justifies overriding DND.
The pattern: be permissive about who can override (so emergencies work) but strict about what justifies overriding (so it's not abused).
The "responding immediately" trap
A common bad pattern: you set DND but check messages anyway and respond.
If you respond to non-urgent messages outside your hours, you signal that you're available — and others ping you more. The DND becomes meaningless.
Discipline: when DND is on, don't check unless you have a specific reason. Read messages tomorrow morning.
The "I'll just respond quickly" trap
Another bad pattern: you check Slack at 11 PM "just to clear the queue" and end up engaged in three threads.
Discipline: if a message wasn't urgent enough to override your DND, it's not urgent enough to engage with at midnight. The thread will be there tomorrow.
What about weekend availability
Most knowledge work doesn't require weekend availability. If your job does (on-call, customer support, breaking news), there should be:
- Compensation reflecting weekend work
- Rotation across team members
- Clear definition of what "weekend availability" means (responding to pages? answering emails?)
If your job doesn't require it but you feel pressure to be available, that's a cultural problem worth addressing with your manager.
Cultural variations
What's normal varies:
Strict separation cultures (Germany, Sweden, Netherlands, Denmark): expectation is zero contact outside working hours. Pings outside are taboo.
Always-on cultures (parts of US tech, parts of finance): expectation is responsiveness even off-hours. Reform is happening but slowly.
Family-time cultures (much of Latin America, parts of Asia): evenings and weekends are family time, not work time.
If you're moving from one culture to another, learn the norms early.
When to override your own DND
Sometimes you should:
- A direct report is having a genuine crisis
- Production is on fire and you have specific knowledge
- A family member needs you immediately
- You're traveling to an unfamiliar location and need to handle logistics
Don't:
- "Quickly" respond to non-urgent messages
- Check Slack "just to see"
- Engage with threads that don't need your input
FAQ
Won't my career suffer if I'm not constantly available?
Generally no, with caveats. If your performance is judged on output (which most knowledge work should be), DND won't hurt. If your performance is judged on responsiveness (which is bad management), you'll need to either change the culture or change jobs.
What if my manager pings me at midnight?
Have an explicit conversation. "I noticed you message at unusual hours. I respond next business day to non-urgent things — does that work for you, or is something coming up that needs immediate attention?"
What if a colleague depends on my real-time response?
Discuss it. "It seems like X is blocking on me. Should we set up a daily handoff or sync window so you have what you need?"
Should I disable DND for VIP contacts?
Yes — most people allow specific people (manager, spouse) to bypass DND. The pattern is "permissive about who, strict about why."
What about emergency contact for production issues?
Have an explicit on-call rotation. PagerDuty, Opsgenie, etc. — these page the on-call engineer regardless of DND. The on-call rotation should cover 24/7 if your service requires it.
How do I know what hours to set?
Start with 9-5 your local time. Adjust based on your actual rhythm. Some people work 10-7, some 7-3, some have split schedules. The right answer depends on your life.
Bottom line
Setting DND hours is the easiest way to prevent burnout from constant interruptions while remaining reachable for genuine emergencies. Slack, Teams, Calendar, and your phone all support it. The key is using it consistently — checking messages outside your DND defeats the purpose.
For finding times to actually meet that respect everyone's working hours, the meeting planner and world clock are the tools.