Skip to main content

Releases FAQs

Find answers to common questions about Fin releases, Fin Main, publishing, testing, conflicts, and permissions.

Use this article to understand what Fin Main and the Publish to Fin Main and Save to Fin Main buttons mean, decide whether you need releases, find and test a release, publish a release, fix a conflict, remove an item from a release, and check whether you can manage releases with the API. Fin Main is the live version of Fin that your customers talk to.


Fin Main FAQs

Does "Fin Main is Live" mean Fin is answering my customers?

"Fin Main is Live" doesn't mean Fin is answering your customers. The Live label shows that Fin Main is your live version of Fin, as opposed to a release you're still working on. To check whether Fin is set live on your channels, go to Fin AI Agent > Deploy.

What does Publish to Fin Main mean?

Publish to Fin Main makes your changes live in Fin straight away. You see the Publish to Fin Main button when you edit content, guidance, escalation guidance, or procedures in Fin Main. Publish to Fin Main doesn't publish a release. To publish a release, open the release and click Release.

What does Save to Fin Main mean?

Save to Fin Main saves your changes in Fin Main without making them live. On guidance, escalation guidance, and procedures, you see Save to Fin Main when Availability is off for every Fin agent. 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 Fin Main doesn't mean Fin is turned off for your workspace, only that Fin isn't using that item.

What are releases, and do I need them?

Releases let you group changes to content, guidance, escalation guidance, procedures, and skills, test them together, and publish them when you're ready. Releases are optional, so if you don't need them, keep publishing your changes to Fin Main as usual.

Are releases new, and are they available to everyone?

Releases are new, and they became available to everyone on November 5th, 2026. Releases are no longer in beta, so every workspace now sees the Publish to Fin Main and Save to Fin Main buttons and the release switcher.


Using releases FAQs

Why don't I see a Releases tab?

Releases don't have their own tab. You find releases in the release switcher at the top left of the navigation in Fin AI Agent. Releases currently work with the Service agent only. To create your first release:

  1. Go to Fin AI Agent.

  2. Select Service from the dropdown at the top of the navigation, then select Fin Main beneath it.

  3. Click Create release.

After you create a release, you're working inside it. The app changes color, and the release switcher shows the release's name.

Where do I find my release drafts?

You find your release drafts in the release switcher at the top left of the navigation in Fin AI Agent. Click the release switcher and select your release to open it. Fin Main is labeled Live at the top of the list.

Do my changes save automatically inside a release?

Changes you make inside a release don't save automatically. To keep your work in a release, click Save to release before you refresh the page, leave the editor, or switch to Fin Main. Saving to the release doesn't make your changes live. They go live only when you publish the release or start a rollout.

Important: If you refresh the page or navigate away from the release editor before you click Save to release, you lose any unsaved edits. Click Save to release often while you work.

How do I know whether I'm working in a release or in Fin Main?

You can tell whether you're working in a release or in Fin Main from the release switcher at the top left of the navigation. It shows the name of the release you're in, or Fin Main. Inside a release, the app has a colored background and your changes save to the release. In Fin Main, the app appears in grey and published changes go live straight away.

To go back to Fin Main, click the release switcher and select Fin Main, which is labeled Live at the top of the list.

What can I add to a release?

You can add, edit, and delete these items in a release:

  • Content, such as snippets and articles

  • Guidance

  • Escalation guidance

  • Procedures

  • Skills

Data connectors, attributes, and workflows aren't supported in a release yet. Make changes to those in Fin Main.

Why is Publish to Fin Main greyed out on guidance or escalation guidance?

Publish to Fin Main is greyed out on guidance or escalation guidance when Availability is off for every Fin agent. The Availability button at the top of the guidance reads Disabled, and the main button reads Save to Fin Main instead of Publish to Fin Main.

Guidance with Availability set to Disabled shows a greyed-out Save to Fin Main button.

Guidance editor for VIP Account Handling with the Availability button reading Disabled next to Everyone, Chat, Email, and Any time, and the Save to Fin Main button greyed out at the top right.

To turn on Publish to Fin Main for guidance or escalation guidance:

  1. Open the guidance or escalation guidance in Fin Main.

  2. Click Disabled at the top of the guidance.

  3. Turn on the toggle for at least 1 Fin agent, for example Service agent.

  4. Click Publish to Fin Main.

After you turn on Availability, the button reads "Enabled for service" and Publish to Fin Main turns green. Clicking Publish to Fin Main makes the guidance live for that Fin agent straight away.

Guidance editor for VIP Account Handling with the Availability button reading Enabled for service, its Availability menu open with the Service agent toggle turned on, and the Publish to Fin Main button active in green.

If Availability is already on and Publish to Fin Main is still greyed out, check whether you're working inside a release, or whether your role can only propose changes. Teammates with Can view configuration and propose changes in a draft release can save changes to a release draft but can't publish.

How do I turn off guidance, escalation guidance, or a procedure?

To turn off guidance, escalation guidance, or a procedure without deleting it, turn off its Availability for every Fin agent in Fin Main:

  1. Open the guidance, escalation guidance, or procedure in Fin Main.

  2. Turn off Availability for every Fin agent.

  3. Click Save to Fin Main.

