Skip to main content

Deploy Fin AI Agent over email

Provide your customers with instant email resolutions using Fin AI Agent.

Written by Beth-Ann Sher

Use this article to set up Fin AI Agent over email — from verifying your email channel and training Fin on content, to testing responses, deploying to customers, and optimizing performance. It also covers multi-participant thread controls, spam filtering, and DMARC email security.

Note: This article is for workspace admins. You'll need billing permissions to set Fin live.

The following instructions have been created based on what we know provides accurate AI-powered email support within your customers’ inboxes.


How to check your email settings before enabling Fin

In order to use Fin over email, you must first ensure you have the correct setup for your email channel. Check your setup in Settings > Channels > Email.

Important: Configuring email settings (such as forwarding rules and reply addresses) is not sufficient on its own for Fin to respond to inbound emails. You must explicitly set Fin up for email by either using the Simple setup in Fin AI Agent > Deploy > Email, or by adding a Let Fin handle step to a workflow. Without one of these steps, Fin will not respond to inbound emails.

Setup requirement

Why it matters

Automatic email forwarding is set up and verified

Automatic email forwarding ensures your support emails are received into your Intercom inbox.

Your domain is connected and authenticated

Authenticating your domain enables you to send emails from your Intercom inbox using your company’s normal support email address e.g. support@yourcompany.com, rather than from an intercom-mail.com address.

This helps protect your email deliverability and gives your customers confidence that your emails are coming from you.

Set the address you want Fin to reply from

To set the address Fin replies from, go to Settings > Workspace > Brands and click on the brand. Scroll to the 'Fin email address' section and select the verified address you want Fin to use.

For multi-brand:

1. Define brand(s) within brand settings and connect each brand to the correct Help Center.

2. Connect email address(es) to the correct brand in email settings.

3. A brand aligned verified default address is selected within brand settings.

4. Set the 'Fin email address' specifically within the Brand settings modal.

Fin references Help Centers based on the brand attribute assigned to a conversation.

Connecting email addresses to a brand ensures any conversations sent to that email will be assigned the correct brand. Connecting the right Help Center to a brand ensures Fin knows which Help Center to reference to ensure answers relate to the correct brand.

Notifications and other automated messages are sent from the default email address associated with a brand; this address needs to be verified so it can be used as a sender.

Set the email address you want Fin to reply from so your customers receive Fin’s replies from the correctly branded email address.


How to train Fin for email conversations

Analyze your email conversations

You'll need to identify the audience or support topics you want Fin to handle over email and set a success metric (e.g. resolution rate, customer satisfaction (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 email queries. Update your content to cover your frequently asked email queries. You can add public articles, PDFs, snippets, URLs, or content from previous conversations.

The Fin AI Agent > Train > Content page showing enabled content sources available for Fin to use when answering email queries.

Notes:

  • Before setting Fin live, you should train it on as much up to date content as possible.

  • Even if an email has no content in its body, Fin can still read and respond to the email's subject line.

  • For emails that are forwarded to Fin, generally Fin will not read forwarded content. A workaround is to copy and paste the forwarded content directly into the email body.

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.

The Fin AI Agent > Train > Guidance page showing a guidance rule being configured to shape Fin's tone and behavior over email.

Tip Use channel-specific guidance to tailor Fin's behavior specifically for email. For example, you can instruct Fin not to suggest phone or live chat as next steps in an email reply, or adjust its tone for longer-form communication. Since Fin sends a single aggregated response over email (rather than multiple shorter messages), guidance that shapes structure and format has a bigger impact than on chat.

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.

The Fin AI Agent > Train > Attributes page showing a Fin Attribute being set up to classify conversations by topic, sentiment, or urgency.

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.

The Fin AI Agent > Train > Escalation page showing escalation conditions configured to hand conversations over to the support team.

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.

The Fin AI Agent > Train > Procedures page showing a procedure being built to automate a multi-step customer process over email.

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


How to test Fin before going live on email

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.

The Fin AI Agent > Test page showing sample customer questions being tested against Fin, with responses marked as Good or Poor.

