# 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.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/discourse-solved-in-group-messages-for-private-escalations/
- Source: [meta.discourse.org](https://meta.discourse.org/t/allow-mark-as-solution-in-group-messages/370496/29)
- GrowthDex source hub: [Discourse Meta: Allow “Mark as Solution” in group messages](/sources/discourse-meta-allow-mark-as-solution-in-group-messages-meta-discourse-o/)
- Last checked: 2026-05-30
- Rarity: rare
- Budget: free
- Channels: Support, Customer Success, Operations
- Stages: private escalations, support workflow, internal help desk, resolution clarity


## Why this can grow

Many support systems break at the handoff from public thread to private conversation. Once the issue moves into a group message, the resolution often stops compounding because nobody can tell when it is done or which reply fixed it. Discourse's `allow_solved_in_groups` setting repairs that gap for chosen groups. The private thread can keep a clear endpoint without turning all personal messages into support tickets, which is useful for escalations, internal help desks, and customer-sensitive troubleshooting.

## 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 solved in group messages for private escalations can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Support and Customer Success 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

A Discourse core change merged in February 2026 added the `allow_solved_in_groups` setting so solved UI can appear in group messages for configured groups while regular one-on-one PMs stay excluded.

## Adjacent tactics in the same lane

- [Linear owner auto-assignment for account threads](/growth-ideas/linear-owner-auto-assignment-for-account-threads/) - 3 shared channels
- [SLA trend review for response and resolution bottlenecks](/growth-ideas/sla-trend-review-for-response-and-resolution-bottlenecks/) - 3 shared channels
- [GitHub issue form auto-labels, assignees, and project routing](/growth-ideas/github-issue-form-auto-labels-assignees-and-project-routing/) - 2 shared channels
- [Retroactive proactive message tagging for support analysis](/growth-ideas/retroactive-proactive-message-tagging-for-support-analysis/) - 2 shared channels

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The support queue should know what kind of thread it is](/blog/the-support-queue-should-know-what-kind-of-thread-it-is/) - support-led growth, community-led growth, brand trust

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.