Salesforce bought Fin, the old Intercom. Stay, but build your exit.

Three dated events, all confirmed by the companies themselves. Intercom renamed itself Fin on 12 May 2026, Salesforce signed a definitive agreement to acquire Fin for approximately $3.6 billion on 15 June 2026, and the acquisition closed on 10 September 2026.

• 12 May 2026, the rename. Intercom announced that the company would take the name of its AI agent. The Intercom name stayed on the customer service platform, the helpdesk your human agents log into, while the corporate identity moved to Fin.
• 15 June 2026, the agreement. Salesforce announced it would acquire Fin for approximately $3.6 billion, subject to customary purchase price adjustments.
• 10 September 2026, the close. Salesforce completed the acquisition, bringing Fin's platform, its AI team and a customer base of more than 30,000 companies into Salesforce. Salesforce positions Fin alongside Agentforce in its customer service AI portfolio, with Fin covering "rapid deployment on existing systems." The same release credits Fin with an average resolution rate of 76 percent across channels, a vendor figure rather than an independent benchmark.

That last phrase is the most useful thing in the announcements for a small team. Salesforce is describing Fin as the fast, works-with-what-you-have option and Agentforce as the deeply tailored enterprise option. That suggests Fin keeps its own identity for now. It does not tell you what Fin will cost in two years, and nobody outside Salesforce knows that yet.

Fin is not the only independent support AI being folded into a bigger platform this year, and it is not the first vendor change to force a support team's hand. Zendesk is switching off its legacy AI agents on 10 December 2026, which we covered in what to do about Zendesk's legacy AI agent removal. The pattern is the same each time: the product keeps working, and the terms around it move.

On published prices, Fin is the cheapest way to buy AI resolutions off the shelf. In our example month, the AI layer costs $990 on Fin, $1,500 to $2,000 on Zendesk and $4,000 on Agentforce's conversation pricing. The gap comes from what each vendor counts, not only from the rate.

The example is ours and it is illustrative, not client data: a 10-agent support team where 2,000 conversations a month reach the AI agent and the AI finishes 1,000 of them. We price only the AI layer on top of the helpdesk seats you already pay for, except in the Intercom row where seats and Fin come together.

Two caveats keep this honest. First, the Zendesk rate comes from third-party pricing trackers rather than a single Zendesk page, and Zendesk plans include a small allowance of resolutions per agent, so confirm your own rate before you compare. Second, Agentforce's action-based Flex Credit pricing can come in well under $2 a conversation if your conversations use only a few actions. We show the conversation model because it is the one Salesforce quotes for customer-facing agents.

The lesson is in the second column. Fin and Zendesk bill when the AI finishes something. Agentforce's conversation model bills when the AI shows up, including the half of conversations it hands to a human. That is why "stay and lock in the outcome model" beats "move to the Salesforce-native option" for a team that is not already on Salesforce.

Own your content, write down your terms, and measure your own resolution rate. None of it requires leaving, and all of it makes leaving a two-week job instead of a two-month one.

1. Export your help center and Fin's content sources. Keep a dated copy of every article, snippet and custom answer Fin draws on, outside Fin. Your content is what makes any support AI good. It should never exist in only one vendor's system.
2. Write your procedures down in plain language. Every workflow Fin runs, such as refunds, order lookups or plan changes, should exist as a written procedure your team could hand to a different agent. That document is your migration spec.
3. Measure resolution yourself. Track resolved conversations from your own helpdesk reports every month, not only the outcome count on the invoice. You need your own baseline to spot tripwire 3 and to compare any alternative fairly.
4. Get your rate in writing at renewal. Ask for the per-outcome rate, the definition of an outcome and the minimum commitment to be stated in the order form for the full term. A renewal is the one moment you have leverage.
5. Keep integrations outside the vendor where you can. Order lookups, CRM updates and ticket tagging that run through an automation layer such as n8n or Make can be pointed at a new AI agent in an afternoon. Logic buried inside one vendor's workflow builder cannot.
6. Pilot the alternative on a slice, once a year. Route one channel or one topic to your helpdesk's native AI for a month and compare cost per resolution. It keeps your numbers honest and your renewal conversation real.

Teams that have been through a forced vendor change before will recognise this list. It is the same stance we took when Bending Spoons bought Airtable: do not migrate on the news, record the numbers an acquirer tends to move, and make sure the vendor never holds the only copy of how your business works.