ACW (After Call Work) 120 seconds not triggering if the call is disconnected from the agent's end.

XMLWordPrintable

    • Type: Bug
    • Resolution: Done
    • Priority: High
    • None
    • Affects Version/s: None

      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.

        1. image-2024-12-20-14-09-53-463.png
          image-2024-12-20-14-09-53-463.png
          198 kB
        2. screenshot-1.png
          screenshot-1.png
          198 kB
        3. screenshot-2.png
          screenshot-2.png
          391 kB
        4. screenshot-3.png
          screenshot-3.png
          348 kB

            Assignee:
            Rohit Jayaraman [X] (Inactive)
            Reporter:
            Rohit Jayaraman [X] (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: