Hi All,
It's been a couple of weeks since implementing 3CX in our business and we are using the 3CX Web Client in softphone mode with Sennheiser Bluetooth headsets. During evaluation we looked at the Windows client but it was suggested that all development was now focused on the Web Client and so we took the decision to go with that as the default. Frustratingly there seem to be a number of 'features' of the Web Client that lead me to question whether it is really ready to be used as the primary softphone?
All this makes me wonder how many other people are using the Web client as their primary softphone? I get that it makes sense for new development to use web technologies to make things platform independence, but it shouldn't provide a worse experience that a dedicated app. I've gone back to running the Windows client with the Web client in CTI mode on my machine which provides the best of both worlds (mostly) but seems a backward step. I would be interested to hear other users experiences where they are using just the Web client softphone
It's been a couple of weeks since implementing 3CX in our business and we are using the 3CX Web Client in softphone mode with Sennheiser Bluetooth headsets. During evaluation we looked at the Windows client but it was suggested that all development was now focused on the Web Client and so we took the decision to go with that as the default. Frustratingly there seem to be a number of 'features' of the Web Client that lead me to question whether it is really ready to be used as the primary softphone?
- The very fact it operates in a web browser means we have to manually configure the PC to auto start the browser. It's also makes it more difficult for the user to find the softphone when multiple browser tabs are open and easier to accidentally close the web client mid call and lose the call!
- The browser issues above can be partially resolved by using 3CX as a Chrome app but this seems to have other restrictions such as the Click2Call not working in this mode
- The web client lacks the ability to have a separate ringing device from the headset, in fact setting separate audio controls in general for the web client is much more convoluted than the Windows client
- The headset integration with the web client is flakey in comparison to the windows client, tends to only work half the time
All this makes me wonder how many other people are using the Web client as their primary softphone? I get that it makes sense for new development to use web technologies to make things platform independence, but it shouldn't provide a worse experience that a dedicated app. I've gone back to running the Windows client with the Web client in CTI mode on my machine which provides the best of both worlds (mostly) but seems a backward step. I would be interested to hear other users experiences where they are using just the Web client softphone
