DEV Community

Wbcom Designs 💡
Wbcom Designs 💡

Posted on AI-assisted

A company closes its customer forum: good riddance, or a library burning down?

When one of the largest tech companies announced it was shutting its long-running customer support community, putting it into read-only mode first and then taking it down, we expected grief. What we found across the communities we follow was a split almost down the middle.

It is worth looking at both reactions closely, because they say a lot about what a company forum is actually for, and about whether any business, large or small, should run one.

"Good riddance"

The loudest group had little sympathy. Their points, paraphrased:

  • Search landed them there and the answer was never there. Plenty of people said they had followed a search result into the forum many times and could not remember a single visit that solved their problem.
  • Answers optimised for reply counts. Long-time helpers were accused of posting non-answers to climb the leaderboard, and of waving away anything critical of the company.
  • "The company doesn't read this." A common reply in threads was some version of "staff don't read these forums, file feedback instead", which made the whole place feel like a waiting room with no door.
  • Threads that never close. People described "this is broken" threads that stayed open for years with the problem still unsolved, visible to every customer who searched for it.
  • Free support as a business model. One sharp take was that the forum was always a way to avoid paying for support, staffed by enthusiasts doing the company's job.
  • Bad answers now travel further. A newer worry: a large pile of incomplete or wrong answers is exactly what gets pulled into AI answers, so shutting it might even be a public good.

"A library burning down"

The other group saw it very differently:

  • The volunteers. Some helpers had tens of thousands of answers on their profiles. Going read-only with little warning and closing shortly after felt cold to people who treated helping as a hobby and a point of pride.
  • The long tail. Even if most threads were weak, the one thread that fixes an odd driver problem or an obscure settings conflict is gold, and those are the ones nobody else will ever write down again.
  • It cost almost nothing. Relative to the company's size, running the forum was pennies. Closing it looks like a choice about image, not money.
  • Where do people go now? Several asked for alternatives that actually work, and were wary of moving the questions to yet another large platform they do not control.

The middle we keep coming back to

A quieter point in the discussion is the one we find most useful: a community forum is only as good as the people answering in it. Years ago, the people who found and used a forum were already fairly technical, so answers were good. As the audience broadened, the average answer got worse, and the company never stepped in to change that.

That suggests the forum itself was not the problem. The staffing was. A forum where staff answer the first reply, mark accepted answers, close fixed issues and feed real bugs into a tracker is a very different place from one left to run itself. The same pattern shows up with smaller site builders that have discontinued their built-in forum features: the software was rarely the issue; nobody owned the outcome.

We run community and support spaces for our own products, so we have a stake here, and we hold this loosely. But we lean towards: keep peer support public, staff the first reply, prune what is wrong, and if you ever close it, archive it in a way people and search engines can still read.

Questions we would genuinely like answered

On value

  • When you search for a fix, do vendor forums still help you, or do you skip them on sight?
  • Is a public forum full of unanswered threads worse for a company than having no forum at all?

On running one

  • If you run a support community for your product, who answers first: staff, power users, or whoever turns up? What changed when that changed?
  • How do you handle the threads that never resolve: close them, merge them, or leave them as a public record?

On ending one

  • If you had to close a forum, what would you owe the volunteers who built it?
  • Read-only archive, export for members, or a clean shutdown: which would you choose, and why?

Your turn

  1. Has a vendor forum ever saved you hours? What made that thread good when so many are not?
  2. If you run support for a product, would you open a public community now, or keep everything in tickets and docs?
  3. What would a company need to do for you to keep answering other customers' questions for free?
  4. When a company closes a forum, what is the one thing it must do before the lights go out?

Top comments (2)

Collapse
 
jes_p_d4f61f7aa2ec405a418 profile image
Dev_PJS •

Library burning, with one honest caveat. A long-running forum is the only support asset that appreciates: every answered question becomes a searchable record that answers the next hundred people for free. Closing it doesn't just remove a channel, it deletes the accumulated memory of what customers actually asked — which is usually more truthful than any FAQ the company would write. The caveat is in your 'good riddance' quotes: a forum where search lands you and the answer is never there has already stopped being a library and become a maze. The asset isn't the forum software. It's the answered, findable record. Keep that alive and the format hardly matters.

Collapse
 
kate_astrid profile image
kate astrid •

It's a library burning down, and the company could have saved the best shelves in a weekend. 📚

  1. Sort the solved threads by views.
  2. Turn the top fifty into docs pages, with credit to the volunteers who answered them.
  3. Redirect every old thread URL to its new page, so search links keep working.

That way, we keep the long tail alive, and the helpers see their work in the official docs, which makes a lovely thank-you.