Plan requirement
| Subscription | Suite Growth or higher, Support Professional or higher |
| Access | Admin |
A separate copy of your configuration where a mistake costs nothing. The habit that separates calm changes from risky ones.
What it is
A second Zendesk with your configuration and no real customers. Triggers, fields, forms and views can be built and broken there without anybody noticing.
Why it matters here specifically
Zendesk has no draft state. Saving a trigger means it fires on the next ticket, and a badly scoped one can touch every ticket in the queue within minutes.
A sandbox is the missing draft state.
What belongs in one
- New triggers and automations, especially anything that sends email.
- Changes to forms and fields, which agents see immediately.
- Routing changes, where the effect is only visible under real volume.
- Anything you would rather not explain if it went wrong at ten on a Monday.
What it is not
Not a backup: it does not protect your live data. Not a full copy: what it includes depends on your plan, and customer data generally is not part of it.
It drifts
A sandbox created a year ago no longer matches production, so testing there proves less than it appears to. Refresh it before relying on it for anything significant.
The habit worth forming
Anything that touches more than one ticket gets built in the sandbox first. It costs a few extra minutes and removes the category of change that ruins an afternoon.
Comments
0 comments
Article is closed for comments.