Ok so we've switched ALL our clients over to the PWA app and some users (a vocal minority) are not happy.
Here are the biggest complaints so far:
PWA app can't be made to consistently run in the background. If users accidentally close the PWA window they miss calls.
With the Desktop app if users closed the program with the "X" in the top-right it would still stay running in the background and would still pop-up or be access-able from the tray icons.
Shared Parking was simple with the BLF and is now confusing to users to have to click > Panel > right-click on the call > click Park > click Un-Park
Before this was just one click in the BLF to park or un-park a call.
If users clear their browser cache (* while troubleshooting other websites) and are getting signed out of of 3CX.
Headset Integration and Headset call control are inconsistent. We've set the permissions in the browser to allow HID device control for Yealink headsets but the results are mixed and unfortunately with receptionists it only takes one dropped or mishandled call to rattle their cage.
Is anyone else having these problems and are their fixes for any of them?
PWA app can't be made to consistently run in the background. If users accidentally close the PWA window they miss calls.
With the Desktop app if users closed the program with the "X" in the top-right it would still stay running in the background and would still pop-up or be access-able from the tray icons.
If you close the Electron app for sure you will not get any calls. What we did though is that if the user presses X it doesnt close it it minimizes it. In the case of PWA, it will work as long as the browser is open in the case of chrome. In the case of Edge the browser will be started. Unfortunately we can not block the browser being closed but i believe most users need a browser open.
Shared Parking was simple with the BLF and is now confusing to users to have to click > Panel > right-click on the call > click Park > click Un-Park
Before this was just one click in the BLF to park or un-park a call.
This is coming in update 7a
If users clear their browser cache (* while troubleshooting other websites) and are getting signed out of of 3CX.
Yes but it should work that way
Headset Integration and Headset call control are inconsistent. We've set the permissions in the browser to allow HID device control for Yealink headsets but the results are mixed and unfortunately with receptionists it only takes one dropped or mishandled call to rattle their cage.
No its exactly the same code and we have verified this. I believe its simply an issue on that machine and not related to electron or PWA. If you can reproduce this let us know and we will follow up to double check.
Nick,
Thank you for your quick and detailed response. Our users are very happy to hear the BLF is coming back soon!
Regarding the closing of the PWA and clearing browser cache. Yes, our end-users will do some strange things and these problems are minor but as an IT admin it's nice to prevent users from making some of these mistakes.
Headsets, that's helpful to know the codebase is the same. We're mostly on Yealink headsets and will troubleshoot this from their end. I will report back if I discover anything useful.
Thanks again Nick. I really appreciate your candor through this.
