Longest Available Agent

[Dan Percy]

I am trying to do some routing based on Longest Available Agent. I am using an Aspect switch and have been trying to monitor an agent group defined in the switch. I have not been able to get any events from this switch defined group via Genesys. Is this even possible ? Any other ideas for receiving LAA on Aspect ?

Thanks

[Bartacus]

In your strategy, perform agent selection "Based on Statistics" , and use the stat "StatTimeInReadyState". This will select the agent that's been waiting/ready the longest.

[Carlos Alanis]

Just remember an Agent can cheat this making a quick logout/login....

[robert_rudman]

I'd like to know more about an agent can cheat this with a quick logout/login?

Do you mean by logging out/in they can avoid calls? Please explain.

[mike kamlet]

If the stat you are using is "most idle agent" then the agent that has been in the ready state for the longest amount of time will get the call.

In a non-busy environment, if an agent quickly hits not-ready/ready they essentially reset their clock.  Instead of being in a ready state for 1 min, they are only ready for 1 sec since they had changed to not ready.

There's no need to log out, nor does the agent need to stay in a not-ready state for any measurable length of time.

Avaya has a method to route to least occupied agent (where they use agent occupancy as the stat) -- there are drawbacks to that approach as well..

[catanirex]

Have you checked out StatAgentLoading statistic?
It is used to select agents based on current agent loading

[gustav]

Create a custom statistic for 'TimeSinceLastCall' which resets the timer based on the time the agent last received an inbound call, vs, time in Ready state.  This prevents agents from going 'ready / not-ready' to beat the system, or agents calling eachother to 'knock eachother out of agent queue'.

As for the switch defined groups, if they are not dynamic, could you not create a physical group in Genesys to mirror the switch group.

[Fouad douhan]

[quote author=mike kamlet link=topic=612.msg15965#msg15965 date=1231942990]
If the stat you are using is "most idle agent" then the agent that has been in the ready state for the longest amount of time will get the call.

In a non-busy environment, if an agent quickly hits not-ready/ready they essentially reset their clock.  Instead of being in a ready state for 1 min, they are only ready for 1 sec since they had changed to not ready.

There's no need to log out, nor does the agent need to stay in a not-ready state for any measurable length of time.

Avaya has a method to route to least occupied agent (where they use agent occupancy as the stat) --[glow=red,2,300] there are drawbacks to that approach as well..[/glow]
[/quote]

What are the drawbacks to that approach?