Details
-
Bug
-
Resolution: Done
-
High
-
None
-
None
-
AMRIT Sprint 26, AMRIT Sprint 27
Description
Description
At the Associate level, the ACW (After Call Work) timeout of 120 seconds is not working when the call is disconnected from the Agent's end. This behavior is not aligned with the expected application functionality. Interestingly, the same functionality is working correctly in the Production environment, where ACW triggers regardless of how the call is disconnected.
Steps to Reproduce
Log in as an Associate.
Make or receive a call.
Disconnect the call from the Agent's end.
Observe that the ACW 120-second timer does not activate.
Expected Behavior
The ACW 120-second timer should start after the call ends, irrespective of whether the call is disconnected from the agent's end or the recipient's end.
Actual Behavior
The ACW timer does not trigger if the call is disconnected from the Agent's end, which contradicts the expected application behavior.