Fin AI Agent is designed to resolve customer questions autonomously while escalating to a human teammate at the right moment. You can control when escalation happens, whether Fin offers escalation or escalates immediately, and what Fin says during the handover.

Fin escalation behavior is powered by:

Default escalation behavior
Escalation Rules (data-driven)
Escalation Guidance (natural language)
Workflows (post-escalation routing and actions)

This article explains how each method works and how to set them up.

Default Fin escalation behavior

Out of the box, Fin is already designed to escalate in several key scenarios:

When a customer clearly asks to speak to a human.
When Fin detects strong frustration or anger.
When the customer is stuck in a repetitive loop.

You can add Escalation Rules and Escalation Guidance on top of this default behavior to gain more precise control.

Note: Escalation Guidance and Escalation Rules will override Fin’s default behavior.

When Fin offers to escalate

In some cases, Fin sends a message offering escalation instead of escalating immediately.

Example offer message:

“I understand this is causing frustration. Would you like to speak with a human teammate, or would you prefer to continue working with me?”

Fin offers escalation when:

How: The customer asks how to contact support.
Anger: The customer is upset or showing frustration.
Keyword: The customer says “agent” or “support” without clarity.
Loop: The customer repeats themselves across three turns.
First-turn escalation: The customer tries to escalate immediately after Fin introduces itself.

Note: Fin will only offer escalation once per conversation.

When Fin escalates immediately

Fin escalates directly when:

Direct request: The customer clearly asks for a human.
Escalation Guidance or Escalation Rule: Explicitly instruct Fin to escalate.

Guidance can also explicitly prevent escalation or require more information first.

When escalation offers don’t appear

Escalation offers are skipped when:

No human support is available: Your workflow ends without assigning to a teammate/inbox.
Phone requests: Phone is a separate channel.
Previous offer: Fin has already offered escalation.

Escalation methods

Fin supports two escalation configuration methods, each designed for different use cases.

Escalation Rules

Escalation Rules trigger a handoff to your team when defined data attributes are detected in a conversation. It’s perfect for situations where you have structured data about your customers or the conversation itself.

For example, you could set up a rule to automatically escalate a conversation if:

The detected value for the Fin attribute "Sentiment" is "Negative".
The detected value for the Fin attribute "Issue Type" is "Bug".
The conversation data contains an order total over a certain value.
A custom data attribute like "VIP_customer" is true.

Tip: You can view and manage Fin attributes, like "Sentiment" and "Topic", by navigating to Train > Attributes.

To create an Escalation Rule:

Navigate to the Train > Escalations.
Click + New under Escalation Rules, add a condition to define the triggers for the escalation. These conditions can be based on Users, Company, or other conversation data.
Click the Audience dropdown and select who this rule applies to (e.g., "VIP customers" or "EU audience"). By default, "Everyone" is selected.
Once you’ve configured your conditions, click Save and Enable.

Pro tip: To safely test a new rule before it affects all customers:

Add a condition to the rule that targets only your team (e.g., Email contains "@yourcompany.com").
Click Save and Enable.
Go to the Preview window on the right and set the "Testing as" user to an email that matches your condition (e.g., your-email@yourcompany.com).
Type a message that should trigger the rule and check the Event log tab. You'll see a confirmation that your rule was correctly followed.

Once you've confirmed it works, you can remove the email condition to activate the rule for all customers.

Escalation Guidance

This method triggers an escalation using natural language scenarios or customer behaviors. This is ideal for responding to a customer's intent or actions when specific data attributes aren't available.

For example, you could set up a scenario based rule to automatically escalate a conversation if a customer:

Uses words that indicate frustration, like “angry” or “not working”.
Asks to speak directly with a human teammate.
Repeatedly visits your pricing or cancellation page.

To create Escalation Guidance:

Navigate to Train > Escalations.
Click + New under Escalation Guidance, add fine-tune Fin’s escalation behaviour in specific scenarios using natural language.
Click the Audience dropdown and select who this rule applies to (e.g., "VIP customers" or "EU audience"). By default, "Everyone" is selected.
Once you’ve written your guidance, click Save and Enable.

