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
- What do you need before you start in Intercom?
- What are the three ways to add AI to Intercom without Fin, and which one should you pick?
- How to add a third-party AI agent to Intercom, step by step
- Step 1: Check your permissions and what the app will ask for
- Step 2: Install the app from the Intercom App Store
- Step 3: Point it at your knowledge
- Step 4: Add the agent to the Workflows you want it in
- Step 5: Scope which conversations it sees
- Step 6: Run it in note mode first (Route B)
- Step 7: Set the handoff, then turn on direct replies for one conversation type
- What changes if you build it yourself (Route C)?
- How to test it before you let it near customers
- What breaks when you add AI to Intercom, and how do you tell?
- What should you do next once the AI agent is live in Intercom?
- FAQs
Created time
Aug 19, 2026 02:43 AM
Title length (<60)
Author
Last optimised
Ecomm?
Tags
Image
Publish date
Aug 4, 2026
Video
Slug
how-to-add-ai-to-intercom-without-intercom-fin
Featured
Type
Article
Ready to Publish
Ready to Publish
By the end of this you will have a third-party AI agent answering real Intercom conversations, and it will see only what you scope it to see through the Workflows and tags you already have.
If you want AI answering Intercom conversations without Fin, there are three routes: an App Store install, a note-mode test where the agent only drafts for a teammate, or your own build against the Intercom API. The App Store install is the one I would take, and it needs no developer: nothing you already built in Intercom has to change. The catch is that you inherit the app's routing model, and you scope it yourself by adding it to the Workflows you want it in.
You own the Inbox. You have built Workflows, a macro library and assignment rules that mostly behave themselves.
Fin has been sitting in the Messenger doing its thing. Then the bill starts growing faster than your volume justifies, or you ran it for a month and the answers were not good enough.
So you want a different agent in there, without pulling Intercom apart to get it. The job is the install, the knowledge sync, the Workflow changes and a test plan (in that order). One conversation type answers by the end.
Go in the right order and this is dull. Go out of order and two agents answer the same customer, or an untested one answers them first. Nothing here asks you to leave Intercom.
What do you need before you start in Intercom?
TL;DR: Intercom access with app-install and Workflow rights, and knowledge for the agent to read: your Help Center articles, or your historic tickets. You do not need a developer for the route most teams take.
The four checks below take about ten minutes.
- Permissions: the one that gates everything is called "Can install, configure and delete apps". It sits in the "Apps and integrations" group of the teammate permission list, at
Settings > Workspace > Teammates.
- Plan tier: check yours before you start. Your plan is not where Fin's cost sits: Fin is billed on usage on top of it, and a third-party agent is a separate bill again from whoever makes it (ours included).
- Data prep: group your articles into collections, which is what makes them visible and searchable in your Help Center. Thin Help Center? Your historic tickets can seed the knowledge instead: we train on 5,000+ of them by default, and you can ask us to narrow that to a subset. Either way, you decide through your Workflows and tags what the agent gets to see.
- What you can skip: a full Help Center rewrite, and an audit of every Workflow before you begin. The note-mode week is what makes testing on what you have safe. We would rather you fixed the articles the agent actually missed.
If you are not an admin, you request the install from someone who is. Intercom's permission list is clear about it:
"Without this, teammates can visit the app store but must request an app be installed from an admin in a dropdown list."
Ten minutes of an admin's time clears it.
Articles also need grouping:
"you need to group them into collections to publish them on your Help Center (articles are only visible on your Help Center if they're in a collection)."
You set the Help Center itself live at
Settings > Help Center, from the dropdown at the top of the page.What are the three ways to add AI to Intercom without Fin, and which one should you pick?
TL;DR: Fin is the option you already have. If it prices past your volume, or it did not land, there are three routes: an App Store install, a copilot test that never reaches a customer, and a custom API build.
Intercom has its own AI agent, and Intercom documents it properly. Two reasons bring people looking for a different one.
The per-resolution billing grows past what their volume justifies, or they ran it and it did not land. Our full guide to Fin covers what it is and what it does. If your real question is which vendor to pick, the roundup of Fin alternatives is the better place to start.
You also do not have to turn it off to do any of this. I once stopped a live demo and told the prospect to buy Fin rather than us. So "keep Fin and split the work" is a real answer here.
Route | Best for | What setup involves | Needs a developer? | Trade-off |
A. Intercom App Store install | Most teams | An App Store install and a knowledge sync | No | You inherit the app's routing model |
B. Copilot / internal-note test | Proving it before anyone sees it | The same install, switched to note mode | No | Drafts only: a teammate still sends every reply, so handle time is the only number that moves |
C. Custom API / webhook build | Non-standard routing, or an in-house model | A Workflow, a webhook and a service you host | Yes | You own it forever, including the 401s |
Route A is an install from the Intercom App Store. One practitioner reviewed nearly all the apps listed under its Automation category, and was clear about what they were escaping:
"Initially, we built workflows to handle basic support tickets, but we quickly found this approach to be unsustainable, as it became burdensome to maintain and scale." — u/West_Hospital8648, r/SaaS, January 2025
That is the trade: the flow maintenance comes off your team.
Route B is the same app in note mode. It drafts a reply your teammate can send or bin, and no customer sees a word of it.
Its case is risk: you prove the thing works on your own conversations before anyone outside the building meets it. I would take that week even if you are confident.
Route C is a Workflow that fires a webhook at your own service, which then replies through the Intercom API.
Route C works, and its edges are the token exchange, retries and the Workflow loop. My view has not moved: building your own AI support agent almost never makes sense.
If you are not sure, I would take A, run it in B's note mode for a week, then widen. C is for the minority whose routing an App Store app cannot reach.
How to add a third-party AI agent to Intercom, step by step
TL;DR: Seven steps: check your permissions, install it, sync your knowledge, add it to the Workflows you want it in, scope which conversations it sees, run it in notes for a week, then let it reply to one conversation type.
Two questions decide which agent you pick. Does it connect to Intercom natively, meaning it has its own App Store listing? And can it read the knowledge you already have: your Help Center, your macros and your past conversations?
Both are answerable from a listing page in under a minute.
Step 1: Check your permissions and what the app will ask for
Go to
Settings > Workspace > Teammates and click your own name. Look in the "Apps and integrations" group for "Can install, configure and delete apps".Seeing that permission switched on against your name is how you know this step is done.
The app itself will ask for read and write access on conversations. Intercom grants that through per-capability OAuth scopes, so an agent that answers customers needs the conversations scope (read alone will not do, because it has to reply).
Step 2: Install the app from the Intercom App Store
Navigate to
Settings > Integrations > App Store, find the app, and click Install now. The category filter in the top left menu is the fastest way to find it. It splits by team ("For support admins", "For support agents" and so on).Third-party listings carry their own short instructions once you open them, so follow those. A third-party install also does not finish inside Intercom: the listing links out to the developer's website, and you complete the installation there. Expect a flurry of Slack messages once it lands (fun fact: your teammates are notified automatically when an app goes in).
You are done when the app shows in your installed list and can see conversations.
Step 3: Point it at your knowledge
Help Center articles first, then macros, then your historic tickets.
The Help Center is the easy one: our Intercom connector pulls your articles in directly (yes, even the ones behind a login). There is nothing else to do on the Intercom side.
Macros need a conversion step first.
Export them from
Settings > Inbox > Macros with the Export macro content button. Then convert that export into knowledge with an LLM first, using the prompt in our guide to adding macros to an AI agent.When a customer tells me the agent is answering incorrectly, the reason is almost always the same. The information behind it is out of date, ambiguous, incorrect or conflicting, and a raw macro dump manages three of those in one move. Where the wording is scripted and has to come back exactly, that belongs in Custom Answers instead.
Then the historic tickets, which is the part that rescues a team with a thin Help Center. We train on 5,000+ of your historic tickets by default (ask us and we will narrow it to a subset), and the drafts land in Self-Learning for a human to review first. If nothing is written down anywhere, that is how you start with something on day one.
Step 4: Add the agent to the Workflows you want it in
One thing to clear first. Fin may already be answering in the workspace you have just installed into, and it can get there before your agent does.
Fin can be live from two independent places. One is its own deploy surface at
Fin AI Agent > Deploy > Chat; the other is any Workflow you have wired it into.
If you turn it off, check both places. Pausing is the reversible version: go to
Fin AI Agent > Deploy > Chat and pause it for chat, then pause it again at Fin AI Agent > Deploy > Email, which is a separate surface.
"It's possible that you have Fin activated through the "Simple deploy" workflow and you might need to deactivate it there."
Our own Intercom app is one install and covers both. The Messenger and email sit under the same connection.
Now your own agent. Left alone, ours replies to every inbound conversation, so the Workflows you add it to are what decide where it speaks.
Open
AI & Automation > Workflows. Click + New workflow, or open one you already run, and pick a trigger such as a customer sending their first message.Inside a path you click
Add step. Send an app is the message type that puts an installed app into a workflow: you add the step, then choose the app.I would follow our own wiring, which is documented separately. In the My AskAI dashboard, turn on the toggle for Workflow/Triage settings and write a trigger phrase.
In Intercom, put that phrase on a button in your workflow message, worded to match it exactly. Then turn off "Let customer type" on your welcome message (yes, that one too).
The agent only begins responding once the AI chat button has been pressed. It answers inside the Workflows you put it in, and it stays quiet everywhere else.
Step 5: Scope which conversations it sees
Three layers, in the order I would apply them: the workflow trigger, your tags, then the mailbox.
Workflows are the main gate. In the trigger settings, the Channels section decides which channels may fire the workflow at all, and the audience rules decide who the customer has to be. One limit is worth knowing before you draw it up: the audience filter takes a People or Company tag, and a conversation tag cannot be used for it.
Intercom also separates background workflows from customer-facing ones. That split is what stops an automation firing on the AI's own reply, the same loop that bites a Route C build.
Tags are the finer control. You tag a conversation with the
T shortcut, and our own ticket tagging then tells the agent which tickets it should respond to.
To keep it out of a category altogether, go to
AI Agent Setup > AI Tagging, pick the attribute holding the tag you want blocked, then find that tag and click Block. A blocked tag means the agent does not reply, and the conversation forces a human handover instead.Two constraints travel with it on Intercom. Only List attribute types are supported, and the auto-tagging updates attributes rather than Intercom's own Tags.
The mailbox is the third layer. For answering support@ but not vip-support@, you triage those tickets with an Intercom workflow and only hand the agent the addresses you want it on.
On our side, two controls decide what it does once a conversation reaches it. Guidance is where you write behavior in plain sentences, split into Communication and Style, Context and Clarification, and Handover and Escalation.
Auto-tagging reads what the customer actually wrote and routes on that. A message mentioning canceling, or one that reads as frustrated, can go straight to a person.
Our ticket auto-tagging guide goes deeper on the routing rules.
Step 6: Run it in note mode first (Route B)
For the first week, the agent drafts and a human sends. On our side that is one toggle,
Draft 'note' replies under Channels > Intercom, and it is already on when you first connect. The agent writes its whole reply as an internal note on the ticket, for a teammate to send, edit or bin.Nothing the agent writes reaches a customer.
A week is usually enough to see the pattern. Your teammates send the good drafts, bin the bad ones, and you end up with a list of what the agent did not know. I would spend week two fixing the articles behind that list.
One gotcha catches teams in that first week. Notes are where your teammates talk to each other, and once the toggle is on the same panel carries the agent's drafts too, so a note stops being proof that a person wrote it. I would say so to the team before the first one lands.
If a single conversation should not have drafts on it, a note on that conversation turns them off.
Step 7: Set the handoff, then turn on direct replies for one conversation type
Do the handoff before anything else. It should always be easy for a customer to reach a person. That means when they ask for one, when the agent cannot answer, when they sound frustrated, and on any topic a human should own.
Our escalation carries a summary of the conversation so far. Control passes to a teammate inside the same Inbox, and the agent stays quiet until it is handed back.
Escalation lands on a team or a teammate, so pick that destination now, before you discover it at 9am on a Monday. Ours sits under
Helpdesk & Channels > Intercom, in the "Assign to Team Inbox on escalation" section.Settings > Inbox > Assignments has a "Teammate assignment limit" tab as well, which is what stops an escalating AI burying one person. Most agents have a confidence threshold sitting behind the same behavior. Find out what yours does before you move it.
Then turn on direct replies for exactly one conversation type. One tag, one view, one team, on your highest-volume lowest-risk queue.
On Intercom I would start on a Messenger queue. Intercom treats chat and email as separate deploy surfaces, and the email side carries an extra Workflow constraint.
What changes if you build it yourself (Route C)?
The chain is Workflow, then webhook, then your service, then a reply through the Intercom API.
If you want the agent rendering inside the Inbox, Canvas Kit is that surface. Intercom describes the contract: "The Canvas Kit works by sending you POST requests to the URLs you provide us with. You then take any actions with your service and respond to these POST requests with JSON objects, letting us know what UI to show."
Three things bite here, and the token is the first. Intercom's own docs say to "double check the code value provided in the token exchange POST request if you get a 401 response with error message Unauthorized Code". So it is the OAuth exchange that needs the second look.
Retries come second, because a slow endpoint on a POST-response contract shows up as a dead panel in front of a teammate. The Workflow loop is third, where a rule re-fires on the agent's own reply. That is what the background-workflow type exists to prevent.
One edge is not reversible. Intercom's Canvas Kit docs spell out the consequence: "Removing a Canvas Kit location causes the app to be deleted and removed from all contexts it was inserted into."
How to test it before you let it near customers
TL;DR: Replay closed conversations in note mode, force a handoff, check it cannot invent a policy, confirm Fin and the new agent are not both answering, and baseline first response time and CSAT before you widen it.
Five checks, each with a pass condition you can see.
- Replay a batch of closed conversations in note mode. Our batch testing is how you run the replay. Compare each draft to what your teammate sent. Pass: every material difference has a named cause, whether a missing Help Center article, a scoping gap or a stale macro. Ask Echo, the in-dashboard assistant your team talks to, why the agent gave an answer and which knowledge source it used.
- Force a handoff. Ask it something well outside your knowledge base. Pass, and this one is binary: it hands over instead of guessing. The conversation is summarized, control reaches a human in the same Inbox, and the agent does not reply again until handed back.
- Check it cannot invent a policy. Ask a question your knowledge base does not answer. Pass, again binary: it hands over or says nothing. On our side, the categories you cannot afford to get wrong are blocked at the routing layer, where you control them.
- Check Fin and the new agent are not both answering. Raise a conversation that matches both scopes. Pass: only one of them replies, and the Workflows you scoped decided which.
- Baseline first response time and CSAT. Do this before direct replies go on. Pass is that the baseline exists, is dated and covers a full week. You are writing the numbers down so you have something to compare against once direct replies are on.
Those five checks pass before I let a customer see an AI-written reply. Checks two, three and four pass on the live workspace. A full week of note-mode drafts has run, with a named cause behind every binned draft.
Both baselines are recorded and dated. And direct replies are on for exactly one team or view.
For what a settled deployment looks like later on, our own AI resolution-rate benchmark study puts the median AI-handling rate at 70% across 195 rated deployments spanning 38 vendors.
Read that as background, and set your target off your own baseline. It is an aggregate. The teams who publish a number tend to be the ones who like their number.
RecruitCRM runs our agent on Intercom. They connected their Intercom help center through the Intercom connector.
They also switched the AI on for certain Intercom Workflows only, to control the experience and how much AI they used.
They now run a 68% AI resolution rate and handle around 1,088 conversations per month, with 62 hours saved per month and a 75% AI CSAT score. They started at roughly 35% at go-live (the climb came in the months after).
What breaks when you add AI to Intercom, and how do you tell?
TL;DR: Most failures trace back to the Workflow or the knowledge sync, and on Intercom the most common one is Fin still answering first.
Symptom | What's actually happening | Fix |
Fin answers first and the new agent never sees the conversation | Fin is still live from a surface nobody checked. Simple deploy and a live Workflow are separate, and so are chat and email | Check Fin AI Agent > Deploy > Chat and the Advanced-deploy Workflow section, then Fin AI Agent > Deploy > Email |
The Messenger still presents as AI-handled, even though Fin is off | Messenger conversation expectations are a separate setting from Fin's deploy state | Change Settings > Channels > Messenger > Conversations > With Fin |
The Workflow does not fire and the agent never picks the conversation up | Assignment Workflow misconfiguration, common enough that Intercom publishes a troubleshooting article for it | Walk the assignment workflow's conditions one at a time |
It answers from a stale Help Center article | The source article is out of date, ambiguous, incorrect or conflicting. Invention is rarely the cause | Trace the answer back to its source article, then fix the article |
A macro and the agent collide on the same conversation | A macro cannot both reply and add a note, so teams build two and fire the wrong one | Open Settings > Inbox > Macros and check which are reply-type and which are note-type |
The API returns a 401 on a Route C build | The code value sent in the token-exchange POST | Re-check the token-exchange request |
What should you do next once the AI agent is live in Intercom?
TL;DR: Once one conversation type is holding, widen by tag, then by channel, then by a second workflow, and fix the articles behind whatever it could not answer.
Widen slowly and in that order. Add a second tag once the first one has run clean for a week, then turn on another channel in the workflow trigger, then put the agent into a second workflow.
Keep the note-mode habit for anything new you switch on. Watch the binned drafts for a week before you widen.
The other half of the job is the questions it could not answer. Our Self-Learning drafts new articles by comparing what the agent said to what your teammate actually replied on handed-over conversations.
It works in note mode as well as direct replies. Review those drafts weekly and approve the good ones into the agent's knowledge. Anything your customers should be able to find for themselves, copy across into a Help Center article too.
If you would sooner not wire any of this by hand, our Intercom integration page covers the same setup natively. It is also where to start if you are still choosing which agent to install.
FAQs
How do I add AI to my customer support without replacing my helpdesk?
You install it into the helpdesk you already have. On Intercom that means an App Store install, scoping it with your existing Workflows and tags.
Then run it in note mode until you trust it, and turn on direct replies for one conversation type. You decide through your Workflows, tags and assignment rules what the agent sees; we work inside them.
Do I need admin access to do this?
Not necessarily. The permission you need is "Can install, configure and delete apps" in the "Apps and integrations" group. Plenty of the support leads we work with already have it.
Without it you can still browse the App Store and request the install from an admin, so the worst case is a ten-minute wait. Check it before you start and you skip the wait entirely.
Will this break my existing Workflows and macros?
Not by itself. The agent only sees the conversations your Workflows and tags route to it, so the scope is yours to set.
The one real interaction is the macro limit: a single macro cannot both reply to a customer and add a note for teammates. Leave your reply macros alone and build separately if you need a note. I'd still run the note-mode week before trusting the split.
Do I have to turn Fin off?
No, but you do have to decide who takes what. If you keep both, scope them to different conversation types so they are not competing for the same conversation.
If you do turn Fin off, check both Simple deploy and the Advanced deploy with workflow section, and remember chat and email are separate surfaces. Teams hit that trap often enough that it has its own thread on Intercom's community forum (Simple deploy is the surface the thread names).
Can I roll it back?
Yes, and quickly. Go to
Settings > Integrations > App store, find the app you want to remove, and click the Uninstall button.Pausing Fin is equally reversible, and note mode never reaches a customer at all. That is why I'd start with Route A.
One exception: on a Route C build, removing a Canvas Kit location deletes the app outright.
Does this cost anything on my current plan?
An App Store install itself does not change your Intercom bill. The agent you install is priced by whoever makes it, and Fin is priced separately again. We have a full breakdown of Intercom Fin's pricing if that is the number you are trying to work out.