Simply generate questions from previous conversations, bulk upload questions via a CSV (comma-separated values file), 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.

Tip: Learn more about testing Fin.

Test Fin over email in your live environment

It's a good idea to set Fin over email live to a small test or internal audience (e.g. yourself and teammates) and monitor Fin’s replies for quality and accuracy.

  1. Under the "Simple deploy", open Fin will respond to and add an audience rule for Email contains [yourcompanydomain.com] - this will enable you and your teammates to send some test emails 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. Email a question to your default workspace address to see Fin's response.

The Fin AI Agent > Deploy > Email Simple deploy page showing an audience rule set to Email contains [yourcompanydomain.com], used to restrict Fin to internal test emails before going live.

Note: If you test Fin in your live environment, you will be billed per Outcome (a resolved or completed Fin interaction). However, if you or your teammate has asked to "Get more help" or speak to your team, the conversation is considered "unresolved" and you would not be charged for this.

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


How to deploy Fin over email

Expand the audience Fin is replying to, so that Fin is replying to some real customer conversations over email. 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 > Email. At the top of this page, you'll see "Simple deploy" where you can:

  • Determine who Fin will respond to

  • How Fin answers the customer

    • Fin introduces itself

    • Using support content

      Following guidance

  • Decide what happens if Fin can't resolve the conversation

    • Hands over or escalates

    • Asks for a conversation rating (CSAT) Enabled

  • Decide what happens if customer becomes inactive

    • Follow up with inactive customers

    • Auto-closes abandoned conversations

The Fin AI Agent > Deploy > Email Simple deploy page showing all configuration sections: Fin will respond to, Fin answers the customer, handover settings, CSAT, and inactivity options.

Step 1: Fin will respond to

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

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

Tip: Use email predicates such "Email to" if you want Fin to respond to emails sent to a specific address.

Step 2: Via email channel

Before enabling Fin over email, you need to:

  1. Connect and authenticate your domain to send emails from your support address.

  2. Set up email forwarding so customer emails automatically go to your Intercom inbox.

  3. Set the email address you want Fin’s replies to be sent from.

Tip: Learn more about email settings for Fin.

Step 3: Fin introduces itself

Now configure Fin's introduction message to customers who reach out through email. 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.

The Fin introduces itself section of the Simple deploy page, showing the introduction message text field where admins write Fin's opening email message to customers.

Step 4: Using support content

Review the content sources you've enabled for Fin.

Step 5: Following guidance

Review the guidance you've configured for Fin. This is how you can tailor Fin's responses to follow your brand voice and policies. Since email behaves differently from chat, consider targeting relevant guidance rules to the email channel only — for example, to avoid suggesting real-time support options like chat or phone, or to shape how Fin structures its responses.

Step 5b: Managing replies on multi-participant threads

When Fin is deployed over email, you can control how it behaves on threads with multiple participants. Two settings are available in the Fin answers the customer section of Fin AI Agent > Deploy > Email:

The Fin answers the customer section of the Simple deploy page showing the CC behavior and reply scope radio button settings for controlling how Fin handles multi-participant email threads.

CC behavior — controls whether Fin responds when it's only addressed in CC (not in the To field):

  • Reply to all emails (default) — Fin responds to the thread regardless of whether it's in the To or CC field. This preserves existing behavior.

  • Not respond when addressed in CC — Fin stays silent if it's only included as a CC recipient, not a direct recipient.

Reply scope — controls who receives Fin's replies when it does respond:

  • Reply all (default) — Fin replies to all participants on the thread. This preserves existing behavior.

  • Reply only to the sender — Fin's reply goes to the original sender only; CC'd recipients are excluded.

The table below shows how Fin AI Agent's CC behavior and reply scope settings combine on email threads:

Thread type

Setting

Fin behavior

Fin is CC'd only

Not respond when addressed in CC

Fin stays silent

Fin is CC'd only

Reply to all emails (default)

Fin responds to all participants

Fin is a direct recipient

Reply only to the sender

CC'd recipients excluded from Fin's reply

Fin is a direct recipient

