---
slug: fin
name: "Fin"
vendor: "Intercom"
page_url: https://ai-agent.review/agents/fin
record_url: https://ai-agent.review/agents/fin.md
vendor_website: https://fin.ai/
tested_performance: not-yet-tested
facts_checked_at: 2026-09-20
page_updated_at: 2026-10-03
---

# Fin

> A customer-service AI agent that answers from support content and runs configured workflows in Intercom or a connected help desk.

Vendor: Intercom. Website: https://fin.ai/

Fin answers customer questions from connected support content and can use configured Procedures to work with external systems. It runs with the Intercom help desk or supported third-party help desks. Channel availability, permissions, knowledge coverage, and escalation settings determine what a particular deployment can handle.

## Tested performance

Source-based review. This portal has not run a hands-on benchmark, so nothing here reports observed performance. No record contains a score, a rating or a benchmark result, and none will until the agents have actually been tested.

## Fit verdicts

Each state describes what the reviewed sources establish about a workflow, not whether the product is good at it. Vendor-documented means the vendor documents the workflow. External report means a source outside the vendor discusses it. Caveat documented means a cited source describes a limitation or failure in a specific context; read it alongside any capability evidence. Not established means the reviewed sources do not settle it, which is not the same as the product being unable to do it. States are derived from the cited claims below, never stored.

### Billing — Vendor-documented

- **Vendor capability:** Fin advertises invoice requests and subscription management through connected systems on its enterprise page. This is a configured workflow capability, not access to a buyer's billing account by default. _(Vendor-reported, checked 20 Sept 2026; source: [Fin for enterprise](https://fin.ai/solutions/enterprise); claim id: `fin-billing-procedures`)_

> Illustrative scenario: a customer asks for an invoice copy. Give the workflow authenticated access to the correct account and a permitted retrieval action. A disputed charge needs separate policy and escalation rules; the source does not demonstrate reliable dispute adjudication.

### Orders — Vendor-documented