When an Escalation Guidance is applied:

The applied guidance is sent to Fin’s reply prompts.
Fin’s response can explain why it is escalating or why it isn’t.
Only the single applied guidance is used.

Tip: For advice on writing clear and effective guidance, check out our Fin Guidance best practices article.

Escalation Guidance examples

Moments when Fin should route customers straight to your team.

Be extra sensitive to customer frustration - if the customer expresses irritation, disappointment, or uses words like 'ridiculous' or 'waste of time' escalate immediately.
If a customer asks to speak with a human, offer to connect them to a support agent rather than escalating immediately.
Offer to route the customer to a human agent if they ask the same question twice.
If the customer mentions a competitor's name, route to a human agent and let them know you're connecting them with a team member who can better assist.

Using Escalation in workflows

Escalation Rules and Guidance decide when escalation happens. Workflows decide what happens next.

To make it easy for you to configure routing and handover behavior when Fin escalates a conversation to the team, you can create branches in workflows based on which Escalation has been applied. This gives you full control of how Fin routes to the team for specific scenarios.

Simply create a branch in your workflow for each type of escalation, and combine it with other filters like customer type or language for even more control.

To set this up:

Create your escalation guidance in Train > Escalation.
Then go to Deploy, open your Fin workflow and add Branches after the Let Fin answer step.
Choose Escalation as your condition.
Select the escalation guidance you want to branch on (e.g., “Refund requests”).
Assign each branch to the right action in your workflow.

While Escalation Rules and Guidance handle the detection and initiation of escalations, your Fin workflow is used to manage the steps that follow the escalation.

For example:

Escalation Rule/Guidance: Specify when and why escalation should occur.
Workflow: Handle post-escalation actions such as collecting additional information from the customer, creating a ticket, or routing the issue to the appropriate team.

This separation ensures that the escalation process is both efficient and customizable for your needs.

Reducing unnecessary escalations

To improve Fin's efficiency and free up your team, you can take steps to reduce the number of conversations that get escalated unnecessarily.

Use Escalation Guidance only when necessary

Escalation Guidance is powerful, but broad or generic guidance can cause a sharp increase in escalations and a corresponding drop in Fin resolution rate.

The more escalation guidance you add, the more often Fin escalates.
Broader guidance leads to more escalations, fewer resolutions, and higher human support volume.
Most customers accept escalation offers when presented, even if Fin could have resolved the issue.

For best results:

Write escalation guidance for the narrowest possible situations where human support is truly required.
Avoid generic instructions like “escalate if the customer is upset” unless escalation is always the correct outcome.
Prefer asking for clarification or deflecting first when frustration can still be resolved by Fin.
Use escalation offers sparingly, as they often result in a handover even when unnecessary.

Improve your knowledge base

Improve and expand your knowledge base.
Use Analyze to identify knowledge gaps and opportunities for better automation.

Monitoring escalation metrics

To understand Fin's performance and diagnose where it may need adjustment, you should regularly monitor key metrics.

Fin AI Agent routed to team rate: This metric shows the percentage of conversations Fin handled that were escalated to a human.
Fin AI Agent routed to team conversations: This metric shows the total number of conversations Fin escalated.

You can find these metrics in the Custom Report section. Analyzing these metrics can help you identify trends and adjust your escalation guidance or knowledge base accordingly.

FAQs

Can escalation guidance stop Fin from escalating?

Yes. Guidance can explicitly prevent escalation or require additional steps first.

Does escalation guidance affect what Fin says?

Yes. Applied guidance now influences Fin’s replies and send-off messages.

Can I use escalation guidance or escalation rules to specify where Fin should escalate a conversation?

No. Escalation guidance and escalation rules can’t be used to tell Fin where to escalate a conversation (e.g. which teammate or inbox). For example, you can’t create escalation guidance that tells Fin to escalate to the Sales team.

Instead, conversation assignment happens after Fin has escalated the conversation and will follow the rules you've set up in your helpdesk (e.g. Zendesk).

Manage Fin AI Agent's escalation guidance and rules