Reply all (default)

Everyone on the thread receives Fin's reply

Note: Both settings default to their existing behavior — no change occurs in your workspace until you explicitly opt in. These settings are also configurable inside the Let Fin handle step of individual workflows, independently of the deployment-level settings.

Step 6: Hands over or escalates

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. Then click Save and move to the next step.

The Hands over or escalates section of the Simple deploy page showing team and teammate assignment options for when Fin cannot resolve a conversation.

Tip: Use guidance to control how Fin responds to specific questions or customer attributes. For advanced routing, Workflows can automatically hand over to a teammate or another support tool.

Step 7: 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 if customer gives positive feedback

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

    The Ask for conversation rating section showing CSAT toggle settings for sending a rating request when a customer gives positive feedback or goes inactive after Fin answers.

Note: If a CSAT survey has been configured within a workflow, it will be sent as a separate email. Learn more about Fin AI Agent CSAT.

Step 8: Follow up with inactive customers

Customize how long Fin waits before sending a follow-up email to customers who go quiet mid-conversation. Set your preferred delay in the Follow up with inactive customers section:

  • No follow-up: Fin won't send any additional emails if the customer goes inactive.

  • Fin will follow up: Fin sends a follow-up after your chosen delay (anywhere from 1 hour to 7 days). The default is 24 hours.

The Follow up with inactive customers section showing options for no follow-up or a timed follow-up, with a duration selector ranging from 1 hour to 7 days and a 24-hour default.

Step 9: Auto-close pending Fin conversations

Choose when to auto-close conversations by specifying a length of time Fin should wait before before marking a customer as inactive. If you've enabled a follow-up, it will be sent after the last customer message. Once the follow-up is sent, the auto-close timer you set below will begin.

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.

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. Then click Save and move to the next step.

The Auto-close pending Fin conversations section showing inactivity timer options and a text field to customize what Fin says when closing a conversation.

Note: This feature is now multilingual. The closing messages you write will be automatically translated into all your supported languages when you click Save.

Step 10: Preview Fin over email

The Email Preview lets you test Fin's email experience end-to-end before going live. It shows a threaded conversation view — just like a real email inbox — so you can see exactly how customers will receive and interact with Fin's replies, including multi-turn exchanges where Fin reads and responds to follow-up messages in the same thread.

  1. In the Preview panel, type a customer question to see Fin's reply rendered in a threaded email view.

  2. To test a multi-turn conversation, reply to Fin's message in the preview thread. Fin will read the full conversation history and respond accordingly.

  3. To test as a specific customer, use the Testing as dropdown and select User or lead. You can impersonate real users or leads, use live or sample data from connected integrations, and validate personalized responses.

  4. Once you're satisfied with Fin's responses, proceed to set Fin live.

The Email Preview panel in Fin AI Agent > Deploy > Email, showing a threaded email conversation view with a customer question and Fin's reply rendered as they would appear in a real inbox.

To preview Fin over email 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.

The Email Preview panel with the Preview user dropdown open, showing the User or lead option for impersonating a specific customer to validate personalized Fin responses before going live.

Note:

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

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

  • 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.

Step 11: Review and set live

Once you've finished configuring Fin's email experience, click Set Fin Live. Fin will immediately begin responding to new inbound emails that match your configured audience rules. You can pause or update the configuration at any time from Fin AI Agent > Deploy > Email.

The Fin AI Agent > Deploy > Email page showing the Set Fin Live button at the bottom of the Simple deploy configuration.

Note: 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 > Email and open Advanced setup through Workflows.

The Advanced setup through Workflows section of the Fin AI Agent > Deploy > Email page, showing options to use an existing email workflow or create a new one.

Note: Simple deploy takes precedence over Workflows and Simple automations.

If you have an existing workflow set up specifically for email:

  • You can simply edit the workflow and 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 email:

  • We recommend you create a new workflow solely for this channel.

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

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

The Workflows builder showing an email workflow with the Let Fin handle step added to a path, ready for further configuration.

Customize Fin's behavior in your email workflow

