Using Composer 8.1.4 and running into an issue with skill based routing and the error.interaction.redirect.
If the agent workspace (Workspace Desktop 8.5) for some reason rejects the call for a technical issue (not controlled by the agent) in a skills based routing scenario, our routing strategy loops back to the target selection logic and tries again. However, the agent continues to remain available (despite being unable to receive the call). How does one force the target selected to go into a not-ready state from the routing strategy.
Creates instance of RequestAgentNotReady with required parameters set.
Parameters:
thisDN - DN of the controlling agent or Route Point.
agentWorkMode - The current work mode of the agent in question.
Not included in the request above, but these are all of the parms:
Creates instance of RequestAgentNotReady with all parameters set.
Parameters:
thisDN - DN of the controlling agent or Route Point.
agentWorkMode - The current work mode of the agent in question.
thisQueue - The queue related to ThisDN
reasons - Additional data intended to specify reasons for and results of actions taken by the user.
extensions - An additional data structure intended to take account of switch-specific features that cannot be described by other parameters or in the original structure of user data.