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.
We have been iterating on different designs and are starting to test internally. I don’t have a timeframe but will keep you posted.
And the fact that there's no timeframe even after almost a year is really discouraging.
This is a major issue for our org. Everyone wants to treat it like Skype, and now they think Teams is a bad/complicated tool. Even after people understand the concept they still end up starting a new conversation by mistake. There's not enough of a delineation to alert the users. It doesn't help that chat still operates just like Skype. It's especially hard when users have both tools installed at once. We are trying to push adoption of Teams but users are very frustrated and end up talking behind our backs that we are controlling. If we remind them they think we are annoying sticklers. If we don't remind them they get frustrated because they can't track what responses go with what.
We also need this to be addressed ASAP.
This really needs to be addressed! In the mobile app it works fine. Why not use the same layout in the desktop app? Means, have a button for "new conversation", instead of a chat bar, that looks like you can use it to answer.
Actually, this UX-failure is giving me the hardest time, to roll out Teams country-wide. I get so many angry reactions from possible users. I will not be able to succesfully migrate from Skype for Business unless this is addressed.
And if people miss-read this feature, you are not even able to fix it as a moderator. Because there are not moderation-tools.
Jazz Li commented
A reply-to function on a collab desktop app should be standard these days. I absolutely need to be able to use the reply function in chat. It’s still not available on web.
Please add this as soon as possible!
Created on May, 10th 2017...
Last admin edit on April, 13rd 2019...
Today's date February, 24th 2020...
= 1020 days without complete answer...
= 317 days internally testing...
Is it like FDA approved? Like 10 years with placebo and nocebo tests... To see the efficacity?
Which uservoice is fast to be resolved at Microsoft?
What is the average lead time at Microsoft?
What is blocking you?
Open the sources, I'm source it will be solved at the end of the week!
What about a drag and drop feature that lets original posters (and team owners) grab a message and move it into another conversation as a reply?
Any update on this? We've just moved over to Teams from Slack and this is a massive issue. Staff constantly starting new threads. Definitely needs to be more clearly seperated. In my opionion replying to the thread should certainly be the default. With something more obvious to start a new thread.
Update? This is a big fail on the Desktop app. We need it
Eric Jarvis Huang commented
Come on guys, this is a very important feature for teams.
Please add it to desktop version!
Marcus Mangelsdorf commented
@Christina's idea would solve a lot of the most annoying issues and should need no crazy new UI. :thumbs-up:
[Deleted User] commented
On the android app, i can reply to specific messages, why not on the desktop!??!
There should at least be a way to move stray posts into the thread they belong in - even people who understand they replied in the wrong place (started a new post instead of a reply) are unlikely to delete their post and make a reply instead.
Brady Vidovic commented
Charles Pire commented
A reply-to function on a collab desktop app should be standard these days.
Please add this as soon as possible!
Mark Owen commented
This is *the* main interaction you have with this product. It is broken.
When is it going to be fixed?
Why don't you just copy Slack in that regard? It works perfectly there.
Ryan Elliott commented
Andrew Hutchinson commented
This feature would be great, especially as the user experience differs from the client to the mobile app.