Support for RingCX session initiation on mobile web browsers (iOS and Android)
background:
Customers attempting to access RingCX using mobile devices (iPhone/iPad and Android) via supported browsers such as Chrome, Safari, Firefox, and Edge are encountering an error message stating:
"You’re using an unsupported browser. Switch to the latest version of Chrome, Firefox or Edge to start a session."
This occurs even when using updated versions of supported browsers.
current behavior:
Users can access the RingCX login page via mobile browsers
Upon attempting to start a session, the system blocks access
Error message indicates unsupported browser
Issue is consistent across all browsers on iOS devices
Similar limitations may occur on Android devices depending on configuration
root cause (known limitation):
iOS browsers are required to use Apple WebKit engine regardless of browser type
RingCX relies on WebRTC and advanced browser capabilities not fully supported in mobile environments
Platform detects mobile browser environment as unsupported for session initiation
expected behavior:
Users should be able to initiate and manage RingCX sessions from mobile browsers
Platform should properly recognize supported mobile browsers
If full support is not possible, provide:
a mobile-optimized experience, or
a clear and accurate compatibility message with guidance
business impact:
Limits agent and admin mobility
Prevents users from handling calls or sessions while away from desktop
Creates confusion due to misleading “unsupported browser” message
Impacts customer experience and operational flexibility
requested enhancement:
Enable support for RingCX session initiation on:
iOS mobile browsers (Safari/Chrome/Edge)
Android mobile browsers
Improve browser detection logic for mobile environments
Provide fallback or limited functionality mode if full WebRTC support is not feasible
Update error messaging to clearly indicate mobile limitation (if support cannot be implemented)
workarounds:
Use desktop or laptop with supported browsers (Chrome, Edge, Firefox)
No viable mobile workaround currently available
additional notes:
This is a recurring customer inquiry and not an isolated case
Similar requests have been raised regarding mobile accessibility and flexibility
Aligning RingCX with mobile capabilities would improve competitiveness and user adoption