# De-duplicate multi-inbox copies before cutover

> Set duplicate-handling rules before routing the same email to multiple shared inboxes so one customer thread does not turn into several internal copies.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/de-duplicate-multi-inbox-copies-before-cutover/
- Source: [help.front.com](https://help.front.com/en/articles/2265)
- GrowthDex source hub: [Front Help](/sources/front-help-help-front-com/)
- Last checked: 2026-05-25
- Rarity: uncommon
- Budget: free
- Channels: Support, Email, Operations
- Stages: inbox routing, support ops, migration, quality control
- Key metric: 1 master copy across shared inboxes

## Why this can grow

Cutovers often create overlap on purpose: backup inboxes, extra aliases, tier-two visibility, or temporary parallel teams. Without de-duplication, that overlap produces duplicate work and contradictory replies. One master copy keeps the team aligned and makes the new routing design feel calmer almost immediately.

## 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. Email still works when it reads like one person noticed one real thing. If the message could be sent to anyone, it usually works on nobody. I would make the first line specific enough that the right reader knows it was meant for them. 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 1 master copy across shared inboxes before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where de-duplicate multi-inbox copies before cutover can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Support and Email 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: 1 master copy across shared inboxes.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

Front merges emails addressed to multiple shared inboxes into one master copy by default so replies, comments, tags, and status changes stay synchronized across the team.

## Adjacent tactics in the same lane

- [Move conversation, not forward, for shared inbox handoffs](/growth-ideas/move-conversation-not-forward-for-shared-inbox-handoffs/) - same source, 2 shared channels, 2 shared stages
- [Convert email threads into portal conversations](/growth-ideas/convert-email-threads-into-portal-conversations/) - same source, 2 shared channels, 2 shared stages
- [Required tagging before archive or move](/growth-ideas/required-tagging-before-archive-or-move/) - same source, 2 shared channels, 1 shared stage
- [Mirror account manager inbox into a shared support view](/growth-ideas/mirror-account-manager-inbox-into-shared-support-view/) - same source, 2 shared channels, 1 shared stage

## Read GrowthDex essays

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

## Related GrowthDex essays

- [The docs move usually gets judged by the dull pages](/blog/the-docs-move-usually-gets-judged-by-the-dull-pages/) - docs migration, seo, support-led growth
- [The support switch usually leaks in the routing layer](/blog/the-support-switch-usually-leaks-in-the-routing-layer/) - support-led growth, migration, seo

## Reading path: AI products

- [The docs move usually gets judged by the dull pages](/blog/the-docs-move-usually-gets-judged-by-the-dull-pages/) (2026-05-25T12:05:00Z)
- [The support switch usually leaks in the routing layer](/blog/the-support-switch-usually-leaks-in-the-routing-layer/) (2026-05-25)

## Reading path: developer tools

- [The docs move usually gets judged by the dull pages](/blog/the-docs-move-usually-gets-judged-by-the-dull-pages/) (2026-05-25T12:05:00Z)
- [The support switch usually leaks in the routing layer](/blog/the-support-switch-usually-leaks-in-the-routing-layer/) (2026-05-25)

## Advisory

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