As Fin becomes a bigger part of your customer support, managing changes becomes more complex. Content, guidance, procedures and other configuration all work together, which means even small updates can have unexpected effects. Releases give you a structured way to manage those changes.

Releases let you safely prepare and deploy changes to your Fin configuration in a dedicated workspace. Instead of publishing edits directly to your live Fin configuration, every change is added to a release.

With Releases, you can:

A Release holds the changes. You add items to it, edit them safely, and remove anything you no longer want live with Fin as part of that Release. Nothing here touches your live Fin until you go live or run an experiment.

To create your first Release, go to Fin AI Agent > select "Service" from the dropdown at the top of the nav and beneath that dropdown click on "Fin Main". Click on Create Release.

Give it a descriptive name and description — something that says what's changing, like "Refund processing changes". The description is internal for you to easily identify what's in the Release.

Now you can add changes to your Release. For example, select "Content" to test a help article, "Guidance" or "Escalation Guidance" to test behavioral rules, or "Procedure" to test a multi-step flow.

Once you've added a change, it will appear in your list of changes in the Release.

You can easily see the exact changes that were made per item by clicking on the item and viewing the diffs:

To add/edit/delete more items as part of a Release, inside the Release, click on Add more changes. You can add, edit, and delete the following item types inside a Release:

The Release overview lists every item in the Release, so you can easily overview it and make further changes if needed.

Each item in the Release overview is marked with an indicator showing the type of change:

If you want to switch to different Releases, simply use the switcher on the top left of the page in the nav. You can also create new Releases from there and switch to "Main Fin", which is your live production version of Fin.

Before anything reaches a live conversation, preview the release to see exactly how Fin behaves with your changes applied.

Preview tells you how Fin handles one question you type yourself. Evals let you run a whole set of saved test conversations against your Release and get an automatic pass/fail result for each one — so you can check a change hasn't broken Fin's behaviour elsewhere before it reaches customers.

An Eval is a themed group of Simulations (realistic, multi-turn test conversations with criteria you define). When you run one against a Release, every Simulation runs with your Release's changes applied instead of your live Fin Main configuration. Nothing touches live conversations.

For more on how Evals, Simulations and scoring work, see Fin Evals [beta].

To get started, open the Release you want to test. On the Release overview page, find the Evals section and click See Evals.

Pick the Eval you want to run — either an existing one you've built up as a regression suite, or a new one created for this change.

Run it. Every Simulation in the Eval runs against your Release, and you'll get back a pass/fail result, the full conversation transcript, the event log showing Fin's thinking, and the outcome for each Simulation.

Review any failures, make further changes inside the Release, and re-run the Eval to confirm the fix.

To set a release live or start and end a rollout, a teammate needs the "Can manage Automation settings and inbound Workflows" permission.

When your changes preview well, you decide how they reach customers.

Click Rollout release on the Release overview page, then choose one of two options: Merge to main to publish immediately to all customers, or Roll out gradually to run a phased rollout or an A/B test before it goes to everyone.

Merging to main publishes your changes to Fin Main immediately, applying them to all relevant conversations. Choose this when you're confident in the change and want it in effect everywhere.

Select Roll out gradually to test your changes against a share of conversations before committing fully. Choose between two rollout types:

After choosing Phased rollout, configure:

Click Start phased rollout to begin — the rollout starts immediately and appears under Active rollout in the Release's Rollouts tab.

Once a rollout is running, open the Release's Rollouts tab. Active rollouts appear under Active rollout, and completed ones under Past rollout.

Here's what the results of a phased rollout look like. You can easily drill into the conversations that were touched by the release and compare them to the ones in Fin Main for spot checking.

Here's what the results of an a/b test rollout look like. You can easily see:

Significant results:

Inconclusive results:

Regressing results:

You can also create your own custom reports. Simply add Release and Experiment filters to custom reports in the Reports section to compare performance across experiment variants.

To stop a Release rollout affecting customers, end the rollout. New conversations immediately return to your current live setup.

Once a release has been merged into Fin Main, you can roll back its changes from the release itself.

This still uses each item's version history in Fin Main — the release just takes you there directly for every item it changed, instead of you finding and opening each one yourself.

To roll back changes from a merged release:

Fin for Salesforce connects to more than one Salesforce organization. One workspace can hold a live organization and one or more test organizations. Each connected organization is an environment.

You can already scope a workflow to one environment. Open Deploy, open a workflow such as Salesforce cases, then set Environment on the trigger. The default is All environments.

That picker controls which workflow runs. It does not change the content, the guidance, or the procedures that Fin reads. Fin reads the same live configuration in every environment.

A release changes the configuration itself. A release pins a different version of each entity in it, for one audience only. The entity keeps its identifier, so you do not copy it. One audience and one percentage control the whole group, and you can roll back.

Fin writes the environment onto each conversation. The environment is a system-defined conversation attribute. An audience rule can read this attribute.

A release rollout takes one audience. The rollout applies the release only to conversations that match the audience.

Open Connect. Find the organization in Connect Fin to a test organization. The status must be Connected.

Open Settings. In the Data group, select Audiences.

Create a new audience. Give it a name that holds the environment name.

Select Add audience rule. Select Environment in the Conversation data group.

Select the environment that you want to test. Then select Save.

Open your release. Select Rollout release. Then select Roll out gradually.

Keep the type as Phased rollout.

In Audience, select the audience from step 3.

In Traffic split, move the slider to 100%. The panel must show 100% Release (treatment) and 0% Main Fin (control).

Select Start phased rollout.

Start a new conversation in the test organization. Fin answers with the configuration in the release.

Start a conversation in the live organization. Fin answers with Fin Main.