Discourse support category type with solved defaults
Spin up a dedicated support category type so answer workflows, solved states, and support-specific defaults exist before the queue gets noisy.
Why this can grow a startup
Support threads decay when the category is really just general discussion with different branding. Discourse's support category type fixes that at setup time. It gives the team a question-and-answer lane with the solved plugin defaults exposed in one place, which means answer marking, filters, and support behavior are not bolted on later after bad thread habits already spread. That lowers cleanup work and makes the archive more useful to both searchers and moderators.
Company example
Discourse announced in March 2026 that admins can create a Support category type that automatically configures the fields and settings needed for support and question-and-answer workflows with the Discourse Solved plugin.
Source and metric
Source: Discourse Meta: Easily create Support categories using the discourse-solved plugin
Discourse says hosted Support categories using Solved are not available on Free or Starter tiers and are configured through a dedicated category type setup flow.
Source discovered: May 30, 2026
When to use it
Use this when Community, Support, Documentation is relevant to support architecture, answer retrieval, community ops and you can run a bounded test with a medium budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
Founder checklist
- Read Discourse Meta: Easily create Support categories using the discourse-solved plugin and identify what is directly supported.
- Choose one channel context: Community, Support, Documentation.
- Define the test around Discourse says hosted Support categories using Solved are not available on Free or Starter tiers and are configured through a dedicated category type setup flow..
- Set an owner, evidence window, and stop condition before launch.
Explore the context
Apply this with an operator
Build creator and community systems around real incentives, trust, and repeat participation.