Overview
A sandbox is a test workspace, fully isolated from your real workspace data. Use one to try out objects, automations, imports, or AI features without touching live customer records. When you’re done you can wipe it back to empty, delete it entirely, or convert it into a real workspace.How it works
Each sandbox is a separate, isolated workspace marked as a sandbox. Sandboxes skip billing and the usual default setup when created, so they spin up clean and fast. While a sandbox is active, a banner makes the test environment obvious and the tab title is prefixed. When you create a sandbox you pick a starter template. “Empty sandbox” gives you a blank slate; the other starters (grouped as best practices and by category such as Sales, Support, and Operations) seed objects, properties, sample records, and conversations so the workspace is immediately useful. Sandboxes have generous guardrails so they stay test environments. Per-account and per-resource limits apply (for example a cap on records, conversations, channels, and seeded users per sandbox), real-data connections like OAuth and imports are blocked, and there is a daily AI token cap. Hitting a cap is the signal to convert to a real workspace.Using it
1
Open Sandboxes
Go to Settings → Sandboxes. The screen lists every sandbox with its
created and last-accessed dates.
2
Create a sandbox
Click Create sandbox, give it a name, and Choose a starter. Pick
“Empty sandbox” for a blank workspace or a best-practice / category
template to seed sample data, then click Create.
3
Experiment safely
Switch into the sandbox and explore. The sandbox banner confirms you’re in
a test environment, not your live workspace.
4
Wipe, convert, or delete
From the sandbox row choose Wipe data (drops all records, conversations,
and seeded users but keeps the sandbox), Convert to real (turns it into
a real workspace, sandbox features turn off and billing applies), or
Delete (permanently removes the sandbox and its data).
Troubleshooting
When reporting an issue, include the request id shown in the error toast.
It links the in-app error to the server logs.