# The support switch usually leaks in the routing layer > Why forwarding rules, shared-thread handoffs, duplicate control, trigger review, and docs cleanup make support migrations feel safe. - Canonical HTML: https://growth.iangoh.com/blog/the-support-switch-usually-leaks-in-the-routing-layer/ - Published: 2026-05-25 - Updated: 2026-05-25 - Categories: support-led growth, migration, seo - Niches: SaaS, support software, AI products, developer tools ## On this page - The first impression is often a mailbox detail - A handoff should keep the story, not restart it - Parallel routing needs one version of the truth - Automation deserves a review queue before it deserves traffic - Docs can quietly make the whole move look unfinished - Where this is most useful ## Start with these related tactics - [Automatic forwarding and domain auth before support cutover](/growth-ideas/automatic-forwarding-and-domain-auth-before-support-cutover/): Set up automatic forwarding and authenticate the support domain before the inbox migration goes live so the new workspace can handle real mail without looking improvised. - [Move conversation, not forward, for shared inbox handoffs](/growth-ideas/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. - [De-duplicate multi-inbox copies before cutover](/growth-ideas/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. A lot of support migrations get sold like product upgrades. In practice they feel more like routing projects with a trust problem attached. The buyer is not just asking whether the new inbox looks nicer. They are asking whether live mail lands where it should, whether a handoff keeps the thread intact, whether duplicate copies waste the team, whether old automations go strange, and whether the help center looks half-moved in search. ## The first impression is often a mailbox detail That is why [automatic forwarding and domain auth before support cutover](/growth-ideas/automatic-forwarding-and-domain-auth-before-support-cutover/) matters so much. If live messages start landing late or replies come from a sketchy domain, the migration already feels fragile. This sounds operational because it is operational. Buyers do not separate operations from product trust when the support queue is involved. ## A handoff should keep the story, not restart it The cleanest example is [move conversation, not forward, for shared inbox handoffs](/growth-ideas/move-conversation-not-forward-for-shared-inbox-handoffs/). A forwarded copy looks harmless until three people are reading two different versions of the same customer problem. Once the context splits, the new system does not feel modern. It feels sloppy. That is the kind of mistake buyers remember longer than a feature gap. ## Parallel routing needs one version of the truth The next move is [de-duplicate multi-inbox copies before cutover](/growth-ideas/de-duplicate-multi-inbox-copies-before-cutover/). Temporary overlap is normal during a switch. Temporary confusion is not. If the same email can create several open copies, the migration teaches the team the wrong lesson. They stop trusting the routing layer and start building private workarounds. ## Automation deserves a review queue before it deserves traffic That same caution should apply to rules. [Trigger review queue before chat-to-messaging launch](/growth-ideas/trigger-review-queue-before-chat-to-messaging-launch/) is useful because it admits something teams usually learn too late: migrated automations are not innocent just because they were copied by the vendor. A review queue turns the launch into a checkable change instead of a leap. That is stronger proof than another promise about AI support or workflow magic. ## Docs can quietly make the whole move look unfinished The last leak is often search and support navigation. [Help-center collection link cleanup after domain switch](/growth-ideas/help-center-collection-link-cleanup-after-domain-switch/) fixes a problem that looks too small until the old category pages keep showing up. It pairs naturally with [cross-domain help-center 301s before docs move](/growth-ideas/cross-domain-help-center-301s-before-docs-move/) and [single indexed help center during knowledge sync](/growth-ideas/single-indexed-help-center-during-knowledge-sync/). If the help center looks split across two domains or two indexed versions, the support brand looks split too. Customers do not need to know the technical reason. They only need to feel that something is off. ## Where this is most useful For SaaS and support software, this is a reminder that migration proof lives in routing details as much as in roadmap slides. For AI products, it is a warning that automations and handoffs need inspection before launch copy starts promising speed. For developer tools, it is a good pattern whenever the support surface is part of the product evaluation, not just the service layer. If a support-platform switch is slowing down in pipeline, I would not ask first for a shinier comparison page. I would ask whether the routing layer already looks boring enough to trust. ## Related GrowthDex tactics - [Automatic forwarding and domain auth before support cutover](/growth-ideas/automatic-forwarding-and-domain-auth-before-support-cutover/) - Support, Email, Lifecycle - [Move conversation, not forward, for shared inbox handoffs](/growth-ideas/move-conversation-not-forward-for-shared-inbox-handoffs/) - Support, Email, Workflow - [De-duplicate multi-inbox copies before cutover](/growth-ideas/de-duplicate-multi-inbox-copies-before-cutover/) - Support, Email, Operations - [Trigger review queue before chat-to-messaging launch](/growth-ideas/trigger-review-queue-before-chat-to-messaging-launch/) - Support, Lifecycle, Product - [Help-center collection link cleanup after domain switch](/growth-ideas/help-center-collection-link-cleanup-after-domain-switch/) - SEO, Support, Website ## Essay chronology - [Newer essay: The launch only works if the next surface keeps working](/blog/the-launch-only-works-if-the-next-surface-keeps-working/) - launches, community-led growth, SEO - [Older essay: The switch should feel boring before it feels done](/blog/the-switch-should-feel-boring-before-it-feels-done/) - switcher intent, migration, trust ## Keep reading - [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 doc starts working when the product can point to it](/blog/the-support-doc-starts-working-when-the-product-can-point-to-it/) - support-led growth, documentation, seo - [The help page starts earning when it can finish the job](/blog/the-help-page-starts-earning-when-it-can-finish-the-job/) - support-led growth, seo, activation ## Continue through the blog - [SaaS](/blog/#path-saas) - 3 essays in this path - [AI products](/blog/#path-ai-products) - 3 essays in this path - [developer tools](/blog/#path-developer-tools) - 3 essays in this path ## Sources - [Intercom Help](https://www.intercom.com/help/en/articles/9744849-how-to-manage-email-settings) · [GrowthDex source hub](/sources/intercom-help-intercom-com/) - [Front Help](https://help.front.com/en/articles/2089) · [GrowthDex source hub](/sources/front-help-help-front-com/) - [Front Help](https://help.front.com/en/articles/2265) · [GrowthDex source hub](/sources/front-help-help-front-com/) - [Zendesk Help](https://support.zendesk.com/hc/en-us/articles/9863791207066-Migrating-triggers-with-the-live-chat-to-messaging-migration-wizard) · [GrowthDex source hub](/sources/zendesk-help-support-zendesk-com/) - [Intercom Help](https://www.intercom.com/help/en/articles/7301427-troubleshooting-custom-domain-set-up-and-https-ssl) · [GrowthDex source hub](/sources/intercom-help-intercom-com/) ## Editing notes - Kept the article on one blunt claim about routing and trust instead of turning it into a generic migration checklist. - Used short, plain paragraphs and a few operator judgments so the piece reads like lived support work rather than content marketing. - Avoided broad claims about AI or transformation and let each tactic carry one concrete part of the argument. - Ended on a buying question instead of a tidy conclusion. ## Advisory If you want help turning this into a growth system, Ian Goh offers advisory at https://iangoh.com/advisory.