Description/Business Use Case:

Currently, RingCX users (specifically Agents working from home) who attempt to view a Live Wallboard while simultaneously logged into the Agent Interface experience session token conflicts. This occurs because modern browsers share a single "cookie jar" per domain.

When a refresh token for a Wallboard login is processed, it can overwrite the Agent’s digital messaging token, causing the "Messages" function to intermittently disappear.

Requested Change:

Enhance the RingCX authentication architecture to allow for isolated session tokens. This would enable a single browser profile to maintain both an Agent session and a Wallboard/Admin session concurrently without credential crosstalk or the need for separate browser profiles.

Benefit:

Compliance: Supports customers with strict "single-browser" IT policies (e.g., companies restricted to Microsoft Edge only).

Productivity: Removes the need for agents to manage multiple browser profiles or perform frequent cache clears.

UX: Provides a seamless experience for remote agents who need real-time data visibility alongside their active communication tools.