My meetings have a host and co-host (sometimes 2 co-hosts). Participants want to private message specific hosts, and report they are unable to differentiate different hosts/co-hosts. When they click one co-host's name to privately message them, another co-host's name will show in the chat box as the recipient.

Is there a way to differentiate hosts and co-hosts signed into the same zoom account so that it is more clear which leader is being privately messaged?

I am using an up-to-date Zoom application on an up-to-date Windows 10 system. At times that seem random Zoom attempts to start, and then fails with a "no meeting" message. I have no scheduled meetings on my Zoom calendar and no scheduled meetings on Google or any other calendar. I am not pressing any hot key. I do not have Zoom in windows startup, and I always quit fully out of Zoom after every meeting by right clicking the icon in the taskbar and selecting "quit Zoom".

I am not trying to launch Zoom and I am not clicking on any Zoom icon or visiting any Zoom web page. This happens after I have been using the computer for some time, not at startup. I cannot reliably reproduce this behavior because I don't know what is triggering it. It's as if Zoom just decides all on it's own that now is a good time to start a meeting -but there is no meeting and I have no desire to use Zoom at that moment, it is just acting on its own. How do I stop Zoom from doing this?

I don't think this is a "Meeting" issue, it is a higher level Zoom issue, but this forum would not let me post without selecting a board, and this board seemed the least poor fit for this problem.

Heya! I'm using the Linux Flatpak, and it seems to be automatically launching on startup, or tryng to at least (I get crash reports about it). I went into the app to try to disable it, and the setting doesn't seem to be there anymore. I tried in the DE's startup apps (on Gnome 44, using Gnome Tweaks), but it's not listed there.

My only guess is that Zoom added a dbus/systemd message, and I can't seem to find it. Any help is appreciated.

I made this request 2-3 years ago and was summarily refused. This is such an easy code fix; I was truly disturbed by Zoom's response and total failure to understand what is really going on with average users out in the world. Feel free to keep the audio setup methodology that you already have...fine...I love being forced to remember the 3 or 4 steps it takes to get to the audio controls...but please add this "easy button". Along with (1) figuring out how to properly send meeting invitations and (2) meeting hosts to manage their screens, the #1 issue I experience in my use of zoom in multiple groups (over 15) is the simple failure of attendees to mute and unmute themselves and the time wasted with the silence, the additional time to figure out how to mute / unmute, and then even more time to restate whatever they were saying. NOT EVERY USER IS AN EXPERT nor do they want to be. These folks are often embarrassed when they realize what has happened. Is that really the experience with zoom that you want them to have? Bosses and other leaders, as well as some attendees, are already clamoring to go back to in-person meetings. I'm giving you a simple change that will really help out YOUR meeting goers have a better experience. Two more things. If you can, make the button mute zoom ONLY, not the whole system. And, your current output method doesn't actually fully mute the audio. I can still hear it even when the output level in your popout window is at zero.

When I am trying to join a meeting (one that I am not hosting), I get an option to "launch" the meeting, but not one to "join" the meeting. When I click the launch button, I can get into the meeting (eventually), but my camera and audio have big lag times. What is going on?

Is anyone else having trouble with Zoom connecting to USB plug in webcams?

I've had this issue on two different laptops on multiple occasions.

When the webcam is lugged in correctly, Zoom does not recognize the camera and only offer connectivity to the built in laptop camera.

Multiple attempts to connect haven't worked.