Whether you're introducing a new set of articles, sections, and user segments, or refining existing content, the challenge in managing your help center customizations often lies in executing changes efficiently and accurately across multiple instances. Salto can streamline this process, enabling you to replicate customizations without the need for manual intervention.

The Challenge: Manual replication of customizations

Imagine you've crafted a comprehensive suite of support articles under a new section, complete with specific user segments, associated management permissions, etc. You've even added a critical attachment to an article for enhanced user guidance. The next step is to replicate these meticulously created elements from, say, your sandbox to your production environment or vice versa. Traditionally, this would require recreating each element manually—a time-consuming and error-prone process.

The solution: Automated, error-free deployment

Here is a 5-minute video where CE Scott Dixon shows how to push a Guide article from sandbox to production:

Compare environments

Use Salto to compare your source environment, in the case your sandbox guide instance, against your target environment - your production Guide. Here you will be able to pick and choose elements to deploy from sandbox to production. Filtering through all of the configuration elements, you'll focus on the specific article and its related components—sections, user segments, management permissions, and attachments.

Address dependencies

When you choose the article you want to deploy - Salto will immediately call out any dependencies. For instance, if the article we want to deploy contains links to other articles which don’t exist - Salto will point out that you also need to deploy those missing articles.

Deploy

Once you’re ready - deploy to production, and you’re done. The article, along with all its dependencies, is now live in your production Guide. By the way, if you manage your tasks with a ticketing system like Jira or Monday, you can even set up the deployment with the ticket number, and Salto will update the ticket with the changes made in this deployment for your records and continued project management.

Important to note: during the deployment process, Salto will handle updating the reference to other articles, etc. in the target environment. In other words, there's no need to manually update links that refer to an article by its internal Zendesk ID, which can differ between sandbox and production instances.

Instead of having to choose between two far from ideal options:

1. Manually make changes directly to production
2. Creating changes in sandbox and the manually recreating them in production

Salto is giving you a third way - make the necessary changes in your Guide sandbox and then replicate them to production, without any manual work. If you want to see more - you can request a demo or start your free trial.