How to Say Goodbye on Slack Before You Leave: 5 Templates for Your Last Day

Here's the short answer. A good goodbye Slack message names your last day, thanks the team in one specific line, drops your personal contact, and stops there. Three or four sentences. Post it mid-morning of your last day (not 4:45 pm), in the main team channel, from your desktop. Send personal DMs to a smaller list before the channel post, never after.

Why the Slack goodbye is a different message from the email

Most guides treat the Slack farewell and the email farewell as the same thing. They are not. The email lands in inboxes people check twice a day, so it can be a little longer and a little more formal. Slack sits inside the flow of the workday, next to jokes and thread-replies and someone asking about the printer. Long paragraphs die there. What works is short, warm, and specific.

Slack also has a distinct problem the email does not: the people you actually worked most closely with will see your channel post as a stranger might. A one-size message to a 60-person channel is not a substitute for the two or three real conversations that should have happened earlier in the week.

Which is why the five templates below are for the public channel post. The people who really mattered get a DM first, or better, a real goodbye.

5 Slack goodbye message templates

1. The clean sign-off (default for most teams)

Use this when you had a warm, standard-issue relationship with the team and want something short and unfussy. Three sentences.

Today is my last day at [Company]. Thanks for the last [X years/months] — I've genuinely enjoyed working with all of you. If you'd like to stay in touch, I'm at [personal.email@gmail.com] and on LinkedIn at [linkedin.com/in/yourname].

