# Discourse assignment statuses for public support ownership

> Assign support topics to a person or group with visible statuses so customers and teammates can see who owns the thread and what stage it is in.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/discourse-assignment-statuses-for-public-support-ownership/
- Source: [meta.discourse.org](https://meta.discourse.org/t/discourse-assign/58044)
- GrowthDex source hub: [Discourse Meta: Discourse Assign](/sources/discourse-meta-discourse-assign-meta-discourse-org/)
- Last checked: 2026-05-29
- Rarity: rare
- Budget: medium
- Channels: Community, Support, Customer Success
- Stages: queue ownership, support ops, close-the-loop, public accountability


## Why this can grow

A community thread goes stale fast when nobody can tell whether it is waiting on engineering, support, or the customer. Discourse Assign lets teams assign a topic or post to a user or group, add notes, set a status, and keep a small-action history inside the topic. That turns the thread into a lightweight queue instead of a public pile of unanswered asks. The visible ownership helps internally, but it also changes the customer experience. The thread feels maintained instead of forgotten.

## 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 assignment statuses for public support ownership 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 Assign supports topic and post assignment, group assignment, customizable statuses such as New, In Progress, and Done, and status-change tracking posts inside the topic.

## Adjacent tactics in the same lane

- [Mirror account manager inbox into a shared support view](/growth-ideas/mirror-account-manager-inbox-into-shared-support-view/) - 2 shared channels, 1 shared stage
- [GitHub issue template chooser with blank issues disabled](/growth-ideas/github-issue-template-chooser-with-blank-issues-disabled/) - 2 shared channels, 1 shared stage
- [Customer labels on ticket statuses](/growth-ideas/customer-labels-on-ticket-statuses/) - 2 shared channels, 1 shared stage
- [Convert email threads into portal conversations](/growth-ideas/convert-email-threads-into-portal-conversations/) - 2 shared channels, 1 shared stage

## Read GrowthDex essays

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

## Related GrowthDex essays

- [The support forum should stop acting like a chat room](/blog/the-support-forum-should-stop-acting-like-a-chat-room/) - community-led growth, support-led growth, documentation

## Advisory

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