{"id":40552,"date":"2026-05-15T22:05:07","date_gmt":"2026-05-15T22:05:07","guid":{"rendered":"https:\/\/www.europesays.com\/ai\/40552\/"},"modified":"2026-05-15T22:05:07","modified_gmt":"2026-05-15T22:05:07","slug":"intercom-now-called-fin-launches-an-ai-agent-whose-only-job-is-managing-another-ai-agent","status":"publish","type":"post","link":"https:\/\/www.europesays.com\/ai\/40552\/","title":{"rendered":"Intercom, now called Fin, launches an AI agent whose only job is managing another AI agent"},"content":{"rendered":"

The company formerly known as Intercom<\/a> just did something that no major customer service platform has attempted at scale: it built an AI agent whose sole job is to manage another AI agent.<\/p>\n

Fin Operator<\/a>, announced Thursday at a live event in San Francisco, is a new AI-powered system designed specifically for the back-office teams that configure, monitor, and improve Fin<\/a>, the company’s customer-facing AI agent. Rather than replacing human support agents \u2014 which is what Fin itself does on the front lines \u2014 Operator targets the growing army of support operations professionals who spend their days updating knowledge bases, debugging conversation failures, and combing through performance dashboards.<\/p>\n

“Fin is an agent for your customers,” Brian Donohue, the company’s VP of Product, told VentureBeat in an exclusive interview ahead of the launch. “Operator is an agent for your support ops team. This is an agent for the back office team who manages Fin and then manages their human agents.”<\/p>\n

The announcement arrives at a pivotal moment for the company. Just two days ago, CEO Eoghan McCabe formally renamed the 15-year-old company from Intercom to Fin<\/a> \u2014 an aggressive signal that the AI agent is now the business, not merely a feature of it. Fin recently crossed $100 million in annual recurring revenue and is growing at 3.5x. The broader company generates $400 million in ARR<\/a>, meaning the AI agent now accounts for roughly a quarter of total revenue and virtually all of its growth.<\/p>\n

Fin Operator<\/a> enters early access for Pro-tier users starting today, with general availability planned for summer 2026.<\/p>\n

The invisible crisis behind every AI customer service deployment<\/p>\n

As companies push their AI agents to handle more conversations \u2014 Fin alone now resolves more than two million customer issues each week across 8,000 customers globally, including Anthropic<\/a>, DoorDash<\/a>, and Mercury<\/a> \u2014 the operational complexity behind those systems has exploded. Someone has to keep the knowledge base current. Someone has to figure out why the bot entered an infinite loop with a frustrated customer last Tuesday. Someone has to analyze whether the automation rate dropped after a product update.<\/p>\n

That “someone” is the support operations team, and according to Donohue, they are drowning.<\/p>\n

“Almost every support ops team is already doing data analysis and knowledge management \u2014 that’s table stakes today,” Donohue said. “Where teams struggle is the agent builder work. It’s a new skill set, and most don’t have enough time for it. They get their first iteration up and running, and then they get stuck.”<\/p>\n

The problem is structural. AI customer agents are not static software. They require constant tuning \u2014 a process that looks more like training a new employee than configuring a SaaS tool. Each customer conversation is a potential source of failure, and each failure requires diagnosis, root-cause analysis, a configuration fix, testing, and monitoring. It is tedious, technical, and relentless. Fin Operator<\/a> aims to collapse that entire loop into a conversational interface.<\/p>\n

How one AI system plays data analyst, knowledge manager, and debugger all at once<\/p>\n

Donohue described Operator<\/a> as filling three distinct roles that typically consume the bandwidth of support ops teams: expert data analyst, expert knowledge manager, and expert agent builder.<\/p>\n

As a data analyst, Operator can field high-level questions like, “How did my team perform last week?” and generate on-the-fly charts, trend reports, and drill-down analyses across all of the data already stored in Intercom’s platform. The company has loaded Operator with contextual knowledge about customer-specific data attributes to help it interpret workspace-specific metrics accurately.<\/p>\n

As a knowledge manager, Operator can ingest a product update \u2014 say, a three-page PDF describing a new feature \u2014 and autonomously search the company’s entire content library to identify what needs to change. It finds gaps, drafts new articles, suggests edits to existing ones, and presents everything in a diff-style review interface. The underlying search engine is the same semantic search system that Intercom has built and optimized for Fin over more than two years.<\/p>\n

“On that knowledge management front, you just have such a time compression of something that would take, certainly hours, sometimes days, into the space of about 10 minutes,” Donohue said.<\/p>\n

As an agent builder, Operator introduces what the company calls a “debugger skill<\/a>.” Support ops teams can paste in a link to a conversation where Fin misbehaved, and Operator will trace every step of Fin’s internal reasoning, identify the root cause \u2014 often a piece of guidance that unintentionally creates a loop \u2014 propose a rewrite, back-test the change against the original conversation, and then suggest creating a production monitor to catch similar issues going forward.<\/p>\n

“This is literally what our professional services team does,” Donohue explained. “You’ve written guidance that is unintentionally causing Fin to repeat itself \u2014 this happens a lot. You didn’t realize it, but you never gave it an escape hatch.”<\/p>\n

The ‘pull request’ safety net that keeps humans in control of AI changes<\/p>\n

One of the most consequential design decisions in Fin Operator<\/a> is what the company calls its “proposal system” \u2014 a mechanism that functions like a pull request in software engineering.<\/p>\n

Every change that Operator recommends \u2014 whether it is an edit to a help article, a rewrite of an AI guidance rule, or the creation of a new QA monitor \u2014 appears as a proposal with a full diff view. Users can inspect, edit, and approve each change before it takes effect. Nothing goes live without a human clicking “Apply.”<\/p>\n

“Right now, we’re taking zero risk on this \u2014 Fin cannot make any changes to the system without human approval,” Donohue emphasized. “Nothing goes live until a human clicks apply.”<\/p>\n

This is a notable architectural choice. In a market increasingly enamored with fully autonomous AI systems, the company is deliberately keeping a human approval gate in place \u2014 at least for now. Donohue acknowledged this will evolve, but said the current moment demands caution: “It’s too big a leap to just let Operator make changes automatically and then tell the team, ‘Hey, let me tell you about what I did.'”<\/p>\n

For enterprise buyers evaluating AI tools, this design point matters. It is the difference between an AI system that proposes changes and one that enacts them \u2014 a distinction that compliance teams, security officers, and risk managers will scrutinize closely.<\/p>\n

Why Fin Operator runs on Anthropic’s Claude instead of the company’s own AI models<\/p>\n

In a revealing technical detail, Donohue confirmed that Fin Operator<\/a> does not use the company’s proprietary Apex models \u2014 the same custom AI models that power the customer-facing Fin agent and that the company has promoted as outperforming GPT-5.4 and Claude Sonnet 4.6 in customer service benchmarks.<\/p>\n

Instead, Operator runs on Anthropic’s Claude.<\/p>\n

“We’re not using our custom models,” Donohue said. “Those are designed to directly answer customer questions, whereas these are closer to what frontier models are best suited for. This is really closer to software engineering.”<\/p>\n

The distinction is telling. Fin’s Apex models<\/a> are optimized for one thing: resolving customer service conversations with minimal hallucination and maximum accuracy. Operator’s tasks \u2014 analyzing data, writing code-like configurations, debugging complex reasoning chains \u2014 demand a different kind of intelligence. Donohue characterized these capabilities as more akin to software engineering, an area where Anthropic’s Claude models have been deliberately optimized.<\/p>\n

The company has not ruled out building custom models for Operator<\/a> in the future, but Donohue positioned it as a lower priority. What the team has built around Claude, he argued, is the differentiated layer: the proposal system, the debugger skill, the semantic search integration, the data attribution logic, and the charting capabilities that make Operator more than just “Claude inside the app.”<\/p>\n

Early beta testers say Fin Operator feels like adding five people to the team<\/p>\n

Fin Operator<\/a> is currently in beta with roughly 200 customers, a number Donohue said has “ramped up pretty fast the last couple of weeks.”<\/p>\n

Constantina Samara, VP of Customer Support, Enablement & Trust at Synthesia<\/a>, said the tool has already changed how her team works: “Previously, improving how Fin handles a conversation often meant reviewing everything yourself \u2014 the conversation, the configuration, the content. With Fin Operator, you just ask. It walks you through what happened and makes improving Fin dramatically easier.”<\/p>\n

Jordan Thompson, an AI Conversational Analyst at Raylo<\/a>, reported that he has been using Operator daily and has run head-to-head comparisons between Operator’s analysis and his own manual work. “It’s very accurate,” Thompson said. “It’s just as strong at high-level trend analysis as it is at debugging individual conversations. That’s a real limitation when using an LLM connector on its own \u2014 you get conversational depth but nothing on reporting or trends.”<\/p>\n

Donohue also shared an internal anecdote from the company’s own knowledge management team. Beth, who leads knowledge operations, told the product team that Operator made her feel like she had “five more people on my team.” Whether internal testimonials carry the same weight as external customer validation is debatable, but Donohue said the knowledge management use case consistently generates the most visceral reactions because the time savings are so stark \u2014 collapsing hours or days of content auditing into roughly 10 minutes.<\/p>\n

A new pricing model signals how AI is reshaping the economics of enterprise software<\/p>\n

Fin Operator<\/a> will live inside the company’s Pro add-on tier \u2014 a relatively new bundle that already includes advanced analytics features like CX scoring, topic detection, real-time issue detection, and quality assurance monitoring across both AI and human agent conversations.<\/p>\n

The pricing model introduces something new for the company: usage-based billing. Intercom has historically relied on outcome-based pricing \u2014 charging roughly $0.99 per conversation that Fin resolves without human intervention. Operator’s work does not map cleanly to that model because it produces configuration changes, not customer resolutions.<\/p>\n

“This has pushed us to a different model, to go more into that usage model for support ops teams,” Donohue said. “We’ll try to be generous with the usage amounts that come into Pro, but for people who are leaning heavily in, we’ll have the ability to buy more usage blocks.”<\/p>\n

The shift is worth watching. Outcome-based pricing was one of the company’s most distinctive market positions \u2014 a bet that customers would pay for results rather than seats. Extending that philosophy to internal operations work proved impractical, which suggests that as AI agents take on more diverse roles within an organization, the pricing models that support them will need to become equally diverse.<\/p>\n

How Fin Operator stacks up in a crowded field of AI customer service competitors<\/p>\n

Fin Operator lands in an increasingly competitive landscape. Zendesk<\/a>, Salesforce<\/a>, Sierra<\/a>, and a constellation of AI-native startups are all building some version of AI-powered support operations tooling. The broader AI automation market is projected to reach $169 billion in 2026<\/a>, according to Grand View Research, growing at a 31.4% compound annual rate.<\/p>\n

But Donohue argued that Operator’s differentiation lies in two areas. First, breadth: Operator works across the full surface area of the company’s configuration system \u2014 data, content, procedures, simulations, guidance, and monitoring \u2014 rather than addressing a single narrow use case. Second, the fact that it spans both AI and human operations.<\/p>\n

“Most critically, where I think we have the most differentiation is because it’s for your human system and your AI system,” Donohue said. “That’s really one of the unique spaces we have \u2014 to have a first-class AI agent and a first-class help desk, and Operator works across both.”<\/p>\n

The competitive positioning also benefits from timing. The company’s recent corporate rebrand <\/a>from Intercom to Fin signals a wholesale commitment to AI that legacy players may struggle to match. As CEO McCabe wrote in announcing the name change, the AI agent “is about to be the largest part of our business.” The help desk product continues as Intercom 2, but the parent company now carries the name of its AI agent \u2014 a branding move that some industry observers have interpreted as pre-IPO positioning. The Fin API Platform<\/a>, launched in early April, adds another dimension: the company opened its proprietary Apex models to third-party developers and even offered to license the technology to direct competitors like Decagon and Sierra.<\/p>\n

The real paradigm shift isn’t a new chat interface \u2014 it’s an agent that does the thinking for you<\/p>\n

Step back from the product specifics and Fin Operator<\/a> represents something potentially more consequential than a new dashboard or analytics tool. It is one of the first commercial products to explicitly embody the emerging paradigm of AI agents that manage other AI agents \u2014 a two-layer abstraction that is beginning to reshape how companies think about operational software.<\/p>\n

Donohue was emphatic on this point. The real paradigm shift, he argued, is not the chat interface replacing buttons and menus. It is that the AI is doing the actual knowledge work \u2014 figuring out what should change, why, and how.<\/p>\n

“The UX change is secondary, even though it’s most visible,” Donohue said. “The change is that we are identifying and doing the work of support operations. It’s doing the work of what the knowledge manager is doing, so that they just have to approve that. That’s the huge shift.”<\/p>\n

The analogy to software engineering is apt. Over the past year, AI coding agents have fundamentally altered the daily workflow of developers, shifting their primary responsibility from writing code to reviewing and guiding the AI that writes it. Donohue sees the same transformation arriving for support operations professionals.<\/p>\n

“Software engineers \u2014 three months have upended their world, where their primary job now is managing agents who are actually writing the code,” he said. “Similarly now, support ops, your job is to manage an agent who’s managing the agent for your customers.”<\/p>\n

Whether this vision pans out at enterprise scale remains to be seen. The company is still launching Operator<\/a> in beta precisely because it wants to keep refining quality through what Donohue described as a painstaking, conversation-by-conversation debugging process. “We’ve spent three months, conversation by conversation, learning, fixing, learning, fixing, to get it where it’s robust,” he said.<\/p>\n

But if the early returns hold, Fin Operator<\/a> may preview what the next generation of enterprise software looks like: not tools that help humans do work faster, but agents that do the work themselves, subject to human judgment and approval. For customer service leaders already running AI agents in production, the question is no longer just “how good is my bot?” It is now, inevitably, “who is managing it?” And increasingly, the answer is another bot.<\/p>\n","protected":false},"excerpt":{"rendered":"The company formerly known as Intercom just did something that no major customer service platform has attempted at…\n","protected":false},"author":2,"featured_media":40553,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6],"tags":[405,7537],"class_list":{"0":"post-40552","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-agentic-ai","8":"tag-ai-agents","9":"tag-artificial-intelligence-agents"},"_links":{"self":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/posts\/40552","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/comments?post=40552"}],"version-history":[{"count":0,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/posts\/40552\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/media\/40553"}],"wp:attachment":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/media?parent=40552"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/categories?post=40552"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/tags?post=40552"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}