- **Vendor capability:** Fin for Ecommerce documents a native Shopify connection for catalogue and order data, plus APIs and draft Procedures for post-purchase requests. _(Vendor-reported, checked 20 Sept 2026; source: [Fin for Ecommerce explained (Intercom Help)](https://www.intercom.com/help/en/articles/14997821-fin-for-ecommerce-explained); claim id: `fin-orders-vendor`)_

> Illustrative scenario: a shopper asks where an order is. The reply needs a verified customer-to-order match and current delivery data. Check that lookup in the intended channel; shopping features in web Messenger do not establish equivalent functionality elsewhere.

### Returns — Vendor-documented

- **Vendor capability:** Fin for Ecommerce lists returns, refunds, and order changes as supported conversational workflows. These rely on the connected store and configured post-purchase actions. _(Vendor-reported, checked 20 Sept 2026; source: [Fin for Ecommerce explained (Intercom Help)](https://www.intercom.com/help/en/articles/14997821-fin-for-ecommerce-explained); claim id: `fin-returns-vendor`)_

> Illustrative scenario: a customer returns an eligible item. Configure the return window, exclusions, permitted refund action, and human review for exceptions. Listing a returns capability does not establish that a particular store policy is implemented correctly.

### Product questions — Vendor-documented

- **Vendor capability:** Fin builds answers from help articles, internal support content, PDFs, and webpages. Audience rules can limit which content applies to a customer. _(Vendor-reported, checked 20 Sept 2026; source: [Fin AI Agent explained (Intercom Help)](https://www.intercom.com/help/en/articles/7120684-fin-ai-agent-explained); claim id: `fin-product-questions-vendor`)_

> Illustrative scenario: a customer asks whether their subscription includes an export feature. Supply current plan-specific documentation and check that Fin distinguishes plans rather than combining incompatible answers. Documentation establishes the answering mechanism, not an accuracy rate.

### Account issues — Vendor-documented

- **Vendor capability:** Intercom describes account troubleshooting and identity verification as Procedure use cases, with configurable system access and branching logic. _(Vendor-reported, checked 20 Sept 2026; source: [Fin Procedures explained (Intercom Help)](https://www.intercom.com/help/en/articles/12495167-fin-procedures-explained); claim id: `fin-account-procedures`)_

> Illustrative scenario: an authenticated customer changes an account detail. Restrict which fields the workflow may update and route failed identity checks to a human. A support article explaining a password reset is different from permission to change credentials.

### Complaints — Vendor-documented

- **Vendor capability:** Fin documents escalation for explicit human requests, detected frustration, and repeated loops. Custom guidance can override default escalation behavior. _(Vendor-reported, checked 20 Sept 2026; source: [Manage Fin AI Agent's escalation guidance and rules (Intercom Help)](https://www.intercom.com/help/en/articles/12396892-manage-fin-ai-agent-s-escalation-guidance-and-rules); claim id: `fin-complaints-frustration`)_

> Illustrative scenario: a customer says repeated answers have not helped. Check that the configured guidance triggers handoff and preserves the issue history. Detecting frustration does not demonstrate that the complaint was resolved.

### Human handoff — Vendor-documented

- **Vendor capability:** Fin uses configured workflows to route escalations. Intercom states that no escalation offer is shown when no human routing target exists. _(Vendor-reported, checked 20 Sept 2026; source: [Manage Fin AI Agent's escalation guidance and rules (Intercom Help)](https://www.intercom.com/help/en/articles/12396892-manage-fin-ai-agent-s-escalation-guidance-and-rules); claim id: `fin-handoff-vendor`)_

> Illustrative scenario: a customer asks for a person after an unsuccessful answer. Verify the destination inbox, transcript transfer, and after-hours response. A handoff event alone does not show how quickly a human replies.

### Small businesses — Vendor-documented

- **Vendor capability:** Fin publishes an early-stage startup programme with eligibility requirements. This establishes an offer for some small teams, not an exclusion of other small businesses. _(Vendor-reported, checked 20 Sept 2026; source: [Fin for Startups](https://fin.ai/startups); claim id: `fin-small-offering`)_

> Illustrative scenario: a small team starts with common support questions and one monitored human inbox. Compare expected use and ongoing content maintenance with available staff. Programme eligibility and a product trial do not prove affordability or suitability for every small business.

### Mid-market — Vendor-documented

- **Vendor capability:** Fin is sold with Intercom or for use with an existing help desk; the deployment options do not impose a single published company-size category. _(Vendor-reported, checked 20 Sept 2026; source: [Fin pricing and deployment options](https://fin.ai/pricing); claim id: `fin-midmarket-deployment`)_

> Illustrative scenario: a growing team keeps its help desk and adds one authenticated order lookup. Confirm connector coverage, ownership of failed actions, and routing before expanding. Team size alone is not evidence of a successful deployment.

### Enterprise — Vendor-documented

- **Vendor capability:** Fin markets an enterprise offering with workspace permission controls, activity logs, deployment services, and integrations with existing help desks. _(Vendor-reported, checked 20 Sept 2026; source: [Fin for enterprise](https://fin.ai/solutions/enterprise); claim id: `fin-enterprise-vendor`)_

> Illustrative scenario: several brands need different knowledge access and approval rules. Evaluate those boundaries and operational reporting in the planned workspace structure. An enterprise offering does not establish that all data-residency, retention, or approval requirements are met.

## Industries

An industry state says where the cited sources place the product, not how well it performed there. The same four states and the same rubric apply. Industry entries cite claims published in the agent's own record, by id, so a source is never stored twice and the two copies can never disagree. An industry with no entry is unknown, which is a gap in the public record rather than a finding.

### Retail and e-commerce — Caveat documented

- Fin for Ecommerce documents a native Shopify connection for catalogue and order data, plus APIs and draft Procedures for post-purchase requests. _(Vendor-reported, checked 20 Sept 2026; source: [Fin for Ecommerce explained (Intercom Help)](https://www.intercom.com/help/en/articles/14997821-fin-for-ecommerce-explained); claim id: `fin-orders-vendor`)_
- Full ecommerce shopping features are documented for web Messenger. Mobile receives support-only responses; email, social, voice, and Slack are not currently supported for the ecommerce role. This limit does not describe every Fin service capability. _(Vendor-reported, checked 20 Sept 2026; source: [Fin for Ecommerce explained (Intercom Help)](https://www.intercom.com/help/en/articles/14997821-fin-for-ecommerce-explained); claim id: `fin-ecommerce-channel-limits`)_

> Fin for Ecommerce is a documented product with a native Shopify connection, and the same vendor documentation states the ecommerce features are limited to the web Messenger. Read the capability and the channel limit together before assuming coverage of an email or social queue.

### Financial services — Not established

No reviewed source places this product in this industry.

### Telecommunications — Not established

No reviewed source places this product in this industry.

### Travel and hospitality — Not established

No reviewed source places this product in this industry.

### Healthcare — Not established

No reviewed source places this product in this industry.

### Public sector and education — Not established

No reviewed source places this product in this industry.

### Logistics and delivery — Not established

No reviewed source places this product in this industry.

## Strengths

- Intercom documents support for languages including Polish, French, Japanese, and Arabic. With real-time translation enabled, Fin can use content in a configured fallback language when matching content is unavailable. _(Vendor-reported, checked 20 Sept 2026; source: [Set up Fin AI Agent's multilingual support (Intercom Help)](https://www.intercom.com/help/en/articles/8322387-set-up-fin-ai-agent-s-multilingual-support); claim id: `fin-multilingual`)_
- Fin can work alongside Zendesk, Salesforce, Freshdesk, or HubSpot, as well as within Intercom. This offers a deployment route for teams that want to keep their existing help desk. _(Vendor-reported, checked 20 Sept 2026; source: [Fin for enterprise](https://fin.ai/solutions/enterprise); claim id: `fin-helpdesk-options`)_
- Procedures combine written instructions with conditions, code, and connected systems. For example, a team can encode an eligibility check before permitting an account change. Intercom also provides simulations for checking configured workflows. _(Vendor-reported, checked 20 Sept 2026; source: [Fin Procedures explained (Intercom Help)](https://www.intercom.com/help/en/articles/12495167-fin-procedures-explained); claim id: `fin-controlled-procedures`)_

## Weaknesses

- A customer leaving after an answer without asking for more help can count as a billable assumed resolution. Silence after a clarifying question does not. Intercom says a resolution charge is reversed if the customer returns to that conversation for further help. _(Vendor-reported, checked 20 Sept 2026; source: [Fin AI Agent outcomes (Intercom Help)](https://www.intercom.com/help/en/articles/8205718-fin-ai-agent-outcomes); claim id: `fin-assumed-resolution-billing`)_
- Intercom says informational answers cannot reliably calculate dates. Its FAQ directs teams to put date and arithmetic logic in a Procedure. For example, a return deadline should come from configured logic, not a generated guess. _(Vendor-reported, checked 20 Sept 2026; source: [Fin AI Agent FAQs (Intercom Help)](https://www.intercom.com/help/en/articles/7837535-fin-ai-agent-faqs); claim id: `fin-documented-task-gaps`)_
- Intercom says language detection occurs once per conversation. A customer switching language midway through a chat therefore needs explicit evaluation in the intended setup. _(Vendor-reported, checked 20 Sept 2026; source: [Set up Fin AI Agent's multilingual support (Intercom Help)](https://www.intercom.com/help/en/articles/8322387-set-up-fin-ai-agent-s-multilingual-support); claim id: `fin-language-detect-once`)_
- Full ecommerce shopping features are documented for web Messenger. Mobile receives support-only responses; email, social, voice, and Slack are not currently supported for the ecommerce role. This limit does not describe every Fin service capability. _(Vendor-reported, checked 20 Sept 2026; source: [Fin for Ecommerce explained (Intercom Help)](https://www.intercom.com/help/en/articles/14997821-fin-for-ecommerce-explained); claim id: `fin-ecommerce-channel-limits`)_
- Procedure actions run sequentially. Intercom says simultaneous queries that must be combined require a different design, such as consolidation in middleware. _(Vendor-reported, checked 20 Sept 2026; source: [Fin Procedures explained (Intercom Help)](https://www.intercom.com/help/en/articles/12495167-fin-procedures-explained); claim id: `fin-sequential-procedures`)_

## Product information

### Deployment model

- Vendor-hosted service used with Intercom or a supported existing help desk. Configuration and integration work depend on the task. _(Vendor-reported, checked 20 Sept 2026; source: [Fin pricing and deployment options](https://fin.ai/pricing); claim id: `fin-deployment`)_

### Channels

- The FAQ lists web and mobile Messenger, email, WhatsApp, SMS, Facebook, and Instagram. Confirm separate voice or other channel access and feature coverage for the intended deployment. _(Vendor-reported, checked 20 Sept 2026; source: [Fin AI Agent FAQs (Intercom Help)](https://www.intercom.com/help/en/articles/7837535-fin-ai-agent-faqs); claim id: `fin-channels`)_

### Languages

- Intercom lists supported languages and regional variants, including Polish, French, Japanese, and Arabic. Enable the required workspace languages; cross-language knowledge fallback requires real-time translation. _(Vendor-reported, checked 20 Sept 2026; source: [Set up Fin AI Agent's multilingual support (Intercom Help)](https://www.intercom.com/help/en/articles/8322387-set-up-fin-ai-agent-s-multilingual-support); claim id: `fin-languages`)_

### Help desk and CRM integrations

- Intercom, Zendesk, Salesforce, Freshdesk, and HubSpot are documented deployment options. Confirm the connector supports the required channel and actions. _(Vendor-reported, checked 20 Sept 2026; source: [Fin for enterprise](https://fin.ai/solutions/enterprise); claim id: `fin-helpdesks`)_

### Knowledge sources

- Help articles, internal support content, PDFs, and webpages; audience settings control which content Fin can use for a customer. _(Vendor-reported, checked 20 Sept 2026; source: [Fin AI Agent explained (Intercom Help)](https://www.intercom.com/help/en/articles/7120684-fin-ai-agent-explained); claim id: `fin-knowledge`)_

### Actions in backend systems

- Configured Procedures can combine conditions, code, and data connectors or MCP access to external systems. Actions execute sequentially and require the appropriate integration permissions. _(Vendor-reported, checked 20 Sept 2026; source: [Fin Procedures explained (Intercom Help)](https://www.intercom.com/help/en/articles/12495167-fin-procedures-explained); claim id: `fin-actions`)_

### Human handoff

- Escalation rules and guidance control handoff; workflows set the human destination. A bot-only workflow without a human routing target does not offer escalation. _(Vendor-reported, checked 20 Sept 2026; source: [Manage Fin AI Agent's escalation guidance and rules (Intercom Help)](https://www.intercom.com/help/en/articles/12396892-manage-fin-ai-agent-s-escalation-guidance-and-rules); claim id: `fin-handoff`)_

### Target customer size

- Fin has an explicit enterprise offering. Assess required integrations and operating controls instead of using company size as a proxy for fit. _(Vendor-reported, checked 20 Sept 2026; source: [Fin for enterprise](https://fin.ai/solutions/enterprise); claim id: `fin-targetsize`)_

### Vendor-reported performance claims

- Fin's homepage reports a 76% average resolution rate across 12,000+ customers. This is a vendor aggregate, not our result or a forecast for a particular workload. _(Vendor-reported, checked 20 Sept 2026; source: [Fin product overview](https://fin.ai/); claim id: `fin-vendor-metrics`)_

## Product positioning

Product focus: Service + sales. Product breadth: Connected suite.

Editorial view of the documented offering, not a performance ranking or a revenue measurement.

- Fin advertises service, sales, and ecommerce roles with tools for configuring and reviewing its agent. We place it in service + sales and connected suite. The separate Intercom help desk is not included in every Fin deployment. _(Editorial assessment, checked 20 Sept 2026; source: [Fin product overview](https://fin.ai/); claim id: `fin-positioning`)_

Landscape: https://ai-agent.review/positioning.md

## Evidence base

No independent source has been found for any fit area, so every state here rests on vendor material or nothing.

Independent sources behind these verdicts: none.

Verdicts across agents are not directly comparable while the evidence behind them comes from different
kinds of source. See https://ai-agent.review/methodology#evidence-asymmetry.

## Change history

Every change to this record is logged in the public changelog: https://ai-agent.review/changelog

## Corrections

Factual corrections with a public source are accepted at corrections@ai-agent.review and answered within 14 days. Quote the claim id shown with each statement above. Method: https://ai-agent.review/methodology
