Yes. You can test Weflow against a Salesforce sandbox in a separate Weflow workspace connected to that sandbox. When you go live, you connect a new workspace to production and set it up again. Weflow can't promote a sandbox configuration to production.
How Weflow works with a Salesforce sandbox
A Weflow workspace is created against one Salesforce org, whichever org it is pointed at. A sandbox and your production org are therefore two separate Weflow workspaces, each with its own configuration.
A sandbox workspace signs users in through Salesforce's sandbox login rather than the production login.
You do not create the sandbox workspace yourself: your Weflow CSM sets it up and shares a login with you.
Note: Nothing you configure in the sandbox workspace carries over to production on its own. Only teams, templates and recordings move, and Weflow's team moves them.
What you set up again when moving from a Salesforce sandbox to production
Part | In the sandbox | In production |
Weflow Salesforce packages | Installed in the sandbox | Installed again |
Integration user and permission set | Created in the sandbox | Created again |
Mail app for Google or Microsoft | Connected to the sandbox workspace | Connected again |
Teams and templates | Built in the sandbox | Copied by Weflow's team |
Recordings | Made in the sandbox | Can be moved by Weflow's team |
Learn more about the setup steps in Weflow Setup: Salesforce Package, Integration User and Mail App.
How to move from a Weflow sandbox workspace to production
Set up the production workspace: install the packages, connect the integration user and install the mail app against your production org.
Ask Weflow's team to copy your teams and templates from the sandbox workspace to production, and to move any sandbox recordings you want to keep.
Switch off Activity Capture and Conversation Intelligence in the sandbox workspace before the production workspace goes live.
Once production is live, Weflow's team deletes the sandbox workspace on request.
Note: Do not run Activity Capture or Conversation Intelligence in both workspaces at once. Running both against the same users causes conflicts.
