# Move conversation, not forward, for shared inbox handoffs

> When a support thread needs a new owner during a migration, move the conversation into the right shared inbox instead of forwarding a fresh copy.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/move-conversation-not-forward-for-shared-inbox-handoffs/
- Source: [help.front.com](https://help.front.com/en/articles/2089)
- GrowthDex source hub: [Front Help](/sources/front-help-help-front-com/)
- Last checked: 2026-05-25
- Rarity: uncommon
- Budget: free
- Channels: Support, Email, Workflow
- Stages: handoff, support ops, migration, retention
- Key metric: 1 shared thread stays intact instead of creating another forwarded copy

## Why this can grow

Forwarded copies split the context right when a team most needs continuity. A move keeps the thread history, status, and accountability tied to one object. That makes escalations easier to trust and gives evaluators visible proof that the new support system can hand work across teams without losing the story.

## 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. For retention, I would watch the second and third use, not just the first click. A tactic is real when it changes a habit. 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 move conversation, not forward, for shared inbox handoffs 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: 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 recommends moving conversations to another inbox when the goal is to hand a thread to the right team, because the same conversation stays intact instead of becoming a forwarded side thread.

## 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, 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
- [Mirror account manager inbox into a shared support view](/growth-ideas/mirror-account-manager-inbox-into-shared-support-view/) - same source, 2 shared channels, 2 shared stages
- [Customer labels on ticket statuses](/growth-ideas/customer-labels-on-ticket-statuses/) - same source, 1 shared channel, 2 shared stages

## Read GrowthDex essays

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

## Related GrowthDex essays

- [The support switch usually leaks in the routing layer](/blog/the-support-switch-usually-leaks-in-the-routing-layer/) - support-led growth, migration, seo

## Advisory

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