← Back to Payloads
automation2026-05-12

How top teams are resolving issues faster without more agent

Intercom's Fin resolves 65%+ of support conversations end-to-end at customers like Lightspeed. The post-trained Fin Apex 1.0 hits 73.1% resolution on support benchmarks, beating GPT-5.4 and Claude Sonnet 4.6. Pricing is $0.99 per resolved outcome, aligning vendor incentives with the customer's goal.
Quick Access
Install command
$ mrt install automation
Browse related skills
How top teams are resolving issues faster without more agent

How top teams are resolving issues faster without more agent

A sponsored VentureBeat piece from Intercom's Fin lays out the playbook the best support teams are using to ship faster resolutions without adding headcount.

What You Need to Know: Intercom's Fin AI Agent now resolves 65%+ of customer conversations end-to-end at customers like Lightspeed, and the post-trained Fin Apex 1.0 model beats GPT-5.4 and Claude Sonnet 4.6 on support-specific resolution benchmarks (73.1% vs 71.1%). The pattern across top teams: stop measuring agent activity, start measuring issue resolution — and remove work from the system instead of adding agents. Pricing is $0.99 per resolved outcome with a 50-resolution monthly minimum, which aligns vendor incentives with the customer's goal.

Why It Matters

  • Outcome-based pricing is finally the default in AI support. Charging per resolved conversation — not per seat, not per message, not per API call — is the only model that aligns the vendor with the buyer's actual goal. If the AI can't resolve the issue, the customer doesn't pay. That alignment is what makes the "without more agents" pitch credible.
  • 65% autonomous resolution is the new bar. A senior human agent handles maybe 70–80% of conversations without escalation. Fin closing the gap to within 5–10 points means the labor arbitrage in tier-1 support is mostly over. The remaining work is the long tail of complex cases — and that's where human agents will still earn their keep.
  • The pattern that drives the gains: "removing work from the system." The teams winning in 2026 are not adding agents, they are preventing avoidable contacts, resolving autonomously, and reducing repeat contacts. The work is in the workflow design, not the headcount.
  • For builders: the lesson generalizes. If you ship an AI product, the question to ask is whether you can charge per outcome. If you can, the customer's ROI math is the same as your revenue math, and the sales cycle shortens dramatically. If you can't, you're selling activity, and activity is what buyers are trying to eliminate.

What Actually Happened

The headline: 65% resolution, no headcount growth

Lightspeed's Angelo Livanos, VP of Global Support, reports Fin is "involved in 99% of conversations and successfully resolves up to 65% end-to-end—even the more complex ones." That number is consistent with the 71% headline resolution rate Intercom reports across its customer base, and is in line with what Fin Apex 1.0 posts on independent benchmarks.

The architecture is the interesting part. Fin runs on Intercom's "Fin AI Engine" — a six-step pipeline that refines the query, retrieves relevant content (via a proprietary fin-cx-retrieval model), reranks for precision (via fin-cx-reranker), generates a response (Fin Apex 1.0), validates accuracy, and tunes engine performance. Every layer is optimized for accuracy, speed, and reliability. The point is not that the LLM is special — it's that the wrapper around the LLM is doing most of the work.

Fin Apex 1.0 beats GPT-5.4 and Claude Sonnet 4.6

VentureBeat reported on March 26 that Intercom's post-trained Fin Apex 1.0 hits a 73.1% resolution rate on support-specific benchmarks, compared to 71.1% for the next-best competitor (GPT-5.4 or Claude Sonnet 4.6, depending on the test). The post-training data is Intercom's domain-specific support corpus — millions of resolved tickets, customer satisfaction scores, and escalation patterns. The lesson: in a domain as well-instrumented as customer support, post-training on your own data beats a frontier model out of the box. The generalist models are catching up, but the specialist is still ahead.

Pricing: $0.99 per resolved outcome

Fin's pricing is straightforward: $0.99 per resolution when used with the customer's existing helpdesk (Salesforce, HubSpot, etc.), or $0.99 per resolution plus $29 per helpdesk seat per month for the Intercom helpdesk bundle. 50 resolutions per month is the minimum. The vendor's incentive: Fin only gets paid when it actually closes the ticket. The customer's incentive: the AI is cheap if it works, and free if it doesn't.

This is the inverse of seat-based pricing. With seat-based pricing, the vendor wins when the customer hires more agents. With outcome-based pricing, the vendor wins when the customer hires fewer agents. The latter is a much better alignment for a buyer in 2026.

"Removing work from the system"

The Intercom playbook that the best support teams are running has four levers, in order: prevent avoidable contacts, resolve autonomously, reduce repeat contact, and remove work from the system. Each lever is operational, not just technical. Preventing contacts means in-product education and proactive notifications. Resolving autonomously means the AI handles the full conversation, not just the first turn. Reducing repeat contact means the AI follows up to make sure the issue is actually fixed. Removing work from the system means redesigning the workflow so the cases that shouldn't reach support never do.

The metric that matters is resolution rate, not agent count. The teams winning in 2026 are the teams that report resolution rate to the executive team, not headcount per ticket.

Where humans still matter

Even with Fin at 65–75% autonomous resolution, the remaining 25–35% is the long tail of complex, emotional, or unusual cases — the kind where context, judgment, and empathy matter. The right operating model is "AI handles tier 1, humans handle tier 2 and beyond." That shifts the human role up the value chain, not out the door. Senior support engineers at companies running Fin today spend more time on the cases that actually need them, and less time on "where is my order."

The Take

The "without more agents" pitch works because the metric is resolution rate, not headcount. Most B2B SaaS products in 2026 are still priced and sold on activity — seats, API calls, messages — even when the buyer wants to buy an outcome. The companies that flip to outcome-based pricing are going to grow faster in 2026 than the companies that don't, because the buyer's CFO is asking the same question in every procurement review: "What does this product eliminate, and how do I measure it?"

Intercom's vertical bet — post-train a frontier model on your own data, wrap it in a domain-specific engine, sell it on outcomes — is the template for a generation of AI products. The same pattern works in legal (post-train on case law), in healthcare (post-train on clinical guidelines), in code review (post-train on your engineering style), in finance (post-train on your GL). The generalist LLM is the substrate. The post-trained model is the product. The wrapper is the moat.

The labor arbitrage in tier-1 support is mostly over. The teams that don't move to AI-first support in 2026 will find themselves in a brutal cost competition against the teams that did, with the same SLAs and half the cost. That's not a place you want to be in 2027.

For builders: the takeaway isn't "build an AI support agent." It's "design your pricing around outcomes, not activity." If you can charge per resolved issue, per shipped PR, per closed ticket, per filed brief, the buyer's CFO is your friend. If you charge per seat or per API call, you are competing on activity, and activity is what your customer is trying to eliminate.

Quick Summary

Intercom's Fin resolves 65%+ of support conversations end-to-end at customers like Lightspeed. The post-trained Fin Apex 1.0 hits 73.1% resolution on support benchmarks, beating GPT-5.4 and Claude Sonnet 4.6. Pricing is $0.99 per resolved outcome, aligning vendor incentives with the customer's goal. Top teams are removing work from the system, not adding agents.

Sources

Related Dispatches