Intercom becomes Fin and moves to Salesforce: what changes for your support team
Renamed in May, a $3.6B acquisition announced in June, Fin metrics recomputed since. What's settled, what isn't, and the three decisions not to rush.
In four months, the tool your support runs on changed its name and its owner. Intercom has been called Fin since May 2026, and Salesforce announced its acquisition on 15 June for roughly $3.6 billion. Here's what's established, what isn't, and what it concretely means for a support team in 2026.
The timeline, without the noise
| When | What |
|---|---|
| May 2026 | Intercom renames itself Fin, aligning the company name with its AI agent. |
| 15 June 2026 | Salesforce announces the acquisition for roughly $3.6 billion in cash. |
| Salesforce fiscal 2027 | Expected close, subject to the usual regulatory approvals. |
| Announced, undated | Fin folded into Agentforce, Salesforce's AI agent platform. |
Two numbers are circulating that deserve care. The 30,000 customers figure covers the whole base, not AI agent users alone. And the 76% "resolved without a human" rate is vendor communication, computed on a scope the vendor picks: it's an argument, not a measurement of your instance.
What doesn't change today
An announced deal isn't a closed deal, and a closed deal isn't a migration. Your workspace behaves identically, your integrations hold, your data stays where it is. Packaging and pricing changes typically land in year two and three after an acquisition, not in the weeks following the announcement.
Worth noting if you aren't a Salesforce customer: Fin is built to work with existing helpdesks, including those of direct Salesforce competitors such as Zendesk. Nothing suggests that compatibility is in question, and Salesforce has said it will keep selling the Intercom helpdesk.
What already changed, and few people noticed
The real operational change of the period isn't the acquisition, it's the revision of Fin performance metrics. The definition of a resolution doesn't move, but conversations flagged "Fin Constrained" now drop out of the resolution rate denominator.
Direct consequence on your reports
Your resolution rate mechanically went up without Fin's quality changing by a point. If you track that metric in a monthly report, you have a break in series in the middle of your charts. Check the date before crediting the gain to your knowledge base.A useful reminder while we're here, because the confusion is common: a resolution counts when the customer confirms, or leaves the conversation without asking for more help, and only after Fin has actually answered. An exchange of pleasantries is not a resolution. We break down what that means on the invoice in our analysis of the $0.99 per resolution.
The three questions we get asked
"Should we migrate?" Not on the basis of an announcement. A helpdesk migration costs weeks to months, breaks the conversation history that feeds your analysis in the first place, and exposes you to the same risk at the next vendor. The question is fair if you were already rubbing against the product or the price, in which case the acquisition is a calendar trigger, nothing more.
"Will prices move?" Probably, but not tomorrow, and not necessarily upward on every line. The $0.99 per outcome model holds as we write. The real risk isn't the unit price, it's repackaging: features included today sliding into a higher tier. That's what to watch, not the sticker.
"What happens to the Intercom helpdesk?"Salesforce has said it will keep selling it. Medium term, product attention will logically go where it serves Agentforce. Without a public roadmap, everything else is speculation, and we won't be doing any.
What we'd do this quarter
- Freeze a snapshot of your metrics. Export twelve months of resolution, reopen and CSAT figures, keeping the date of the metrics revision. Without a reference outside the platform, you won't be able to separate a change of calculation from a change of performance.
- Check your data can get out. Working API export, conversations and notes included, before the question becomes urgent. This isn't an exit plan, it's dependency hygiene.
- Reread your contract. Term, auto-renewal, notice period. A renegotiation is prepared before, not during.
- Don't freeze your projects. The most expensive mistake we see is waiting: six months of support work suspended pending clarity, over a change that won't be visible for a long while.
The heart of it isn't who owns the tool. It's keeping a measure of your answer quality that doesn't depend on the vendor's calculation, especially when that calculation has just changed. That's exactly what ResponZ quality scoring does: one score per answer, on your criteria, independent of the rate shown in the dashboard.