Summary
Request to enhance RingCX agent state handling by automatically restoring the previously assigned auxiliary state (reason code) after a session reconnect or brief network interruption.

Background
Currently, when an agent experiences a temporary network disruption or session reconnect, the system may restore only the base state (e.g., “Working”) without the associated auxiliary state (custom reason code). While the backend retains the correct state for reporting and analytics, the agent’s UI may display an incomplete or generic state.

This creates a mismatch between the agent interface and the Live Dashboard, which can lead to confusion and unnecessary troubleshooting.

Problem Statement
After a reconnect event:

The agent UI may lose the auxiliary state (reason code)
The UI defaults to a base state (e.g., “Working”)
The backend continues to reflect the correct full state (base + auxiliary)
Agents may need to manually refresh the browser to resync

This behavior impacts user experience and may reduce confidence in system accuracy, even though backend data remains correct.

Proposed Solution
Enhance the system to automatically restore the full agent state, including auxiliary/reason codes, after a reconnect or session recovery.

Specifically:

Persist the last known auxiliary state on the server side
Ensure the reconnect payload includes both base state and auxiliary state
Automatically reapply the auxiliary state in the agent UI upon reconnection

Expected Behavior

After reconnect, the agent UI should display the exact previous state (base + auxiliary)
No manual refresh (F5) should be required
UI and Live Dashboard should remain fully synchronized at all times

Benefits

Improved user experience with consistent state visibility
Reduced confusion and support inquiries related to state mismatches
Increased trust in system reliability
Eliminates need for manual UI refresh after reconnect events