How to Improve Intercom Fin Resolution Rate

Summary: Fin resolution rates across Intercom's customer base range from 25% to over 80%. The difference is almost entirely determined by the state of the knowledge base Fin pulls from. The teams above 70% run ongoing content work tied to every product release. The teams below 50% wrote their articles once and left them.

In April 2025, Cursor's AI support bot emailed users that their accounts were being restricted to one device per subscription. Naturally, their users began to cancel their subscriptions. The story hit Hacker News and Reddit within hours. Cursor's cofounder apologized publicly and confirmed the policy had never existed. A session bug was causing the logouts, and the bot invented an explanation because no article documented Cursor's actual session behavior.

One missing article turned into mass subscription cancellations, a front-page incident on three platforms, and a CEO writing a public apology. The bot hallucinated because it was asked a question and had nothing to retrieve.

Fin pulls from the same kind of knowledge base. If the article it retrieves is six months out of date or missing entirely, your resolution rate absorbs the cost.

What follows is the practical checklist for finding and fixing those articles, starting with what Intercom gives you natively and ending with what lives outside it.

Start with Intercom's Optimize tab

Go to Fin AI Agent > Analyze > Optimize. Intercom surfaces AI-powered suggestions here based on conversations Fin could not resolve. Suggestions are generated weekly, with additional triggers for high volume or activity spikes.

Optimize groups suggestions into three categories:

Content gaps are where Fin could not answer because help content was missing, unclear, duplicated, or contradictory. For each suggestion, you can see the exact conversations that triggered it, review an AI-generated draft for new or edited content, and update articles or snippets directly. Intercom's own team says a weekly review yields 10 to 15 suggestions, most implementable in under an hour. Start here.

Customer data gaps appear when Fin needed information from an external system that was not available, like order status or account details. Each suggestion includes a guide outlining the API and data connector needed, an implementation effort estimate, and the customer queries it would resolve. These require engineering work.

Action gaps show where Fin needed to take an action in another system, like updating a record or cancelling an order. These point you toward building Fin Procedures or Fin Tasks.

Data and action gaps require engineering resources and longer timelines. Content gaps you can fix this week.

Check your content performance report

Go to Fin AI Agent > Analyze > Performance. The content performance table shows every article Fin uses, with two columns that matter: involved (how many times Fin referenced the article) and resolved (how many times that reference led to a resolved conversation).

Sort by involved conversations. The articles at the top are the ones Fin relies on most. If the resolved number is significantly lower than the involved number, that article is dragging your resolution rate down. Intercom's knowledge management guide recommends focusing on the top 20% by involvement rate and flagging anything below 50% resolution.

Open the underperforming articles. The usual culprits: outdated screenshots, instructions referencing a renamed feature, steps that no longer match the product, or contradictory information spread across multiple articles on the same topic.

Review negative CX scores

Go to Fin AI Agent > Analyze > Performance and look at the CX Score breakdown. Negative CX scores on resolved conversations are the most useful signal. They mean Fin answered, the conversation closed, but the customer left unhappy.

Open those conversations. You will often find that Fin gave a technically correct answer to the wrong question, or pulled from an article that was accurate six months ago. Intercom's own support team runs weekly reviews of negative CX scores and escalates them for content fixes.

Set up a feedback loop from your support team

Your agents see Fin fail before anyone else does. Intercom recommends creating a back-office ticket type that agents can submit directly from the inbox when they spot an incorrect or unhelpful response. Intercom's own team surfaces 15 to 20 content suggestions per week this way, each taking 15 to 45 minutes to action.

You can also use the Improve Answer button in the inbox on any AI-generated response to review the content Fin used and enhance it, even on conversations that resolved successfully.

"I'm only one person, and we have almost a thousand articles. I know there's misinformation. There's outdated information."

— Knowledge Content manager, consumer app company

Keep content in sync with product releases

Your product ships a change, nobody updates the article, Fin keeps answering from the old version. This is where resolution rates decay.

Intercom recommends partnering with your product team so that every release includes a content step. Their estimate: a typical release requires three to six article updates and a similar number of macros. A significant product change may require five to eight hours of content work. Tools like Pageloop can surface which articles a release affected by monitoring your Slack, Jira, and Linear activity, but most teams track this manually in a spreadsheet or release checklist.

They also recommend refreshing articles untouched for six months or more, focusing on high-traffic articles with high Fin involvement, outdated UI images, features that no longer exist, and duplicate content. Their estimate for a full pass: about seven hours of subject matter expert time.

"Senior managers are now realizing that the help center is more important because it's feeding Fin."

— Enablement lead, customer success platform

The resolution rate trust problem

The resolution rate Intercom reports may be higher than your real resolve rate. In a community thread, a support manager for a hardware company described running a 12% real resolve rate while being charged for significantly more. Fin was marking conversations as "assumed resolved" when a human agent stepped in before the customer clicked "speak to human." The agent was stepping in because Fin had given the customer incorrect steps and they were mid-crisis.

One support lead we spoke to saw the same pattern. Her dashboard showed 84.5% resolution. She put the real number at roughly half that.

An Intercom support engineer in a separate thread said 30 to 50% is a reasonable starting point, depending on how well help center content is written. If your number is much higher than that and you have not invested heavily in your knowledge base, audit a sample of those "resolved" conversations and check whether the customers actually got the right answer.

Where Intercom's tools stop

Everything above lives inside Intercom. For teams in their first few months with Fin, it is enough to get from 30% to 50% or beyond.

The harder problem is connecting a failing article to the product change that broke it. Optimize tells you an article is underperforming. The content performance report shows you the numbers. But the Jira ticket that closed last sprint, or the Slack thread where support discussed the workaround three weeks ago, lives outside Intercom entirely.

A spreadsheet can bridge part of this. List your last five product releases alongside the features that changed, then search your knowledge base for articles that reference those features and check whether they are current. Three to four hours per release, and it catches the most obvious drift.

Pageloop automates that connection. It watches Linear, Jira, and Slack for signals that a published article needs attention. A ticket closes that touched something an article documents. A Slack thread surfaces a question with no matching article. When Fin flags an article as underperforming, Pageloop traces it back to the product change that broke it and shows your team what to fix.


Image courtesy : Birmingham Museums Trust and Unsplash
Loch Awe at Sunset 1899, by Myles Birket Foster