Slack Farewell Message: How to Say Goodbye Channel by Channel

Here is the short answer. Post one short farewell in your team channel on the morning of your second-to-last day, send four to eight personal DMs the evening before that, and leave the company-wide channels alone unless your company's culture asks for it. On Slack, the channel you pick carries as much of the message as the words. Get the channel wrong and even a warm goodbye lands flat.

If you are reading this in your last week, you already know the awkward part. The team channel feels too public for the people who mattered most, and DMs feel too intimate for the people you barely worked with. So the message sits half-drafted in a note somewhere while your last two days fill up.

This is what actually works: sort by Slack surface first, then write the words. Four surfaces, four different messages, sent in a deliberate order.

The four Slack surfaces to think about

Every Slack farewell lives on one of these four surfaces, and each one has its own rules.

1. Personal DMs. One-to-one. For the four to eight people who genuinely shaped your time — the close teammate, the manager who backed you, the cross-functional partner who covered for you, the quiet person who taught you the tool.
2. Your team channel. The 8 to 30 people you worked with day to day. A short warm post here is the main event.
3. Cross-functional or project channels. The 3 to 6 channels where you were a regular contributor to another team's work — the design review channel, the incidents channel, the customer feedback channel.
4. Company-wide channels (#general, #announcements, #random). The whole company. Usually skip this. HR or your manager will announce your departure through the appropriate channel; you do not need to double up.

Confusing these surfaces is the single most common mistake. People post to #general to make sure "everyone sees it," then send the same copy-paste to their team channel, then feel weird about not doing individual notes for their closest teammates. The order is backwards.

Send the DMs first — the evening before

The people who mattered most should not learn you are leaving from a team-channel post that also went to 27 other people. Send four to eight personal DMs the evening before your team-channel farewell goes out. Not a mass BCC, not identical copy — actual short DMs, one at a time.

Three-line template that works:

• Line 1: Warn about tomorrow's team-channel post so they hear it from you first.
• Line 2: One specific thing you will remember about working with them. A project name, a moment, a thing they taught you.
• Line 3: A real stay-in-touch line with an actual plan. Not "let's grab coffee." A dated invitation, your personal email, or "I'll drop you a note in October when I'm settled."

Send these between 6 pm and 9 pm the day before your team-channel farewell. Late enough that Slack notifications feel personal, early enough that you are not messaging anyone after 10 pm. If they DM back that same night, reply once and then let it breathe.

For a shorter guide on picking the people who deserve a personal channel instead of a group email, see 7 colleagues to text (not email) before you leave a job.

Post the team-channel farewell the next morning

Wednesday or Thursday morning of your last week works best. Post around 9:30 to 10:30 am — after everyone is settled with coffee, before the meeting block starts. Never post at 4:55 pm on a Friday. People do not have time to react, and the message sits unread until Monday when your account is already off.

Keep the team-channel post to five to eight sentences. This is a job for words that are simple and short, not an essay. Include these five things and skip everything else:

1. The fact that today or tomorrow is your last day.
2. One specific memory or thanks. Not a career retrospective — one thing.
3. What happens to your work in progress and who to route questions to. Two lines maximum.
4. Your personal email address and LinkedIn URL.
5. A short warm sign-off. Not "keep in touch" — something more concrete, or nothing at all.

A working template:

Hey team — quick note. Today is my last day at [Company]. Two years ago I joined this channel not knowing what a [product term] was; you all taught me that and about forty other things I use every week. I am handing off the [project] work to [name], and [name] can answer anything else. Personal email: name@gmail.com. LinkedIn: linkedin.com/in/name. Thank you for the last two years. Really.

Around 130 words. Enough to land, short enough to read on a phone in a meeting.

Cross-functional channels — one line, not the same post

Do not paste the team-channel farewell into six other channels. It reads as spam by the third one. Pick the three to six channels where you actually contributed regularly and post a shorter, channel-specific one-liner in each. Something like: "Signing off from #design-reviews today. Thanks for pulling apart my mocks every Tuesday for a year. Personal email is name@gmail.com if you want to stay in touch."

If a channel had you as a lurker rather than a regular contributor, do not post at all. Leaving the channel quietly is not rude; the announcement adds noise for people you did not really work with.

Leave #general alone

The company-wide channel is a compliance surface, not a personal one. The HR "so-and-so is leaving" announcement usually goes there anyway, and doubling up with a personal farewell reads as attention-seeking to the 400 people who never worked with you. If your CEO or manager explicitly asks you to post to #general — some smaller companies do this — write a two-sentence version, no personal email in a channel that big, and let it sit.

The exception is a truly small company (under 40 people) where #general is functionally your team channel. In that case, post there once with the team-channel template above and skip the separate team-channel post.

The pivot: knowing WHO to DM in the first place

The team-channel post writes itself in ten minutes. The DMs are the hard part — not the words, but the list of names. Memory over-weights the last two months and quietly drops the cross-functional partner from Q1, the person who covered your on-call rotation last summer, the intern you actually mentored. If your DM list has fewer than four names in it, your memory is playing tricks on you, not telling you the truth.

The honest record of who mattered is not in your head. It is in your calendar — every recurring 1:1, every project kickoff, every "quick sync" that turned into a real working relationship.

Three common Slack farewell mistakes

1. The mass @channel or @here on your way out. Do not @mention a whole channel to make sure your farewell gets seen. It pings people in meetings, at dinner, on vacation. A plain post without a mention is respectful; the people who care will see it. If your team lead specifically asks you to @channel, that is different.

2. The victory-lap post naming your next employer. Do not name the new company in the team-channel farewell. It shifts the message from "thank you" to "look at me," and it can create awkwardness with people who applied for the same role you are moving to. Save the name for the LinkedIn update three weeks later. For guidance on that timing see when to update your LinkedIn after starting a new job.

3. Writing a farewell essay in the Slack post. If your farewell is longer than 180 words in a Slack channel, it is too long. Slack is not the medium for a career retrospective. If you have more to say, put it in personal DMs to the specific people, or in the personal notes you send from your personal email in the weeks after. The channel post is a beacon, not a monument.

Edge cases worth naming

Fully remote team. Your Slack farewell IS the farewell. Send a short pre-recorded Loom or voice note along with the team-channel post if you want it to land warmer. Twenty seconds is enough.

Layoff with same-day access cut. You will not get to post anything on Slack. This is fine and, honestly, cleaner. Send the notes from your personal email in the next 48 hours. Batch by relationship strength. Skip anyone whose email you do not already have; do not chase.

Very small company (under 15 people). Skip the separate team-channel post entirely. Do it as personal DMs to everyone, plus a two-sentence post in whatever channel functions as the daily hangout. That is enough.

You share DMs with a competitor's employee. Give them a heads-up in DM the day before, not the morning of. Say only the last day and the personal email — no mention of where you are going.

The 30-minute Slack close-out block

Block 30 minutes on your second-to-last morning specifically for the Slack close-out. Draft the team-channel post first (it is the anchor). Then draft the short cross-functional channel one-liners underneath it in the same note. Then open a fresh note and list the four to eight DM recipients you will hit that evening — pull them from your calendar audit, not from Slack DMs (which over-weight whoever pinged you most recently). If the list has fewer than four names, go read your last twelve months of calendar again; you missed someone.

The tool most people reach for at this exact moment is It Was Great Working With You — upload your work calendar, get back a ranked list of the people you spent real time with over the last year. Three minutes. Names only. Nothing else is stored. It replaces the ten minutes you would otherwise spend second-guessing your DM list.

Then post the DMs at 7 pm, the team-channel farewell at 10 am the next day, and log off cleanly by 5 pm.

What to do after you hit send

Once the team-channel post goes up, resist the urge to babysit the thread. Reply once to the first ten reactions, then batch the rest into one evening reply session before you sign off. If a coworker replies with something surprising or generous, DM them back privately with two sentences and your personal email — that is where the real farewell happens, not in the thread.

Do not stay logged in past your official last day to keep the conversation going. Access will get cut anyway, and the graceful move is to let the goodbye be complete. If you want to keep in touch with someone, you already have their email; use it in three weeks, not tonight.

The whole Slack farewell is 30 minutes of drafting, an evening of DMs, a morning post, and a clean sign-off. The hard part was never the words. It was knowing exactly who to send them to — and the calendar is the only honest place that answer lives. Start there: It Was Great Working With You.