How to Use Intercom with Slack: Setup, Workflows & Tips

Customer conversations often start in one place and need action in another. Intercom handles the customer side—an AI-first helpdesk with the natively integrated Fin AI Agent—while Slack keeps your internal team connected. Linking the two means a customer message in Slack can become an Intercom conversation, and an urgent ticket in Intercom can alert the right Slack channel without anyone refreshing a dashboard.

This guide walks through the connection, the workflows you can build, and the practical decisions that keep support fast and organized.

Why connect Intercom and Slack?

Slack product interface.

Support teams lose time when customer context lives in one tool and internal coordination happens in another. The Intercom–Slack integration closes that gap in two directions:

• Inbound from Slack: When a customer posts in a connected Slack channel, Intercom creates a conversation. Fin and your teammates reply from the Intercom Inbox, and responses post back into the same Slack thread.
• Outbound to Slack: Intercom workflows can notify a Slack channel when a ticket is created or updated, so engineers, product managers, or account teams see what needs attention.

The result is fewer missed messages, faster handoffs, and a single record of the customer relationship in Intercom.

What you can do with the integration

First viewport screenshot of What's New.

Capability	What it means in practice
Slack as a channel	Customer messages in Slack become Intercom conversations
Fin AI Agent in Slack	Fin answers common questions directly in connected channels
Ticket notifications	Intercom workflows post ticket updates to Slack channels
Thread mirroring	Replies, attachments, and formatting stay aligned across both tools
Direct messages	Teammates can DM Slack users privately from Intercom
Broadcasts	Send one-time outbound messages to Slack channels
Multi-workspace mode	Route channels to the correct Intercom workspace when teams share Slack

Step-by-step: connect Intercom to Slack

First viewport screenshot of Login.

1. Install and authenticate

In your Slack workspace, open the App Directory, search for Intercom, and add the app. You will be asked to sign in to Intercom and approve the connection. Make sure your Intercom account has the permissions needed to manage workspace data.

2. Add Intercom to the channels you want to monitor

You can invite the app from Slack using the /invite command in a channel, or add channels from Settings > Channels > Slack in Intercom. Once added, the channel appears in your Intercom channel list.

3. Decide each channel's purpose

Not every channel should create conversations. Intercom lets you mark a channel as conversational (messages create conversations and can be answered by Fin or teammates) or notification-only (used for alerts without opening a customer conversation).

4. Configure workspace settings

In Settings > Channels > Slack, choose how Intercom should treat new participants:

• Create a new lead, or
• Match the email address to an existing user, falling back to a new lead if no match is found.

You can also control which messages trigger a conversation. By default, every message in a connected channel creates one; you can narrow that trigger if the channel is noisy.

5. Deploy Fin in Slack

To let the Fin AI Agent respond in Slack, add Fin to the relevant channels. When Fin is preparing a reply, Slack shows short loading messages so customers know a response is coming. Fin's final answer appears in the thread.

6. Set up ticket notifications with workflows

In Intercom, go to Automation > Workflows, create a new workflow, and choose a trigger such as A ticket is created. Add the Notify Slack channel action, pick a public or private channel, and publish the workflow. Notifications show the top non-empty ticket attributes so the channel gets useful context at a glance.

7. Handle multi-workspace setups

If several Intercom workspaces share one Slack workspace, request multi-workspace mode. Channels then need to be explicitly claimed by one workspace—only workspace admins can claim them—so messages route to the right place.

Practical examples

Example 1: A community Slack channel as a support front door

A developer community lives in a public Slack channel. A member reports a bug. Intercom creates a conversation, Fin replies with known troubleshooting steps, and a support engineer takes over from the Intercom Inbox. The reply appears in Slack under the engineer's name and avatar, so the community sees a normal conversation.

Example 2: Escalating high-value tickets to a private channel

An enterprise customer opens a billing question. A workflow triggered by ticket creation posts the details to a private #support-escalations channel. The account manager sees it, adds context in the Slack thread, and the support agent updates the Intercom ticket—no separate status meeting required.

Example 3: Tracking ticket progress inside Slack

