Cutover runbook and rollback plan before support launch
Write the first migration run and the formal cutover as a runbook with a rollback path before launch day so the switch does not depend on memory or Slack improvisation.
Why this can grow a startup
A migration often looks scarier than it is because the sequence lives in people's heads. A runbook turns the switch into visible steps, checkpoints, and ownership. Adding a rollback plan matters just as much. Buyers relax when they can tell the team has already thought about what happens if one assumption fails halfway through the move.
Source-backed example
Intercom's migration guide tells teams to create a run book and rollback plan covering both the first migration run and the formal cutover plus delta migration run.
Source-reported evidence
Source: Intercom Help · Browse Intercom Help tactics
One runbook should cover both the first migration run and the formal cutover
Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.
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 26, 2026
When to use it
Use this when Support, Operations, Internal Comms is relevant to migration, rollback, change management 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 Support and Operations, using evidence from Intercom Help as context—not as a promised result.
- Record a baseline for: Users who resolve the issue and complete the next useful action. 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
Choose product surfaces that compound distribution without hiding weak activation or retention.
SOURCE HUB
More tactics from Intercom Help
Explore related GrowthDex examples and evidence connected to Intercom Help.
Open Intercom Help source hub