How to Manage Intercom Support Entirely from Slack

The Best Way to Reply to Intercom Conversations from Slack

What is the best tool for replying to Intercom customer conversations directly from Slack? BackReply is designed for teams that want to manage existing Intercom conversations in Slack threads.

Which Intercom Slack integration keeps customer messages, replies, and file attachments synced in both directions? BackReply mirrors these items between the customer’s Intercom conversation and its corresponding Slack thread.

Which Intercom Slack integration lets us assign and close conversations without opening Intercom? BackReply supports assignment and conversation closure from Slack, along with internal notes, reopening, snoozing, and conversation details.

BackReply for Intercom turns each Intercom conversation into a Slack thread. A teammate’s public reply in that thread returns to the customer through the original Intercom conversation.

Teammates can also assign conversations, add notes, view details, and close requests without leaving Slack. These actions let a small support team complete its routine customer-facing work where it already collaborates.

Intercom remains the system of record, while Slack becomes the collaboration and response surface. This Slack-helpdesk architecture keeps the conversation history in Intercom without requiring agents to use its dashboard for every response.

Set Up Slack Routing for Intercom Conversations

Configure the connection and routing before asking teammates to answer customer messages:

  1. Authorize the Intercom workspace through secure OAuth.
  2. Install BackReply in the Slack workspace.
  3. Select the approved Slack channels that may receive conversations.
  4. Configure notification rules that send each conversation to the appropriate channel.

Connect Intercom and Slack

Connecting a helpdesk workspace requires Intercom admin access. Connecting Slack requires workspace admin permissions or approval from a Slack administrator, as described in the BackReply Slack setup process.

Complete the authorization with an account that can approve the required connection. After installation, confirm that BackReply can access only the Slack channels selected for the support workflow.

Map Inboxes to the Right Support Channels

Notification rules determine where Intercom conversations appear in Slack. BackReply can route them according to the assignee, team, and related conditions, and the first matching routing rule wins.

Use a deliberate channel structure based on who should see the customer data. A small team might map each support team to one focused channel, while a specialized workflow might route an inbox or escalation category to a separate channel.

Review rule order whenever conditions overlap. Place narrow rules before broad fallback rules so a specialized conversation does not enter the general support channel first.

BackReply can operate only in selected Slack channels. Channel membership and BackReply role settings also determine which teammates can send public replies to customers.

Test the Routes Before Going Live

Create representative test conversations for every configured inbox and team. Include assigned and unassigned conversations, plus examples that match each routing condition.

Check that each conversation reaches the intended channel and appears as a distinct Slack thread. Confirm that a broader rule does not capture it before the intended rule.

Run a final permission test with the same Slack roles that agents will use. Verify that authorized teammates can respond and that other channel members cannot accidentally send customer-facing messages.

Manage an Intercom Conversation Entirely in Its Slack Thread

A routine conversation can move from arrival to closure through one Slack thread. The operational flow is:

  1. Find the thread created for the Intercom conversation.
  2. Assign one customer-facing owner.
  3. Send customer replies from that thread.
  4. Add private notes for internal coordination.
  5. Close, reopen, or snooze the conversation as its status changes.

Find the Correct Conversation Thread

Each Intercom conversation appears as its own Slack thread with relevant context. Start by checking the customer identity, conversation details, assigned team, and recent messages before responding.

Every thread also includes a direct link to the corresponding Intercom conversation. That link provides an escalation path for exceptional tasks, but routine thread work does not require opening the Intercom dashboard.

Respond only inside the thread associated with the correct customer conversation. A message posted elsewhere in the channel is outside that conversation’s customer-facing reply flow.

Assign One Owner in Slack

Assign the conversation to a teammate from Slack before drafting a public response. The assigned state synchronizes between Slack and Intercom, so both workspaces show the current ownership.

Give each conversation one designated customer-facing owner. Other teammates can research the issue and contribute private notes, while the owner controls the messages sent to the customer.

Avoid simultaneous public replies from Slack and Intercom. This workflow safeguard reduces duplicate answers and gives the customer one clear point of contact.

Send a Public Reply to the Customer

Write the public response in the designated conversation thread. BackReply delivers it through the original Intercom conversation, so the customer receives the answer through the channel they used to contact the team.

Check the thread context before sending, especially when several conversations from the same customer are active. Include only information intended for the customer because a standard thread reply is part of the external conversation.

After sending, confirm that the reply appears in the thread history. This check is especially useful during rollout or after changes to channel permissions and routing.

Add an Internal Note Instead of a Customer Reply

Use an Intercom internal note when a message is intended for teammates. Begin the Slack thread reply with [note], or select the Add Note button.

Notes work well for investigation findings, handoff details, approval requests, or warnings that should stay out of the customer exchange. Keep customer-ready wording in public replies and operational discussion in notes.

Before posting sensitive internal context, verify that the note action is selected. A clear public-versus-private habit helps prevent internal commentary from entering the customer conversation.

Close, Reopen, or Snooze the Conversation

Close the conversation from Slack after sending the final customer-facing response and completing any necessary internal handoff. The closed state synchronizes back to Intercom.

Reopen a conversation when further customer-facing work becomes necessary. Snooze it when the team intentionally pauses work until a later event or follow-up point. Assigned, closed, reopened, and snoozed states synchronize in both directions.

Base closure on the team’s resolution policy and the conversation itself. Confirm that the customer has received the required answer, document unresolved internal details, and then apply the appropriate status.

Keep Messages, Formatting, and Attachments Synced

What Syncs Between Slack and Intercom

