Many tenants have a split between teams on Slack and teams on Microsoft Teams - typically engineering vs sales, or India vs US. Apragya AI's bidirectional message-routing pattern keeps a conversation in lockstep across both, so nobody has to remember to copy a message between platforms or join two threads to stay current.
The use case
A customer fires a high-priority ticket. Support team lives in Slack. The customer's CSM lives in Teams. With bidirectional routing wired, a message in #cust-acme on Slack auto-mirrors to General > acme on Teams, and replies on Teams flow back to Slack. Same conversation, two surfaces, no manual sync.
How it works
- A Channel Mapping links one Slack channel to one Teams channel (1:1 only - many-to-many introduces noise)
- When a message lands on either side, the connector publishes a copy to the other side with the original sender's name + avatar preserved
- Replies in either thread mirror back to keep the conversation single-threaded
- Attachments (files, images) are re-uploaded to the mirror side
Setup
- Connect Slack and Microsoft Teams under Integrations > Connectors (one-time OAuth each)
- Sidebar > Integrations > Channel Mappings > New Mapping
- Pick the Slack channel + the Teams channel; choose whether to mirror new threads, replies, both
- Optional: per-mapping message filter (e.g., only mirror @here messages, or only messages from specific roles)
The mirror message is clearly marked - a small "via Apragya" tag + the original sender's name - so people on either side can tell when they're reading a mirrored message vs a native one. No accidental impersonation.
Limitations
- Voice/video calls don't mirror - the platforms don't expose call-join APIs for cross-platform forwarding
- Threaded reactions (emojis) mirror but the count is per-side, not aggregated
- Edits and deletes mirror; backdated edits (over 24h old) on one side fall out of sync