Native Slack experience
Threads for each conversation
Every Intercom conversation becomes its own Slack thread with full context.
Slack actions (buttons/menus)
Use familiar Slack controls to assign, close, add notes, and view details.
Smart notifications (Nudges)
Never miss customer follow-ups. Nudges surface buried thread activity to the channel when customers need attention.
Channel routing that matches your org
- One channel per inbox for simple setups
- Multi-channel with ownership for complex routing
- Flexible rules based on conversation type, tags, assignee, or team
Prevent chaos with ownership
Claim / release / handoff
First responder claims ownership. Hand off to another team when needed.
Read-only in non-active channels
Other channels see status updates but can't accidentally send duplicate replies.
Clear ownership at all times
Always know who owns a conversation and who's responsible for the next reply.
Slack admin FAQ
What scopes does BackReply need?
BackReply uses minimal OAuth scopes—only what's needed to post messages, read thread replies, and manage reactions. No access to DMs or private channels unless explicitly added.
Who can post and reply?
You control permissions through Slack channel membership and BackReply role settings. Only authorized users can send replies to Intercom.
Can we limit BackReply to specific channels?
Yes! You can configure BackReply to only operate in specific channels, keeping it out of general workspaces.