What Happens to Customer Feedback When Slack's Free-Plan History Limit Hits?
Nothing dramatic happens at 90 days. The message is still there, technically, sitting in whatever channel it was posted in. What happens is that Slack stops showing it to you: search won't return it, scrollback won't load it, and the thread just stops existing as far as anyone using the free plan can tell. Slack's own page on free-plan limitations puts it plainly: "you'll be limited to the most recent 90 days of message and file history." Older content is hidden, not gone, and upgrading to a paid plan reveals it again.
The second cutoff is the one that actually destroys data. Starting August 26, 2024, Slack began permanently deleting anything over a year old from free workspaces, upgrade or no upgrade. At that point there's no reveal button. If the feature request your customer filed in a shared Slack channel eighteen months ago was never copied anywhere else, it's gone, and no admin setting brings it back.
The two cutoffs, and why they're different problems
It helps to treat these as two separate failures, because the fix for one doesn't fix the other.
90 days: hidden, still recoverable. Content between 90 days and one year old still exists in Slack's systems. It just isn't visible or searchable on the free plan. Upgrade to Pro, Business+, or Enterprise+, and per Slack's pricing page, you get "unlimited message history," and everything in that 90-day-to-one-year window comes back into view. If your team is on the free plan and worried about a request from four months ago, the fix is an upgrade, not a recovery project.
One year: permanent, not upgrade-recoverable. Once content crosses the one-year mark on a free workspace, it's deleted. Upgrading after the fact does nothing for what's already gone, because there's nothing left to reveal. This is the cutoff that actually matters for anyone asking "what happened to that feedback."
There's a narrower path even on the free plan: a workspace owner can apply to Slack directly to export content, including private channels and DMs, under specific conditions. Slack's export guide lists valid legal process, member consent, or a legal requirement as the qualifying reasons. That's a compliance mechanism, not a feedback-retrieval tool, and it doesn't help with content already deleted at the one-year mark. Business+ and Enterprise+ workspaces get self-serve export access instead, which is a meaningfully different guarantee: you don't need a reason to pull your own data.
“we need SSO before rollout”
“any update on single sign-on?”
“SSO came up twice on this call”
Linear issue, quotes attached
insight report in NotionWhat this looks like when someone goes looking
At Driftwell, a returns-management platform for footwear and apparel brands, the shared customer channel is where support drops anything that sounds like a request, whichever account it comes from. About a dozen of Driftwell's larger accounts sit in that channel, a mix of Slack Connect threads and one general free-tier workspace, and Priya Nakamura is the one who ends up digging through it when someone needs to find something specific.
A new hire on the product team, sizing work for the Q1 roadmap, asks Priya whether a specific account, a footwear brand called Torvale, ever actually asked for a bulk-refund endpoint, or whether that's an assumption built off a support ticket.
Priya is sure they did. "I remember the thread," she tells him, and goes to pull it up. She searches the channel for "bulk" and "refund" and gets nothing from more than three months back.
She can't find it, because Driftwell's internal workspace is on the free plan and the message is somewhere past the 90-day line. She doesn't know if it's fourteen months old or five, so she can't tell whether upgrading would bring it back or whether it's already past the one-year deletion. She ends up writing "customer feedback (unverified, ~Q3 last year)" into the roadmap doc instead of the actual quote, missing the exact wording, a way to check it later, and anything a customer-facing rep could resurface on a follow-up call.
That gap between "someone remembers a request happened" and "here's the exact message and who sent it" is the whole cost. It shows up as a weaker roadmap doc today and, if the message crosses one year old before anyone thinks to look again, as a permanently lost data point.
Why the built-in habits only go so far
A few habits reduce how often this bites, and they're worth doing regardless:
- Pin anything that reads as a real request, using Slack's
has:pinsearch modifier to find it fast while it's still findable. This doesn't extend the clock: a pin just points at the underlying message, and Slack's own free-plan documentation describes the 90-day cutoff as a blanket limit with no stated carve-out for pinned or starred items, so once a message goes dark, the pin pointing at it goes dark too. - Copy the exact quote into a running doc the moment it's identified as a request, rather than trusting it'll still be findable in Slack next quarter.
- Track your plan's clock. If you're on the free plan, know roughly how old your oldest live conversations are, so "should we upgrade before this becomes 90 days old" is a decision someone actually makes instead of a surprise.
These habits work fine for a team with one channel and a handful of requests a month. They stop working once support and product both drop things into Slack without a shared discipline, or once there are enough customer channels that nobody's copying quotes out consistently. At that point the fix isn't a better habit, it's not depending on Slack's retention clock for anything you care about keeping.
Where Modem picks this up
Modem reads the Slack channels you connect it to and writes what it finds into topics tied to the person and company who said it, the moment the message posts. The record lives outside Slack from the start, so Slack's 90-day visibility window and one-year deletion policy stop being a data-loss risk, because the quote, the requester, and the account were already copied out before either cutoff was reached. The Slack integration covers both regular channels and Slack Connect channels shared with customers. We build Modem, so weigh that against the manual habits above, which are genuinely enough if your Slack footprint is small and your team is disciplined about copying quotes out.
For teams whose customer conversations already span Slack, support tickets, and calls, the same durability question applies everywhere at once, which is the case made in how to centralize customer feedback. If some of your channels are Slack Connect specifically, the visibility rules differ slightly from a plain internal channel, and that's covered in managing feedback from Slack Connect channels.
Check your oldest live Slack channel this week
If your team runs on Slack's free plan and treats a shared channel as a feedback record, check how old your earliest still-live conversations actually are. If any customer channel is approaching a year, either upgrade before the deletion date passes, or start copying the requests you can still find into a doc now. A year from now, if that channel is still on the free plan, "I remember the thread" won't be a way to answer the question, because the message itself will be gone.
