Fin, formerly Intercom, after the acquisition closed

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 target containment rate copied from a slide someone saw at a conference. Support operations asks which queue disappears on that date. Nobody can say. The rate has no denominator.

Take the rate off the plan. Then separate two facts that the announcement does allow from the one it does not. Fin's platform joins Salesforce. Fin continues to serve its customers. Your org is not automatically one of those customers.

#What completed on 10 September 2026

The investor release says: "Salesforce today announced it has completed its acquisition of Fin, formerly Intercom, an industry-leading customer agent company." Salesforce completed that acquisition on 10 September 2026. Fin, formerly Intercom, is the company named. The same release says Fin's customer agent platform joins Salesforce, and Fin will continue to serve its customers as part of AI Labs.

Three clauses, and they do different jobs. Completed: the deal is done as of that date. Joins: the platform is coming into Salesforce, not remaining a permanent outsider with no relationship to the company. Continues to serve its customers, as part of AI Labs: the customers Fin already has are still to be served, under that part of Salesforce. None of the three clauses says that a Service Cloud org which never bought Fin woke up on 10 September with Fin switched on.

Formerly Intercom is a name change in the corporate sense the release uses. People will search for both names for years. Your contract, your invoice, and your admin login may still say Intercom, or Fin, or both. Follow the paper you signed. Do not follow a headline into a cutover you have not been offered.

AI Labs is the part of Salesforce the release uses for where Fin will serve those customers. It is not a description of your org's setup menu. If you cannot find Fin in your org, that absence is consistent with this source. It is not a provisioning ticket you should file on the assumption the menu is merely hidden.

#Not every Service Cloud org includes Fin

Say this to anyone who writes the rollout note. The acquisition does not put Fin in every Service Cloud org. Service Cloud is a product family many companies already run. Fin is a customer-agent platform that joins Salesforce and continues to serve its own customers. Overlap is something you establish from contracts, not from a press date.

Ask three questions before anyone announces a change to agents on the service desk.

Does your company have a Fin or Intercom contract today. If yes, you are in the set of customers the release says Fin will continue to serve. Your questions are about continuity, data, and how that service sits beside the Salesforce org you also run. If no, you do not become a Fin customer by owning Service Cloud. A wish to become one is a purchase conversation. It is not a weekend configuration.

What does the contract say you can do with conversations, contacts, and articles. Continuity is not permission to copy every transcript into a Salesforce object because the logos now share a parent. Copying is a project. It needs a purpose, a retention rule, and a field list. The release does not do that project for you.

Who is the admin. Fin's admin and the Salesforce admin may be different people. A rollout email that tells Salesforce admins to "enable Fin" will create tickets they cannot close. Name the admin of each estate. If you have only one estate, say which one it is.

A partner who draws a single box labelled Service Cloud, with Fin inside it, for a company that has never held a Fin contract, has drawn the mistake. Ask them to show the contract. If they cannot, the box comes off the slide.

#Do not invent a containment rate

Containment is a ratio: conversations that never reach a person, divided by conversations you chose to count. The release does not publish your ratio, and it does not publish a ratio you are allowed to borrow. Do not invent one. A conference slide, a competitor's claim, and a round number that makes a business case tidy are the usual sources. None of them is your denominator.

If you want a rate later, define it before you announce it. Which channels. Whether a customer who returns within a day counts as contained. Whether a handoff you forced still counts. Who signs the definition. Until that page exists, the business case can talk about scope. It cannot talk about a percentage. A percentage without a definition will be repeated by people who did not attend the workshop, and you will not be able to walk it back cleanly.

There is a worse version: a target given to the support team as a performance number before the agent is even in the pilot. People then steer towards the target. They close conversations the customer did not consider finished, or they refuse handoffs the policy requires. You will have manufactured the rate and damaged the queue. Leave the number out until you have measured the definition you wrote, on a pilot you can stop.

This page will not suggest a "good" containment figure. Suggesting one would be the invention the brief forbids. Your figure, if you ever have one, comes from your traffic and your definition.

#What to scope if you are already a Fin customer

You are not required, by this source, to migrate off Fin. The release says Fin will continue to serve its customers. A crash migration into Service Cloud, justified only by the close date, throws away that sentence. Plan continuity first. Change second, and only where you have a reason.

Customers. Which brands, which regions, and which products Fin fronts today. A global cutover diagram that ignores a region still on a different desk will double-reply or drop a queue. List the desks.

