Skip to main content

Deploy Fin AI Agent over chat

How to set up and go live with Fin AI Agent over your live chat channels.

Written by Beth-Ann Sher

Use this article to deploy Fin AI Agent over live chat (Web, iOS, Android, WhatsApp, Slack, Facebook, Instagram, and SMS), test your configuration before going live, and troubleshoot common issues — including unwanted conversation closures and Fin re-engaging after escalation. Fin is available on trial and paid plans.

Note:


Train Fin to handle chat conversations

Analyze your chat conversations

You'll need to identify the audience or support topics you want Fin to handle over chat and set a success metric (e.g. resolution rate, CSAT). For example, this could include specific high-volume topics or a sub-set of customers.

Train Fin on Content

Go to Fin AI Agent > Train > Content and ensure you've enabled content which Fin can use to support chat queries. Update your content to cover your frequently asked chat queries. You can add public articles, documents, snippets, or public URLs.

Fin AI Agent > Train > Content page showing enabled content sources including articles, documents, and snippets

Fin uses articles from the Help Center connected to the brand you've set up.

Train Fin with Guidance

Go to Fin AI Agent > Train > Guidance and set up guidance to train Fin how to speak in your brand’s voice, follow your policies, and handle conversations the way you want—using simple, natural-language instructions. You can set clear rules for what Fin should say and do, from using the right terminology to handing sensitive topics over to your human support team.

Fin AI Agent > Train > Guidance page showing a list of active guidance rules

Train Fin with Attributes optional

Go to Fin AI Agent > Train > Attributes and set up Fin Attributes to automatically classify conversations by topic, sentiment, urgency, or any custom attribute you define. Fin sets these attributes during a conversation, and you can use them as conditions in workflows to automatically route or escalate conversations to the right team.

Fin AI Agent > Train > Attributes page showing Fin Attribute configuration with custom attribute types and values

Train Fin with Escalation guidance optional

Go to Fin AI Agent > Train > Escalation and configure Escalation guidance to define when and how Fin should hand conversations over to your human support team. Use natural-language or rules to specify escalation conditions—for example, escalating when a customer asks the same question twice, mentions a specific keyword, or expresses frustration.

Fin AI Agent > Train > Escalation page showing escalation rules and guidance settings

Train Fin to handle Procedures optional

Go to Fin AI Agent > Train > Procedures and build Procedures to automate more complex processes. Often times, these processes may involve actions in your external systems that need to reliably follow your specific business rules (e.g. cancel an order, refund a subscription). Fin will trigger the procedure and be actively involved each step to resolve customer queries.

Fin AI Agent > Train > Procedures page showing a list of configured Fin Procedures

Tip: Add Data connectors for Fin to retrieve information from your external systems and apps to deliver personalized answers (or set this up later).


Test Fin with chat conversations

Test Fin in your workspace

From Fin AI Agent > Test you can see if you're ready to deploy Fin by testing how Fin responds to actual customer queries.

Fin AI Agent > Test page showing test conversation questions with Good and Poor rating buttons

Simply generate questions from previous conversations, bulk upload questions via a CSV, or manually add specific questions you want to test Fin on. Then review Fin's responses and mark them as "Good" or "Poor".

When marking a response as "Poor" you can leave a reason and dig into where Fin's answer came from (i.e. which content source, guidance, or personality settings were used). You'll also get recommendations on how to improve Fin's answer. Then you can export this as a report to share with your teammates.

Learn more about testing Fin.

Test Fin over chat in your live environment

It's a good idea to set Fin live over chat to a small test or internal audience (e.g. yourself and teammates) and review the full customer experience from Fin's greeting to it's response and handover.

  1. Under the "Simple deploy", open Who will see Fin and add an audience rule for Email contains [yourcompanydomain.com] - this will enable you and your teammates to send some test questions for Fin to answer.

  2. You can also set up the following:

    • Handover experience from Fin to a teammate.

    • When to auto-close conversations.

    • When a conversation rating (CSAT) is requested.

  3. Select Set Fin Live.

  4. Open the Messenger (installed on your website or app) and send a question to see Fin's response.

