Growth idea action plan
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.
Why this can grow a startup
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
- Define one narrow startup segment where discourse solved in group messages for private escalations can create a measurable lift.
- Turn the tactic into one offer, page, campaign, or workflow for the Support and Customer Success channel.
- Use the evidence from meta.discourse.org to set the first version of the message, format, and audience.
- Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
- 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.
Source: Discourse Meta: Allow “Mark as Solution” in group messages (meta.discourse.org)
GrowthDex source hub: Discourse Meta: Allow “Mark as Solution” in group messages
Last checked: 2026-05-30
Adjacent tactics in the same lane
If this page is close to your problem, these tactic pages usually belong in the same working set.
- Linear owner auto-assignment for account threads 3 shared channels
- SLA trend review for response and resolution bottlenecks 3 shared channels
- GitHub issue form auto-labels, assignees, and project routing 2 shared channels
- Retroactive proactive message tagging for support analysis 2 shared channels
Related GrowthDex essays
- The support queue should know what kind of thread it is support-led growth, community-led growth, brand trust
Read GrowthDex essays
The Blog turns real growth tactics into plain-English case studies by niche, channel, and buying situation.
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.
- Helped scale Tiki to 100M+ users.
- Doubled BIGO's MENA revenue in 7 months.
- Raised OYO's direct booking share by 50% 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