Slack Etiquette for Global Teams: 10 Rules Every Distributed Team Needs
Most of what a distributed team knows lives in Slack. Decisions, context, the running joke nobody can explain to new hires. That's also where things go wrong when half your team is asleep while the other half is shipping. The tool itself isn't the problem. The habits people carry over from a single-office life are.
In one room, you can be sloppy and it works out. Someone overhears, someone taps you on the shoulder, the gaps fill themselves. Spread that same team across eight timezones and the gaps stop filling. Below are 10 rules the teams that get this right tend to follow. None of them are hard. They just have to become reflex.
1. Always include the timezone when you mention a time
"Let's ship at 5pm" reads fine to you and means four different things to four teammates. "Let's ship at 5pm ET" means one. That's the whole rule, and it's first for a reason.
When you can, spell out the conversions for your main clusters: "5pm ET / 2pm PT / 10pm GMT." Nobody has to open a calculator.
Easier still, let a tool do it. Timely converts times right inside Slack, so when you type "let's meet at 3pm ET," each person sees that moment in their own timezone. You stop thinking about it, which is the point.
2. Put replies in threads
When everyone's online at the same time, a busy channel reads fine. You can follow three conversations at once because they're all happening in front of you. Across timezones that same channel turns into a transcript of overlapping conversations stitched together out of order, and the person reading it woke up four hours after the last reply.
Threads fix that. Reply in the thread, not the channel. Conversations stay grouped, catching up takes minutes instead of scrolling, and the context you posted at 11pm is still attached to its question when your teammate finds it at 9am their time.
3. Respect notification boundaries
Slack is always on. Your teammates aren't, and shouldn't be.
Practical tips:
- Use Slack's scheduled messages (click the dropdown arrow next to the send button) so your message lands during the recipient's working hours, not at 2am theirs.
- Don't wait on a reply from someone who's offline. They'll get to it.
- Set up Do Not Disturb schedules in Slack's notification settings, and nudge your team to do the same.
Here's the thing about "no rush, but..." at 2am: the words say no rush, the notification says otherwise. The phone still buzzes. Schedule it.
4. Set your status and timezone
Your profile should answer two questions before anyone has to ask: where are you, and are you reachable right now.
- Set your timezone in Slack settings so your profile shows your local time.
- Use status updates to signal availability: "In meetings until 2pm PT," "OOO back Monday," "Deep work, slow to respond."
I've watched this one habit kill off most of the "you around?" pings a team sends in a week. People check the status instead of asking.
5. Use @here and @channel sparingly
@channel pings everyone, including the people who are asleep and the person who's on PTO in a different hemisphere. On a global team, there is always someone who didn't need that notification.
Use this guide:
@herenotifies only people currently active in Slack. Good for anything relevant to whoever happens to be online.@channelnotifies everyone, including those who are away with notifications on. Save it for outages and hard deadlines.- Neither is the right answer most of the time. Just post the message. People read it when they're back.
Rough test: if you wouldn't physically walk over and tap someone on the shoulder for this, don't @channel it.
6. Write the whole thought, not five fragments
In the same room or the same timezone, this is harmless:
"hey" "so I was thinking" "about the auth flow" "what if we..."
Spread out, it's five notifications that wake a teammate up to "hey" and "so I was thinking" with no idea whether the thing got resolved or whether they're on the hook for it. They have to wait around for the rest, except you've logged off by then.
So write it once:
"Hey, I've been thinking about the auth flow. What if we moved the token refresh logic into middleware instead of handling it per-route? That would centralize the error handling and cut the duplication. Thoughts?"
One message, one ping, the full picture.
7. Treat emoji reactions as a quiet yes
In a meeting you nod. In Slack you react. Same signal, no extra message.
A reaction tells the sender you read it, you agree, you're on it, without piling another reply onto a thread someone else has to scroll past. That's most useful on async updates and standups, where a 👀 or a ✅ says "I saw this" and saves everyone a round of replies.
It helps if the team agrees on what a few of them mean:
- 👀 means "I'm looking at this"
- ✅ means "done" or "acknowledged"
- 👍 means "sounds good"
- 🎉 means "nice work"
8. Default to public channels over DMs
A decision made in a DM is a decision the rest of the team can't see. That's bad anywhere. It's worse across timezones, because the people who'd object or build on it won't even be awake to find out it happened, and by the time they catch up the thread is buried.
So default to channels. If a DM turns into something other people should know about, drag it into a channel. If you're deciding something, decide it where the team can read along.
The mantra: if it's work-related, it probably belongs in a channel.
9. Name channels clearly and consistently
Naming matters more here because a confused teammate in Manila can't lean over and ask where this goes. They either find the right channel on their own or they post in the wrong one.
Pick a convention and hold to it:
#team-[name]for teams#project-[name]for projects#help-[topic]for support#social-[topic]for the non-work stuff
Someone six timezones away should be able to guess the right channel cold. The name carries the information so a person doesn't have to.
10. Watch the time-relative language
Timezone abbreviations on actual times are step one. The sneakier problem is the phrases that quietly assume everyone shares your clock:
- "let's discuss this this afternoon" becomes "let's discuss this by EOD Tuesday ET"
- "I'll get to this in the morning" becomes "I'll get to this by 10am PT"
- "see you tomorrow" becomes "see you in tomorrow's async standup"
- "is anyone around?" becomes "looking for input on X, reply when you're online"
"This morning" and "this afternoon" mean your morning and your afternoon. To a teammate twelve hours off, they're noise. Swapping in a concrete time costs you nothing and saves a clarifying reply later.
Making it stick
Writing rules is easy. Keeping them alive is the hard part. Three things help.
Pin them. Drop your team's Slack norms into a pinned message in the main channel so every new hire trips over them on day one.
Model them. If the leads use threads, tag their times, and schedule their late-night messages, the rest of the team copies it without being told. Behavior teaches faster than a wiki page nobody reads.
Automate the parts you can. Empathy doesn't automate. Timezone math does. Timely takes care of Rule #1 on its own: someone mentions a time in Slack, and every channel member sees it in their local time. That's one less thing anyone has to remember.
You're not aiming for a perfect team. You're aiming for fewer moments where the person two continents away feels like an afterthought. The small courtesies are the whole game, and they add up faster than you'd expect.
For the groundwork under all of this, read 7 Timezone Tips for Remote Teams. And when you're ready to go past habits into how the team actually thinks about time, Why Your Team Needs a Timezone-Aware Culture gets into the empathy and process side.
Automate the Hardest Part of Slack Etiquette
Timely handles Rule #1 automatically — every time someone mentions a time in Slack, everyone in the channel sees it in their own timezone. No more "what timezone?"