Fin AI Agent > Deploy > Chat page configured with an internal test audience using an email domain rule

Note: If you test Fin in your live environment, you will be billed per Outcome. However, if you or your teammate has asked to get additional help or speak to your team, no outcome is counted and you would not be charged for this.

Learn more about testing and rolling out Fin to your customers.


Deploy Fin over chat

Expand the audience Fin is replying to, so that Fin is replying to some real customer conversations. Review the results from Fin AI Agent > Analyze then expand Fin to handle more of your volume or topics.

Simple deploy (without workflows)

Go to Fin AI Agent > Deploy > Chat. At the top of this page, you'll see "Simple deploy" where you can:

  • Determine who will see Fin in chat conversations.

  • Configure the handover experience from Fin to a teammate.

  • Choose when to auto-close conversations.

  • Ask for a conversation rating (CSAT) after Fin's conversation.

Simple deploy configuration panel showing audience, channel, handover, auto-close, and CSAT settings

Step 1: Who will see Fin

First, decide which of your customers can interact with Fin AI Agent. You can allow Fin to provide answers to your users, leads, and/or visitors.

Click + Add audience rule and use data attributes in Intercom to target your audience further. Then click Save.

Simple deploy audience rule editor showing an Email contains filter targeting a specific company domain

You can also use channel attributes in the audience rules to configure channel-specific actions and content. Then click Save and move to the next step.

Simple deploy channel attribute filters for targeting Fin to specific chat channels

Step 2: In selected channels

Now select which chat channels you'd like Fin to be available on:

  • Web

  • iOS

  • Android

  • WhatsApp

  • Slack

  • Facebook

  • Instagram

  • SMS

Then click Save.

Simple deploy channel selection checkboxes for Web, iOS, Android, WhatsApp, Slack, Facebook, Instagram, and SMS

Note: You'll need to install / connect chat channels you use within Settings > Channels before you can deploy Fin with them. Learn more.

Step 3: Let Fin introduce itself

Now configure Fin's introduction message to customers who reach out through chat. This helps your customers better understand what Fin can do and how to interact with it. You only need to write Fin's introductory messages in your workspace's default language. When you click Save, these messages will be automatically translated into all of the supported languages you have enabled for Fin. Fin will then greet customers in their detected language.

Note: Enabling "Let Fin introduce itself" is required for Fin to trigger and engage with customers in chat conversations.

Simple deploy Step 3 showing the Let Fin introduce itself toggle and greeting message editor with automatic translation options

Step 4: Uses support content

Review which content sources Fin uses to answer questions. Go to Fin AI Agent > Train > Content and confirm the articles, snippets, and documents you want Fin to use are enabled.

Simple deploy Step 4 showing the list of enabled content sources Fin uses to answer customer questions

Step 5: Follows guidance

Review the guidance rules that shape how Fin responds. Go to Fin AI Agent > Train > Guidance to check your active rules — these control Fin’s tone, terminology, escalation behavior, and any topic-specific instructions.

Simple deploy Step 5 showing the active guidance rules Fin follows when responding to customers

Step 6: If Fin can't resolve the conversation

Specify what action should be taken if Fin cannot resolve the conversation. You can choose how Fin hands over or escalates to a particular team or teammate.

Simple deploy Step 6 handover configuration showing team assignment and escalation path options

To gather more information from a customer before Fin hands over to your team, simply toggle on "Collect more information when a customer asks to speak to the team".

Simple deploy Step 6 showing the Collect more information before handover toggle enabled

Fin will encourage the user to share more information. The exact message it sends will be something along the lines of "Sure! While I connect you, could you provide us with more details about your issue to help us find an answer faster?" This will be adapted to the context of the conversation and your workspace’s Fin personality settings.

By prompting the customer for more context before Fin hands over to a teammate, there is another opportunity to get more and/or better information than presented the first time around. The benefit to this is two-fold:

  1. Gives Fin another chance to answer: often customers don’t give the AI Agent a chance, asking to speak to a human before asking Fin a question.

  2. If context is provided, even if Fin can’t provide an answer, the teammate will spend less time gathering context and will be able to troubleshoot faster.

