Workflow exceptions before API-led migration
Before importing conversations by API, disable or exempt the automations that would treat imported records like fresh customer activity.
Why this can grow a startup
A migration can look broken even when the data import succeeds, because the surrounding automations fire at the wrong time. Surveys send, notifications leak, states change, and users get pulled into a fake live conversation. Guarding the workflows first prevents avoidable trust damage and makes the cutover feel controlled instead of messy.
Source-backed example
Intercom's migration guide warns teams to add trigger-rule exceptions for records created via API or temporarily turn workflows off during migration, and to suppress email notifications when imported conversations would otherwise message customers.
Source details
Source: Intercom Help · Browse Intercom Help tactics
Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.
Source discovered: May 25, 2026
When to use it
Use this when Lifecycle, Support, Product is relevant to migration, lifecycle, risk control and you can run a bounded test with a free 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.
How to do it
- Choose one target segment and define the exact next action this tactic should prompt.
- Adapt the tactic to Lifecycle and Support, using evidence from Intercom Help as context—not as a promised result.
- Record a baseline for: Share of the target cohort repeating the core action within the chosen period. Set a guardrail that would make you pause the test.
- Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
- Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Compare a stack for your situation
Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.
Explore the context
Did you launch this experiment?
Report a launch to help us understand which growth ideas founders put into practice.
Apply this with an operator
Connect activation, customer value, retention, and referral into one measurable loop.
SOURCE HUB
More tactics from Intercom Help
Explore related GrowthDex examples and evidence connected to Intercom Help.
Open Intercom Help source hub