What happened to Fin, formerly Intercom, after Salesforce bought it

A service director hears that Salesforce bought Fin and tells the steering group that every Service Cloud org now includes it. The rollout plan is a date, a login announcement, and a containment rate copied from a slide. Support asks which queue disappears on that date. Nobody can say. The room agrees the rate can stay until the denominator is found. That agreement is the problem. The rate has no denominator, and the close did not put Fin into an org that never bought it.

The sentence to read is the investor release: "Salesforce today announced it has completed its acquisition of Fin, formerly Intercom, an industry-leading customer agent company." "Today" in that sentence is the day of the release. The completion date is 10 September 2026. Fin, formerly Intercom, is the company named. The phrase in the quotation that praises the company stays inside the quotation. It is not repeated here as a description. The description that will stand is narrower: a customer-agent platform, formerly Intercom, acquired, still serving its existing customers as part of AI Labs, and not assumed present in every service org.

Fin’s customer-agent platform joined Salesforce. The release says Fin will keep serving its customers as part of AI Labs. Those clauses do different jobs. Completed: the deal is done. Joined: the platform came into Salesforce. Keeps serving its customers, as part of AI Labs: the customers Fin already has are still to be served, under that part of Salesforce. None of those clauses says that a Service Cloud org which never bought Fin woke up on 10 September with Fin switched on. Fin is not automatically inside every Service Cloud org. If it cannot be found in an org, that absence is consistent with this source. It is not a hidden menu to file a ticket to reveal.

#What did the 10 September 2026 release actually complete?

Salesforce owns Fin. The completion on 10 September 2026 is the ownership fact. The release’s "formerly Intercom" is part of the same fact, so a search that only says Intercom is still this company. Formerly Intercom is the name history the release uses. People will search both names for years. A contract, an invoice, and an admin login may still say Intercom, or Fin, or both. Follow the paper that was signed. Do not follow a headline into a cutover that has not been offered.

A good answer sounds like the release dated 10 September 2026, Fin described as formerly Intercom, the platform described as having joined Salesforce, and the next sentence kept as written: Fin will keep serving its customers as part of AI Labs. The person announcing can say the praise inside the quotation is not a claim being adopted.

A bad answer sounds like the deal completed, so every service org includes it, and AI Labs is the menu where an administrator enables it for the whole company. AI Labs is the part of Salesforce the release uses for where existing customers are served. It is not a description of a setup menu. Do not tell an administrator to look under AI Labs for a switch that enables Fin for the whole company. The release does not say that switch exists. Why Salesforce acquired Fin, on this source, is no wider than what the release says the company is and what it says happens next. Do not add a motive essay. Why the company sold is not a statement available here. A founder profile is not a source.

#Which customers keep being served, and which orgs are not included?

Owning the company does not own every service conversation already running. A Service Cloud agent already configured, and Fin, are two designs until someone writes down which one owns the conversation. The acquisition does not pick the winner. A briefing that says "Salesforce owns it, so our bot is now Fin" has skipped that writing. The bot has the name and the contract it had the day before, unless the contract changed.

Impact splits. Fin’s existing customers are the ones the release says will keep being served. Everyone else’s Service Cloud org is not automatically included. If the organisation is in the first group, the questions are contractual: names on the invoice, who supports the account, what changes and what does not. If it is in the second group, there is no Fin rollout to announce. Do not announce one because the close date has passed.

A good answer sounds like a named reader of the contract who can say whether Fin, or Intercom, appears on it, and a separate statement that existing Fin customers continue as part of AI Labs. Those two facts are allowed to both be true. The mistake is treating them as one org.

A bad answer sounds like every Service Cloud customer has been included, and every Fin customer has been moved onto a different bot. Neither force is in the release. Do not tell Fin customers they have been forced onto a different bot. Do not tell Service Cloud customers they have been forced onto Fin. The release says existing customers keep being served. That is the opposite of a shutdown notice for those customers. It is still not a promise about an org that is not one of those customers.

#Which date would switch an org on, if any date does?

The date is 10 September 2026. The release says "today" because that was the day it was published. "When did Salesforce acquire Fin" is that day. A timeline is that day, plus the statement that existing Fin customers continue as part of AI Labs. There is no shutdown, no forced cutover, and no day on which every org is switched on to add from this source.