We've tested this feature extensively at Intercom and observed an increase in answer rate, confirmed resolutions, and CSAT.

Important: If the user does not reply to Fin's prompt for more information, or if Fin is unable to find an answer to a new user query, the conversation will be automatically routed to the team (and thus will not count as an Fin Outcome).

An Outcome is counted when Fin either resolves a customer's issue — when the customer confirms their question was answered (a confirmed resolution, such as 'That helped, thanks') or exits without requesting further assistance (an assumed resolution) — or successfully completes a Procedure configured to end in a handoff.

Or, instead of escalating conversations straight to your team, choose to close conversation and offer other ways for the customer to get help. For example, provide a contact number or link to another resource.

Simple deploy Step 6 showing the close conversation option with a custom closing message configured

Then click Save and move to the next step.

Note: The closing messages will be automatically translated into all your supported languages on your workspace when you save the message.

Step 7: Auto-close pending Fin conversations

Choose when to auto-close conversations by specifying a length of time Fin should wait before closing conversations.

Select if you want Fin to automatically close the conversation after customer becomes inactive:

  • If Fin has answered the question, and/or

  • If Fin was not able to answer the question or the customer left before asking any questions.

Simple deploy Step 7 auto-close settings showing checkboxes for closing after answered and unanswered conversations

You can also Customize what Fin says when closing the conversation to make sure the customer got what they needed and remind them they can still speak to your support team, even if the conversation is being closed. The closing messages will also be automatically translated into all your supported languages when you click Save.

Simple deploy Step 7 showing the custom closing message editor for auto-closed conversations

Note: If you previously had custom translations for these messages, saving any changes to the default language text will overwrite them with the new automatic translations.

Note: Auto-close is a workflow-scoped behavior — it only applies while Fin's workflow is actively managing the conversation. Once a conversation is routed to a team inbox via handover, the Fin workflow is no longer in control and the inactivity timer stops. The auto-close settings configured here will not apply to conversations that have been handed over to a team.

Step 8: Ask for conversation rating (CSAT)

At the end of a customer's interaction with Fin AI Agent you can ask them to give a conversation rating by toggling these settings on:

  • 👍 Send CSAT when the customer replies with a positive message (ie. 'That helped, thanks')

  • ⏳ Send CSAT if the customer becomes inactive after Fin showed an answer

    Simple deploy Step 8 showing CSAT request toggles for positive customer replies and inactive conversations

Step 9: Preview Fin over chat

To preview Fin over chat before setting it live:

  1. Use the interactive Messenger preview on the right to start typing questions you think Fin should be able to answer from the content you've enabled.

  2. Once you've previewed the experience, you can set Fin live.

Fin AI Agent > Deploy > Chat page showing the interactive Messenger preview panel on the right side

To preview Fin over chat as a specific user or brand, select the Preview user dropdown at the top of the preview and then select User or lead. This let's you impersonate real users/leads and see exactly how Fin will respond. You can simulate real scenarios using live or dummy data, test data connectors, and validate every answer.

Messenger preview with the Preview user dropdown open, showing options to select a specific user or lead for impersonation testing

Note:

  • To preview Fin AI Agent the Messenger must be installed on web.

  • You won't be charged for conversations generated through this preview.

  • Previewing Fin always creates a test user called "Preview User" in your inbox so you can also preview the teammate experience in the inbox. Currently, there's no way to deactivate the creation of these conversations in preview mode. To avoid creating new inbox conversations, use Fin Testing instead.

  • The preview will follow any handover setup you've configured if Fin can't resolve the conversation (i.e. routing to a team inbox).

  • Conversations created via the Fin preview won't be closed and will remain open even if you have a close action that should be applied.

  • The preview won't send a CSAT survey at the end of your conversation.

  • While the preview doesn't require Fin to be set live, it still requires the content to be available to Fin.

  • Notification behavior does not work when using the Preview.

Step 10: Review and set live