With Slack connected, customers can track an Intercom ticket's progress in real time from the channel. That reduces the "any update?" messages and lets agents focus on resolution.

Best practices

First viewport screenshot of Login.

• Separate conversational and notification channels. Mixing both in one channel creates noise and confusion about what needs a reply.
• Authenticate teammate Slack accounts. When teammates link their own Slack identity in Intercom, replies appear from them rather than from a generic bot.
• Review public channel exposure. Public Slack channels can expose customer data. Use private channels for sensitive tickets and keep an eye on who is in the room.
• Tune reply time expectations. Reply time settings live in Simple Automations or Workflows; adjust or disable them so SLAs match the channel's purpose.
• Enable bot reply syncing if needed. By default, replies from other bots in a connected channel are not synced to Intercom. Support can enable Slack Bot reply syncing so those messages appear in the conversation.

Limitations to plan around

• Only one Intercom workspace can use the full conversational Slack integration per Slack team unless multi-workspace mode is enabled.
• Channels in multi-workspace mode stay pending until an admin claims them.
• Conversation notifications do not carry ticket attributes, while ticket notifications do.
• Public channels carry data exposure risk that private channels avoid.

How this fits a broader support stack

Slack is a collaboration layer, not a replacement for a helpdesk. Intercom remains the system of record for conversations, tickets, and AI-driven insights. If you are evaluating how Intercom compares with other platforms before wiring up Slack, see the comparison of Intercom vs HelpDesk vs Dixa and the breakdown of Intercom vs Zendesk vs ClickDesk.

If your goal is to extend Intercom beyond Slack into SMS, email, and voice, the guide on using Intercom with conversational AI and APIs covers that setup.

For the official setup reference, see Intercom's article on connecting your Slack channel. For a walkthrough of adding the Slack app, the step-by-step Slack app guide is a useful companion.

Related reading

• Intercom vs NiCE CXone: AI Helpdesk or Contact Center? - Intercom vs NiCE CXone compared: native Fin AI Agent and helpdesk vs CCaaS contact center suites. Pricing, strengths, limits, and who should pick each.
• CM.com Review 2026: Conversational Commerce Platform Pros & Cons - Evidence-based CM.com review covering messaging, payments, HALO AI agents, pricing signals, setup effort, limitations, and who should buy it in 2026.
• Fin Alternatives: How to Evaluate AI Customer Service Platforms - Compare Fin alternatives and learn how to evaluate AI customer service platforms on resolution depth, action execution, handoff quality, and cost per resolution.

Sources and further reading

• How to Integrate Intercom With Slack [2026 Tutorial for Beginners] - Enjoy the videos and music you love, upload original content, and share it all with friends, family, and the world on YouTube.

FAQ

Can Fin answer customers directly in Slack?

Yes. When Fin is added to a connected Slack channel, it can respond to messages there. Fin shows brief loading messages while preparing a reply, then posts the final answer in the thread.

Do I need to build a workflow for Slack notifications?

Only for outbound alerts. Inbound conversations from Slack work once the channel is connected. Ticket notifications require a workflow with a trigger and the Notify Slack channel action.

What happens if a Slack user is not in Intercom?

Intercom can create a new lead or match the email address to an existing user, depending on your workspace settings. If no match is found, a new lead is created.

Can multiple Intercom workspaces use the same Slack workspace?

Yes, with multi-workspace mode enabled. Each Slack channel must be claimed by one Intercom workspace, and only workspace admins can claim channels.

Are bot replies from other apps synced to Intercom?

By default, no. Support can enable Slack Bot reply syncing so bot replies appear alongside other messages in the Intercom conversation.

Can customers track tickets in Slack?

Yes. With Slack connected, customers can follow an Intercom ticket's progress in real time from the channel, which reduces manual status updates.

Conclusion

Connecting Intercom and Slack turns two separate workstreams into one loop: customers get answers where they already are, and your team gets alerts where it already works. Start with one conversational channel and one notification workflow, confirm the routing is correct, then expand. Keep sensitive conversations in private channels, authenticate teammate accounts for cleaner replies, and let the Fin AI Agent handle the repeatable questions so your team can focus on the ones that need a human.