Better visual delineation between `Reply` and `Start a new conversation`
It's very confusing to new users that there is a difference between replying to an existing conversation and starting a new one within a channel. This is a visual thing as much as anything else. The 'reply' buttons are not naturally attractive if you just want to start typing a message. There should be a logical gap between the bottom of a conversation and 'start a new conversation'. 'Start a new conversation' needs to be separated visually, as if it's a second order command rather than a first order...reply.
Rollout of the new conversation button to the general public is complete! Enjoy.
851 commentsComments are closed
Seeing the same thing in our testing.
Pepo Heraud commented
Hey Travis, I like this approach and would like to see it in action.
Travis Staggs commented
Move into reply. If you mean to reply to an ongoing conversation but accidently 'start a new convo,' you could hit the eclipses and choose to move to 'reply' on chosen conversation. Then people get alerted for the thread you wanted and conversations continue.
the reply to a conversation should be the default when wihtin a channel rather than the "start new conversation". otherwise you end up with new conversations and people don't reply, which is the pointless.
Paul Delgado commented
Yes having same issue with others accidentally starting a new conversation when they intended to reply to the ongoing conversation. So having an better visual queue to differentiate between reply and starting a new conversation would be good.
Threaded conversation and chat are two different things, and Teams has them both. Moving the "new conversation" box to the top would help this.
@DarrellCWebster Overall it appears that people feel having threading is more of a confusion & hindrance rather than a benefit.
Josh Hoey commented
With the "Start a new conversation" field at the bottom of the screen, it makes it easy for inexperienced users to begin new conversations instead of contribute to an existing thread.
For chat systems that don't allow threaded conversations, a text field at the bottom is the proper way to chat, but in Teams, this is the way to split conversations into unfollowable tangents.
So please make it so that a user needs to click a button before they can "Start a new conversation", so that it isn't done by accident.
Using reply makes sense. That allows you to have threaded conversations rather than one long thread.
James S commented
We connected our room up to VSTS to replace the old team room that was part of VSTS itself. We're seeing that replies to conversations get lost *really* quickly...it would be nice to have some sort of way to disable replies, or at least make them more discoverable. There is definitely an ambiguity whether to create new conversations or reply. We tend to use the room where each event/message is its own discrete thing, not as the starting point for a threaded conversation.
Angela Sze commented
It seems odd and unlike other chat/team experiecnes that the compose box at the bottom is always ‘starting a new conversation’ rather than just adding to the ongoing conversation in the Channel. I often send a few short snippets, and these all get started as separate conversations. If I want to respond to someone in the channel, and its at the bottom of the window, why do I have to click ‘reply’ to reply to them? Please make chat like chat :)