Often, the <--Reply appears hidden behind the "Start a new conversation" field. This results in forking conversations rather than keeping all under a single topic thread.
Could the Reply button move out where we already expect to see Conversation tools?
Donnie Funderud commented
I have shared this in other points as well. This is a major headache and hopefully can be addressed sooner rather than later.
I agree with a more prominent reply button and also changing the "Start a new conversation..." field in a way that won't be confused with replying to a conversation thread. Maybe a button instead to start a new conversation?
Gary R commented
Fully support this idea, we have a large number of Teams users in our organisation and there are repeated instances of people clicking on the new conversation field instead of reply. I think the Reply button should be placed to the right or made more prominent, it's directly above the New conversation field and it's very easy to mistakenly click on the wrong one.
I think there should only ever be a single text-entry field. When I reply, either accept the input in the main sticky text entry field at the bottom of the window, OR hide that field and it's controls while the reply field is active and available. I see an ongoing UX issue with explicitly selecting to Reply via the CTA, then the system invalidating that selection because I clicked on the ALWAYS PRESENT text-entry field where I usually enter text.
Forking conversations cause major headaches during a major incident where many people are responding quickly. Making it easier to reply to a current thread would be a big bonus.