After you save, the item stays in your workspace, but Fin doesn't use it. To turn it back on, turn on Availability for at least 1 Fin agent and click Publish to Fin Main.

Important: Don't use a release to turn off guidance, escalation guidance, or a procedure that's live in Fin Main. If you click Remove from release on an item that's already live in Fin Main, that item is deleted when the release is published.

How do I test a release before it goes live?

You can test a release before it goes live with Preview, Evals, and A/B tests, without changing Fin Main:

  • Preview: Fin answers with your release's changes applied, so you see how it would respond to customers. Preview conversations don't touch Fin Main and aren't charged.

  • Evals: Fin runs your saved test conversations using the release's version of your content, guidance, procedures, and skills, with a pass or fail result for each one.

  • A/B test: When you roll out the release, you can compare Fin Main with the release on real conversations before you publish it to everyone.

How do I publish a release?

To publish a release, open the release and click Release. Publishing a release puts every change in it live on Fin Main together:

  1. Click the release switcher at the top left of the navigation and select your release.

  2. Click Release at the top right.

  3. Select Publish to Fin Main to put every change live for all customers straight away, or Roll out gradually to run a gradual rollout or an A/B test first.

Before the release goes live, a Publish release panel shows how many changes will be published and lists each one. After you publish, the changes become part of Fin Main, and you can't edit the release anymore.

Note: Don't switch to Fin Main to publish a change you saved in a release. Fin Main doesn't have your release changes, so publishing there leaves them behind. To publish a release, you need the publish level for every kind of change in it.

Should I use a gradual rollout or an A/B test?

Whether you use a gradual rollout or an A/B test depends on whether you want to adjust the rollout as you go or need a statistical result. Both send a share of conversations to your release while the rest stay on Fin Main:

  • Gradual rollout: Try a change on a share of conversations, watch how it performs, and raise or lower the share while it's running.

  • A/B test: Get a statistically significant result on the metric you're measuring. You can't change the traffic split after an A/B test starts, but you can end it at any time.

Can two releases roll out at the same time?

Yes. Each release runs one rollout or A/B test at a time, but different releases can roll out at the same time, as long as they don't change the same item. If an item in your release is already in a live rollout or a scheduled publish in another release, you can't start your rollout until that one is completed or stopped. You can also keep several draft releases open at once.

How do I remove an item from a release?

To remove your changes to an item from a release, click Discard changes on the release overview. What happens next depends on whether the item already exists in Fin Main:

  • 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.

  • A new item you created inside the release: Discard changes deletes the item, because it was never in Fin Main.

Important: Remove from release isn't the same as Discard changes. If you click Remove from release on an item that's already live in Fin Main, that item is deleted when the release is published.

How do I fix a conflict between a release and Fin Main?

A conflict between a release and Fin Main happens when an item in your release is changed in Fin Main after you added it, or when another release that edits the same item is published. While there's a conflict, you can't publish the release or start a rollout. To fix a conflict:

  1. Open the release and find the item marked Has conflicts.

  2. Click the item to see what changed. Under Body, the live version from Fin Main is struck through in red, and your release version is shown in green.

  3. Copy your release version from the green text. Discarding removes your edits from the release, so copy them before the next step.

  4. Click Discard changes on the item to remove your edits from the release.

  5. Add the item back to the release. It now starts from the latest version in Fin Main.

  6. Paste the edits you copied, then click Save to release.

When you click an item marked Has conflicts, the release shows a comparison of the live Fin Main version and your release version.

Edited public article panel inside a release, with the Body section open. The live Fin Main text, VERSION 3, is struck through on a red background, and the release text, VERSION 2, is shown on a green background.

Note: There isn't a way to resolve conflicts automatically yet, so you need to reapply your changes manually. Don't use Remove from release to fix a conflict.

Can I schedule a release to publish at a specific date and time?

You can't schedule a release to publish at a specific date and time yet. To publish a release, open it and click Release when you're ready, then select Publish to Fin Main or Roll out gradually.

Can I scope a release to a brand?

You can't scope a release to a brand. To test a release with a group of customers first, open the release, click Release, and select Roll out gradually to release your changes to a percentage of conversations or a specific audience.

To keep content for one group of customers permanently, use the audience settings on the content instead of a release.


Releases API and MCP FAQs

Can I create Fin releases with the API or MCP?

You can't create Fin releases with the Intercom REST API, because releases don't have public API support yet. If your workspace has Fin Operator, you can manage releases from your own AI tool instead. Connect the tool to the Intercom MCP server, then ask Fin Operator to create a release, save changes to it, check it for conflicts, and roll it out or publish it.

To manage releases with Fin Operator from your AI tool, you need:

  • Fin Operator in your workspace. Fin Operator is included in the Pro add-on.

  • An OAuth connection to the Intercom MCP server. Bearer token connections don't get the Fin Operator tools.

  • Permission to use Fin Operator. Fin Operator follows your permissions, so you can only do what you could do in the release yourself.

  • A US or EU hosted workspace. The Intercom MCP server isn't available for AU hosted workspaces yet.


💡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?