Intents. The requests Fin is allowed to finish, and the requests it must hand to a person. Billing disputes, account access, and anything that changes a contract belong on the handoff list until a person has agreed otherwise. An intent you have not named is not an intent the agent should invent on the day of the close.

Handoff. The queue, the fields the person needs, and whether the transcript travels with the case. A transcript can carry data the Salesforce user was never meant to see. Decide that with the same care you would use for any other paste into a case comment. The close does not make the paste safe.

Knowledge. Which articles Fin may quote, who updates them, and what happens when an article is wrong. Joining Salesforce does not merge your article base with a Salesforce knowledge base by itself. If you want one store, that is a project with an owner. If you keep two, write which one the agent uses, so you do not debug the wrong set.

Identity. What the agent may read about the customer in Fin, and what it may read from Salesforce if you connect them. A connection is a grant. A helpful connection that can see every case, every note, and every attachment is a broad grant. Name the objects. Test a customer the agent must not discuss.

What you will not do in the first phase. A full historical load of every conversation into Salesforce. A single containment target. A promise that Service Cloud users who are not Fin customers will see the same agent on Monday.

#What to scope if you are not a Fin customer

Your scope is smaller, and it should stay smaller until you buy something. Confirm you have no Fin or Intercom tenant hiding in a regional contract. Confirm marketing or support did not start a trial. A trial is still a tenant. It may hold conversations. Find it or record that you looked.

Then stop. Do not build Salesforce objects "ready for Fin". Empty objects become a shadow design. When a real entitlement arrives, it will not match the shadow, and you will migrate from your own fiction. The cost of waiting is low. The cost of a premature data model is a cleanup.

If the business wants a customer agent and does not have Fin, say so as a buying question. Which product your account team will actually sell you. What it is allowed to do. What it costs in the contract, not in a blog. This source does not answer those questions for a non-customer. Pretending the September close answered them is how the steering group gets a date with no licence.

#Cost is a list, and it depends on the fork

No containment rate, and no implementation price, belongs here. The release does not carry either. Price the fork you are on.

Already a customer:

• A list of brands, regions, and desks Fin fronts, with an owner for each.
• Intents that may finish, and intents that must hand off.
• The queue and the fields on the handoff, including whether the transcript is attached.
• The article source the agent quotes, and its editor.
• The grant if Salesforce data is connected, plus one customer the agent must not see.
• Retention for transcripts, in Fin and in any Salesforce copy.
• Out of scope: a historical load, a containment target, a claim about other orgs.

Not a customer:

• A search for an existing tenant or trial, with a yes or no.
• Nothing else, until a contract exists.
• Explicitly not priced: a Salesforce build to receive Fin data you do not have.

A migration-services proposal that assumes every Intercom workspace must be emptied into Service Cloud has ignored "continue to serve". Ask the author to point at the sentence in your contract that requires the empty. If they point at the press release instead, they are quoting the wrong document.

#The test for a partner

"Best fin intercom salesforce integration agency" is a ranking you do not need. Nobody is the best agency for every Fin customer and every non-customer at once. The situations differ, and a firm that cannot tell them apart will sell you the blend.

They ask whether you have a Fin or Intercom contract before they draw a target. They will not say every Service Cloud org includes Fin. They will not put a containment rate in the proposal, not even as an illustration. They can explain continuity: Fin continues to serve its customers as part of AI Labs, which is not a cutover date for your queues. They name intents that must hand off. They treat a Salesforce connection as a grant and can show a record the agent must not read. They keep historical conversation loads out of phase one unless you have a written reason.

Hiring a Fin Intercom Salesforce consultant fails when the first deliverable is a containment dashboard. You do not have a definition, and the release did not give you one. An implementation partner who schedules a go-live for all Service Cloud users, in a company with a single regional Fin workspace, has not listed the desks. Send them back to the list. The firm you want can leave a line blank. The firm you do not want will fill the blank with a percentage.

#What to know before you brief the desk

An earlier conversation-intelligence team is not a screen you can buy to fill a gap while you wait, and it is not Fin under an old name. Keep that history separate: Bonobo, and what 2019 does not sell.

#The other searches

The project quote is on fin intercom implementation cost. That page does not print a figure. Who bought the company is on what happened to fin intercom. The connector is on integrating fin intercom with Salesforce. Whether to move is on should I migrate from fin intercom. The customer fee is on fin intercom licence cost. Who to hire is on hiring for fin intercom. This page does not rank an agency.