Skip to main content

Getting started with Releases

Learn what releases are, how they keep changes away from live conversations, and when to use one to prepare, test, and roll out Fin changes.

Use this article to understand what releases are, how they keep Fin changes separate from live conversations, and when to use one to prepare, validate, and roll out changes.


What are releases?

A release is a dedicated workspace where you prepare and deploy changes to your Fin configuration. Instead of publishing edits straight to your live Fin configuration, you can add changes to a release. Nothing in a release affects Fin Main, the live production version of Fin, until you publish the release or start a rollout.


Why use releases?

Content, guidance, procedures, and other configuration all work together, so even a small update can have unexpected effects. Releases give you a structured way to manage those changes. With a release, you can:

  • Bundle related changes into a single release.

  • Collaborate with teammates before changes go live.

  • Validate changes using Preview and Evals before deployment.

  • Deploy with confidence by publishing immediately, rolling out gradually, or running an A/B test against Fin Main.


How do releases work?

A release moves through 4 stages, from preparing changes to shipping them:

  1. Create the release. Give it a descriptive name that says what's changing. The name is for your team only, and Fin doesn't use it.

  2. Add changes. A release can hold content, guidance, escalation guidance, procedures, and skills. You can add, edit, and delete these items inside the release.

  3. Validate the changes. Use Preview to test how Fin behaves with your changes applied, and run Evals (themed groups of simulated test conversations) to check the release hasn't broken Fin's behavior elsewhere.

  4. Ship the release. Publish it to Fin Main for all conversations, roll it out gradually to a percentage of conversations or a specific audience, or run an A/B test that splits conversations between the release and Fin Main.

Because changes are saved to wherever you're working, the release switcher tells you whether you're editing a release or Fin Main. A change saved inside a release never reaches customers on its own.


When should I use a release?

Use a release whenever a change is large enough that you want to test it before customers see it. These are common cases:

Case

How a release helps

Prepare for a product launch

Update articles, add guidance, and create a procedure for the new feature in one release, then publish everything together or roll it out gradually first.

Improve how Fin answers customer questions

Group your content changes into a release and compare the new configuration against your live setup to measure whether answer quality improves.

Move from answering questions to resolving them

Introduce a procedure that lets Fin process refunds end-to-end, then use a phased rollout or A/B test to compare it with your existing content-based experience.


What happens when a release conflicts with Fin Main?

If an item in a release is changed in Fin Main after you added it to the release, the release detects a conflict. While a conflict exists, you can't publish the release or start a rollout until you fix it. A conflict can also happen when two releases modify the same item: their changes aren't combined, and publishing one release causes a conflict in the other.


Who can propose and publish a release?

Working with releases depends on 2 permission levels for each kind of change in the release:

  • Propose: Teammates can make changes in a draft release, but can't set them live.

  • Publish: Teammates can publish changes directly to Fin Main, either one at a time or in a release. This includes gradual rollouts and A/B tests.

To set a release live, a teammate needs the publish level for every kind of change in it. You set the propose and publish levels for each area when you edit a teammate's permissions in Settings.

Which permissions control releases for Knowledge?

The Knowledge section of a teammate's permissions has one setting for content (snippets, internal articles, and syncs) and one for help center articles. Each setting has 3 options:

  • Content: Can view content; Can view content and propose changes in a draft release; Can view content and publish changes directly to main (individually or in a release).

  • Help center articles: Can view help center articles; Can view help center articles and propose changes in a draft release; Can view help center articles and publish changes directly to main (individually or in a release).

The Knowledge section of a teammate's permissions in Fin, showing the propose and publish options for content and for help center articles, with the publish option selected for both.

Which permissions control releases for Fin AI Agent & Automation?

The Fin AI Agent & Automation section has one setting, Permissions for workflows and all Fin configuration. It covers Fin configuration such as guidance, escalation, and procedures, and it has 4 options:

  • Doesn't have access to view configuration

  • Can view configuration

  • Can view configuration and propose changes in a draft release

  • Can view configuration and publish changes directly to main (individually or in a release)

When you select the publish option, an Inbound workflows & Fin configuration checkbox appears beneath it.

The Fin AI Agent & Automation section of a teammate's permissions in Fin, showing the four configuration options with the publish option selected and the Inbound workflows & Fin configuration checkbox ticked.


FAQs

What is Fin Main?

Fin Main is your live production version of Fin. Changes in a release don't affect Fin Main until you publish the release or start a rollout.

Can a teammate with the propose level publish a release?

A teammate with the propose level can't publish a release. They can make changes in a draft release, but can't set those changes live.

Do changes inside a release reach customers before I publish?

Changes inside a release don't reach customers before you publish the release or start a rollout. They're saved to the release, and Fin Main stays unchanged until then.

What do Publish to Fin Main, Save to Fin Main and Save to release draft mean?

Publish to Fin Main saves your edit to Fin Main, and it goes live straight away. The button reads Save to Fin Main instead when your edit won't go live, and what controls that label depends on what you're editing:

  • Articles: the Publish to help center toggle. When it's off, the button reads Save to Fin Main, and the article is saved as Not published and disabled for Fin. Turn the toggle on to change the button to Publish to Fin Main. Fin availability doesn't change this label on articles.

  • Guidance, escalation guidance, and procedures: Availability. When Availability is off for every Fin agent, the button reads Save to Fin Main, and Fin doesn't use the item until you turn Availability on for at least one Fin agent and click Publish to Fin Main.

Save to release draft, in the arrow menu next to the button, saves your edit to a release instead. None of these buttons publishes a release.

What happens when I discard changes to an item in a release?

Discarding changes to an item in a release works differently depending on whether the item already exists in Fin Main. For an item that already exists in Fin Main, Discard changes undoes your edits in the release, and the item stays live in Fin Main as it is. For a new item you created inside the release, Discard changes deletes the item, because it was never in Fin Main.

Important: Clicking Discard changes on an item you created inside a release deletes it, including everything you built in it. To keep a new item, publish the release, or copy its content before you discard it.

How do I delete a release?

To delete a release, go to the Releases page in Fin AI Agent, hover over the release, click ..., then click Delete. Deleting a release doesn't change Fin Main, because changes in a release never went live.

Note: You can't delete a release that's running an A/B test or a gradual rollout, or one that's already published. The edit and delete options don't appear for those releases.

How do I edit a live procedure without changing what Fin uses?

To edit a live procedure without changing what Fin uses, save your edits to a release instead of to Fin Main. Open the procedure in Fin Main, make your changes, click the arrow next to Publish to Fin Main, and under Save to release draft, select a release or New release draft. Fin keeps using the live version until you publish the release.


💡Tip

Need more help? Get support from our Community Forum
Find answers and get help from Intercom Support and Community Experts


Did this answer your question?