Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
chat 3.11
-
None
-
None
-
CRM Connector (CRMCONNECT)
Description
Consider the following scenario:
- Configure a queue with two steps with timeout 0 for both steps. It means chat won't wait in step # 1.
- Configure an agent with step # 1
- Configure another agent with step # 2 (this agent should not be the same agent that is configured with step # 1)
- Login both agents and set the state to NOT_READY
- Initiate a chat request, the request should be evaluated on both steps because step timeout for step # 1 is 0.
- Set agent with step # 2 state to READY, the chat will not route to that agent.
Attachments
Issue Links
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...