# The support queue should know what kind of thread it is > Why solved category defaults, solved tags, private-message resolutions, cohort-based approvals, and staged community rollouts make support archives easier to trust. - Canonical HTML: https://growth.iangoh.com/blog/the-support-queue-should-know-what-kind-of-thread-it-is/ - Published: 2026-05-30 - Updated: 2026-05-30T08:40:00Z - Categories: support-led growth, community-led growth, brand trust - Niches: SaaS, AI products, developer tools, B2B software, open-source software ## On this page - Start by giving support its own operating lane - Some categories need only a few questions, not a full support conversion - Private escalations still need a visible ending - Approval should slow the risky thread, not the whole forum - Roll out support behavior the same way you would roll out product behavior ## Start with these related tactics - [Discourse support category type with solved defaults](/growth-ideas/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. - [Discourse solved tags on mixed discussion categories](/growth-ideas/discourse-solved-tags-on-mixed-discussion-categories/): Use a solved tag such as `question` so only the threads that need an accepted answer behave like support topics inside an otherwise mixed category. - [Discourse solved in group messages for private escalations](/growth-ideas/discourse-solved-in-group-messages-for-private-escalations/): Enable solved states in selected group messages so private escalation threads can still finish with an explicit answer instead of fading into DM ambiguity. A support forum becomes expensive the moment every thread starts looking the same. One post is a real question that needs a durable answer. Another is a discussion with no final state. Another starts in public, then has to move private because an account detail or billing screenshot is involved. Another should not go live until a moderator sees it. If the system treats all of those as one generic thread type, the queue turns into cleanup work. The better move is to make the thread reveal what kind of job it is doing. ## Start by giving support its own operating lane [Discourse support category type with solved defaults](/growth-ideas/discourse-support-category-type-with-solved-defaults/) is the plainest version of that idea. Instead of asking a general-purpose category to behave like a help desk, the team starts with a support lane where answer-state defaults already exist. That fits naturally beside [Discourse solved schema and search priority](/growth-ideas/discourse-solved-schema-and-search-priority/). One gives the support queue the right operating shape. The other helps the finished answer travel better once the thread is done. ## Some categories need only a few questions, not a full support conversion [Discourse solved tags on mixed discussion categories](/growth-ideas/discourse-solved-tags-on-mixed-discussion-categories/) is useful because many communities do not want to split every conversation into separate categories. A tag like question lets one thread behave like a support topic without forcing the whole category into support mode. That sounds small, but it keeps taxonomy honest. A category can stay broad while the threads that actually need a finish line still get one. ## Private escalations still need a visible ending [Discourse solved in group messages for private escalations](/growth-ideas/discourse-solved-in-group-messages-for-private-escalations/) fixes the support handoff that usually breaks the archive. A public thread often goes private for legitimate reasons, but the moment it becomes a loose group message the answer can disappear into DM fog. I would pair that with [Discourse assignment statuses for public support ownership](/growth-ideas/discourse-assignment-statuses-for-public-support-ownership/). One keeps the public queue visibly owned. The other keeps the private escalation visibly finished. ## Approval should slow the risky thread, not the whole forum [Discourse category approval rules by trust group](/growth-ideas/discourse-category-approval-rules-by-trust-group/) matters because moderation is usually ruined by blunt settings. If every reply needs review, the queue becomes a tax. If nothing needs review, the archive fills with noise. Group-based approval rules give the team a more surgical filter. That is especially useful for support categories, beta programs, and feedback queues where some cohorts need extra checking and others absolutely do not. ## Roll out support behavior the same way you would roll out product behavior [Discourse Upcoming Changes opt-in before community rollout](/growth-ideas/discourse-upcoming-changes-opt-in-before-community-rollout/) is the quiet trust move in this batch. Community settings are product settings. If a new category type, moderation rule, or answer pattern changes how people post, the operator should stage it instead of surprising everyone at once. The support queue is strongest when each thread advertises its job early: discussion, answerable question, private escalation, moderated intake, or experiment in progress. That is a practical lesson for SaaS, AI products, developer tools, B2B software, and open-source products whose community doubles as help desk, onboarding surface, and trust layer. If you want help tightening support threads, docs, and community infrastructure into a cleaner growth system, the advisory CTA is here: [work with Ian Goh](https://iangoh.com/advisory). ## Related GrowthDex tactics - [Discourse support category type with solved defaults](/growth-ideas/discourse-support-category-type-with-solved-defaults/) - Community, Support, Documentation - [Discourse solved tags on mixed discussion categories](/growth-ideas/discourse-solved-tags-on-mixed-discussion-categories/) - Community, Support, Product Feedback - [Discourse solved in group messages for private escalations](/growth-ideas/discourse-solved-in-group-messages-for-private-escalations/) - Support, Customer Success, Operations - [Discourse category approval rules by trust group](/growth-ideas/discourse-category-approval-rules-by-trust-group/) - Community, Support, Operations - [Discourse Upcoming Changes opt-in before community rollout](/growth-ideas/discourse-upcoming-changes-opt-in-before-community-rollout/) - Community, Operations, Brand ## Essay chronology - [Newer essay: The directory profile should do the shortlist work before the demo](/blog/the-directory-profile-should-do-the-shortlist-work-before-the-demo/) - SEO, brand trust, demand capture - [Older essay: The review request should show up after the proof](/blog/the-review-request-should-show-up-after-the-proof/) - brand trust, customer feedback, marketplaces ## Keep reading - [The customer-facing answer should keep the context attached](/blog/the-customer-facing-answer-should-keep-the-context-attached/) - support-led growth, brand trust, customer success - [The Show HN thread should finish the first technical conversation](/blog/the-show-hn-thread-should-finish-the-first-technical-conversation/) - community-led growth, brand trust, launches - [The feedback board should recruit the beta cohort before the roadmap meeting](/blog/the-feedback-board-should-recruit-the-beta-cohort-before-the-roadmap-meeting/) - community-led growth, product ops, brand trust ## 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: Easily create Support categories using the discourse-solved plugin](https://meta.discourse.org/t/easily-create-support-categories-using-the-discourse-solved-plugin/398338/1) · [GrowthDex source hub](/sources/discourse-meta-easily-create-support-categories-using-the-discourse-solv/) - [Discourse Meta: Convert a topic to a question which can be marked as solved](https://meta.discourse.org/t/convert-a-topic-to-a-question-which-can-be-marked-as-solved/73791/13?silent=true) · [GrowthDex source hub](/sources/discourse-meta-convert-a-topic-to-a-question-which-can-be-marked-as-solv/) - [Discourse Meta: Allow “Mark as Solution” in group messages](https://meta.discourse.org/t/allow-mark-as-solution-in-group-messages/370496/29) · [GrowthDex source hub](/sources/discourse-meta-allow-mark-as-solution-in-group-messages-meta-discourse-o/) - [Discourse Meta: More flexible category-level topic and reply approvals](https://meta.discourse.org/t/more-flexible-category-level-topic-and-reply-approvals/401132) · [GrowthDex source hub](/sources/discourse-meta-more-flexible-category-level-topic-and-reply-approvals-me/) - [Discourse Meta: Introducing Upcoming Changes](https://meta.discourse.org/t/introducing-upcoming-changes-a-system-to-manage-new-features-and-changes-to-existing-functionality-in-your-community/392894/) · [GrowthDex source hub](/sources/discourse-meta-introducing-upcoming-changes-meta-discourse-org/) ## Editing notes - Kept the essay anchored to one plain claim: support threads get expensive when the system hides what kind of job each thread is doing. - Used ordinary scenes like private escalations, mixed discussion categories, and moderation queues instead of abstract community theory. - Let the Discourse workflow details carry the argument rather than inflating the piece with generic trust language. - Closed on an operating standard and direct advisory CTA instead of a padded wrap-up. ## Advisory If you want help turning this into a growth system, Ian Goh offers advisory at https://iangoh.com/advisory.