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.
Why this can grow a startup
Support migrations often fail in the dull layer first. Messages route late, replies come from the wrong domain, and the team starts apologizing before the new workflow has even had a fair shot. Forwarding plus domain authentication lets the team test live traffic early and makes the cutover feel legitimate to both agents and customers.
Company example
Intercom's email support setup requires automatic forwarding and domain authentication for support mail, and it treats the shared intercom-mail.com domain as a temporary testing setup rather than a long-term answer.
Source and metric
Source: Intercom Help · Browse Intercom Help tactics
1 shared domain for initial testing before a custom reply domain is recommended
Source discovered: May 25, 2026
When to use it
Use this when Support, Email, Lifecycle is relevant to migration, deliverability, support ops and you can run a bounded test with a low budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
Founder checklist
- Read Intercom Help and identify what is directly supported.
- Choose one channel context: Support, Email, Lifecycle.
- Define the test around 1 shared domain for initial testing before a custom reply domain is recommended.
- Set an owner, evidence window, and stop condition before launch.
Explore the context
Apply this with an operator
Connect activation, customer value, retention, and referral into one measurable loop.