Using your sandbox to experiment safely – Gravity CX

Ref: C19 · Track: Knowledge Base Admin · Time to complete: ~5 min

Why this matters

You're about to restructure 40 articles, test a new theme, try a user segment configuration. You do not want to do that in production. A sandbox is a parallel Zendesk instance where you can experiment without the consequences. Use it.

What a sandbox is (and isn't)

A sandbox is an isolated Zendesk account that mirrors (in structure) your production account. It's not: - A live backup — data may not sync from prod. - A staging deploy pipeline — changes you make in sandbox don't automatically promote. - A free second production — it has separate users/tickets/agents.

It is: - A safe place to test theme changes, triggers, user segments, article drafts, category restructures. - A learning environment for new admins. - A demo environment for showing customers or stakeholders.

Plan and availability

Sandboxes are a paid feature, included on certain Zendesk plans (Enterprise and above on most pricing tiers). Two types:

Standard sandbox

Empty of tickets/users, mirrors schema.
Resets or is maintained on demand.
Best for structural experiments.

Premium sandbox

Includes a partial or full copy of production data.
Better for realistic testing (real triggers firing, real data flows).

Your admin will know which type your org has.

Typical sandbox uses

Restructuring categories

Want to split "General" into "Billing" and "Admin"? Try it in sandbox first. See how it feels. Measure clicks/depth. Decide. Then do it in prod.

Testing themes

Customising Copenhagen. A bug that breaks the search page is fine in sandbox; disastrous in prod. Preview, test, then replicate to prod (or export theme from sandbox and import to prod).

Trying new triggers/automations

The automation "auto-close after 5 days of customer silence" — does it misbehave around weekends and holidays? Test in sandbox by creating test tickets with forged timestamps.

Onboarding new admins

Give a new admin the sandbox, let them break things, teach them.

Customer demos

Need to show a prospect how agent workspace works without exposing your production data? Sandbox.

What doesn't transfer

Changes made in a sandbox don't auto-sync to prod. You have to replicate manually:

Articles: export and re-import, or copy content manually.
Themes: export ZIP from sandbox, import into prod.
Triggers / automations / views: replicate manually. There's no one-click sync. Some tools help but require care.
User segments: replicate manually.

Some organisations keep a spreadsheet of "config changes to promote" — tested in sandbox, replicated in prod. Discipline matters.

How to access the sandbox

Your admin configures access: 1. Sandbox has its own URL: typically yourbrand1234567890.zendesk.com or similar. 2. Your admin adds your email as an agent/admin in the sandbox. 3. Log in normally; it'll feel identical to production but completely separate.

Always check the URL and branding before making changes. It's easy to think you're in sandbox when you're in prod, especially if your theme is copied to look similar.

A discipline: label your sandbox

Make the sandbox visually obvious: - Change the header colour to red or orange. - Put "SANDBOX" in the brand name. - Add a banner via theme customisation.

"I accidentally made changes in prod thinking I was in sandbox" is a real story. Prevent it visually.

Gotchas

Sandbox doesn't reflect live customer data. Users/tickets/orgs will differ. Testing things that depend on real data needs a premium sandbox.
APIs from integrations. Third-party integrations (Slack, Jira, CRM) typically don't connect to sandbox. You'll get gaps.
No one-click promote. Changes in sandbox → prod are manual. Don't skip that discipline.
Sandbox can feel outdated. If you don't refresh it periodically, sandbox schema lags prod. Refresh on a cadence.
Limit of one. Most plans provide one sandbox instance. If two people are working on different experiments, coordinate or step on each other.

Quick check — have you got this?

You're about to restructure 30 articles' categories. Where first?
You've built a working theme in sandbox. Changes auto-apply to prod?
A colleague says "let me just fix this in sandbox". What's the next step?

Answers

- Sandbox. Test the restructure end-to-end. Then replicate in prod. - No. Export the theme ZIP from sandbox and import into prod. - Document the change so it can be replicated in prod. Sandbox fixes don't promote automatically.

C04 — Preview modes before publishing
C17 — Themes, versions, and Copenhagen
D01 — Omnichannel routing and capacity rules (if testing config)