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.
Stephen Ellis
shared this idea
We have been iterating on different designs and are starting to test internally. I don’t have a timeframe but will keep you posted.
427 comments
-
Anonymous
commented
Get it done fast please
-
Mike Todd
commented
Adding to this topic.
Problem: Users use the "Start a new conversation" field to reply to existing conversations, including their own just-entered conversations. This leads to broken messaging. People want to use this feature similar to apps they're familiar with (SMS text messaging, iMessage, Slack, AOL Instant Messenger) -- one long conversation string.Exacerbation: Teams mobile app users are presented with ONLY the particular message when they access a new message via Activity--they are not taken to the conversation tab for a channel, and have no context for the message.
Possible solution: Copy what Slack does. Rename the Conversations tab "Conversation" or "Chat"--singular. Rename the "Start a new conversation" field to "Message [Channel name]". Move the Reply button to the top, far right edge of the message, leading to nested conversations. Do not show all replies to messages by default--they should be collapsed since they're technically asides. This will clean up the Conversations tab and allow users familiar with other services and apps to instantly utilize Teams Conversations without a hitch.
Also, when users access a new message via Activity in Teams mobile, they should be led to the full Conversations tab, at that message's point in the history.
-
Kevin Rupe commented
This is #1 issue that M$ needs to fix. Every single person who is new to Teams makes this mistake. It breaks up the conversation is nearly impossible to follow the thread later down the road when this is done. Please fix ASAP!
-
Anonymous
commented
yes I agree - but I think this is a Graphic Design Issue... as the reply and start a new conversation buttons are so close together and the graphics are very light, or not distinct enough... a bit of a a graphic improvement, or more contrast and this issue would probably dissapear...
-
Beth Dane
commented
This is a much needed change! The sooner the Teams Community has the change the happier we will be!
-
Chris Olson
commented
Just to chime in, EVERY single new person I introduce to Teams trips on this issue. EVERY SINGLE ONE. Please fix!
-
Thomas Garrity
commented
I agree with Miguel Caldeira
-
Sean Ellis
commented
A very common complaint. This is an example of what happens when you violate the UI rules of consistency. Pretty much every other text messaging app uses the box at the bottom to continue the current conversation, so this is what users expect.
A good solution to this would be the ability to put conversations into their own tabs, and then to let these be "torn off" into separate windows so you can see more than one at once.
This is part of the (very popular) request for a more compact and professional view. Main thread at: https://microsoftteams.uservoice.com/forums/555103-public/suggestions/17408641-please-create-a-professional-compact-chat-layout
-
Jon Webster
commented
Start a new conversation in mobile app should only let you start one new conversation at a time. I have accidentally started a new conversation and then tried to reply to my newly created conversation only to start a second conversation from my mobile device.
-
Stephen Herrick
commented
This is extremely aggravating. I would vote to move the whole start a new conversation to top left corner. The reply and 'start a new conversation' are too close together and are easily confused. My team continually creates new threads and this constant segmentation makes it hard to find/keep a consistent discussion.
-
Anonymous
commented
I would like the option to have a dedicated button to start a new conversation, instead of having the text box at the bottom. I'd rather the bottom text box default to replying to the current conversation. I am always starting new conversations when what I really want to do is reply to the one I'm currently viewing.
-
ed hansberry
commented
Please please please do this. Hide the "new conversation" box! Make it so you have to click something to show it or something. It is horrible the way it is now. Especially if when scrolling the message you want to reply to has its reply box obscured by the New Conversation box.
-
[Deleted User]
commented
Figured that after pressing 'reply', I tend to scroll and read the text/images given by other writers to form my answer. When the reply field is outside the visible window, I tend to write into the 'New conversation' field, without noticing that I'm using the wrong field.
-
[Deleted User]
commented
I'd argue that the problem is that you're required to click a button to bring up the reply field, while the 'start new conversation' field is readily visible. It should really be the other way around.
-
Michael Todd
commented
After pushing my team to migrate from Slack, and only reading through the first page of this, the answer seems kind of obvious:
Copy what Slack has already done so well. A channel is the entire conversation, but users can respond directly to a message. The default method for replying to the conversation is to use the large text entry field at the bottom of the screen (where Teams has the New Conversation entry field). To reply directly to another user in Slack, you must create a conversation directly with an existing message (where Teams has the Reply button).Currently, the interface feels more like Yammer than Slack. Microsoft Partners are positioning Teams as an option to Slack, and corporations are anticipating being able to deprecate their Slack accounts in favor of something already bundled in their MS subscriptions. So what functionality does this product rival? Yammer or Slack? At the very least give Admins the ability to set affinity for Yammer or Slack style replies.
-
Ian
commented
Maybe a big floating + sign button to start a new conversation, with the actual new conversation field hidden until that button is pressed.
-
Anonymous
commented
The users I work with have trouble understanding the concept of a conversation within a Team. They tend to use a new conversation for each message, because this is what the user interface looks like (the "chat" at the bottom), instead of starting a conversation then using the reply feature to keep with that conversation. It would be much better to have something that hides the new conversation box to it makes it more intuitive that you should reply to existing conversations. This could be either having to do something extra to start a new conversation (click a button first, which would be on par effort wise with clicking the reply button), or moving the new conversation box to somewhere within the UI that doesn't look like a traditional chat.
-
eric
commented
The problem is a chat is the conversation. To create a new conversation would be to create a new channel for your team. Threaded chat makes absolutely no sense and should be removed from the product.
-
Anonymous
commented
Just like on here, the "Post comment" button does not start a new thread. Coz that would be pretty bad too. :)
-
Kathryn Goble
commented
Great idea, having a "NEW CONVERSATION" button or menu would be very beneficial!