A friend of mine runs a twelve-person design studio. Last month she spent two days on a proposal, then dropped the final PDF into a shared Slack channel where the client’s main contact had been marked away for a week. Six days of silence. The proposal was good. The channel was wrong, and the mistake cost her the deadline.
Every team I’ve worked with has a version of this story. The tools are rarely the problem. You have email, you have Slack, you have Teams, and all three work. The problem is that nobody ever says out loud which message belongs where. Most of the advice out there compares two channels at a time. The email vs. Slack debate fills entire blogs, and Teams usually shows up as a footnote at the end.
That framing skips the question you actually face, usually several times a day: this message, right now, which channel? Here’s the rule I’ve settled on, plus the table I wish someone had handed me years ago.
When should you use email instead of Slack or Teams?
Use email when the message needs to be found months later, needs to reach someone outside your company, or deserves a considered reply. Use Slack when someone needs an answer in minutes and everything stays internal. Use Teams when the whole organization needs to see a message once, alongside its files and meetings.
The rest of this article unpacks that answer, gives you a decision table you can copy into your team wiki, and walks through the messages that belong in each channel, including the awkward ones that start in one place and need to move..
A rule you can run in ten seconds
Before you send anything, ask three questions. Who needs to see this? How fast does it need an answer? Will anyone need to find it again?
Here’s the rule I use. If it needs to be found in six months, or it needs to leave the building, it goes in email. If it needs an answer before your coffee goes cold, it goes in Slack. If everyone needs to see it once and then get on with their day, it goes in Teams.
When two answers pull in different directions, default to the more durable channel. You can always point someone from chat to an email you already sent. The reverse rarely works, because digging a decision out of a chat thread three weeks later is archaeology, and in my experience the dig comes up empty about half the time.
| What you’re deciding | Slack | Teams | |
| Expected reply time | Hours to days. Asynchronous by design; nobody expects you to live in your inbox | Minutes. Built on presence, so a green dot invites an immediate reply | Hours. Fast in a small channel, slow in a company-wide one |
| Formality | Highest. Complete sentences, subject lines, signatures | Lowest. Fragments and half-finished thoughts are normal | In between. Conversational in team channels, formal in announcements |
| Search and record-keeping | Strongest. The inbox is an archive that maintains itself; mail from 2019 is still sitting there | Good, but history lives inside the workspace and admins can trim it | Good, and tied to Microsoft 365 retention and compliance settings |
| Who can see it | Only the people you name, every single time | Anyone in the channel; public channels are visible workspace-wide | Channel members, gated by org structure and guest permissions |
| Notifications | Batched and calm. The reader chooses when to look | Immediate by default, which is the point and also the problem | Configurable, with an activity feed and email fallback |
| Best-fit messages | Proposals, contracts, performance feedback, external communication, decisions of record | Blockers, quick questions, standups, small coordination | Policy changes, all-hands announcements, file-heavy project updates |
| Team size fit | Any size, and non-negotiable once outsiders are involved | Shines below roughly 50 people; culture-dependent above that | Mid-size and enterprise, especially offices already on Microsoft 365 |
Some teams call this a communication channel matrix and pin it in their wiki or onboarding doc, which I’d recommend. The point isn’t that the table settles every argument. It’s that when someone sends contract redlines as a chat message at 6pm on a Friday, you have something to point at that isn’t your personal opinion.
Email: the channel of record
Email gets treated as the boring legacy channel, the thing that refuses to die. I think that’s backwards. Email is the only one of the three that does four things at once, and the chat tools have spent a decade quietly copying all of them.
It goes outside the company. Your client, your candidate, your accountant, your supplier: they’re all on email. No workspace invite, no app download, no guest permissions to configure.
It survives everything. Platforms get merged, renamed, migrated, and retired. The email you sent in 2019 is still sitting in the same inbox, readable and searchable, exactly as you wrote it.
It’s asynchronous by design. Nobody expects a reply in four minutes, which is exactly what makes it right for messages that deserve thought instead of reflexes.
It belongs to the reader. A chat message lives in the sender’s tool; an email lives in the recipient’s. That difference matters more than it sounds.
The test I run before sending anything: will anyone need to find this in six months? Does it leave the building? Does it deserve a reply that took more than thirty seconds of thought? One yes means email.
That plays out in specific messages. The client proposal, with the PDF attached and the price stated in the body, so the number is quotable and forwardable. The salary negotiation, which is personal, sensitive, and the kind of thing both sides need to reread before responding. The contractor onboarding brief, one message containing access details, expectations, and the first-week plan, which the new person will search daily for a month. The decision email after a messy meeting: here’s what we agreed, here’s who owns what, here’s the deadline.
None of that makes a badly written email good, though. An email that buries its ask in the fourth paragraph fails in every channel, and it fails email hardest because that’s where important messages live. Writing the ones that matter is a genuine skill, and it’s the one place I’ll happily take help: when a message really counts, I draft it, then run it through Writemail.ai to tighten the subject line and make sure the ask is impossible to miss.
Slack: the channel of momentum
Slack’s whole product is speed. The message arrives, the person is there, the answer comes back before you’ve switched tabs. When that’s what your message needs, nothing else competes.
The messages that fit: the release-blocker ping at 4pm, when the build is broken and the engineer who can fix it is in a meeting, so you need her to see it the moment she’s out. The standup update, three lines on what you did, what’s next, what’s stuck, posted where the whole team reads it. The “is this the latest version of the deck?” check, which takes eleven seconds in chat and would take a day in email. The schedule swap for tomorrow’s client demo, where you need a yes or no in the next twenty minutes.
Slack’s own guidance on picking channels comes down to identifying what kind of message you’re sending and matching the delivery method to your audience, which is a sensible place to start (Slack’s blog on picking communication channels). One of their points is worth copying: keep the quick-and-dirty stuff out of email, because one-line emails are how inboxes become noise. I’d add one of my own. Keep conversations in public channels rather than direct messages, so what the team works out stays findable by people who weren’t in the room.
The tax is real, though. Slack assumes you’re present, and presence is a budget. A ten-person agency called Uproer counted their own traffic and found that at their peak they were sending between 250 and 500 Slack messages a day, then realized the volume itself was fragmenting their work, so they wrote an explicit policy for what goes where (Uproer’s Slack vs. email policy). Their diagnosis matches what I’ve seen everywhere: the messages are individually harmless and collectively exhausting.
So the line I’d draw: if the message needs an answer in minutes and takes fewer than a handful of replies, it belongs in Slack. The moment a conversation runs longer than that, or the answer matters beyond the people in the thread, it’s outgrown chat.
Teams: the channel of the organization
Teams is the one that email-vs-Slack guides skip and Slack-vs-Teams guides treat as a feature list. What’s actually distinct about it is structural. Teams is where the org chart lives. Channels map to departments and projects, managers post to their teams, and the shape of the company is visible in the shape of the sidebar.
It’s also where the work artifacts live together in a way neither email nor Slack manages. The Files tab is a real SharePoint document library, meetings are scheduled from the channel, and the project plan sits next to the conversation about it. In my experience this is why bigger companies settle on Teams even when individual employees prefer chat elsewhere: the documents, the calendar, and the announcements are all in one place, with the same permissions underneath.
Announcements deserve their own mention, because they behave differently here. Teams has a dedicated announcement post type, available only in channels rather than one-to-one or group chats, with a headline and a customizable background (Microsoft Support on channel announcements). Slack expresses “this is important” with an @here and a pinned message, which reads like shouting. Teams built a formal format for it instead, which fits what the channel is for.
The messages that fit: the policy change everyone has to acknowledge, posted as an announcement in the general channel with the updated policy in the Files tab. The project kickoff, where the plan, the recurring meeting, and the working documents all live inside one team from day one. The IT maintenance window notice, which needs to reach everyone once and be findable when someone asks why the VPN was down. The Monday leadership update, pinned at the top of the department channel so nobody has to dig through Friday’s noise.
One caution from experience: Teams channels read more formally than Slack channels because HR and leadership post in them, and employees notice. Treat it as the official channel and it behaves like one. Treat it like casual chat and you get the worst of both.
Moving a conversation between channels
Most workplace advice tells you to use both channels. Almost none of it explains the handoffs, which is where the actual damage happens. Four moves cover most of it.
The thread that outgrew chat. A release postmortem starts as a two-line question at 10am and by 3pm it’s 40 messages deep, half of them reactions. In my experience, threads past about 30 messages stop being readable to anyone who wasn’t there. The move: stop, summarize, email. What happened, what was decided, what’s still open, who owns each piece, by when. Five sentences. Turning 40 scattered messages into a summary like that is exactly the job I hand to Writemail.ai, because it’s tedious, high-stakes, and easy to get wrong by hand.
The email chain that should have been a call. The budget question that’s gone eight replies deep, each one longer and more defensive than the last. Email is for considered messages, not for negotiation at speed. The move: suggest a five-minute call or a huddle, then write the decision back into the thread as one short email so the outcome outlives the call.
The decision that lives nowhere. The pricing change agreed in a Tuesday Slack thread, remembered by three people and disputed by two the following month. A decision made in chat isn’t recorded until it’s written somewhere durable. The move: same day, one email titled “Decision: X, agreed [date]” with the reasoning in three bullets. If your company runs on Teams, the announcement channel works too.
The announcement that opens a debate. The new expense policy goes out as a Teams announcement and the replies turn into a forum. Announcements are for broadcast, not discussion. The move: point replies to a thread, a channel, or a scheduled Q&A session, and keep the announcement itself clean.
Make it a policy, not a mood
Your internal communication channels only work when the routing rules are written down. Otherwise every message becomes a judgment call, and judgment calls default to whichever app is closest to your thumb.
It doesn’t need to be elaborate. Uproer’s policy is one page, and it cut their message volume by giving everyone permission to say “this should be an email” without it sounding like a rebuke. Slack’s own three-step process, identify the message type, consider your culture, match the channel to the audience, is a fine skeleton. Steal the matrix above, write down your three defaults, and pin the page where new hires will actually see it. The first week someone joins is when these habits form, and it’s much easier to hand someone a rule than to retroactively explain why their contract redlines shouldn’t have gone to #general at 6pm on a Friday.
