How to stop duplicate replies when your support team uses both Slack and Intercom

It's 2pm on a Wednesday. A customer message lands in Intercom. It pops up in your support Slack channel. Two agents see it at the same time. Neither knows the other is already typing. Two minutes later, your customer gets two nearly identical responses within 30 seconds of each other.

I've watched this happen hundreds of times. It's not a minor annoyance. It looks broken. It tells your customer you don't have your act together. And it's the second biggest problem I hear about from support teams running Slack and Intercom together.

This happens because Slack and Intercom don't share ownership signals. When an agent sees a message in Slack, Intercom doesn't know they're working on it. When another agent sees that same message in Intercom, they assume it's unhandled. Both agents start typing. Both hit send before either one realizes what's happening.

Why emoji systems don't actually work

One team I worked with invented a workaround: a Slack emoji system. When you picked up a ticket, you'd react with a 🙋 emoji to signal "I've got this one." It worked for about three weeks until people got too busy to use it, or someone forgot, or the channel was moving too fast. Then you're back to duplicates.

The problem with workarounds is they're fragile. They depend on people remembering to do something extra in a busy moment. They don't integrate with Intercom's actual state. If you assigned yourself to a ticket in Intercom, Slack has no idea. If you replied in Slack, Intercom doesn't know the message is handled.

What you really need is a system where ownership and reply state sync across both tools.

The two-system ownership problem

Here's the core issue: you have two places where the state of a conversation can exist. An agent assigns themselves in Intercom. But if half your team works primarily in Slack, they never see that assignment. Someone reads the Slack message and doesn't realize another agent is already on it.

The reverse is equally broken. An agent replies to a customer in a Slack thread. Intercom shows the conversation as unhandled because no one has assigned it there. Another agent sees that in Intercom and starts drafting a response. The customer gets replied to twice.

You need visibility into who has claimed responsibility. That visibility needs to exist in both tools simultaneously.

Closing the ownership gap

The fix has to work in both directions. It's not enough to route Intercom conversations into Slack with context attached — you also need Intercom's assignment and reply state reflected back in Slack. That's the piece we built into BackReply's routing and ownership system: when you reply to a conversation from a Slack thread, the conversation gets marked as handled on the Intercom side automatically. Other agents see an assignment, not just a hope that someone already grabbed it.

Each conversation has a clear owner at any given time, and that ownership is visible in both tools. If someone starts typing a response in Slack, Intercom knows about it. If someone assigns it to themselves in Intercom, the Slack channel knows it's claimed. The ambiguity that causes duplicates goes away because the state isn't split between two systems anymore.

The second-order benefits

The deeper benefit is that you stop wasting support labor. Every duplicate is time spent typing something another agent already handled. When you scale to 15 or 20 agents, duplicates add up to meaningful productivity loss. Most teams with five plus agents in Slack-first workflows generate 5 to 8 duplicates per day. That's wasted focus at scale.

The customer experience impact matters too. Duplicate replies signal chaos and signal your company lacks visibility. Stopping them changes how professional your team looks.

Making it work

The fix requires alignment: if you reply in Slack, you own it in Intercom. If you assign in Intercom, the Slack channel knows. The tool just makes this possible.

Start with a duplicate audit. Log how many your team generates in a week and what that costs in wasted replies before deciding whether it's worth fixing.

If you want to see how the ownership sync actually works, the Routing and ownership page covers it in detail. And since most duplicates start with an agent replying from Slack in the first place, Reply from Slack shows the flow that keeps that reply in sync with Intercom.