Mike HeapMike is an experienced Product Manager who focuses on all the “non-development” areas of My AskAI, from finance and customer success to product design, copywriting, testing and more.
Table of Contents
- Intercom vs Front at a glance
- How are Intercom Fin and Front AI different from their old 'AI bots'?
- How does an AI customer service agent work in Intercom and Front?
- How can I use my AI agent in Intercom and Front?
- Direct replies
- Copilot replies
- Voice
- Which is easier to set up: Intercom Fin or Front AI?
- How do Intercom Fin and Front AI differ in what they can be trained on?
- 'Static' content
- 'Dynamic' content
- Which has better answer quality, Intercom Fin or Front AI?
- Is Intercom Fin or Front AI easier to improve?
- Which has more features: Intercom Fin or Front AI?
- How easy is it to customize Intercom Fin and Front AI?
- What about vendor lock-in?
- Do Intercom Fin and Front AI have any other AI features?
- Tagging
- Agent translation
- What about security, is Front more secure than Intercom?
- Front vs Intercom: which costs more to run?
- The pricing model
- The overall cost
- Conclusion - should I choose Intercom or Front?
- FAQs
Created time
Aug 26, 2026 11:12 PM
Title length (<60)
Author
Last optimised
Ecomm?
Tags
Image
Publish date
Aug 6, 2026
Video
Slug
intercom-front-comparison-2026
Featured
Type
Article
Ready to Publish
Ready to Publish
Intercom rebuilt its whole product around Fin, an agent that runs by default and bills per outcome, while Front layered AI onto its shared inbox so Autopilot only touches the topics an admin switches on. Pick Intercom for the deeper agent and published resolution rates, or Front if you want the AI gated topic by topic inside a collaborative inbox.
Fin bills $0.99 per outcome (a resolution or a Procedure handoff) inside a $49 a month base plan covering the first 50, while Front's Autopilot charges $0.05 to triage a conversation, $0.39 to hand one off and $0.89 to resolve one. Your bill turns on how often the AI finishes the job for you. That makes Front the cheaper meter across most mixes, and Intercom the stronger agent for a support team willing to do the content work behind it.
Both vendors meter the AI agent separately from the seat price. At 10,000 AI conversations a month on a 10-seat team, the meter costs more than the seats on both sides.
Disclosure: My AskAI publishes this comparison. We run inside Zendesk, Intercom, Freshdesk, Freshchat, Gorgias and HubSpot, so the third option I mention exists on the Intercom side of this comparison only. Both platforms below are scored on their own AI, on their own published numbers.
Intercom takes seven of the eleven scored categories, Front takes two, and two are tied. The two rows Front wins are the two a buyer feels in week one.
One live risk sits outside that scorecard. Salesforce has agreed to acquire Fin, and that deal has not closed.
Prices, rates and certification lists in this post come from each vendor's own site, checked at the end of August 2026. Both vendors move fast (Front folded four AI products into one in a single release), so click through before you sign anything.
Intercom vs Front at a glance
Intercom (Fin) | Front (Front AI) | |
What it is | AI-first helpdesk built around the Fin agent | Collaborative shared inbox with AI layered on |
Headline price | $0.99 per outcome, on top of $29-$132 per seat | $0.05 triage, $0.39 handoff, $0.89 resolution, on top of $25-$105 per seat |
How you buy it | Self-serve; 14-day trial includes unlimited Fin outcomes | Self-serve plans; the 14-day trial mirrors Professional and excludes Autopilot |
Best for | Teams who want the deepest agent available today | B2B teams who want AI released one topic at a time |
Not a fit for | Teams who want the AI bill flat as quality improves | Teams who want the agent without moving their helpdesk |
Biggest limitation | Resolution rate needs content work, best improvement tooling from $99/mo | Autopilot is English-only, shared-inbox only, and cannot be bought standalone |
Scorecard | 7 category wins of 11, 2 tied | 2 category wins of 11, 2 tied |
How are Intercom Fin and Front AI different from their old 'AI bots'?
TL;DR: Both replaced a rules-based bot with an AI agent that writes its own answers, by very different routes. Intercom rebuilt the company around the agent. Front layered AI onto a shared inbox and retired its earlier bot outright.
Front got there by deprecation. AI Compose and AI Summarize came first, then AI Answers and AI Tagging. Both of those later products are now legacy.
Front's help center records that AI Tagging is no longer available to new users, and AI Answers is no longer sold either. Topics replaced the first, and Autopilot replaced the second (so older write-ups of Front AI are describing retired products).
The current generation arrived when Front unified Topics, Copilot, Smart QA and Smart CSAT into one product called Front AI. Autopilot shipped after that, followed by Playbooks and Resolve. So when I score Front AI, I am scoring a product that is still filling out.
Intercom's version of that arc is a company-level rebuild. Fin 3 is the current generation and it runs on Intercom's own Fin Apex 1.0 model. Apex is a model inside Fin 3 rather than a new version of the agent (an easy one to misread).
The parent company has since renamed itself Fin, and "Intercom" survives as the name of the helpdesk product. That naming is confusing, and both vendors' sites assume you know it already.
Both vendors publish headline customer counts. Front claims 9,300+ companies on its homepage. Intercom claims 30,000+ customers across the whole platform, with the Fin-specific cohort at 7,000+ teams (that last figure is the one to hold against Front's).
Those are two different counts and they should not be read as one.
Both products review well on G2:
Intercom Fin | Front | |
Rating | 4.5/5 | 4.7/5 |
Reviews-page link |
Both vendors publish named customers, which makes the proof checkable. Front's headline Autopilot reference is Boundless Immigration, which reports 10,000+ hours saved per quarter, alongside Reed & Mackay at 97% CSAT and Uber Freight. On the Intercom side, Anthropic is written up as a build-versus-buy decision, Lightspeed Commerce as an enterprise rollout, and Kalshi and Nuuly as automation stories.
Want the full picture of what Fin does before you compare it? Our complete guide to the Intercom Fin AI agent covers it properly. We have a matching explainer for Front AI.
How does an AI customer service agent work in Intercom and Front?
TL;DR: Fin retrieves from connected knowledge and can run multi-step Procedures. Front's Autopilot only acts inside Topics an admin has switched on, and it learns from your past conversations as well as a connected knowledge source.
Front is opt-in by topic. Fin is on by default and escalates by exception.
Front AI reads your historical conversations all the time, looking for tone, common questions and successful resolutions. On top of that you connect one knowledge source (just the one).
Autopilot then gets switched on per Topic, and only after an admin has compared its sample drafts against what teammates actually wrote. Front describes the product plainly in its Autopilot documentation:
"Autopilot is an omnichannel AI agent built for automation, handling both the generation and sending of replies on its own."
Copilot is the other half. Front draws a clean line between the two. Autopilot generates and sends replies on its own (sending is the whole difference).
Copilot summarizes a conversation for a teammate and surfaces relevant history and knowledge. It drafts a reply that a person prompts for and reviews before anything goes out.
Fin answers from your connected knowledge as standard, then hands to a human when it should. I find it the easier model to explain to a team.
On top of retrieval it runs Procedures, which are multi-step workflows written in plain language. They handle if/else branching, wait steps, steps that pause until another system reports back, and Python snippets for the parts that need real logic. Tasks were the earlier name for this, and new Task creation has been switched off, so Procedures is the term to search for.
Fin also runs a content-gap loop in the background. I rate it one of the most useful things in the product.
It drafts new snippets for the questions it could not answer and puts them in front of an admin to approve or reject. Nothing publishes without a person saying yes.
How can I use my AI agent in Intercom and Front?
TL;DR: Both run direct customer replies and an agent-side copilot. Fin adds a first-party voice agent, while Front routes voice through Dialpad, Aircall or RingCentral.
Direct replies
Front's Autopilot is properly omnichannel. That surprised me. It covers email, chat, SMS, WhatsApp, Slack and custom channels, and Autopilot Resolve embeds self-service inside your own product.
There is one real fence around it, and Front states it in its own FAQ: "No. Autopilot only applies to shared inboxes." The workaround Front suggests is creating a shared inbox that only one person can access, then moving conversations into it.
Front's AI coverage is also uneven at the edges, and this is where I docked the Modes row. The Copilot and Smart CSAT help articles do not list Facebook or Instagram. So AI coverage on Meta channels is limited, even though the inbox itself supports them.
Fin's channel list is longer. It covers Fin Messenger on web, iOS and Android, email, phone, WhatsApp, SMS, Facebook Messenger, Instagram, Zendesk Messenger and tickets, Salesforce Messenger and Cases, Slack, Discord and the public API. Telegram is on the list too.
Copilot replies
Both sides ship an assistant that drafts for your team rather than the customer (both called Copilot, confusingly). Front's Copilot sits in a sidebar next to the conversation, summarizes it, surfaces related history and drafts a reply with sources attached.
One correction (and it changes who can use Copilot): Front's Copilot works in individual inboxes too. The shared-inbox limit applies to Autopilot only. I read that as the difference between a one-person desk getting AI from Front and getting none.
Intercom's Copilot lives in the inbox sidebar and answers agent questions from the same knowledge Fin uses. It shows which source it pulled from and pastes the answer into the composer. Intercom bundles a small free allowance with every seat.
Voice
Voice is the cleanest split I found in this comparison. Fin ships its own voice agent.
Fin Voice 2 ships on Fin Apex Flash, with 28 voice languages. Intercom quotes it through sales, with no published rate (so budget for it off a sales call).
Latency, which means how long a caller waits for an answer, is what Intercom tuned it for. Intercom's changelog describes it this way:
"Fin Voice 2 runs on Fin Apex Flash, our latest model built for latency-sensitive tasks. It delivers a 24.5% higher resolution rate and responds 0.43 seconds faster, with 20+ updates across call quality, actions, and insights."
In my experience a caller notices a pause on the phone far more than a chat user does.
Front has no voice AI agent of its own. Voice on Front comes through Dialpad, Aircall or RingCentral integrations. Front's Idiomatic acquisition was voice-of-customer analytics, which is a different thing from telephony, and it is easy to misread on a feature list.
Which is easier to set up: Intercom Fin or Front AI?
TL;DR: Front is faster to a first useful reply. Topics auto-generate in one to two hours from your recent conversations, and you switch on one at a time. Fin turns on instantly but needs content work before the resolution rate is worth having.
Front's setup flow is documented step by step, and it is short. Front AI scans up to 10,000 conversations from the past 30 days and proposes Topics, which takes about one to two hours. You review, rename and merge them (the only part that takes real thought).
You connect one knowledge source. You pick a Topic and toggle auto-replies on for it. Then you set the disclosure text customers will see.
All of it is no-code, and none of it needs a developer. There is one gate: Front AI needs a Front plan that includes AI access, and a company admin has to turn most of them on.
Fin turns on faster on paper, and that is what made the setup row the hardest one for me to score. The trial is 14 days, needs no card, has no seat minimums and includes unlimited Fin outcomes. Native Help Center articles import automatically and update instantly.
The catch is what happens after that. Intercom's own guidance is that Fin needs content work to perform. Getting from a fresh install to a number worth paying for is a content project.
My AskAI closes that gap with our Train on Historic Tickets backfill. It auto-drafts starter articles from your last 5,000 historic tickets, and you review them before they go live.
Front's testing story is thinner. You get branching rule testing and per-Topic sample replies, which compare AI drafts against what your teammates wrote.
Fin gives you Previews, Batch tests of up to 50 questions with CSV export, Simulations and Controlled Rollout with a hard cap that auto-disables Fin. Front's help center documents no way to replay past tickets before you go live.
The Autopilot trial is self-serve, which I did not expect from a plan-gated product. Front's own pricing article spells it out.
"To try Autopilot for free, navigate to the Front AI page in your workspace settings, hover over the Get add-on button for Autopilot, then select Start free trial. This will start a 30-day trial with full access to all Automations and up to 1000 Resolutions."
I held Front to an 8 on the setup row because of that paywall. The 14-day new-customer trial mirrors the Professional plan, and Professional does not contain Autopilot.
How do Intercom Fin and Front AI differ in what they can be trained on?
TL;DR: Front connects Notion, Google Drive and SharePoint and always learns from past conversations, but it caps public-site crawling at roughly 3,000 pages with manual re-sync. Fin's connector list is longer, and its knowledge is scoped per brand where Front's is scoped per workspace.
Knowledge source | Intercom Fin | Front |
Native help center | ✅ ingested almost instantly | ✅ Front's own recommended best source |
Public website crawl | ✅ up to 10 external sources at 3,000 URLs each, weekly re-sync | ✅ roughly 3,000 pages per source, manual re-sync once per 24h, no protected sites |
Notion | ✅ syncs every 24h | ✅ supported as an AI knowledge source |
Google Drive | ✅ | ✅ Google Docs |
SharePoint | ❌ not in Fin's list | ✅ Word and Doc files |
Past tickets / conversations | ⚠ Copilot uses recent chat and ticket history; the agent learns through auto-drafted snippets | ✅ always on, for tone, common questions and successful resolutions |
File upload | ✅ document upload is a documented Fin source | ❌ no first-class file upload documented; files arrive through the Drive, SharePoint and Notion connectors |
Live backend data | ✅ Data Connectors for Shopify, Stripe, Salesforce and custom APIs, plus Fin Vision for images | ⚠ Playbooks can call connected systems, but there is no documented knowledge connector to live data |
'Static' content
Front is direct about where its AI works best. Front's own knowledge-source documentation says: "Using a Front knowledge base as the source for AI features provides the most reliable performance."
The public-website source is where Front's ceiling shows (and where I expect most teams will feel it). It handles roughly 3,000 pages per source, it will not read anything behind a login, and refreshing is a manual job.
Front answers the obvious follow-up itself: "No. To update your content, you must manually trigger a re-sync in the AI knowledge source settings." If your docs change weekly, someone owns that button.
Fin's training-source list is longer: internal articles, snippets, website sync, Zendesk articles, Salesforce articles, Freshdesk articles, Guru, Notion, Confluence, Box, Document360 and direct document upload. Front supports Notes and attachments as supporting material, and Autopilot and Copilot can read PDF and image attachments.
Scoping is the other split. Front's knowledge is workspace-scoped (one pool for everyone).
Fin's is scoped per brand, with multibrand Messenger and Help Center gated to the Expert tier.
My AskAI connects Notion, Confluence, Google Drive, SharePoint, OneDrive and Dropbox, and we let you mark any source internal-only. Train on Historic Tickets also drafts starter articles from your last 5,000 historic tickets, the default backfill.
'Dynamic' content
Fin is clearly ahead on live data. Data Connectors pull order status, subscription state and account records from Shopify, Stripe, Salesforce and your own APIs. That is how the agent answers a where-is-my-order question with a real answer.
Fin Vision reads images customers attach.
Front's equivalent is Playbooks, which can call a connected system as part of a workflow. That covers actions, but Front does not document a general live-data knowledge connector, so the agent's factual grounding stays on documents and past conversations.
Front does add one control I like. Fact invalidation lets an admin trash a specific fact the AI has learned. It stays struck through and out of future replies until you undo it.
It is a small thing that saves a support lead a lot of arguing. I wish more agents had it.
On the training question Intercom publishes its own boundary. I like that it is written down. Fine-tuning, which means Intercom adapting a model on your data, is what your legal team will ask about:
"Fin trains only on your knowledge and Procedures, never on data you haven't approved, and you can opt out of fine-tuning anytime, with data deleted within 30 days."
The opt-out is the clause they will want, so put it in front of legal early.
Which has better answer quality, Intercom Fin or Front AI?
TL;DR: Fin publishes resolution rates and Front does not. Front claims Autopilot can resolve up to 70% of requests, and its named customer proof measures hours saved.
Front's claim sits on its AI product page and its homepage: "Resolve up to 70% of requests". There is no benchmark behind it, and that shaped how I scored the answer-quality row. Front's help center publishes no auto-resolution rate at all, and no competitive test.
Front does publish productivity proof. Four customers put numbers on it.
Boundless Immigration reports 10,000+ hours saved per quarter. Fathom reports a 56% cut in reply time (with over 65% of suggested replies used).
Front's homepage credits Branch Insurance with 482% ROI and 75% faster response after moving off Zendesk. Reed & Mackay reports 97% CSAT.
Those numbers cover time and satisfaction (take vendor-picked wins with a grain of salt).
None of them tells you how many tickets the AI closed on its own.
Intercom publishes the number, and then publishes a different one somewhere else. Fin's guarantee page says:
"Fin's average resolution rate has grown from 30% to 76% since launch."
Fin's comparison page says:
"Fin's average resolution rate is 71% across 7,000+ customers, improving approximately 1% per month."
Both sit on Fin's own site at the same time. They are different figures with different framing (only one carries a customer count).
Treat each as a claim attached to the page it appears on, and do not read 71% and 76% as a trend line. I hold the 71% figure as the readable one, because it names a customer count.
Fin's definition is what makes either figure readable. A resolution counts when the customer confirms the answer helped, or when the customer simply leaves without asking for more help.
That second case is an assumed resolution after 24 hours of silence (clawed back if they come back). Ask any vendor how they count this before you compare rates.
For context on where the field sits, our own AI resolution rate benchmark study covers 195 rated deployments across 38 vendors. The median lands around 70%. Three caveats travel with that number.
It aggregates across vendors, so no single vendor's score sits inside it. It is directional, because every vendor defines resolution its own way (Fin's 24-hour silence rule above is a good example). And the teams who report tend to be the ones happy with their results.
So Front's "up to 70%" is a normal claim. Fin's 71% to 76% sits at the upper end of a self-selecting sample.
Is Intercom Fin or Front AI easier to improve?
TL;DR: Fin has the deeper improvement loop, with batch tests, simulations and controlled rollout, but the richest part sits behind a $99/month add-on. Front gives you sample-reply review and fact invalidation, with no way to replay past tickets first.
Front's levers are all about what the AI is allowed to use. Tone matching happens automatically, and fact invalidation lets you retire a specific fact.
Topics can be merged and renamed (a similarity score guides you). Before auto-reply goes on for a Topic, you compare the AI's sample drafts against teammate replies. That is the closest thing Front has to a dry run, and I gave Front credit for having one.
Front puts Topic accuracy at around 85%.
Front is also open about the ceiling, in its own community Q&A. LLM there stands for large language model, the software that writes the reply:
"We do not train any models ourselves; we work through vendors for LLM use."
That is a reasonable engineering decision (plenty of vendors do the same), and Front puts it on the record. You improve Front's AI by fixing your knowledge and the messages your team send.
Fin's loop is deeper on every axis. Previews, Batch tests, Simulations and Controlled Rollout all exist.
The content recommendations dashboard groups what Fin is missing into content gaps, data gaps and action gaps. It drafts the missing article and waits for you to accept or reject it. There is an Improve Answer button in the inbox, though it does not appear when the answer came from a Procedure.
Here's the catch. The best of that tooling sits behind Intercom's Pro add-on, from $99 a month for 1,000 conversations. That covers AI Recommendations, CX Score, AI Topics, Trends, Monitors and Custom AI Scorecards.
The add-on now includes 2,000 Operator credits a month (then $0.01 per credit). Intercom also documents that recommendations are static as of the moment they were generated, so treat them as a to-do list you work through.
Which has more features: Intercom Fin or Front AI?
TL;DR: Fin has the broader AI feature set, with an eight-model engine, Procedures, Memory, ecommerce catalog sync and incident detection. Front's set is narrower and built around control and quality assurance.
Feature | Intercom Fin | Front |
Autonomous customer-facing agent | ✅ Fin AI Agent | ✅ Autopilot, shared inboxes only |
Multi-step agentic workflows | ✅ Procedures, plain language plus Python | ✅ Autopilot Playbooks, plain language |
Embedded in-app self-service | ✅ Fin over API and Messenger | ✅ Autopilot Resolve |
Agent-side copilot | ✅ $29/agent/mo annual, $35 monthly | ✅ $20/seat/mo, bundled on Enterprise |
First-party voice AI agent | ✅ Fin Voice 2, 28 voice languages | ❌ integration-only via Dialpad, Aircall, RingCentral |
Automated QA scorecards | ✅ Custom AI Scorecards, Pro add-on from $99/mo | ✅ Smart QA $20/seat/mo |
AI-inferred CSAT | ✅ CX Score across all conversations, Pro add-on | ✅ Smart CSAT $10/seat/mo, no survey needed |
Image and attachment understanding | ✅ Fin Vision | ✅ PDF and image attachments |
Live commerce catalog | ✅ Fin for Ecommerce, live Shopify sync | ❌ not documented |
Cross-conversation memory | ✅ Fin Memory | ⚠ tone and past-conversation grounding only |
Proactive or triggered engagement | ✅ Proactive Procedures | ❌ not documented for Autopilot |
Incident detection | ✅ Incident Detection | ❌ not documented |
Escalation analytics | ✅ Escalation Reporting | ✅ Autopilot Report, resolved and handed-off percentages, CSAT split |
Multi-brand isolation | ✅ multibrand Messenger and Help Center on Expert | ⚠ workspace-level segmentation |
"Not documented" means Front's public help center and product pages do not describe the capability. It is not a claim that Front cannot do it.
My AskAI covers a lot of this from inside the helpdesk. We have a pre-built Shopify connector for product and order lookups, image reading, Tasks and Tools workflows, internal-note replies and one agent per brand.
Fin's model page enumerates eight purpose-built models: Fin Apex 1.0, Fin Apex Flash, Fin Retrieval, Fin Reranker, Fin Issue Summarizer, Fin Feedback Parser, Fin Language Detector and Fin Escalation Router. Intercom describes the first one this way:
"Fin Apex 1.0 is the flagship of the Fin model suite - our first model that generates the final answer Fin gives to every customer."
Read the FAQ at the bottom of that same page and it still says seven, so quote the numbered list if anyone asks.
Front's set is smaller and organized around control and measurement: Topics, Copilot, Smart QA, Smart CSAT, Compose, Summarize, Autopilot with Playbooks and Resolve, and an AI replies hub that lists every message the AI generated. That last one has real audit value. I like being able to hand a reviewer every message the AI sent.
Front's packaging is the part to read twice (this is where a budget gets a surprise). Three of these are bundled and one never is:
"For new customers, all Front AI features except for Autopilot are included in the latest version of the Enterprise plan."
So Enterprise bundles Copilot, Smart QA and Smart CSAT. Every plan below buys them per seat. Autopilot is metered per conversation on every plan, Enterprise included.
How easy is it to customize Intercom Fin and Front AI?
TL;DR: Front's customization is about permission, covering which topics the AI may touch and what the disclosure text says. Fin puts the emphasis on capability, with Procedures that run real logic. Both sets of knobs are useful.
Front hands a compliance officer a surface they can audit, and that is the row where I gave Front the win. You choose which Topics are automated and which are not, and Front is direct about that being the control.
There is no formal blacklist on Front, and you decide topic by topic what should be automated and what should not. An auto-generated rule governs when the AI engages, a teammate can step in mid-conversation, and facts can be invalidated one by one.
Two more Front controls do real work (both easy to miss on a demo). The disclosure text is editable, which matters if your region requires specific wording, and Front's Autopilot configuration article sets out the setting: "By default, Front adds a disclosure to every AI-generated reply as a short message. You can adjust the disclosure language in your Front AI settings." And Copilot inherits its user's access: "Copilot has the same permissions as the teammate using it."
Front is equally direct about where the customization stops:
"You cannot explicitly train Copilot or Autopilot to sound like you"
Fin's knobs are about what the agent says and when it escalates, and I found more of them. Fin Guidance lets you write natural-language instructions across communication style, context and clarification, content and sources, spam and escalation, plus channel-specific rules.
On top of that sit five tone presets, answer-length controls, per-language pronoun formality, per-brand knowledge isolation, and Procedures that execute actual logic.
So Front hands a compliance reviewer something to sign off. With Fin, a support lead writes the instructions the agent follows. Both are useful, and which one you want depends on who in your business owns the AI (compliance or support).
What about vendor lock-in?
TL;DR: Fin runs on Zendesk, Salesforce, Front and Freshdesk as well as Intercom, so you can try it without leaving your helpdesk. Front AI cannot be bought standalone, so using it means moving support onto Front.
Lock-in is the widest gap on the scorecard.
Front's prerequisites page is unambiguous: "You must be on a Front plan with access to AI features." The AI is a property of the plan. If Autopilot is the reason you are interested in Front, you are buying a helpdesk migration.
Fin can be bought on its own, and I scored the lock-in row almost entirely on that. Fin's own pricing page covers running it on Salesforce, HubSpot, Freshworks, Front, Gorgias and other helpdesks at $0.99 per outcome.
That sits inside a $49 a month base plan with 50 resolutions included. There are no seat costs for teammates and no integration, setup or platform fees.
The standalone version does have fences (check these before you plan around it). Slack and proactive outbound messaging are not supported when Fin runs on Zendesk or Salesforce, and Fin for sales qualifications and disqualifications is Intercom-only.
Salesforce signed a definitive agreement to acquire Fin for around $3.6 billion, announced on 15 June 2026. Salesforce's press release says the deal is expected to close in the fourth quarter of Salesforce's fiscal year 2027, subject to regulatory clearances.
It has not closed (Salesforce does not own Fin today), and Fin and Agentforce remain separate products. Put it on your risk register.
Buyers on Reddit describe lock-in in a more practical way than any contract does:
"both ship with AI deflection priced as part of the seat rather than metered. trade-off is you lose Intercom's outbound + tours, which might or might not matter depending on whether you actually use them." - u/Equivalent-Sky-7052 on r/SaaS
"when you switched off Intercom, what did you move to and how painful was the knowledge base migration specifically? That's one of our bigger concerns" - u/Old-Source2534 on r/SaaS
The knowledge base is the real switching cost. That is the argument for keeping the agent layer separate from the desk.
We run My AskAI inside Zendesk, Intercom, Freshdesk, Freshchat, Gorgias and HubSpot, so the agent you train follows you when you change desks. That route exists on the Intercom side of this pair.
Do Intercom Fin and Front AI have any other AI features?
TL;DR: Front's extras cluster around measurement, with Smart QA scorecards, Smart CSAT and Topics analytics. Fin aims its extras at operations, covering incident detection, escalation reporting and CX scoring. Both charge extra for the good parts.
Tagging
Front's AI Tagging is legacy and closed to new users. Topics is the replacement, and I rate it the better of the two. Topics clusters your conversations into subjects with volume counts, so you can see what people are actually writing in about.
There is a real limit here, and Front states both halves of it: "Topics are only available in English. However, Front can interpret conversations in dozens of languages to generate corresponding Topics in English." So a multilingual inbox will get sensible clusters, written in English.
Fin's equivalents point at operations. AI Topics, CX Score, Monitors and Custom AI Scorecards all sit behind the Pro add-on, from $99 a month. Incident Detection and Escalation Reporting are recent additions (aimed at spotting a spike or a broken handoff).
We tag tickets inside Intercom, and our Insights view groups conversations into topics and scores all of them for AI CSAT.
Agent translation
Front's Translate applies to email channels only. Front's own prerequisites page scopes it: "Email channels only: Automatically detect the message language in your conversations and quickly translate content into your preferred language, all within Front." Front's pricing page caps it at 200 requests per teammate per day. Compose polishes email and knowledge base drafts (a different feature entirely), capped at 200 actions per teammate per day.
Fin covers 45 languages. Intercom's model list names the piece doing the work:
"The Fin Language Detector model uses XLM RoBERTa to accurately identify the user's language across 45 supported languages."
In plainer terms, a dedicated model spots the customer's language before Fin answers (no per-inbox setup).
We answer in 95 languages, auto-detected per message.
Intercom's allowance on its pricing page is worth reading before you budget: "Copilot is a personal AI assistant in the Inbox that helps your team resolve conversations faster. Every agent also gets 10 Copilot and 10 AI Auto-translation conversations free each month." Ten and ten per agent per month is a sample allowance.
Both vendors charge again for the measurement layer. I did not score that against either of them. Front asks $20 per seat for Smart QA and $10 for Smart CSAT, or $25 per seat for the pair, all included on Enterprise.
Intercom asks $99 a month for Pro. On both sides, the QA and analytics you will want sit on a second line of the invoice.
What about security, is Front more secure than Intercom?
TL;DR: Intercom documents the wider grid on its own security page, including HIPAA, four ISO certifications and an AI-specific one for Fin. Front's page is narrower, and Front's edge is naming its AI suppliers publicly and stating that it trains no models itself.
Both vendors publish a security page, and I have rarely seen two read so differently.
Intercom's security page enumerates the wider list:
"Intercom and Fin hold SOC 2 Type II and HIPAA compliance along with ISO 27001, ISO 27018, ISO 27701, and ISO 42001 certification, and Fin AI Agent is also AIUC-1 certified (the industry standard for AI agent security). We also comply with GDPR and CCPA."
Two of those are AI-specific. I have not seen them on many vendor pages yet. ISO 42001 covers AI management systems, and AIUC-1 is an AI agent security standard.
The same page states US, EU and Australian data hosting (plus a 99.8% uptime SLA). It also states the data boundary in prose: "Fin can use anonymized customer data for model fine-tuning, and you can opt out at any time, with data deleted within 30 days."
Front's security page is shorter:
"We’re proud to be SOC 2 Type II and ISO 27001 certified, ensuring that client data is processed in a secure manner."
Front adds AES-256 encryption at rest, TLS in transit, GDPR readiness with a published data processing addendum, and a HackerOne bug bounty. Front covers HIPAA with a BAA, CCPA and US or EU residency in its Security & Compliance Handbook. That sits one step further from the page a reviewer lands on first.
If your compliance team works from public pages (mine would), that difference costs Front a round of emails.
Front keeps one real advantage here. It names its AI suppliers on the record: "We're using OpenAI and Azure OpenAI's GPT models. We also use Mistral models hosted on Amazon AWS." It publishes a subprocessor list and states that it trains no models itself.
Intercom makes an equivalent commitment about zero retention and no third-party training on its security page, but it does not publish those agreements as documents. Anyone can read Front's supplier list without asking.
So I gave Intercom the row on documented breadth, and Front the sub-argument on transparency. Neither vendor lists PCI-DSS on its security page, so ask if you handle card data directly.
Front vs Intercom: which costs more to run?
TL;DR: Fin charges $0.99 when it produces an outcome and nothing when a conversation is simply passed to your team. Front bills every Autopilot conversation on a three-tier scale, at $0.05, $0.39 or $0.89, on top of per-seat plans and per-seat AI add-ons.
The pricing model
Front meters by the conversation. Intercom bills per outcome. That single difference drives both bills (and it is why the two rate cards do not compare line by line).
Front's Autopilot pricing article publishes the whole rate card. Triage costs $0.05 and covers understanding a conversation well enough to organize it (no drafting, no replying, no Playbooks).
Handoff costs $0.39, defined as executing one or more tasks that end in human takeover as intended by you. Resolution costs $0.89, defined as "Fully resolve the conversation without any human replies."
One rule stops those tiers stacking on the same conversation:
"Conversations will only be charged once for the highest automation level achieved."
On one conversation you pay the top tier it reached, once. That is fairer than I expected.
Front also publishes what counts as resolved. A conversation resolves if no teammate follows up within 24 hours on Resolve, SMS, WhatsApp and custom channels, or within 72 hours on email and portal.
Three things are never billed: a teammate canceling an automation before it completes, a customer asking for a human instead, and a technical failure on Front's side. Front frames the whole model the same way Intercom does: "With our outcome-based pricing for Autopilot, you only pay when Autopilot delivers the outcome."
On top of the meter sit Front's plans at $25, $65 and $105 per seat per month on annual billing. Copilot is $20 per seat, Smart QA $20, Smart CSAT $10, and the QA and CSAT pair is $25. Enterprise bundles those three.
Autopilot is metered on every plan, so no tier includes it. There is no free tier (and an onboarding package is required above $25k).
Intercom's side is simpler to state, and I found it easier to model. Resolutions, Procedure handoffs and disqualifications are $0.99 each. Qualifications are $9.99.
Fin's pricing documentation spells out the rest:
"Fin AI offers a base plan at $49 per month, which includes 50 resolutions."
You are charged once per conversation, and Intercom says so directly: "You'll only be charged once per conversation, even if Fin resolves multiple questions."
You are not charged when a conversation is simply passed to your team with no outcome.
Intercom's pricing page puts helpdesk seats at $29, $85 and $132 per seat per month on annual billing. Copilot is $29 per agent per month annually ($35 monthly).
The Pro add-on is $99 a month, covering up to 1,000 conversations. It bundles 2,000 Operator credits (then $0.01 per credit). Fin pricing is USD only.
Both vendors also hide the same thing. Front says only that volume discounts are pre-paid commitments and to contact sales. Intercom says minimum resolution commitments apply, without a figure.
The overall cost
Here is my arithmetic on both vendors' published units. Assume 10,000 AI-handled conversations a month and 10 support seats. Of those conversations, 60% are resolved by the AI, 20% are handed off after the AI did work, and 20% are triaged with no reply sent.
Front's AI bill works out like this. 6,000 resolutions at $0.89 is $5,340. 2,000 handoffs at $0.39 is $780.
2,000 triage-only conversations at $0.05 is $100. That is $6,220 of AI spend (before a single seat).
Intercom's AI bill works out differently. 6,000 resolutions at $0.99 is $5,940. The 2,000 Procedure handoffs cost $0.99 each as well, because Intercom bills a handoff like that as a full outcome, so $1,980.
The 2,000 triaged conversations cost nothing, because you are not charged when a conversation is simply passed to your team. That is $7,920 of AI spend.
Then the platform underneath (where the two bills separate). Ten Front seats on Professional is $650, Copilot for ten is $200, and Smart QA plus Smart CSAT for ten is $250, which puts Front at $7,320 all-in. Ten Intercom seats on Advanced is $850, Copilot for ten is $290, and the Pro add-on is $99, which puts Intercom at $9,159 all-in.
Monthly AI mix, 10,000 conversations | Front AI spend | Intercom Fin AI spend |
60% resolved, 20% handed off, 20% triaged | $6,220 | $7,920 |
30% resolved, 10% handed off, 60% triaged | $3,360 | $3,960 |
85% resolved, 15% triaged | $7,640 | $8,415 |
Front comes out cheaper here, and I put it down to three numbers. Front's resolution tier undercuts Fin's, $0.89 against $0.99, and Front's seats are cheaper.
Front's handoff tier is the surprise: at $0.39 it is well under Fin's $0.99, because Intercom bills a Procedure handoff as a full outcome. Front's model is the more granular one.
The triage nickel is where I looked first, and I spent longer on it than it deserved.
At 20% of 10,000 conversations it adds $100 a month. Fin's number moves on the $9.99 qualification outcome, the Pro add-on and the seat delta.
The other two mixes move the totals around (the rates stay put). At 30% resolved Front pays $2,670 plus $390 plus $300.
At 85% resolved it pays $7,565 plus $75. Intercom's equivalents are $2,970 plus $990, and $8,415 with nothing for the triaged remainder.
Front stays cheaper across a wide band on these published rates, and I still scored the price row a tie. But the gap turns on your own mix. Put your own resolution and handoff rates in and it can close either way.
Buyers are vocal about what the per-outcome meter feels like in practice:
"Intercom Fin is $0.99 per resolution, which sounds better per unit, but once you factor in seat costs ($29–132/seat/month depending on plan) and the unpredictable nature of usage-based billing, total cost adds up fast." - u/Old-Source2534 on r/SaaS
"Plain is what we migrated to and love it. They don’t charge the “per resolution” balloon that drove us off Intercom." - u/whosecarwetakin on r/SaaS
That objection is not new either. Back in November 2023 one r/SaaS poster asked:
"Did I just pay $1 for intercom to supply a link to an internal document ?" - u/DeliJalapeno on r/SaaS
Both meters share the same property: the bill rises as the AI gets better at its job.
At My AskAI we charge roughly $0.10 per ticket, flat, billed when the AI works. A rising resolution rate does not raise the invoice. The trial runs 30 days with every feature unlocked, unlimited tickets and no card.
Conclusion - should I choose Intercom or Front?
TL;DR: Intercom takes the scorecard on capability. Front wins where control, setup speed and compliance sign-off matter more than autonomy, and if you are already on Front that is most of the decision made.
On capability alone, Intercom wins this one. Front's gated control model suits teams who work B2B threads together, where how you work matters more than how deep the agent goes.
The eleven categories are modes, ease of setup, training and integrations, answer quality, improving, features, price, customization, lock-in, other AI features and security (voice sits inside modes, not on a row of its own). Evidence comes from both vendors' live pages, help centers, pricing docs and published customer stories.
Each category scores out of 10 on what those sources document. A 4 marks a documented blocker, a 6 a capability with a stated limit, an 8 a capability complete for most teams, and a 9 or 10 the side that leads this pair.
Intercom Fin | Front AI | ||
Modes | 9/10 | 7/10 | Intercom win |
Ease of setup | 7/10 | 8/10 | Front win |
Training/Integrations | 9/10 | 7/10 | Intercom win |
Answer Quality | 8/10 | 6/10 | Intercom win |
Improving | 9/10 | 6/10 | Intercom win |
Features | 9/10 | 7/10 | Intercom win |
Price | 7/10 | 7/10 | Tie |
Customization | 7/10 | 8/10 | Front win |
Lock-in | 8/10 | 4/10 | Intercom win |
Other AI features | 8/10 | 8/10 | Tie |
Security | 9/10 | 8/10 | Intercom win |
That is 7 category wins of 11 for Intercom, 2 for Front and 2 tied on my scoring.
Six of Intercom's seven are capability wins, and capability is what you notice in month six. Front's two wins are setup speed and customization by permission. Those are what you notice in week one, when your team is deciding whether to trust the thing at all.
I scored the security row on documentation breadth, and Front's page is narrower. And the pricing row is a real tie, because Front's cheaper resolution tier and cheaper handoff tier offset the triage charge across most realistic mixes.
Choose Intercom if:
- You want the deeper agent available today, with Procedures that run real logic
- You need voice, or coverage across 45 languages
- You want to run the agent on Zendesk, Salesforce or Freshdesk without migrating
- You want published resolution numbers to argue from, contradictions and all
- Your reviewer needs HIPAA, four ISO certifications or an AI-specific certification on one public page
Choose Front if:
- You are already on Front, in which case most of this decision is made
- You want the AI gated topic by topic before it ever touches a customer
- You want your team live on AI drafts within a couple of hours
- You want the AI's suppliers named and its non-training stated in the vendor's own words
- Your team works B2B threads together, with several people on one conversation
My AskAI runs inside Intercom on a flat core rate per ticket. The agent sits outside the platform decision, and our core rate does not rise as the resolution rate climbs.
Worth reading next: our head-to-head of My AskAI against Intercom Fin. If your shortlist is wider than two, we have a roundup of Intercom Fin alternatives and a roundup of Front AI alternatives. There is a Zendesk AI versus Intercom Fin comparison too.
FAQs
Can Front's Autopilot fully replace Intercom Fin?
Not on a like-for-like basis, and the reason is structural. Front AI cannot be bought standalone. Front's prerequisites page says so directly: "You must be on a Front plan with access to AI features." So replacing Fin with Autopilot means moving your helpdesk.
Fin runs on other vendors' helpdesks. Fin's pricing page advertises it plainly:
"Fin AI Agent works seamlessly with any helpdesk, including Salesforce, HubSpot, and more."
Autopilot is also shared-inboxes-only and officially English-only. That rules out a couple of common setups on its own (multilingual teams especially).
The wider point is that the agent layer can be chosen separately from the helpdesk. We run inside six desks including Intercom, so switching desks does not mean rebuilding the AI.
What can Front AI and Intercom Fin each be trained on?
Front connects its native knowledge base, a public website, Notion, Google Drive and SharePoint, and it always learns from your past conversations. Notes, attachments and fact invalidation round it out.
The public-site source has two limits Front states itself: "Front supports a maximum of roughly 3,000 pages." and "No. We can only sync content from publicly available websites." Copilot also needs the connection made first: "Copilot does not have access to knowledge base content until you connect it in your Front AI settings."
Fin's list is longer. It covers internal articles, snippets, website sync, Zendesk, Salesforce and Freshdesk articles, Guru, Notion, Confluence, Box, Document360 and direct document upload. Data Connectors add live backend records.
How long does Front AI or Intercom Fin take to set up, and do we need developers?
Both are no-code for the core setup (no developer on either side). On Front, Topics generate automatically from your recent conversations and Front puts a number on it: "Click Save to finish. It may take 1-2 hours to identify Topics from your conversations." You then switch on one Topic at a time.
Permissions are tight: "You must have Front company admin or workspace admin permissions to manage Topics."
Copilot needs even less: "Copilot is designed to work off-the-shelf; no complex setup necessary!"
Fin goes live faster still (instant import from the native Help Center). Engineering only enters the picture for Fin Data Connectors and Python steps inside advanced Procedures.
Content work is what takes the time on Intercom.
We built around that with Train on Historic Tickets. My AskAI drafts starter knowledge from your last 5,000 historic tickets, so a thin help center does not stall the launch.
How do Front vs Intercom pricing models differ, and what might we actually pay?
Intercom charges per outcome on top of seats (two lines on the invoice). Front charges per conversation at three tiers, on top of seats and per-seat AI add-ons.
Intercom counts an outcome when Fin resolves a customer's issue. It also counts one when a Procedure ends in a handoff to a human or a workflow.
Front's has three levels where Intercom's has two, and it bills once at the highest level reached. Front's Autopilot add-on is pay-as-you-go: "Pricing is pay-as-you go, invoiced monthly based on your actual usage." The worked totals below are my calculation from both vendors' published rates.
Intercom Fin | Front | |
Pricing model | Per outcome, on top of seats | Per conversation at three tiers, on top of seats and per-seat AI add-ons |
Headline rate | $0.99 per outcome, $9.99 per qualification | $0.89 resolution, $0.39 handoff, $0.05 triage |
Worked example, 10k conversations at 60% resolved | AI $7,920, all-in $9,159 | AI $6,220, all-in $7,320 |
Free trial | 14 days, no card, unlimited Fin outcomes | 14 days, no card, mirrors Professional and excludes Autopilot; a paying customer can self-serve a 30-day Autopilot trial capped at 1,000 resolutions |
Can Front AI and Intercom Fin handle multilingual support and agent translation?
Front's Autopilot is officially English-only. Front's own documentation is direct about the risk:
"Only English is officially supported at this time. While it is possible to use this feature with other languages, unexpected results may occur."
Front does note separately that "Our AI vendors support 40+ common languages." Topics generation is English-only too. Front can still read conversations in dozens of languages to build those English Topics.
Compose is a drafting and polish feature, and Translate is scoped to email channels. Fin covers 45 languages (28 on voice, one language per phone line).
How do Front and Intercom compare on security and compliance?
Intercom documents the wider grid on its own security page: SOC 2 Type II, HIPAA, ISO 27001, ISO 27018, ISO 27701, ISO 42001, AIUC-1, GDPR and CCPA, plus a 99.8% uptime SLA. Front's security page documents SOC 2 Type II, ISO 27001 and GDPR. HIPAA and a BAA, CCPA and residency are covered in its Security & Compliance Handbook instead.
Residency is the cleanest illustration (one page names three regions, the other two). Intercom's security page says:
"Data is hosted in the US, EU, or Australia based on your residency needs, with redundant systems architected for continuous uptime across regions."
Front's security page says: "We support data hosting options in the U.S. or the EU."
Front's edge is transparency about the AI itself: "We're using OpenAI and Azure OpenAI's GPT models. We also use Mistral models hosted on Amazon AWS." Neither security page names PCI-DSS.
Does Front or Intercom offer a free trial of their AI agent?
On Intercom the agent is what you trial: "Free trials require no credit card to sign up. During the 14-day trial, you'll have unlimited access to Fin outcomes, with no limits on usage." On Front you unlock the agent after you buy.
Front's trial mirrors its Professional plan, in Front's own words: "Our free 14-day trial offers all the features available in our Professional plan."
Autopilot is not part of Professional, so a Professional-mirroring trial cannot contain it. Once you are a paying Front customer, you can start a self-serve 30-day Autopilot trial with up to 1,000 resolutions. Front is clear about what happens at the end:
"After the trial ends, if you don't actively opt-in to the paid version, any Autopilot rules, Playbooks, and Resolve channels will stop running."
