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.
Source-backed 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-reported evidence
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.
Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.
Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.
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.
How to do it
- Choose one target segment and define the exact next action this tactic should prompt.
- Adapt the tactic to Community and Support, using evidence from Discourse Meta: Easily create Support categories using the discourse-solved plugin as context—not as a promised result.
- Record a baseline for: Users who resolve the issue and complete the next useful action. Set a guardrail that would make you pause the test.
- Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
- Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Compare a stack for your situation
Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.
Explore the context
Did you launch this experiment?
Report a launch to help us understand which growth ideas founders put into practice.
Apply this with an operator
Build creator and community systems around real incentives, trust, and repeat participation.