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
Temo Lopez commented
I can't wait for this feature to be implement. Everyone keeps making this mistakes at my work place. No one wants to fix their new conversations.
Sam Anderson commented
I see this issue expressed many times a day, every day, across my organization. In aggregate it is a huge drag on efficiency and usability.
Every time somebody starts a new conversation instead of replying - I reply with a link to this "suggestion." Then we all have a good laugh at how long this has been "in progress."
Didier Loiseau commented
So what's the status on this? Today we have to basically tell every newcomer that they should use "reply" instead of starting a new conversation!
Stephan G commented
How about using AI to analyze the last thread and ask the user:
"Your message seems to belong to the last thread - attach?"
Did anyone happen to save a screenshot of the prototypes in the https://aka.ms/ComposeButtonSurvey survey? I'm curious to see what those were.
@Florian RD, can you post a link to a blog post with one of these screenshots? I looked thru the past several and couldn't find one. I'd like to see what the early versions of this are looking like.
Richard D commented
Josh Baker commented
I'm astonished that this feature is still not implemented. We've been using Teams for over 2 years and still people are accidentally starting new conversations instead of replying. I'm a power user and yet occassionally I accidentally start a new conversation so have to delete and reply.
Stuart Ginns commented
Come on Microsoft this is a real bug bear for all users of Teams. When is this going to be resolved.
Tom Engman commented
I swear there is an additional issue with this too where actual correct replies still end up as a separate discussion.. But come on, fix this, it's really not hard at all and would make Teams a little less.. Bad.
Florian RD commented
Come on, you already have this: each time there is a screen capture in Teams blog we see it !
Release it and be done with it !!
Stuart Montgomery commented
When scrolling the reply box becomes hidden behind the Start a new conversation box.
The reply box should always be visible/on top for the conversation that you are currently viewing.
Too many forked conversations are created by users accidentally starting new conversations rather then replying.
Stuart Montgomery commented
This is a big irritation.
When scrolling the reply box goes behind the Start a new conversation box.
The reply box should always be visible for conversations that you have selected.
Mike Fourie commented
Silvio Pellas commented
This is a major usability issue, and the primary reason why we are using CHATS instead of Team Channels.
Shannon Lewis commented
An update would be fantastic!
Daniel Kristensen commented
This is inconsistent on Mobile vs Desktop, and it is confusing.
PLEASE implement this ASAP. A majority of conversations are broken / fragmented because users instinctively want to use the "Start a new conversation" box to reply to an existing conversation
This has to be such a small development effort.
1. Add a prominent "+" button to the bottom right corner of the UI - that is what users can use to create a new Conversation.
2. Get rid of the "Start a new conversation box" at the bottom of the UI.
3. Leave the "Reply" button at the bottom of each existing conversation. (should also be able to "reply+quote" messages in the middle of an existing conversation - but that's a different feature request.
I think there needs to be more separation between the reply button and the thread or making it stand out more. I'm hoping the new design will resolve the confusion.