Why Fin AI Escalations Land in the Wrong Inbox, and How to Fix Your Routing Setup

Most teams set up Fin AI Agent, watch it deflect a healthy share of conversations, and assume the handoff part will sort itself out. Then a customer who explicitly asked for a human sits in an unassigned queue for twenty minutes, or their conversation lands with someone on a completely different team. The AI agent did its job. The routing behind it didn't.

This is one of the more common gaps I see when auditing Intercom setups. Fin AI decides when to escalate. It does not decide who catches the conversation afterward. Those are two separate systems, and if you only configure one of them, conversations fall through the seam between them.

What Fin AI actually controls at escalation

Fin AI Agent escalates to a human teammate for a handful of reasons: the customer explicitly asks for a person, Fin detects real frustration in the message, or the conversation is stuck repeating the same question without resolution. You can shape this behavior in two ways.

Escalation Guidance lets you write plain-language instructions describing when and how Fin should hand off, for example telling it to escalate immediately for billing disputes, or to ask one clarifying question before offering a human. Escalation Rules work more mechanically: they trigger a handoff whenever specific data attributes show up in a conversation, such as a customer's plan tier or a company field, and you can scope which channels and audiences the rule applies to.

What neither of these does is choose a destination. Fin can decide a conversation needs a human. It cannot decide which team or teammate that human should be. That part lives entirely in a different part of Intercom's settings, and if you never touch it, the conversation just goes wherever your default assignment rule says, which is often nowhere in particular.

What only assignment workflows control

Routing who actually receives a conversation is handled by Workflows configured for assignment, not by anything in Fin's own settings. These workflows fire on triggers like a customer opening a new conversation or sending their first message, then apply conditions such as audience type, tags, conversation source, or custom attributes, and finally take an action like assigning to a specific team or teammate.

This is the piece that has to be built deliberately. A workflow that assigns billing questions to your billing team and product questions to support only works if someone defined those conditions and paired them with an explicit assignment action. Skip the assignment action, and the workflow can look complete while doing nothing for routing.

Intercom also enforces that only one customer-facing workflow runs per conversation, decided by priority ranking. If a broader, catch-all workflow is ranked above a narrower one meant for a specific escalation type, the broad one wins and the specific routing never fires. This is a frequent silent failure: the narrow rule exists, it's just never reached because something more general outranks it.

Why conversations still land unassigned

Even with workflows in place, conversations can slip through for reasons that have nothing to do with Fin. If a workflow's conditions don't match (say, the audience is set to exclude Leads and a lead triggers it), the conversation skips that rule entirely and falls to whatever default assignee is configured in your inbox settings, which for many accounts is nobody specific.

Round robin assignment has its own quirk worth knowing: it assigns once. If that conversation later gets unassigned for any reason, round robin does not automatically pick it back up, so it can sit idle until someone notices. Away status matters too. If a teammate is marked away, they'll be skipped by default unless you've turned on the option to ignore activity status for that rule, which is worth doing deliberately for any queue where being away shouldn't remove someone from rotation entirely.

Building a routing setup that actually works

The fix isn't complicated, but it does require treating escalation and assignment as one connected system instead of two separate settings screens you configured on different days.

Start by mapping the reasons Fin escalates (explicit request, frustration, stuck loop, a specific data attribute like enterprise plan tier) to the teams that should actually handle each one. Then build assignment workflows with conditions that match those same attributes, so a frustrated enterprise customer and a frustrated free-tier customer can route to different places if that's how your team is structured.

Check your workflow priority order next. If you have a general "assign anything unhandled" rule, make sure it's ranked below your specific rules, not above them, or it will quietly swallow conversations meant for a narrower workflow.

Set a real default assignee, not a blank one. Even a general support queue beats an unassigned conversation that nobody is watching for.

Finally, decide deliberately where round robin and away status should behave differently than the default. A billing escalation queue that needs coverage even when people step away is a good candidate for ignoring activity status; a lower-urgency queue probably isn't.

A simple test to run this week

Pick three of Fin's actual escalation reasons and trace each one by hand: open a test conversation, trigger the escalation, and watch where it lands. If any of them end up unassigned, in the wrong team's queue, or waiting on someone who's away with no backup, you've found a real gap, not a hypothetical one. This takes twenty minutes and catches problems that customer complaints would otherwise surface for you.

Fin AI Agent is genuinely good at recognizing when a human needs to step in. Whether the right human actually shows up is a setup problem, not an AI problem, and it's usually fixable in an afternoon once you know where to look.

If you want a second pair of eyes on how your escalations and assignment rules connect, this is the kind of setup and tuning work I do for businesses running Fin AI. Feel free to get in touch if you'd like help auditing yours.

Cover photo by BaljkanN 4 on Unsplash.