Once you've finished configuring Fin's chat experience, click Set Fin Live 🎉 Fin will immediately begin handling conversations for the audience you’ve configured. To pause Fin at any time, return to Fin AI Agent > Deploy > Chat and toggle Fin off.

You'll need billing permissions to set Fin live if the T&Cs haven't been accepted yet. Accepting these terms is mandatory to be able to use Fin AI Agent.


Advanced setup through Workflows

If you want to add Fin to a workflow, or customize Fin in an existing workflow, go to Fin AI Agent > Deploy > Chat and open Advanced setup through Workflows.

Fin AI Agent > Deploy > Chat page showing the Advanced setup through Workflows panel with existing workflows listed

Note: Simple deploy will always take precedence over any "When customer opens a new conversation in the Messenger" Workflows, as well as any user-facing "When customer sends their first message" Workflows over email. Simple deploy also takes precedence over Simple automations.

If you have an existing workflow set up specifically for inbound conversations through the Messenger or other chat channels:

  • You can simply edit the workflow add the "Let Fin handle" step, where appropriate.

  • Customize Fin's behavior in the workflow such as setting expectations, handovers, and closing pending conversations by clicking on "Let Fin handle".

  • When you add Fin to your existing workflows, you'll find these under Fin AI Agent > Workflows if you filter by "Type is Using Fin".

If you don't have a workflow set up specifically for inbound conversations through the Messenger or other chat channels:

  • We recommend you create one using the "When customer opens a new conversation in the Messenger" or "When customer sends their first message" trigger.

  • You can ensure a workflow is only enabled for chat channels in the trigger settings.

  • Add Fin to your workflow by creating a path and selecting Let Fin handle.

Workflow builder showing an inbound Messenger workflow with a Let Fin handle step added

Customize Fin's behavior in your workflow

To customize Fin's behavior in a workflow, open your workflow and click on the Let Fin handle step. Here, you can:

  • Control the answer type.

  • Set expectations for human support.

  • Ask for more information before handover.

  • Follow up with inactive customers.

  • Ask for conversation rating (CSAT).

  • Auto-close pending conversations.

  • Customize what Fin says when closing conversations.

Let Fin handle step settings panel showing customization options: answer type, human support expectations, handover information, inactive customer follow-up, CSAT, and auto-close

Note: For Messenger and chat channels, the inactivity follow-up timer is fixed at 4 minutes and cannot be extended. Unlike email, there is no option to trigger a custom workflow when a chat conversation becomes inactive — this is only available for email. To act on inactivity in chat, use the built-in follow-up to offer escalation at the 4-minute mark.

Have Fin respond to a specific audience

By using branching, you can create different Fin experiences for different audiences.

For example:

  • For paying customers, you might want to hand over to a teammate when Fin can't answer but for non-paying customers, you might want to direct them to your Help Center.

  • See additional ways and examples of how you can target specific audiences or customers.

Add as many branches as you need to create different experiences for your different customers.

Workflow builder showing branching paths for paying and non-paying customers with different Fin experiences configured per branch

While you can also determine audience rules within the workflow trigger settings, we recommend only doing this if you have an additional workflow to cover everyone who doesn't match those rules.

Have Fin respond to a specific topic

You can also use branching to create different Fin experiences and paths based on your different conversation topics.

  1. Click Add step to start creating your branching logic.

  2. Then select Branches under "Proceed to another path".

  3. Once you’ve added a branch, click on Missing condition to open up your branch settings.

  4. Click + Add condition to set different conditions, e.g. if you want to escalate conversations based on a keyword in the message, select "Message Content" as a condition.

  5. You can repeat this step to add multiple branches per keyword.

  6. Once you’ve defined your branches, click on the arrow to the right to determine the path specific to that branch, e.g. assign to a teammate or let Fin answer.

For example, you can use a "Message Content" filter to escalate conversations which contain the keyword "billing" directly to your Billing team.

Workflow builder showing a branch condition where message content contains the keyword billing, routing those conversations to the Billing team

