Learn how Crisp sandbox mode works for development and staging workspaces.

If your product runs across production, staging, and development environments, you can use the same Crisp workspace everywhere. When you prefer to keep test conversations and integrations separate, Crisp can provide a dedicated sandbox workspace linked to your paid production subscription.

How sandbox mode works

Crisp offers a free staging environment for workspaces subscribed to a paid Essentials or Plus plan. This lets you test Crisp features in a separate development or staging workspace without polluting your production inbox.

A sandbox workspace can be useful for testing:

• Crisp Chatbox JavaScript SDK integrations
• Automated Campaigns
• Workflows and routing changes
• Email and chatbox configuration
• Internal QA before production release

Create a sandbox workspace

Sandbox mode must be manually validated by the Crisp team. Start by creating the secondary workspace, then contact Crisp support so they can review and enable sandbox mode.

Before contacting support

Create a second workspace on the Free plan from Crisp. Name it close to your production workspace name, with a clear suffix such as Staging, Sandbox, or Dev.

For example:

• CookieFactory → production workspace
• CookieFactory Staging → sandbox workspace

Information to send to support

Contact Crisp support and share the details needed to identify both workspaces.

Include:

• Your production workspace name
• Your production workspace domain
• The secondary workspace name
• The secondary workspace domain
• The secondary workspace CRISP_WEBSITE_ID

You can find the CRISP_WEBSITE_ID in your chatbox installation code.

After support approves the request

Once Crisp confirms the sandbox request, upgrade the secondary workspace to Essentials. You should not be charged immediately while support applies sandbox mode.

Then:

• Tell Crisp support that the secondary workspace has been upgraded
• Wait for support to apply sandbox mode
• Log out and log back in to refresh your Crisp app session
• Start using the workspace for development or staging tests

Eligibility requirements

To qualify for sandbox mode, the production workspace must be subscribed to an active Essentials or Plus plan.

The sandbox workspace should:

• Be used only for development, staging, or QA purposes
• Have a name clearly linked to the production workspace
• End with a suffix such as Dev, Staging, or Sandbox

Sandbox mode limitations

A sandbox workspace behaves like a normal paid workspace for most configuration tests, but a few restrictions are applied to prevent it from being used as a production subscription.

Sandbox limitations include:

• A sticky banner reminding your team that the workspace is in sandbox mode
• A confirmation step before messages can be sent from the Inbox
• Reduced one-shot Campaign recipient limits, similar to trial workspaces

You can learn more about Campaign limits here: What are Email Campaigns recipient limits?

Updated on: 03/05/2026