Support for threaded conversations

When an org depends on Glip conversations to handle all sorts of matters throughout the day, it's easy to loose a thread in the current schema.

Add support for threaded conversations, please. This will be understandably difficult given the variety of platforms you're supporting. I'm not sure what it will even look like. Perhaps you could simply have two places in each conversation to write: replying to a prior comment or starting a new comment. Whenever someone replies to an older comment, that whole thread becomes the latest message, maybe simply appearing as two comments, first and last, connected by ellipses. Click on this and you actually open a sub-version of the current room. So if you started in the "Marketing" room and click on the sub-thread, you enter a new room called "Marketing - Don Knotts 3/4/18 3:34" unless Don renames his thread.

Good luck with this one and its design. Really hopeful you'll do something for threaded conversation support in 2018.

Seconding this request. My company is just starting to use Glip, and I can see how a Team chat can get really confused. Having the ability to have conversation threads will make the tracking of what is being said and in connection with what, much easier.

Yes. SLACK has this option. It works like this: within the team there is a message; each individual message has an option to create a thread. this creates a sub-message in the same place but eliminates others in the team, if they do not need all the notifications but also have the option to be involved in that side conversation. So what I did in Slack was start a message by naming it the topic of what the sub-message needed to be, to be found easier in the future, and anyone wanting to follow they can. SLACK has the market on the messaging thing, I miss some of the features for sure!! THREADS!!!

I agree with the others. This feature/behaviour in Slack is crucial for a multi-skilled/agile team because there are technical conversations happening between developers that non-techies don't want to be involved in, but often technical discussions require product involvement at somepoint to help understand requirements, etc. It's never perfect but it works very well in Slack and keeps the main channel cleaner than it is possible in Glip.