To customize Fin's behavior in an email workflow, click on the Let Fin handle step in the workflow path. Here, you can:

  • Follow up with inactive email customers and customize the inactivity duration.

  • Ask for conversation rating (CSAT).

  • Control CC behavior and reply scope for multi-participant threads (see Step 5b below).

    Control CC behavior and reply scope for multi-participant threads.

  • Customize what Fin says when closing conversations.

The Let Fin handle step settings panel in the Workflows builder showing email-specific options including follow-up timing, CSAT, CC behavior, reply scope, and auto-close settings.

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.

  • You can also use the ‘Email’ predicates to exclude specific email addresses or domains, if you don’t want Fin to engage with a certain company or reply to a specific person.

  • For greater flexibility with email workflows, use the “Email to, "Email cc" and "Email bcc" predicates if you would like to create different auto-reply messages (and other steps and actions) depending on the email address a customer sends their message to.

  • See additional ways and examples of how you can target specific audiences or customers.- Use rules like Email does not contain support@[DOMAIN] to exclude specific addresses from Fin's workflows.

  • Apply tags like converted-ticket for follow-up emails to ensure Fin bypasses these conversations entirely.

  • Design workflows that skip emails from internal company email addresses by settings such as Email domain does not contain [COMPANY DOMAIN].

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

A branched email workflow in the Workflows builder showing different Fin paths configured for paying customers (handover to a teammate) and non-paying customers (directed to the Help Center).

Pro tip: 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 email 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.

A branched email workflow in the Workflows builder showing a Message Content condition used to route emails containing the keyword 'billing' directly to the Billing team.

Note: Any message added to the workflow immediately before "Let Fin handle" will be included in the same email notification as Fin's response.

Tip: With Fin Attributes, Fin can classify conversations by topic and use these attributes as conditions in workflows to automatically escalate conversations to the right team, ensuring customer requests are handled efficiently.

Managing unwanted emails

You can use workflows to automatically handle unwanted emails—such as newsletters, out-of-office auto-replies, or emails from known spam senders—before they reach your inbox or Fin.

  • Add a branch condition based on the sender's email address or message content to identify unwanted emails.

  • Route matching emails to a tag-and-close path: apply a tag (e.g., 'unwanted') and close the conversation automatically.

  • This keeps your inbox clean and prevents Fin from engaging with emails that aren't genuine customer queries.

Test your Fin over email workflow

If you want to test a Fin over email workflow, send an email to your support email address configured in Settings > Channels > Email > Domains & addresses.

Best practices for email workflows

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

  • Not all workflow steps are available over email. Check what actions are compatible with this channel. For this reason, we recommend creating a separate workflow solely for email as a channel i.e. don't add email / Fin over email to a workflow that has been set up for Messenger.

  • We don't recommend having multiple workflows per topic. We recommend you have one workflow for your email channel, with each email 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.

  • For workflows that use branching based on message content or keywords, add a fallback branch to route unmatched free-text messages to Fin. This ensures customers who don't match a specific branch still receive an automated response rather than falling through to an unassigned state.

Known limitations for multi-participant email threads

  • Fin defaults to treating the sender as the customer. If the sender isn't the actual customer (for example, a colleague forwarded the email), Fin has no way to identify who the end user is — it always treats the sender as the person to assist.

  • Cross-workspace CC isn't handled. If another organization's Fin is monitoring a CC'd email address, it may still respond to the thread independently.

  • Contact attachment limitations. On threads with multiple participants, Intercom may attach the conversation to the wrong contact record. These CC/reply scope settings don't resolve that issue.

  • Fin's behavior is rule-based. Fin applies these settings exactly as configured — it doesn't use AI judgment to determine how to handle CC'd participants beyond what the settings specify.


Analyze and optimize Fin over email

After you've deployed Fin over email, 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.

A circular diagram showing the continuous Train, Test, Deploy cycle for optimizing Fin AI Agent performance over time.


How Fin responds to emails