With Fin Attributes, Fin automatically classifies conversations based on attributes you define, like issue type, sentiment, or urgency. You can then use these attributes in Workflows to automatically escalate conversations to the right team, ensuring customer requests are handled efficiently.

Preview your Fin over chat workflow

If you want to test a Fin over chat workflow, select the Preview button at the top of the Workflows builder. This will give you an interactive preview of the Messenger experience when talking to Fin.

Workflow builder with the Preview button highlighted, showing the interactive Messenger preview alongside the workflow canvas

Best practices for chat workflows

  • The Simple deploy for Fin AI Agent takes priority and will trigger before Advanced setup through Workflows. Please keep this in mind if setting Fin live through "Simple deploy" and adding Fin to your workflows.

  • We don't recommend having multiple workflows per topic. We recommend you have one workflow for your inbound chat, with each conversation topic defined using branches.

  • When creating a workflow, you should always set a path for "Else". In the event a customer doesn’t fall under a specific topic or audience, this ensures there is a fallback option to support them.


Analyze and optimize Fin over chat

After you've deployed Fin over chat, go to Fin AI Agent > Analyze to get real-time metrics like Customer Experience (CX) score, automated conversation analysis at scale, and AI-powered suggestions for optimizing Fin.

Here, you'll find the following dashboards:

  • Performance

  • Topics Explorer

  • Optimize

  • Conversations

As you analyze Fin’s performance and identify opportunities for improvement, you’ll need to continuously train, test, and deploy Fin to achieve an increasing number of Outcomes.

Circular diagram showing the Fin improvement cycle: Train, Test, Deploy, Analyze, and Optimize


Troubleshooting Fin over chat

Why is Fin closing conversations before they’re resolved?

If Fin is closing conversations prematurely:

  1. Navigate to Fin AI Agent > Deploy > Chat and pause Fin for chat if needed.

  2. Review and disable any auto-close settings in Workflows:

    • Check the "Let Fin Answer" block for settings like "Auto-close pending conversations."

    • Ensure settings like "Auto-close pending workflow conversations" are turned off. With these adjustments, conversations will remain open until manually resolved.

How to stop Fin interfering with handovers

If Fin is interfering with handovers when customers request a human agent:

  1. Disable the "Ask for more information before handover" setting:

    • Go to Fin AI Agent > Workflows.

    • Edit workflows with a "Let Fin handle" block.

    • Open the Let Fin handle step settings and disable Ask for more information before handover.

  2. Structure escalation guidance clearly in the "Handover & Escalation" tab:

    Example: "When routing to a human agent, inform the customer that support will assist shortly." To create more effective escalation paths, add specific escalation guidance under the "Escalation Guidance" tab with rules such as: "If a customer asks the same question twice, escalate the conversation to a human agent."

Why is Fin still replying after a conversation is escalated?

When Fin escalates a conversation, it ends its active session and stops responding. However, Fin can be re-engaged on a subsequent customer message if a workflow trigger fires again after the escalation. The most common cause is using the “Customer sends any message” trigger in a workflow that contains Fin — this fires on every customer message, including those sent after escalation, routing the conversation back to Fin.

To avoid this:

  • Use guard conditions such as:

    • Check if a teammate's reply already exists.

    • Skip Fin for conversations tagged as "Escalated" or with states other than "New."

  • Update triggers to apply only to new conversations.

Note: If Fin has unexpectedly re-engaged in an escalated conversation, a teammate must send a customer-facing (public) reply in the Intercom conversation to stop it. An internal note will not stop Fin — only a reply visible to the customer ends Fin’s session.

How to monitor escalated conversations

Monitor conversations escalated to humans by creating a custom view with filters:

  • Include "Fin AI agent involved" = true.

  • Add "Fin AI agent resolution state" = Escalated.

This view allows detailed tracking of escalated items.

How to assign conversations when Fin escalates

Control routing through the bot inbox configuration. Define handover rules that:

  • Assign unresolved conversations to specific teams.

  • Ensure smooth transitions between Fin's handling and manual intervention.


💡Tip

Need more help? Get support from our Community Forum
Find answers and get help from Intercom Support and Community Experts


Did this answer your question?