The 15-Minute Daily Fin Review That Lifts Resolution

Most teams switch Fin on and then wait for the resolution rate to climb on its own. It won't. The single highest-return habit you can build is fifteen minutes each morning spent reading the conversations Fin couldn't resolve — because those are the ones telling you exactly what to fix.

Here's the trap. You turn Fin on, the resolution rate settles somewhere, and then you leave it alone and hope. Meanwhile the same questions keep getting routed to your humans, week after week, and nobody notices the pattern because nobody's looking.

The fix isn't clever. It's a ritual. And it's probably the highest return-on-investment fifteen minutes of your day.

I walked through this with Jen Weaver — a customer support specialist at Supportman who runs Intercom for Tettra — on Support Stack. Here's the routine.

The 15 minutes: read the conversations Fin lost

Open the Fin AI Agent section in your Intercom inbox. Filter for the conversations that were routed — the ones where a customer started with Fin and then asked to speak to a human.

That's the gold. Those are the conversations where Fin either couldn't resolve it, or the customer decided it couldn't. Either way, each one is a signal pointing straight at a gap in your setup.

As you read, keep one question in your head: what content, what data, and what actions does your version of Fin need to have resolved this — or to do a better job next time? Most days you're looking at the first one. Content is where you'll get the quickest wins.

Acting on a gap: the content snippet

When a routed conversation shows Fin giving a weak answer, you don't have to write a whole help article on the spot. Intercom's "Improve the answer" tool lets you create a content snippet — a targeted piece of knowledge that trains Fin to reply better next time.

The structure matters, so here's the shape that works:

• A clear question title — the way a customer would actually ask it. "How can I fix page loading problems?" Fin reads this first.

• A variation on the phrasing — the same question in different words ("my page won't load", "I'm getting a 404"). This widens what Fin recognises as the same question.

• A well-formatted answer — the reply Fin draws on. Bulleted lists work well, and numbered lists are perfect when the steps have to happen in order; Fin understands the sequence.

Save it, and the next customer with that problem gets the better answer automatically. Small, fast, and it compounds.

The caveat: snippets are easy to make and easy to let rot

Here's the honest bit. Snippets are so quick to create that they pile up. A busy team with no content hygiene strategy can end up with hundreds of them, sitting alongside hundreds of help articles — and because snippets are unstructured, you get far more duplicates, and they go out of date far more easily.

So use them with a bit of judgement. Snippets are great for information you don't want on a public help page — sensitive billing options, say, or something that's only true for certain customers — and for genuinely temporary things, like a bug that'll be fixed in a fortnight. For anything that's stable and public, reach for a structured help article instead. The structure forces you to spot duplicates and makes the whole thing far easier to keep current.

And if you've already let it run away from you? You're in good company. One team I worked with had somewhere near 700 snippets; we ran a proper trimming exercise and got it down to about 170. Twenty-five is perfectly reasonable. Seven hundred is a maintenance problem wearing a helpful disguise.

The minimum effective dose

You don't need a dashboard, a project, or a quarter set aside for this. You need fifteen minutes, the routed filter, and the discipline to actually act on one gap you find. Route each fix to the right place — content, data, or actions — and favour the structured version wherever you can.

It's the smallest habit with the biggest payoff in your whole Fin setup. Start tomorrow morning.

Frequently asked questions

How long should a daily Fin review take?

A daily Fin review should take about fifteen minutes — it's deliberately small so you'll actually keep it up. That quarter of an hour, spent reading the conversations Fin couldn't resolve and fixing one gap, is usually the highest-return habit in your support workflow, especially in the early weeks after turning Fin on.

Which conversations should I look at first?

The conversations to look at first are the routed ones — where a customer started with Fin and then asked for a human. Filter for those in the Fin AI Agent section of your Intercom inbox. They show you exactly where Fin's content, data, or actions are falling short, which makes them the most valuable signal you have for improving resolution.

When should I use a content snippet instead of a help article?

Use a content snippet instead of a help article when the information shouldn't live on a public page — sensitive billing details, or something true only for certain customers — or when it's temporary, like a known bug due to be fixed soon. For stable, public information, use a structured help article: it's easier to keep up to date and forces you to catch duplicates.

Why do content snippets get out of hand?

Content snippets get out of hand because they're so quick to create that a busy team racks up hundreds without noticing. Because they're unstructured, you get far more duplicates than you would with help articles, and they slip out of date more easily — which is why a periodic content-hygiene pass (one team went from around 700 snippets down to 170) is worth building in.

This Long Read is written from Support Stack Ep. 3, The 15-Minute Daily Ritual That Transforms Fin AI Performance, with Jen Weaver (Supportman / Tettra).