← Back to GrowthDex

Growth idea action plan

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.

rare tactic medium budget Community, Support, Documentation Stages: support architecture, answer retrieval, community ops, queue hygiene

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.

Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

Action plan

  1. Define one narrow startup segment where discourse support category type with solved defaults can create a measurable lift.
  2. Turn the tactic into one offer, page, campaign, or workflow for the Community and Support channel.
  3. Use the evidence from meta.discourse.org to set the first version of the message, format, and audience.
  4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
  5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

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: Discourse Meta: Easily create Support categories using the discourse-solved plugin (meta.discourse.org)

GrowthDex source hub: Discourse Meta: Easily create Support categories using the discourse-solved plugin

Last checked: 2026-05-30

Markdown mirror

Adjacent tactics in the same lane

If this page is close to your problem, these tactic pages usually belong in the same working set.

Related GrowthDex essays

Read GrowthDex essays

The Blog turns real growth tactics into plain-English case studies by niche, channel, and buying situation.

Browse the GrowthDex Blog

Why this is worth your time

GrowthDex starts with tactics that founders, marketers, and product teams have actually tried. Each essay turns the evidence into a practical move you can test without pretending one case study is a guarantee.

Ian Goh has helped grow consumer platforms across Southeast Asia, India, and MENA. His work includes scaling Tiki to 100M+ users, doubling BIGO's MENA revenue in 7 months, and increasing OYO's direct booking share across 6 Southeast Asian markets.

Want help turning this into a growth system?

If you want someone to pressure-test this against your real market, Ian works with founders on growth, market entry, and operator-led distribution.

Work with Ian on growth advisory