A Slack community can follow a familiar arc: a strong launch, a wave of introductions, a few good threads, maybe an event. A few weeks in, the party starts to wind down.
Then replies slow down. The #introductions channel dries up. The community manager posts more, tries to look excited about it, and can't work out why nobody is reacting anymore.
Most revival advice is the same list: post on a schedule, run events, DM inactive members, offer incentives, announce a contest. None of it is wrong, and I've given some of it myself. But on a community with no sharp purpose and no new members coming in, the lift can be short-lived.
This guide works on what sits underneath: what your Slack data says, who the community is really for, what a new member sees in the first 30 seconds, and where new members will come from. Then it puts all of that into a 90-day plan. The usual tactics come back in that plan, once there's something for them to work on.
Why Slack communities go quiet
Slack was built for teams that have a daily reason to open it: their job. That's why it works so well for marketing, engineering and support teams, and why it did away with a lot of internal email.
A B2B community doesn't get that daily reason for free. It has to manufacture one, week after week, and that can be hard to sustain after the excitement of launch.
Chat also has a short half-life. Even with ten active members, a good answer scrolls out of view within days. Skip a week and last week's best thread is buried. Those threads aren't public pages that Google or public AI search can send people to. Unless someone publishes an answer outside Slack, people searching the web won't find it, and community managers can end up answering the same question again.
New members feel this before they can name it. They open Slack and hit a wall of chat between strangers, with no obvious place to start. A few introduce themselves and dig through old threads. Others leave without joining in.
Free workspaces have a harder limit. Slack shows only the most recent 90 days of message and file history on the free plan, and since August 26, 2024 it has been deleting data more than a year old from free workspaces (Slack Help Center). Whatever good content your community produced is on a clock.
I ran a B2B SaaS community on Slack for 14 months and wrote up what went wrong in 650 Members, Zero Growth. This guide assumes you're staying on Slack for now and want it working again. The platform question comes at the end.
Why the usual revival tactics don't work on their own
Post more, tag inactive members, run an AMA, send a reactivation email, get the founder to show up and say something. It's the advice you'll find everywhere, but on its own it may not address what made people leave.
The thinking behind it is that if you ask nicely enough, the people who went quiet will start showing up again. Sometimes they do, but the lift can fade if nothing else has changed.
Whether a revival lasts often comes down to a handful of questions the community has not answered clearly. Answer those first and the same tactics have a better chance of working. Before you commit to a relaunch, check your community readiness to find gaps in member purpose, ownership and the time you can actually put in.
Start with what Slack already tells you
Before you talk to anyone, open your workspace analytics: click Admin in the sidebar, then Workspace analytics. What you see depends on your plan. The free plan gives you a high-level Overview tab. Pro and Business+ add Channels and Members tabs with more detail (Slack Help Center).
Look for two things on the Overview tab, where available on your plan. Treat them as clues for the interviews, rather than proof of what went wrong.
The first is weekly active people against weekly people posting. Slack distinguishes people who read or send messages from people who post, and defines the reporting windows for each metric (Slack Help Center). If plenty of members still read but few post, they may be getting what they need by reading. Or something may be stopping them from joining in. If readership itself has dropped, ask what changed: the content, their needs, their available time, or how often they notice the community.
The second is where messages are sent. Slack splits it across public channels, private channels and DMs. When most messages go to DMs, useful conversations may be happening out of view. That is not always a problem, especially when the subject is private. In the Slack community I ran, that looked like members messaging senior people directly for job referrals, and two or three complaints from those senior members every month.
On Pro or Business+, go one level deeper:
- The Channels tab shows each public channel's last active date, members who posted, members who viewed, and the change in members who posted compared with the previous 30 days. Channels with viewers but no posters may need a better prompt, or they may be doing their job as a resource or announcement channel. Channels with neither are candidates for review before archiving.
- The Members tab shows days active, last active and messages posted for each member. This is your list for the interviews in the next step. Slack only shows a member's last active date if they were active in the past 90 days.
Before you plan anything, check your plan against the steps below. On the free plan you can't create workflows, canvases or user groups, and huddles are one-to-one only (Slack Help Center). Decide whether the relaunch needs a paid plan before you publish seed content that drops out of view after 90 days.
Talk to old members
Old members can tell you what the dashboard can't. Reach out to 10 to 20 of them directly. On a paid plan, the Members tab shows who used to post the most. A casual Zoom or Google Meet call gives you room to ask follow-up questions that a written survey can miss.
Find out:
- How they discovered the community
- What they hoped to get from it
- At what point it stopped pulling them back
- Whether they're active in a similar or competing community
People usually sugarcoat feedback. Some will be blunt. Note everything down.
Tell them what you're planning, but don't build the relaunch around their return. Some will come back if you fix what made them leave. Others may have moved on. Use what you learn to decide how much the relaunch should focus on returning members and how much on new ones.
Who is this community for?
This is the most important question to answer before anything else. The usual answer, "We are building a community of {developers / customers / marketers / data professionals}," feels right, but it's a trap.
Narrow it down.
Better answers:
- "First-time customer marketers building advocacy programs at Series B SaaS companies"
- "First-time founders struggling with SEO"
- "Sales professionals at Series A SaaS companies in cybersecurity"
"A place to network" may be too vague to give someone a reason to join. "Find practical advice for getting your first 5 customers" is useful and easy to relate to. It sets the expectation and makes the community manager's job easier.
Before touching anything else, answer:
- Who is this really for?
- What problem are they actively trying to solve?
- What would make them come back weekly?
- What would make them invite a peer?
- What would they search for before they found this community?
Fix the first 30 seconds
In the first 30 seconds after joining, a new member should understand what the community can do for them, through its content or its people.
For welcome sequences and first-week rituals, see the Community Onboarding Guide. In Slack specifically, three things matter.
Cut the channel list
A quiet community with 20 channels feels emptier than a quiet community with 5. Cut it down to something simple:
- Announcements
- Introductions
- Ask Us Anything
- Resources
- {topic-specific channel 1}
- {topic-specific channel 2}
Archive channels that no longer serve a purpose instead of deleting them. Keep useful resource and announcement channels even if people rarely post there. An archived channel is closed to new messages but keeps its history, subject to your plan and retention settings. Archiving does not bypass the free plan's history limits. Deleting a channel removes its history permanently (Slack Help Center).
Don't rush to add channels back. Add one only when members keep asking for it.
Decide where new members land
Set default channels so new full members join the same small set. Default channels work on every plan. There are three catches: only public channels can be defaults, existing members aren't added when you change the list, and full members are added to the general channel automatically. Guests are not automatically added to default channels (Slack Help Center).
Since full members land in the general channel, make it worth landing in. It may be named #general, #all-companyname, or something you have renamed it to. Pin a short post that says who the community is for, what to do first, and where to ask a question.
Welcome people yourself
On a paid plan, a Workflow Builder workflow can post a welcome message and prompt a first action. Workflow Builder isn't available on the free plan, though apps can offer other ways to automate a welcome. During a relaunch, a personal welcome gives you a chance to hear what brought someone in and help them take that first step.
Build a new-member acquisition loop
This is a part revival plans can overlook, especially when the community is meant to grow.
Check who owns new-member growth. Is it the community manager's job, or marketing's? Make that clear before the relaunch.
For a community that needs to grow, a steady flow of relevant new members helps. They bring fresh questions, ideas and perspective, and they give old members a reason to show up and answer. A closed cohort or established customer group may do well with the members it already has. Start with the community's purpose.
Slack conversations do not provide a public search presence on their own. Community managers and marketing teams end up relying on:
- Emails to the existing customer base
- Auto sign-up into the community (avoid this one)
- Monthly events
- Social media posts
- Ads, where the budget and cost per relevant member make sense
Where Slack caps the loop
There's one channel almost no Slack community gets to use: someone searching for the exact question your community has already answered, and finding the answer on Google or in ChatGPT. Those people arrive with some useful context. They've already read something useful, they know what the community is about, and they arrive with a reason to stay.
Slack keeps that from happening. Everything sits behind a sign-in, so an answer only helps people who are already inside. A public answer keeps working for new people months or years later, as long as someone keeps it accurate and useful.
You can work around this without leaving Slack. When a question keeps coming back, turn the best answer into a public guide or FAQ on your own site, and link to it from the channel. Get permission before republishing members' contributions, and remove confidential or identifying details that should not be public. That's the work in days 61 to 90 below.
A hybrid approach can work well: keep reusable answers public and sensitive conversations private. There is no fixed percentage that suits every community. Slack plus a public knowledge base is one option; a platform with public and private spaces is another. Closed vs. Open Community: Let's Settle the Debate covers the reasoning.
The 30/60/90 day plan
This plan is for a community that already exists and has gone quiet. If you're launching from scratch, the B2B SaaS community launch plan covers the same 90 days for a first launch.
Days 1 to 30: Diagnose and rebuild the foundation
Pull your Overview numbers and, where available, write down weekly active people, weekly people posting, and the share of messages going to DMs. On a paid plan, use the Channels tab to review activity and readership before deciding which channels to archive. Interview 10 to 20 old members. Rewrite who the community is for and why it exists, and pin it in the general channel. Set your default channels. Decide whether you need a paid plan for workflows, message history or analytics. Draft 10 to 20 pieces of seed content around real questions your ideal member has.
Days 31 to 60: Relaunch with a sharper experience
Personally invite a small group of high-fit members. Invite back the old members who told you they're still interested. Publish the seed content. Run one focused event or async discussion. This is where the usual tactics start earning their keep, because there's now a reason to show up. Welcome every new member and give each of them one clear first action.
Days 61 to 90: Build the growth loop
Turn the most common recurring questions into public guides or discussions outside Slack, and link to them from the channels where they came up. Link related Slack conversations together. Invite a few subject-matter experts to answer specific high-intent questions. Share the public pages through your existing channels too. Track which bring in visitors and how many of those visitors join. Search traffic may take longer than 90 days to develop, so judge this phase by useful answers, returning members and early referrals as well.
What to measure
Message volume alone won't tell you whether this is working. Across all three phases, watch:
- Weekly people posting as a share of weekly active people (Overview tab, where available)
- The share of messages sent in public channels rather than DMs (Overview tab, where available)
- Change in members who posted, channel by channel (Channels tab, paid plans)
- New members joining each week
- Questions answered: the percentage of new questions that receive a useful answer within a window you choose, such as seven days. Count this by hand for the channels that matter.
- Time to first reply: the median time from a question to its first reply from another person. Slack's dashboard does not report this, so track it separately.
- Returning members and whether they found the answers useful
- Search visitors to the public pages you published, and how many of them join
A quiet expert community can be worth more than a noisy general one. Message count alone won't show you that.
Stay on Slack, or move
Slack still makes sense when the community is small, private, and everyone is already there for work. Paid masterminds, cohort groups and short-lived event communities can stay exactly where they are.
Consider moving when public discovery, reusable customer education and finding old answers are central to the community, and maintaining Slack alongside a public knowledge base creates too much work. Those goals do not automatically require a move, but they give you a useful way to compare the options. 650 Members, Zero Growth walks through that decision, and How to Migrate Your Community Without Losing Members covers the move itself.
That second case is the one I built Jatra for: a community made to be found on your own domain, not a workspace only the people already inside can see.
If a Slack community has gone quiet, find out what stalled it before choosing the fix. A clearer purpose, a useful answer or a better welcome may be where the revival starts.
Related question from the Jatra community
