Skip to content
← Analytics & Reporting

How can we improve RingCentral?

Analytics & Reporting: Other

Categories

JUMP TO ANOTHER FORUM

(thinking…)

Park Call to Direct Extension

The customer has an idea of being able to call a park to a specific extension.

19 votes

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We’ll send you updates on this idea

Kenneth Tarosa shared this idea  ·   ·  Report…  ·  Admin →
How important is this to you?

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Autumn commented  ·   ·  Report

    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

  • Angela commented  ·   ·  Report

    o 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 o 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.

  • Corise commented  ·   ·  Report

    o 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.

  • Patricia commented  ·   ·  Report

    o 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.

  • June commented  ·   ·  Report

    o 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.

  • Josh commented  ·   ·  Report

    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.

  • Rick commented  ·   ·  Report

    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.

  • Greg commented  ·   ·  Report

    This is critical for our Tech Department especially during our busy season.
    If a customer calls in and they need a specific tech person they had been talking to we need to make sure they are next in line to talk to that person if they are currently on a call.

  • Houston commented  ·   ·  Report

    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.

  • Bob commented  ·   ·  Report

    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.

  • Tim commented  ·   ·  Report

    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.

  • Angie commented  ·   ·  Report

    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.

  • Kris commented  ·   ·  Report

    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.

  • Kristina commented  ·   ·  Report

    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.

  • Jenna commented  ·   ·  Report

    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.

  • Jennifer commented  ·   ·  Report

    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.

  • Adam commented  ·   ·  Report

    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.

  • Sherri commented  ·   ·  Report

    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.

  • Julie commented  ·   ·  Report

    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.

  • Christina commented  ·   ·  Report

    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.

← Previous 1