Slack and Teams handle replies differently - Slack has explicit threads, Teams has reply chains in chats. convly bridges both so a reply on one side shows up as a reply on the other, not as a fresh standalone message.
Replying from Slack
Use Slack's normal "Reply in thread" action on any message that came from the Teams side. Your reply appears on the Teams side as a reply to the original message, not as a new chat message.
If you reply with a regular message instead of a thread reply, it lands as a new top-level message on Teams - that's expected, since you didn't tell Slack to thread it.
Replying from Teams
Use Teams' built-in "Reply" action. The reply lands on the Slack side as a thread reply under the original message, mirroring the structure on the Teams side.
What's preserved
- The link between the original message and the reply
- The author's identity (Teams users keep their name and avatar when their reply lands in Slack, and vice versa)
- Edits and deletes - if you edit a reply, the edit propagates
- Reactions - emoji reactions sync both ways
Older messages
Replies and threading only work for messages sent after convly was set up on the conversation. Historical Slack threads stay Slack-only; historical Teams reply chains stay Teams-only. New activity from this point onward is what gets bridged.