# The support forum should stop acting like a chat room > Why structured intake, solved-state search, public ownership, docs indexes, and visible experts turn a community archive into a better growth surface. - Canonical HTML: https://growth.iangoh.com/blog/the-support-forum-should-stop-acting-like-a-chat-room/ - Published: 2026-05-29 - Updated: 2026-05-29T23:20:00Z - Categories: community-led growth, support-led growth, documentation - Niches: SaaS, AI products, developer tools, open-source software, customer support software ## On this page - The thread should start with enough shape to be useful - A forum answer becomes more valuable when it can be recognized as finished - Public threads need visible ownership - The best answers should graduate out of thread gravity - Not every question needs the whole crowd ## Start with these related tactics - [Discourse topic template before support post submit](/growth-ideas/discourse-topic-template-before-support-post-submit/): Prefill support categories with the fields you actually need so bug reports and setup questions arrive with enough context to answer on the first pass. - [Discourse solved schema and search priority](/growth-ideas/discourse-solved-schema-and-search-priority/): Turn solved support threads into a cleaner answer surface by marking accepted solutions, adding solved filters, and letting solved topics rank better in on-site search. - [Discourse assignment statuses for public support ownership](/growth-ideas/discourse-assignment-statuses-for-public-support-ownership/): Assign support topics to a person or group with visible statuses so customers and teammates can see who owns the thread and what stage it is in. A lot of support forums still behave like a chat log with good branding. Someone drops a vague problem into the queue. A staff member asks for the missing details. A few replies later the answer exists, but it is buried in a thread that looks half-finished to the next person who lands there from search. That is usually a product mistake, not a community inevitability. ## The thread should start with enough shape to be useful [Discourse topic template before support post submit](/growth-ideas/discourse-topic-template-before-support-post-submit/) is the plainest fix in this batch. If the support category keeps asking for version, workspace, browser, repro steps, or screenshots, those fields should be waiting in the composer before the post goes live. I would keep that next to [subject-field article suggestions before ticket submit](/growth-ideas/subject-field-article-suggestions-before-ticket-submit/). One tactic shapes the question. The other tries to stop the ticket when the answer already exists. Both are cheaper than letting every thread begin with cleanup. ## A forum answer becomes more valuable when it can be recognized as finished [Discourse solved schema and search priority](/growth-ideas/discourse-solved-schema-and-search-priority/) matters for a simple reason. Most readers are not there to watch the conversation. They are there to steal the answer and leave. Solved markers, solved filters, and better on-site search ranking make that easier. The schema setting is especially interesting because it treats the solved thread as a real answer object, not just a conversation that happened to end well. That belongs beside [ticket-to-search ratio as self-serve failure signal](/growth-ideas/ticket-to-search-ratio-as-self-serve-failure-signal/) and [top no-result queries become the docs repair queue](/growth-ideas/top-no-result-queries-become-the-docs-repair-queue/). The archive should not only exist. It should get easier to retrieve. ## Public threads need visible ownership [Discourse assignment statuses for public support ownership](/growth-ideas/discourse-assignment-statuses-for-public-support-ownership/) fixes the dead middle of support work. The question is real. The answer is not ready yet. Engineering might need to inspect it. Support might be waiting on the customer. Without visible ownership, the thread just looks abandoned. A visible assignee and status does not solve the product issue by itself. It does something almost as useful first. It tells the reader the company still knows this thread exists. ## The best answers should graduate out of thread gravity [Discourse doc category index sidebar for evergreen answers](/growth-ideas/discourse-doc-category-index-sidebar-for-evergreen-answers/) is the move that keeps a community from having to relearn itself every month. When the same answer keeps proving useful, it should not remain trapped in a chronologically sorted thread list forever. I like this next to [curated strategic resources inside help-center articles](/growth-ideas/curated-strategic-resources-inside-help-center-articles/) and [help-center to blog resource map with UTM dashboard](/growth-ideas/help-center-to-blog-resource-map-with-utm-dashboard/). The common idea is that durable answers deserve a route, a shelf, and a feedback loop. The built-in reports for missing or extraneous docs entries are what make this operational instead of aspirational. Somebody can actually maintain it. ## Not every question needs the whole crowd [Discourse category experts for ask-an-expert routing](/growth-ideas/discourse-category-experts-for-ask-an-expert-routing/) is useful when the community is large enough that credibility has started to matter. Some questions need a maintainer, a solutions architect, or the person who has debugged this exact edge case ten times already. Once the forum can signal who has earned trust in a narrow category, the archive gets better too. The next reader learns not only the answer, but whose answer usually holds up. This cluster is strongest for SaaS, AI products, developer tools, open-source software, and support-heavy platforms where the community archive doubles as onboarding and search inventory. The standard is plain. If a forum keeps producing answers, it should stop presenting them like disposable chat. If you want help turning support threads, docs, and community surfaces into a cleaner acquisition and retention system, the advisory CTA is here: [work with Ian Goh](https://iangoh.com/advisory). ## Related GrowthDex tactics - [Discourse topic template before support post submit](/growth-ideas/discourse-topic-template-before-support-post-submit/) - Community, Support, Documentation - [Discourse solved schema and search priority](/growth-ideas/discourse-solved-schema-and-search-priority/) - Community, Support, SEO - [Discourse assignment statuses for public support ownership](/growth-ideas/discourse-assignment-statuses-for-public-support-ownership/) - Community, Support, Customer Success - [Discourse doc category index sidebar for evergreen answers](/growth-ideas/discourse-doc-category-index-sidebar-for-evergreen-answers/) - Community, Documentation, SEO - [Discourse category experts for ask-an-expert routing](/growth-ideas/discourse-category-experts-for-ask-an-expert-routing/) - Community, Support, Education ## Essay chronology - [Newer essay: The G2 Profile should help the buyer check the claim](/blog/the-g2-profile-should-help-the-buyer-check-the-claim/) - brand trust, SEO, conversion - [Older essay: The help center should stay private until it can carry the work](/blog/the-help-center-should-stay-private-until-it-can-carry-the-work/) - support-led growth, documentation, brand trust ## Keep reading - [The forum should route the newcomer before they post](/blog/the-forum-should-route-the-newcomer-before-they-post/) - community-led growth, support-led growth, product feedback - [The docs page should show signs of life before support does](/blog/the-docs-page-should-show-signs-of-life-before-support-does/) - documentation, proof surfaces, support-led growth - [The support report should write the next help page](/blog/the-support-report-should-write-the-next-help-page/) - support-led growth, SEO, documentation ## Continue through the blog - [SaaS](/blog/#path-saas) - 3 essays in this path - [AI products](/blog/#path-ai-products) - 3 essays in this path - [developer tools](/blog/#path-developer-tools) - 3 essays in this path ## Sources - [Discourse Meta: Using topic templates for categories](https://meta.discourse.org/t/using-topic-templates-for-categories/38295?tl=en) · [GrowthDex source hub](/sources/discourse-meta-using-topic-templates-for-categories-meta-discourse-org/) - [Discourse Meta: Discourse Solved](https://meta.discourse.org/t/discourse-solved/30155?tl=en) · [GrowthDex source hub](/sources/discourse-meta-discourse-solved-meta-discourse-org/) - [Discourse Meta: Discourse Assign](https://meta.discourse.org/t/discourse-assign/58044) · [GrowthDex source hub](/sources/discourse-meta-discourse-assign-meta-discourse-org/) - [Discourse Meta: Discourse Doc Categories](https://meta.discourse.org/t/discourse-doc-categories/322376?tl=en) · [GrowthDex source hub](/sources/discourse-meta-discourse-doc-categories-meta-discourse-org/) - [Discourse Plugin: Category Experts](https://discourse.org/plugins/category-experts) · [GrowthDex source hub](/sources/discourse-plugin-category-experts-discourse-org/) ## Editing notes - Kept the essay on one blunt claim: a support forum should behave like an answer system, not an endless conversation log. - Used ordinary scenes like missing repro steps, buried solved replies, stale ownership, and repeated questions instead of padded community language. - Let the product mechanics carry the proof and avoided generic claims about engagement, empowerment, or ecosystem effects. - Ended with a concrete operating standard and the advisory CTA instead of a vague summary. ## Advisory If you want help turning this into a growth system, Ian Goh offers advisory at https://iangoh.com/advisory.