After Fin's Salesforce deal, audit three AI support agent contract terms before renewal

Your AI support agent renewal may be closer than the acquisition timeline. Salesforce completed its $3.6 billion acquisition of Fin on September 10, 2026, ahead of the previously stated Q4 FY2027 target. If you run an AI support agent, that close is a dependency event: the vendor's ownership changed, and your renewal now depends on a platform decision.

The company formerly known as Intercom now operates under the Fin name, while the customer service platform keeps the Intercom label. At closing, Salesforce absorbed Fin's 30,000-plus company customer base, including Asana, Shutterstock, and Riot Games. The close landed the same day Salesforce unveiled Trusted Enterprise AI Harness, a governance layer for internal and third-party agents.

Absorption changes the vendor you are buying

When a support agent vendor joins a larger platform, the product can stay the same for a while. The contract changes first. Your renewal should test whether the agent remains a standalone capability or becomes a feature inside a suite you may not want.

Vendor dependency is manageable when the vendor is independent. After acquisition, the product may still answer tickets, but the roadmap may no longer answer to your use case.

Salesforce agreed on June 15 to buy Fin. Fin’s quickly deployable AI agent connects to existing help desks and systems used throughout the customer experience. Fin will continue serving customers and advancing AI agent capabilities as part of Salesforce AI Labs.

For operators, the practical question is whether the next version depends on a platform you do not control. Request the product roadmap and support commitments in writing. Do not rely on a sales deck. Get the data export path, the pricing change notice period, and the written support commitment. If the answer is a verbal promise, treat it as missing.

These checks decide whether the renewal is safe

Use the list below before you sign. Each item should be answerable in a minute, with a contract clause, a roadmap statement, or a support metric in front of you. When the vendor cannot answer, that is the renewal issue.

• Contractual lock-in: Identify what is locked through the term, including pricing, data portability, model updates, and exit assistance. Ask for a written commitment that the current agent remains available on your existing help desk when the vendor can change the product surface after acquisition.
• Roadmap independence: Confirm whether the agent can still run standalone on the help desks and systems you already use. Require a migration path and a date for when standalone support ends when the roadmap points to a larger AI platform.
• Resolution-rate benchmark: Re-price the stack against end-to-end resolution, not seat count. Fin’s AI customer agent was reported to achieve an average 76% end-to-end resolution rate across its supported channels. Some Fin deployments reportedly reach 85% or higher. Salesforce's Agentforce Help Agent is reported to process about 2 million customer requests a year and resolve more than 68% of them. Treat the renewal as a pricing risk when your vendor cannot show a comparable number.

You are buying a reduction in human support load, and the contract should say what happens when the vendor's ownership changes. Keep the answer in the renewal file. Treat the renewal as a dependency review.

Resolution rate is the re-costing benchmark

Support agents are often priced per seat, per conversation, or per outcome. After an acquisition, the pricing model can drift toward the parent platform. The metric that keeps you honest is end-to-end resolution. A vendor can raise the price and still claim the agent is working. The resolution rate is what separates a working agent from a more expensive ticket router.

Use the figures above as the reference points. Your vendor should be able to show where it sits against them. When it cannot, the renewal is a bet. Ask for the measurement method, the channel mix, and the human-handoff definition. A resolution rate without a method is a marketing number.

Salesforce's internal support headcount fell from roughly 9,000 to roughly 5,000 as AI agents took on half of incoming customer interactions. Use the headcount drop to translate resolution into labor savings. When the agent resolves more, the support team should shrink or redirect. When it does not, the renewal buys software without buying capacity. Build the renewal case around the labor line.