Fin AI Agent can reply to your customers' questions over email just like it does in the Messenger. Every email response from Fin will:

  • Indicate that it’s an AI agent.

  • Provide the source of the answer inline (if public to your audience).

  • Give users options for next steps, including speaking to a teammate.

  • Show your email signature.

  • Show the AI disclosure in a footer below the signature.


What customers experience when Fin replies over email

You can choose how Fin follows up with customers over email. By default, Fin will ask a relevant question to encourage a natural conversation.

Note: The email will always include a sentence indicating it was generated via AI to ensure transparency with customers. This disclosure helps set the right expectations by informing customers that they are interacting with an AI agent rather than a human. It also aligns with best practices for AI communication, where clarity about the nature of the interaction is crucial. Additionally, this transparency can help manage customer expectations regarding the type of assistance they are receiving and provide them with options for next steps, such as speaking to a human teammate if needed.

If the customer's message is not clear, Fin will send a message asking to clarify what they need assistance with.

A sample customer email with Fin's AI-generated reply, showing the answer text, inline source citation, and next-step options including confirming the answer helped or requesting a human teammate.

Note: If Fin doesn't have an answer, it will let the customer know and give them the option to ask another question or talk to a person. Fin will not send any error messages over email like it does for chat (i.e “Oops, something went wrong”). Instead, it will immediately escalate to your team.

When the customer responds, they have the following options:

  • Reply with additional information.

  • Reply confirming the answer helped, which will mark the conversation as a confirmed resolution.

  • Reply asking for help, which will trigger the handover process.

Customers will receive a follow-up email confirming the action:

  • When a customer asks for more help or requests a person, the handover between Fin AI Agent and a teammate will be triggered.

  • When a customer confirms the answer helped, Fin AI Agent will respond and close the conversation - unless otherwise configured.


How Fin filters spam on email

Intercom has a sophisticated built-in spam filtering system that automatically checks incoming emails for hidden links, malware, phishing attempts, and proper authentication of sender's address. We assign all inbound emails a spam score and filter messages that exceed our spam threshold. This is Intercom's infrastructure-level spam filter, which runs first on all inbound email.

Tip: If you need help finding spam-filtered emails or pinning the Spam folder to your sidebar, see How does spam filtering work? in the Inbox FAQs.

An overview of Intercom's infrastructure-level email spam filtering system, showing how inbound emails are scored against a spam threshold before reaching Fin or the inbox.

Customize Fin AI Agent's spam guidance

Fin AI Agent uses an AI spam detection system that triggers very early in the inbound email processing pipeline, before a conversation is created. Emails flagged as spam by this system are automatically routed to the Spam folder. This prevents Fin from engaging with spam messages, leading to more accurate metrics for Fin’s Involvement Rate. Unlike the infrastructure-level spam filter, which uses a numeric score against a configurable threshold, the AI spam filter makes a binary yes/no decision — there is no score or threshold involved.

You can customize the behavior of the AI spam detection using Spam Guidance.

  1. Scroll down to the "Spam" section and click New.

  2. Add your customized guidance on how Fin should identify and handle potential spam messages.

The Fin AI Agent > Train > Guidance page showing the Spam section, with a new spam guidance rule being added to customize how Fin identifies and handles potential spam emails.

The Spam inbox view

The Spam view shows all email conversations Fin has flagged. Each flagged conversation includes a brief reasoning note from Fin, so your team can quickly understand why it was flagged and decide what to do next.

  • Review Fin's reasoning — each flagged conversation includes a note explaining why Fin flagged it

  • Mark as Not spam — clears the flag and returns the conversation to your inbox for normal handling

  • Manually flag spam — mark any conversation as spam from the conversation header in the All inbox

If a genuine customer follows up on a spam-flagged conversation, Fin automatically re-evaluates and can clear the flag. Follow-ups from actual spam are re-evaluated and can be confirmed as spam.

Note:

  • The Spam inbox view requires Fin AI Agent to be enabled and applies to email conversations only. The view starts empty — conversations aren't classified retroactively.

  • The Spam inbox holds all spam emails. These conversations do not have conversation IDs and therefore do not count towards reporting.

