Posts

How can we exclude agents from targeting?

We have some scenarios where we do not want to route an interaction to a specific agent.  For example, when Agent1 initiates an instant transfer to the same skill group, Agent1 should not receive the interaction and it should be routed to some other available agent.    There is a function available in the Genesys queue interface which instructs the functional module, not to route interactions to any agent on the specified list of agents.  _genesys.queue.excludeAgents(ixnid, agents) Parameters: ixnid:  STRING which can be a variable or a constant - This parameter is mandatory. It defines the ID of the interaction which should have this action applied. agents:  STRING which can be a variable or a constant - This parameter is a comma-separated list of agent IDs. To implement the above instant transfer example, we need the 'Employee ID' of  Agent1  and it can be found in the attached data with the key - ' IW_RoutingBasedOriginalEmployeeId'. Reference:...

How to test Genesys co-browse without workspace or agent.

You are a front-end developer working on Genesys Cobrowse implementation on multiple web pages and want to validate the standalone Cobrowse feature without any active workspace interaction. It can be done using the slave page.  Slave page  URL Format:  http://<Co-browse_Server_host>:<port>/cobrowse/slave.html . Example:   http://localhost:8700/cobrowse/slave.html Steps: Open the slave page URL in the web browser. Initiate a Cobrowse session inside web page. Copy the Cobrowse session id from web page. Enter the Cobrowse session id in slave page and connect.