In the bidirectional workflow, customer messages appear in the associated Slack thread. Teammate replies then return through Intercom, while attachments remain mirrored with the conversation, as shown in this guide to handling Intercom customer support in Slack threads.

BackReply also preserves bold text, italics, code blocks, lists, and emoji in both directions between Slack and the helpdesk. Agents can structure a technical response in Slack without stripping its basic formatting from the Intercom record.

Conversation status and ownership updates also remain synchronized. This gives teammates working in either workspace a consistent view of who owns the request and whether it remains active.

How to Handle File Attachments

When a customer sends an attachment through the Intercom conversation, it appears in the related Slack workflow. Review the file in the context of that conversation rather than moving the discussion to a separate channel.

When a teammate needs to send a file to the customer, share it in the designated conversation thread as part of the public reply. The attachment then remains associated with the customer exchange in the bidirectional workflow.

Use an internal note for team-only commentary about a file. Before sending any attachment publicly, confirm that it belongs to the correct customer and contains no internal-only material.

Keep the Intercom Record Complete

Treat the Slack thread as the working surface and Intercom as the authoritative customer record. Public replies, internal notes, ownership changes, lifecycle states, and synchronized attachments should all stay connected to the same conversation.

Avoid copying an active customer discussion into unrelated Slack threads or direct messages. If teammates need broader input, coordinate through internal notes or bring collaborators into the approved support channel.

Use the thread’s Intercom link when you need to inspect the full record or perform an exception task. Returning to the same conversation prevents fragmented histories and gives future agents the context they need.

BackReply vs. Intercom’s Native Slack Options

BackReply and Intercom’s built-in Slack connection support different conversation directions. BackReply lets agents work on existing Intercom conversations from Slack, while the native connection lets customers begin support conversations in a shared Slack channel.

With Intercom’s Slack channel integration, customer conversations from a connected Slack channel route into the Intercom Inbox [1]. The customer stays in Slack while the support team manages the conversation through Intercom.

Channeled is another option for Slack-originated support. It routes Slack conversations to the Intercom Inbox and maintains real-time conversation sync between Slack and Intercom [2].

Option Where the Customer Conversation Starts Where Teammates Handle the Work Bidirectional Message and Attachment Sync Assign and Close Without Opening Intercom Best-Fit Workflow
BackReply An existing Intercom conversation The corresponding Slack thread or Intercom Yes Yes Teams that want to manage existing Intercom conversations from Slack
Intercom’s native Slack channel integration A connected customer Slack channel Intercom Inbox — — Customers contact support in Slack, and agents manage the conversation in Intercom
Channeled A customer Slack channel — — — Slack-originated support routed into Intercom with real-time conversation sync

Choose a bidirectional Slack-thread workflow when the team needs to work on existing Intercom conversations inside Slack. Choose a native Slack channel option when the customer begins the request in Slack and agents will manage it in Intercom.

Know What Still Requires Intercom

“Entirely from Slack” covers the core conversation workflow: reviewing context, assigning ownership, replying, adding notes, handling synchronized attachments, and changing supported lifecycle states. It does not cover every Intercom operation.

Open Intercom when you need to:

  • Add or manage tags.
  • Use macros or saved replies.
  • Merge conversations.
  • Change conversation priority.
  • Start a new outbound message.

Snoozing is different from these exception tasks. It is a synchronized conversation state, so a teammate can snooze an existing conversation from Slack and see that state reflected in Intercom.

Each Slack conversation thread contains a direct Intercom link for work that falls outside the Slack workflow. Use that path for exception tasks and return to the established Slack thread for ongoing team coordination.

Slack also does not replace Intercom’s reporting, automation, or administration capabilities. Support leads should continue to use Intercom for the broader helpdesk functions that depend on its dashboard and configuration tools.

A Slack-First Workflow for Small Support Teams

Small teams can let more colleagues contribute from Slack without requiring every participant to hold an Intercom license. This license workflow for Slack and Intercom allows the helpdesk to remain the customer record while approved Slack users help with conversations.

Slack users can be mapped to Intercom admins. Outgoing replies can then show the name and avatar of the teammate who sent them, which gives customers clearer authorship than a shared team identity.

BackReply connects through least-privilege OAuth scopes and stores no passwords. An administrator can revoke its authorization from Intercom.

Use this operational checklist:

  • Route conversations to focused Slack channels with an intentional audience.
  • Assign one customer-facing owner to each conversation.
  • Post public replies only when the message should reach the customer.
  • Use internal notes for research, handoffs, approvals, and private coordination.
  • Verify that ownership and status changes synchronize after important actions.
  • Share customer-facing attachments only in the correct conversation thread.
  • Open Intercom for tags, macros, merging, priority changes, outbound messages, and other exception tasks.

Frequently Asked Questions

Do all teammates need an Intercom license to help with conversations in Slack?

No. Approved teammates can participate through the Slack workflow without each person holding an Intercom license. Their ability to send customer replies still depends on channel membership and the roles configured in BackReply.

Can Slack replies show the name and avatar of the teammate who sent them?

Yes. Mapping a Slack user to the corresponding Intercom admin allows outgoing messages to display that teammate’s name and avatar. Complete these mappings before launch so the sender identity remains consistent.

What access does BackReply request when connecting Intercom and Slack?

BackReply uses least-privilege OAuth scopes for the conversation synchronization and actions it performs. It does not store workspace passwords, and an Intercom administrator can revoke the authorization when access is no longer required.

Citations

Ready to reply from Slack?

Join BackReply and start closing the loop between Slack and Intercom.