2. The warm-but-not-sentimental version (for teams you'll actually miss)

Use this when you liked the team and want to name one real thing without it turning into a speech.

Signing off Slack for the last time today. Three years, one very good product launch, and about a hundred #random threads I will genuinely miss. Thanks, all. Reach me at [personal.email@gmail.com] or [linkedin.com/in/yourname] if you want to keep in touch.

3. The informal version (for smaller startup teams and casual cultures)

Use this when the team's chat has always been informal and a stiff message would read as odd. Keep the tone matching what the channel already sounds like.

Last day, team. It's been a real pleasure — thank you for everything. Keeping the memes in a folder somewhere. [personal.email@gmail.com] · [linkedin.com/in/yourname] if you want to stay in touch.

4. The manager-to-team version (if you're the one leading)

Use this when you led the team and are announcing yourself. Slightly more content because your report has expectations of you here. Still short. Say who is picking things up so nobody has to ask.

Today is my last day. It has been the honor of my career to lead this team, and I mean that. [Name] will be your acting manager from Monday and knows about your open projects — please loop them in on anything you would have brought to me. Personal contact: [personal.email@gmail.com] · [linkedin.com/in/yourname]. Take good care of each other.

5. The layoff or short-notice version

Use this when the exit was not your choice, or the notice was compressed to hours instead of weeks. Warmth, not bitterness. Nothing about the company, nothing about your next step (there may not be one yet), and no apology for the shape of the exit.

Team — my role was affected in yesterday's changes, so today is my last day. It's been a real pleasure working with you and I mean that. Please keep in touch at [personal.email@gmail.com] and [linkedin.com/in/yourname]. Wishing you all the best.

The pivot — who should get a DM first (not the channel post)

The channel post is the easy part. The harder question is the one most people skip: which handful of people should get a real goodbye before the channel goes public? A DM after your channel post has already dropped reads as an afterthought — because it is one. The order matters.

The trap is memory. Ask most people on their last morning to list the coworkers they most want to keep, and they will name the people they saw in the past three or four weeks. The senior PM they collaborated with tightly for two months last summer, the cross-functional partner from the launch a year ago, the quiet designer who fixed their embarrassing typo three times without saying anything — memory drops those people first. Your work calendar does not.

This is what It Was Great Working With You is for. Upload your calendar export and it surfaces the ten or fifteen coworkers you actually spent the most real time with over the last twelve months, ranked. You send DMs to those people first, then post the channel goodbye an hour later. Takes about three minutes.

When to post the Slack goodbye (and when not to)

The 4:45 pm Friday goodbye is a mistake almost everyone makes. Half the team is already offline for the weekend, the other half is winding down, and the replies that do come in will trickle into your inbox on Monday when you have no access to reply. You get a two-day silence right when the emotional weight of the last day lands hardest.

The window that works: 10:30 to 11:30 in the morning of your last day. Late enough that everyone is at their desk and past their first Slack scroll, early enough that people have time to react before lunch. If your last day is not a Friday (see our take on what day of the week your last day should be), even better — Thursdays and Wednesdays give the goodbye more breathing room.

One exception: if your team is fully distributed across time zones and the mid-morning-in-your-time-zone window is 3 am in Sydney, post at a time when the largest overlap of your team is online. Otherwise the message drops into silence and the replies fragment across two days.

What to include, and what to leave out

Every version above shares five things: your last day, one line of thanks, one specific detail (a project, an inside joke, a length of time), your personal email, and your LinkedIn. That's the whole checklist.

What every version leaves out:

• The name of your next employer. Save it for LinkedIn a few weeks in. In the Slack post it reads as a humblebrag and it distracts from the goodbye.
• A career retrospective. "When I joined in 2021, I was a junior engineer who didn't know what a code review was..." No. Nobody reads past line four. Save it for a private note to the two people who watched you grow.
• "I'll keep in touch." Empty. If you actually want to keep in touch with someone specific, message them that in a DM with a real next step.
• An apology. Neither "sorry to be leaving" nor "sorry this is short" needs to be in your message. Both invite a "you don't need to be sorry" reply that adds nothing.
• The reason you're leaving. Not in the Slack post. Even a warm reason ("new adventure in a different city") pulls the reader's attention away from the actual message, which is the goodbye and the personal contact.

Common Slack goodbye mistakes to skip

These are the ones we see most often, and they map neatly onto the broader farewell email mistakes we've written about before:

1. Posting in the wrong channel. Post in your immediate team's channel and, optionally, in one wider #department channel. Do not post in #general at a 200-person company — it comes across as broadcast and reads flat.
2. Multiple crossposts. One team channel, one department channel, done. If you post in six channels it feels performative.
3. The DM blast after. If your DMs go out after the channel post, the recipient sees the channel message first and the DM feels like a batch send. Reverse the order — build your DM shortlist the night before (running your calendar through It Was Great Working With You takes a few minutes), then send the DMs in the morning, then post the channel goodbye.
4. Turning it into a farewell speech. If someone hands you the floor at your leaving drinks, that's a two-minute speech, not a Slack thread. Different medium, different message.
5. Editing the message after replies come in. Slack shows an "edited" tag on your original message forever. Read it three times before you send, then leave it alone.

Edge cases (remote-only teams, layoffs, huge companies)

Fully remote teams: the Slack post is doing more work than it would in a hybrid office because it's the closest thing to standing up and waving. Consider pairing it with two or three short Loom videos to the people who mattered most, sent as DMs the day before your last day.

After a layoff: some companies revoke Slack access within an hour of the notification, so you may not have the option to post at all. If you do, template 5 is the version. If access is already cut, send from your personal email — a short group email to the people you'd have DM'd, and one to your closest teammate, forwarding your personal contact.

Big-company #general channels: resist. In a company of 500+, #general is not the place. Your team channel is. If your VP wants an announcement in a bigger channel, they can post it — that carries a different weight than you posting it yourself.

Small startups: the whole company might be in one channel, in which case that channel is the department channel. Template 3 works well here.

A last thought before you hit send

The Slack goodbye is the message everyone will see. The DMs are the messages a few people will remember. Get the DM list right — the ten or fifteen coworkers who actually shaped your last twelve months, not just the ones you saw last week — and the channel post can be short, because it does not have to carry the weight of a personal goodbye you never sent.

If you're short on time and only have a few minutes tonight, use It Was Great Working With You to surface that shortlist from your calendar, DM those people first thing tomorrow, then drop the channel post at 10:30. That's the whole play.