cancel
Showing results for 
Search instead for 
Did you mean: 

Non-verbal feedback on Chromebook

tsengf
Newcomer
Newcomer

Hi, I'm using Zoom version 5.0.1 (4292.0916)  on the Chromebook. According to the following URL, non-verbal feedback such as the ability to raise hand, the ability to indicate go faster or slower, and to use emojis should be supported. https://support.zoom.us/hc/en-us/articles/115001620786-New-Updates-for-Chrome-OS

 

I can locate the raise hand option by clicking on Participants during the meeting. However, I can't locate the emojis. Are they hidden in another location?

5 REPLIES 5

Rupert
Community Champion | Customer
Community Champion | Customer

Hi @tsengf 

 

For your own Meetings, where you are the Host, Non-verbal feedback is dependent on also being enabled in your Zoom account settings at https://zoom.us/profile/setting

 

If you are attending other people's meetings, you will only get those features in your client if the Host as enabled them for Meetings in their account.

 

Rupert_0-1632921929627.png

 

 

 

I am not the host. The other meeting participants are able to send Meeting Reactions. I am unable to access the feature on the Zoom app on my chromebook.

Rupert
Community Champion | Customer
Community Champion | Customer

If your Chromebook is logged in to a Zoom profile, I would check online anyway at  https://zoom.us/profile/setting

 

Bort
Community Champion | Employee
Community Champion | Employee

Due to all ChromeOS apps being depreciated by next year, I would recommend switching to using the web client, rather than continuing to use the Zoom for ChromeOS app. The web client already has more features and will continue to get new features and updates, whereas the ChromeOS app is just getting security and bug fixes until the Chrome team disables them entirely on the backend. 

In my case, zoom URL links automatically open the app. I also do not manage the system and any options to change this behavior has been blocked out for me.

 

Fortunately, I'm getting around this by editing the meeting URL to look like the form

*/wc/join/*

rather than

*/j/*

 

Although annoying, this has resolved the problem.