By default, emails marked as auto responders go to your Spam folder but if you need these to appear in your inbox, you can turn off this setting so they are routed to the inbox from Settings > Channels > Email > Email settings.

The Settings > Channels > Email > Email settings page showing the toggle to route auto-responder emails to the inbox instead of the Spam folder.

Note: Do not use your custom domain email address to sign up to newsletters or advertisements. This will prevent Fin from getting involved in these conversations.


How to enhance email security with DMARC authentication

You can add an important layer of security to your inbound email flow by preventing Fin from processing emails that fail DMARC authentication. This ensures Fin only engages with emails sent from legitimate, verified domains, reducing the risk of fraud.

DMARC (Domain-based Message Authentication, Reporting, and Conformance) is an email authentication protocol designed to protect your domain from spoofing and phishing. It allows you to specify how incoming messages should be handled if they fail authentication checks.

When the “Prevent Fin from processing emails that fail authentication (DMARC)” setting is enabled, any inbound email that fails this check will be blocked from reaching Fin and Fin will not respond.

To enable this:

  1. Navigate to your Fin AI Agent > Fin settings > General.

  2. Go to the Fin's email responses section.

  3. Click the toggle to enable Prevent Fin from processing emails that fail authentication (DMARC).

The Fin AI Agent > Fin settings > General page showing the Fin's email responses section with the DMARC authentication toggle enabled to block emails that fail authentication checks.

Important: Enabling DMARC protection in Fin settings will stop Fin from responding to any users with unauthenticated email setups. If a sender fails these checks, the conversation will remain unassigned and will need to be manually routed to a teammate if required. You can create a workflow rule to automatically assign these conversations based on your team's preferences.

Note: Only teammates with the appropriate permissions, such as workspace admins, can access this setting. If you do not see the toggle, please contact your Intercom admin to check your access level.


FAQs

Does Fin reply when it's CC'd on an email?

By default, yes — Fin replies to all emails regardless of whether it's a direct recipient or CC'd. You can change this.

Go to Fin AI Agent > Deploy > Email and find the CC behavior setting under "Fin answers the customer":

  • Reply to all emails (default) — Fin responds regardless of whether it's in the To or CC field.

  • Not respond when addressed in CC — Fin stays silent if it's only CC'd, not a direct recipient.

Note: This setting defaults to existing behavior — Fin's response pattern won't change unless you opt in. It's also configurable per workflow in the Let Fin handle step.

Who does Fin send replies to on a CC'd thread?

By default, Fin replies to all participants — the sender goes in the "To" field and anyone CC'd stays in the "Cc" field. You can restrict this.

Go to Fin AI Agent > Deploy > Email and find the Reply scope setting under "Fin answers the customer":

  • Reply all (default) — everyone on the thread receives Fin's reply.

  • Reply only to the sender — Fin's reply goes to the original sender only; CC'd recipients are excluded.

This setting defaults to existing behavior. It's also configurable per workflow in the Let Fin handle step, independently of the deployment-level setting.

Is multilingual Fin available over email?

Yes, Fin for email is also multilingual and can assist your customers in different languages. To learn more about this feature and how it works, check out the article Multilingual Fin AI Agent.

How are Fin email conversations and outcomes billed?

Fin AI Agent email conversations are charged per Outcome, the same as all other channels. An Outcome is counted when Fin either resolves the customer's issue (a Resolution) or successfully completes a Procedure configured to end in a handoff. Learn more about Fin Outcomes.

How does Fin over email work with Customer tickets?

Fin AI Agent over email will respond to Customer tickets the same as it does with conversations. This includes the email setting to auto-convert emails into tickets, where emails will be automatically converted into tickets and Fin will handle the ticket conversation as normal.

Why is Fin replying to emails with a handle like "Examply at Examply," and how can I fix it?

This happens when your AI agent is using the same name as your brand. If both the bot and the brand name are set to "Examply," the email sender name will appear as "Examply from Examply."

To fix this, change the AI agent's name:

  1. Under Choose an identity for your bots, update the bot’s name to something different from your brand name.

  2. This will ensure the sender name appears correctly in emails sent by Fin.


💡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?