Can this please be made the default option for call distribution? Seems like a very basic function to not be able to route calls based on longest in 'available' status

not sure if this point has been raised but an supervisor view of the actual available time would also be handy, currently we can only see how long in current state.

I pulled this screenshot from the "Intro to inbound call routing in RingCX"

The 2nd paragraph states "By default, the call is distributed through the queueing engine to the next available agent assigned to the queue"

When I read this, that makes me believe the next call goes to the rep who has been available the longest.

Is there any way to confirm the priority here or I am misinterpreting what is being said in the screenshot?

*EDIT*
So, I've been testing RCX to get more information regarding this problem. In my testing, the calls are routed to the Agent who has been available for the longest time.
I did find one exception to this rule. When an Agent goes into a non-available status (break, away, approved busy, training, ect...) the duration that they are in that status, counts towards how long that Agent has been "available"

Example: If I go lunch for 1 hour. When I return and place myself as Available, RCX will show that I've been "available" for 1 hour, so I will get priority for the first call. Otherwise, calls are routed to the longest available Agent.

I hope this clears up some confusion.

Having the system properly route, calls to whoever's been waiting the longest, would greatly improve team productivity and make things a lot smoother and balanced for everyone.

Swift implementation would ensure our team / dept performs to the best of our abilities

assumed, this was the case. I'm surprised this isn't default. ensures true distribution

This would allow our team to be more productive and serve our customers in a more time effective way

This is really important to the distribution of work within our team.  For our function, the team, of 55, are regularly in and out of different states,completing differing off phone tasks for our customers.  Allocating calls based on an Agent's highest available time to take a call, rather than the longest time between when they last actually took a phone call, would provide a better spread of overall workload.  
Another example of where this allocation of calls would better suit our service would be relating to the types of calls we take.  Our service is not based on transactional type calls and therefore there is a big difference in the length and complexity of the calls we take.  This can mean that call lengths regularly vary between 1 minute to over an hour.  This variety translates into the length of time it takes an agent to make the notes from the call (in wrap time).  Where an agent has been talking for 50 mins, wrapping for 20 mins and then receives the next inbound call - over an agent that has been sat in 'available' waiting for a call for 15 mins is not an even spread of work. 

Calls should be received exactly in the way a queue or line works. If 3 agents are available and 4 are on other non-call related tasks - the calls should just cycle through the available 3 agents. So the agent at the top of the line gets the first call and once they complete their call, they go to the back or end of the line/queue. Anyone returning from unavailable to available gets put at the end of the queue and the system simply cycles through available agents in turn.

A straight round robin without any modifying math would work well for us as we have work tasks as un-available status which agents should not be effectively penalized for by giving them incoming calls ahead of staff who have not been working on such tasks.