We use cookies for essential site functions and anonymous analytics. Choose what to allow.
Kumar Makala · Founder & CEO, SyncRivo
Kumar Makala leads platform engineering and technical content at SyncRivo, focused on enterprise messaging interoperability, messaging bridge architecture, and cross-platform integration patterns across Slack, Microsoft Teams, Google Chat, Zoom Team Chat, and Cisco Webex. LinkedIn
Updated · 10 min read
Intercom posts conversation notifications through its Slack integration and has no native Teams integration. SyncRivo does not relay bot or app messages — it bridges the human conversation, so support and CS teams on Slack and Teams can discuss customer issues together in one bridged channel.
New conversations, assignments, SLA warnings, enterprise account activity, and resolutions — delivered by Intercom's own integrations.
New customer support conversations posted to team queue channels by Intercom's Slack integration so no inbound goes unnoticed.
Assignment changes delivered by Intercom notifications so agents know what they own.
First response and resolution SLA warnings delivered by Intercom before the breach occurs.
High-intent leads captured via Intercom, posted to sales channels by Intercom's integration.
Conversations from high-value accounts posted to dedicated account channels — discussions SyncRivo can bridge to account executives on Teams.
Resolution events delivered by Intercom so team leads can track closure.
Intercom posts the notifications; SyncRivo bridges the discussion.
Example layout: Intercom posts to Slack; Teams entries show where the human discussion is bridged by SyncRivo.
| Intercom Event | Native Integration Posts To | Result |
|---|---|---|
| New conversation (any) | → Slack #support-queue | Support agents see new inbound on their native platform |
| SLA breach warning (first response) | → Slack #support-lead (discussion bridged to Teams #cs-leadership) | Leadership on Teams can follow the breach discussion |
| Enterprise account new conversation | → Slack #enterprise-cs (discussion bridged to Teams #account-execs) | CS team and AEs coordinate in one conversation |
| Conversation assigned | → Intercom notification to the assigned agent | Assignment reaches the agent |
| Conversation resolved | → Slack #support-metrics | Closure logged for team metrics tracking on Slack |
| New lead from chat | → Slack #sales-alerts (discussion bridged to Teams #sales-leadership) | Sales team and leadership discuss the lead in one conversation |
| Capability | Intercom Native | SyncRivo |
|---|---|---|
| Notify Slack | ✓ Native Slack integration | — Not relayed (SyncRivo does not relay bot or app posts) |
| Notify Microsoft Teams | ✗ No native Teams integration | — Not provided; SyncRivo does not receive Intercom webhooks |
| Human discussion across Slack, Teams, Webex, Google Chat, Zoom | ✗ Not available | ✓ Bridged channels, threads, edits and files |
| Healthcare customers | — | BAA available for Enterprise customers |
| Setup | Configured in Intercom | First channel bridge typically live during onboarding, after admin approval |
Intercom has a native Slack integration but no native Microsoft Teams integration. SyncRivo does not fill the Teams gap: it does not accept Intercom webhooks and does not relay messages posted by bots or apps. It bridges the human conversation, so agents on Slack and managers on Teams can discuss a customer issue together in one bridged channel.
Intercom supports outbound webhooks (Settings → Integrations → Webhooks), so a Teams notification needs a Teams-side receiver or automation tool you manage that accepts the webhook. SyncRivo is not a webhook receiver and does not route Intercom events. Use it to bridge the channel where the support team discusses the conversation between Slack and Teams.
No. SLA notifications are configured in Intercom and delivered by its own integrations. SyncRivo does not route tool alerts; it bridges the human discussion, so on-call agents on Slack and CS leadership on Teams can coordinate on the breach in one conversation.
Use Intercom's own Slack integration and workflows to post top-tier account conversations to a dedicated #enterprise-cs channel in Slack. SyncRivo can then bridge that channel with an account executive Teams channel so the human discussion is shared; the Intercom notification itself is not relayed.
None — SyncRivo does not route Intercom events. Intercom's Slack integration and webhooks deliver new conversations, assignments, SLA warnings, resolutions, and new leads. SyncRivo bridges the messages people write about those conversations across Slack, Teams, Google Chat, Webex, and Zoom Team Chat.
They do different jobs. Intercom's native Slack integration sends conversation notifications to Slack. SyncRivo is a messaging interoperability platform that bridges human conversations between Slack, Teams, Google Chat, Webex, and Zoom Team Chat — it does not relay bot or app messages, so it complements the native integration.
Bridge the conversation around Intercom notifications across any combination of Slack, Teams, Google Chat, Webex, and Zoom Team Chat.
Slack + Teams + Google Chat
Bridge Slack, Teams, and Google Chat simultaneously.
Slack + Teams + Webex
Connect Slack and Teams users with Cisco Webex.
Slack + Teams + Zoom
Unify Slack, Teams, and Zoom Team Chat.
Slack + Google Chat + Zoom
Three-way bridge for Slack, Google Chat, and Zoom.
Slack + Google Chat + Webex
Unify Slack, Google Chat, and Cisco Webex.
Slack + Zoom + Webex
Bridge Slack with both Zoom and Webex.
Teams + Google Chat + Zoom
Connect Teams, Google Chat, and Zoom Team Chat.
Teams + Google Chat + Webex
Bridge Teams, Google Chat, and Cisco Webex.
Teams + Zoom + Webex
Unify Teams, Zoom, and Webex in one bridge.
Google Chat + Zoom + Webex
Connect Google Chat with Zoom and Webex.
Intercom posts the notifications. SyncRivo bridges the human discussion across Slack, Teams, Webex, Google Chat, and Zoom.
Ready to connect? Slack ↔ Teams connection setup →