Skip to content
  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

188 results found

  1. Though there are other ways to accomplish this, many customers would like to have this functionality.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Many APIs require an initial authentication call in order to make the main API request, which requires two API calls for an event.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. When a WWW node times out there is no reason code in the debug. It would be helpful to see the reason code so that it can be determined why it’s not working.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Troubleshooting would be made easier with access to the debug results for web services and agent scripts

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. The ability to check queue status (available agents, number of calls waiting, average wait time, etc) from the IVR will help greatly in some of the routing scenarios customers have.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Within the "track numbers" section of the RingCX platform, we have the ability to ring multiple destinations in parallel or sequential. This is a great tool, since there isn't a 'technology cap,' limiting the amount of destinations can be run simultaneously. However, from a management perspective, there is little ability to search/filter on the assigned number destinations. For customers who wish to use both RingCX as well as RingEX features, having the ability to use the track number feature for high volume 'ring groups' would be advantageous. One example would be when a customer hits the ring-group limitation of RingEX.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. The 'modular' nature of Engage Voice is helpful. However, with this design, some feature-sets of one routing component are not found in others. Having a if/and feature enhancement to inbound queue events would bridge this gap. Example: Play audio file 'A' for normal conditions. If wait time is 'x' then play audio file 'B'. This idea could be expanded to any queue event type.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
1 2 6 7 8 10 Next →
  • Don't see your idea?