Teams Chat on Mac - Is there a way to change the chat "send" command from "enter" to "command-enter"?

Dear Mitchell Lustig (LATENTVIEW ANALYTICS CORPORATION),

Good day! Thank you for getting back to me.

I understand your frustration with the current behavior of the Enter key in Teams Chat on Mac. It's incredibly annoying when you accidentally hit Enter and send a message before you're ready, especially during important conversations.

I'm truly sorry that the workarounds I suggested didn't fully address your needs. I know that changing the send command to Command+Enter would be a significant improvement for many users, including yourself. As you mentioned, you've already submitted feedback to the Microsoft Teams community, which is the best way to make your voice heard. I'll do my best to keep an eye out for any updates from Microsoft regarding this issue and will share any relevant information I find.

Please understand that nobody here, including us as community moderators, are the product developers or decision-makers and have no control over the product. We can only assist you with available solutions and provide the feature's availability status within our scope and capability. Please help vote for the reply so that many other users may find it easier and push Microsoft to change this.

In case I get further info on this feature, I'll surely revert on the thread. Thank you for your kind understanding, and have a great day!

thank you for the reply, however neither of those options solve the issue of sending the unfinished/unedited chat message when accidentally pressing the enter key. I have filed the feature request with the team as you suggested. -M

YES PLEASE .... Command Enter to send messages on Mac.

Ideally.. peeps should be able to configure this to their own preferences.

Hello,

I would also very much welcome it if there was a dedicated command (cmd+Enter) for sending.

The worst thing is the inconsistency. I usually use Shift+Enter to avoid accidentally sending a message half finished. But if I have an enumeration, for example, and want to create the next bullet point, I have to press Enter. Or if I want to end the enumeration, I press Enter twice in succession, a third time then sends the message - but not always, according to my observations.

All very frustrating.

Dear Mitchell Lustig (LATENTVIEW ANALYTICS CORPORATION),

Good day! Thank you for posting to Microsoft Community. We are happy to help you.

I understand your issue with accidentally sending incomplete messages due to fat-fingered Enter presses. While it appears that Command+Enter should be the shortcut for sending messages according to the official Microsoft article (Keyboard shortcuts for Microsoft Teams - Microsoft Support [cedb-3ddc-6a1-bdf3]), it seems there might be a discrepancy between the documentation and the actual functionality.

In my tests, both Enter and Command+Enter seem to send messages in Teams chat on Mac. Unfortunately, there's currently no built-in option to change the default "send" command from Enter to Command+Enter.

Here are some workarounds that might help you avoid accidental message sends:

1. Use Shift+Enter/Return: Pressing Shift+Enter inserts a new line within the chat window without sending the message. This allows you to compose your message and hit Enter only when you're ready to send it.
2. Preview Before Sending: If you're comfortable using the mouse, you can compose your message in the chat box and then hover your cursor over the send button (the arrow icon). A preview of your message will appear. You can then double-check it before clicking the button to send it.

I apologize for the inconvenience caused by this inconsistency. I'll keep an eye out for any updates from Microsoft regarding the ability to customize the send command in Teams chat on Mac.

In the meantime, please consider submitting feedback to Microsoft to request its inclusion in future updates, you may create an entry as a feature suggestion in the Feedback Portal at Microsoft Teams · Community, Other users may vote it and make it more visible to the service team so that it may be considered for future upgrades.

For other concerns, please do not hesitate to add you post in the Microsoft Community Team.

Thank you for your cooperation and understanding.