I consider this to be critical to maintain the integrity of the queue call order. Would appreciate attention given to this feature!
The way it functions now, doesn’t work to allow calls to be handled in the order they were received; it essentially takes any call that must be parked ‘out of line’ due to two reasons – A: Having the ‘Park Location’ as general, rather than for an individual recipient, and B: Due to that, it doesn’t stop the flow of incoming Queue calls for that specific recipient.

I consider this to be critical to maintain the integrity of the queue call order. Would appreciate attention given to this feature!

The way it functions now, doesn’t work to allow calls to be handled in the order they were received; it essentially takes any call that must be parked ‘out of line’ due to two reasons – A: Having the ‘Park Location’ as general, rather than for an individual recipient, and B: Due to that, it doesn’t stop the flow of incoming Queue calls for that specific recipient.

This was a basic function in our Avaya PBX system and is crucial to ensuring calls are answered in the order they were received. Parking a call to someone's extension ensures that it is the next call they receive and that no queue calls ring to them before they can retrieve the parked call.

This was a basic function with our Mitel system before we switched over to RingCentral. Implementing this feature is crucial to our workflow.

This feature was included in our old Mitel and is essential to our workflow. We would really appreciate this feature being available.