A good answer sounds like 10 September 2026 as the completed acquisition, and any "all service orgs" milestone either deleted or labelled as invented. Do not backfill a rumour date and call it the close. The close is the completed acquisition on that day. The date does not retire Intercom as a word on old invoices. Formerly, in the release, is the corporate naming. Paper may lag. Chasing a rename on a contract is a legal task. It is not evidence that a product in use has moved, and it is not evidence that a product never bought has arrived.

A bad answer sounds like "went live for everyone on 10 September". Live, for the deal: yes, the acquisition completed. Live, in every Service Cloud org: no, not on this source. If a workshop timeline has an all-service-orgs milestone the week after, that milestone is internal only if someone invented it. Do not attribute it to the release. A plan that says "turn Intercom off on 10 September" needs a contract that says that. The release does not.

#Where a price or a containment rate would have to come from

The cited page does not publish a purchase price or a licence fee. How much Salesforce paid for Fin, how much it was sold for, and the acquisition price are not here. Do not supply them from a clip or a memory. There is no figure to round. There is no statement that Fin became free inside Service Cloud. A free trial is not established by the completion sentence. Do not tell a service director that the close included a trial for every org. If a commercial offer exists, it is on a document that is not the source here, or it is on the order form. Read that document. Do not let the release stand in for it.

A good answer sounds like finance told the price was not published, and the steering pack left with no percentage. A containment rate is not a price, and it is also not in this source. People put a rate in the business case because a price was refused and they still want a number. Refuse the rate as well. No containment rate. A conference slide is not a denominator.

A bad answer sounds like a percentage copied from a slide about a company the organisation may not even be a customer of, offered as the result of the acquisition. Spending, in a clip, is the same gap as the deal price. A DVD, a Reddit thread, a YouTube video, a TikTok, a course, a book, or a certification is not a source for the date, the price, or a shutdown. A one-minute video that states a containment rate is not a source, and the rate would still be refused if it had been watched. Your own measured handoffs, later, might become a study. They are not a number to borrow on 10 September and call a result of the acquisition.

#Which design owns the conversation?

Fin is not automatically inside every Service Cloud org. Say that before AI Labs is mentioned, or the room will hear AI Labs as a menu they already own. Existing Fin customers continue, as part of AI Labs. A company that has only Service Cloud has a Service Cloud contract. Fin and the Service Cloud agent already running stay two designs until the writing exists. A single login announcement on 10 September is not a design. It is a date with an assumption attached.

A good answer sounds like a written choice, made by service operations, of which design owns the conversation, which intents exist, and what the handoff is, with the containment cell left blank. If the organisation is already a Fin customer, the first questions are the ones the release leaves to the contract: what continues, what the invoice will say, and who is called. If it is not, the first question is whether anyone has offered Fin at all. Until they have, there is nothing to roll out.

A bad answer sounds like the agent already running can be renamed Fin because the close was in the news, and the target can be typed in so the steering pack has a goal. If a measurement of how often a conversation is resolved without a person is made later, that measurement needs a definition, a queue, and a period. It does not need a number copied from a slide. Inventing the rate is how a rollout gets funded before anyone has written which bot owns the conversation. There is no end date for Fin in this source. Do not invent a sunset for Fin, and do not invent a sunset for the Service Cloud agent already run, on the strength of the close. Intercom, as a name people still type, was not given a shutdown day here either. Formerly is not "switched off on this date". Worth is not a containment rate and not a verdict. The record can say the deal completed, who is served, and who is not automatically included. That is as far as it goes.

Leave the steering pack with the lines that can be checked, and with no percentage. Owned by Salesforce. Completed 10 September 2026. Formerly Intercom. Existing customers continue as part of AI Labs. An org is included only if its contract says so. Anything past those lines is a design that has not been written yet. A roadmap that enables Fin for all service teams on a date someone chose is an internal plan. Do not stamp the release’s date on it and call it theirs.

#What to do with the answers

Read the five as a set. Specific answers mean the room can tell a completed acquisition from a rollout. General answers mean the decision rests on a shared feeling that a close date switches a product on everywhere, which the release does not say.

Which design owns the conversation, which intents exist, and what the handoff is are set out in Fin, formerly Intercom, after the acquisition closed. That work will not invent the rate either. If the organisation is not a Fin customer, it is legitimate to finish here and stop. Not every Service Cloud question is a Fin question. A conversation about the agent already running can stay on that agent. Do not rename it Fin because the close was in the news.