The Problem: Building and validating complex workflows in the Intercom test sandbox is essential, but the current deployment process creates a massive bottleneck. Once a Custom Bot, Series, or complex set of assignment rules is fully tested and approved in the sandbox, we currently have to manually recreate it from scratch in our live Production environment. This manual dual-entry is time-consuming, tedious, and highly prone to human error.
Additionally, over time, our sandbox drifts out of parity with our Production environment, meaning we are often testing new builds against outdated workspace configurations.
The Proposed Solution: We are looking for two core environment management capabilities to make the sandbox genuinely enterprise-ready:
-
Sandbox-to-Production Deployment (Copy/Paste): Introduce a "Deploy to Prod" or "Copy to Workspace" function for individual assets. If we build a complex Series, Workflow, or Custom Bot in the sandbox, we should be able to push that specific asset directly to our live workspace in a paused/draft state, carrying over the exact logic, paths, and tags.
-
Production-to-Sandbox Sync (Cloning): Add a one-click ability to refresh or overwrite the test sandbox with our current Production configuration (Custom Data Attributes, existing Workflows, tags, and Teams). This ensures that when we build in the sandbox, we are simulating against a true, up-to-date replica of our live environment.
Business Impact: Implementing these mechanics would completely eliminate the risk of manual recreation errors during deployment. It would drastically reduce administrative overhead, speed up our time-to-value for new Intercom builds, and give our team the confidence that what works in the sandbox will execute identically in Production.
Has anyone else built workarounds for migrating complex builds out of the sandbox, or is everyone currently relying on the dual-screen manual rebuild method?