# Required tagging before archive or move

> Force teams to tag a support thread before they archive or reroute it, so the queue keeps producing usable product and operations signal.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/required-tagging-before-archive-or-move/
- Source: [help.front.com](https://help.front.com/en/articles/2106)
- GrowthDex source hub: [Front Help](/sources/front-help-help-front-com/)
- Last checked: 2026-05-28
- Rarity: uncommon
- Budget: free
- Channels: Support, Operations, Product
- Stages: feedback loop, support ops, queue hygiene, analytics


## Why this can grow

A lot of support analytics fail because categorization is optional when the team is busy. Front's required tagging rule moves that discipline into the workflow itself. If a conversation cannot be moved or archived without a tag, the queue starts generating cleaner topic data, cleaner routing, and better evidence for product decisions. The move is simple, but it turns support from memory-driven anecdote into something the team can actually measure.

## 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 required tagging before archive or move can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Support and Operations channel.
3. Use the evidence from help.front.com 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

Front's required tagging rule prompts teammates to add approved tags before they can archive or move conversations in the targeted inboxes.

## Adjacent tactics in the same lane

- [De-duplicate multi-inbox copies before cutover](/growth-ideas/de-duplicate-multi-inbox-copies-before-cutover/) - same source, 2 shared channels, 1 shared stage
- [Customer labels on ticket statuses](/growth-ideas/customer-labels-on-ticket-statuses/) - same source, 1 shared channel, 1 shared stage
- [Move conversation, not forward, for shared inbox handoffs](/growth-ideas/move-conversation-not-forward-for-shared-inbox-handoffs/) - same source, 1 shared channel, 1 shared stage
- [Snoozed triage that returns on new activity](/growth-ideas/snoozed-triage-returns-on-new-activity/) - 3 shared channels, 2 shared stages

## Read GrowthDex essays

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

## Related GrowthDex essays

- [The request system should keep the customer on the same thread](/blog/the-request-system-should-keep-the-customer-on-the-same-thread/) - support-led growth, brand trust, customer operations

## Advisory

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