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

230 results found

  1. There should be a way in RingCX to enhance the callback experience by allowing callback requests to be honored immediately after the caller’s initial input, without requiring a second confirmation—even if the caller disconnects early.

    Current Behavior
    1) Callers press “1” to request a callback.
    2) A second confirmation (“press 1 again”) is required before the callback is officially queued.
    3) If the caller disconnects before completing the second confirmation or before system disconnect, the interaction is marked as “Inbound ACD Callback Incomplete.”
    4) No callback is generated, even if the caller already indicated intent.

    Problem Statement
    • The two-step…

    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. Feature Request: Create a feature that can dynamically determine when a callback queue event should be offered based on specific thresholds (i.e SLA, elapsed time (currently in place), abandoned rates, # of calls waiting, etc.)

    5 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. Currently, RingCX supports agent priority ranking for voice skills, allowing administrators to route interactions to the most qualified agent first, with automatic fallback to other available agents. This same capability does not exist for digital skills.

    We are requesting the ability to assign priority rankings to agents within digital skills, enabling digital interactions to route to the highest-ranked available agent before cascading to others. This would support proficiency-based routing, improve efficiency, and provide consistency across voice and digital channel configuration.

    7 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. Executive Summary As customers migrate from RingEX to RingCX (or adopt a hybrid setup), reconstructing complex Interactive Voice Response (IVR) menus manually in RingCX is a major pain point. It is time-consuming, prone to human error, and delays the onboarding process.

    This feature will allow administrators to export an existing RingEX IVR configuration and import it directly into RingCX, automatically mapping menus, prompts, audio files, and key presses (extensions) to the corresponding RingCX queues, scripts, or flows.

    1. Problem Statement
      "Rebuilding a 5-level IVR menu with dozens of audio prompts in RingCX takes hours of manual labor and requires dual-monitoring both…

    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)
  4. customers would like to have the Hashtag in the list of possible DTMF codes in IVRs and Queue events.

    45 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. Ability to filter the numbers added in route properties for all workflows instead of checking them manually. It will be efficient and time-saving if there's an option for this. In this way, we can change the number added to another number we prefer and resolve the issue as soon as possible.

    10 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. Manager would like the option to assign out callback to agents and then have agents pick up those calls once available

    12 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. Option to modify the Caller ID number used for Inbound ACD Queue Callback Answered in RingCX
    The customer would like the ability to change the Caller ID number used for Inbound ACD Callback Answered within the RingCX platform. They want to be able to manually update this number through their RingCX portal.

    12 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. Current Behavior:
    When a call routed to a workflow or voice queue is sent to voicemail, the email notification received contains only the voicemail recording as an attachment. There is no voicemail transcription included in the email body.

    Requested Enhancement:
    Enable voicemail transcriptions to be included directly in the email notifications sent when a voicemail is left for a workflow or voice queue.

    This functionality already exists in the RingEX platform, and we would like to have the same capability available in RingCX for consistency and usability.

    Important Clarification:

    This request is not related to the Queue Voicemail Channel feature.…

    6 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)
  9. When using the (warm) "Transfer" feature, agents are given call controls for both calls independently. This allows agent to switch between both calls as needed by placing one leg on hold. It also provides options to disconnect certain legs, their leg only, or the entire call.

    In contrast when using the (Stay on call) "Requeue" feature agents do not have any ability to switch between both calls.

    If an agent needs to reconnect the voice path to the original while utilizing "Requeue", they must hit "Resume". By doing the Requeue is effectively cancelled and agents would need to restart the…

    23 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)
  10. Hello RingCX Product Team,

    We are currently using the callback feature for our patient call flows and have identified a usability issue that is impacting completion rates.

    Our reporting shows that approximately 7% of callers fail to complete the callback setup process. After reviewing call recordings, we believe this is due to the confirmation message played during callback setup, which can reasonably lead callers to think the process is complete and hang up prematurely.

    The current message played is:

    “Thank you for using our callback service. We will maintain your place in queue and return your call as soon as…

    5 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)
  11. Currently, if you requeue a call and select say on the call, there is not a way to take the call back. If you click end call, it will disconnect the call. There is no option to cancel the requeue. With transferring calls, you can cancel the transfer, but you cannot cancel a requeue.

    45 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)
  12. Route digital interactions to the longest available agent, regardless of how many concurrent interactions each agent can handle. For example, we have agents set to two concurrent digital interactions, and when two come in they both go to the same agent. We would want one to go to the first, then the second to go to the next available agent. An additional option to choose to have this work for voice interactions as well could also be useful.

    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)
  13. Allow RNA callers to be given priority in being answered next, rather than being sent back to the queue as a new segment in their call and having to wait in line again.

    5 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)
  14. Currently, all inbound calls to our RingCX Queues will only show the callerID as, "UNKNOWN."

    Meanwhile, callerID works just fine for all inbound calls coming into RingEX.

    This function needs to exist so that our Agents can better identify our customers as the call in.

    25 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)
  15. Currently, the callback feature has no caller ID override. By default, it uses the DNIS as the caller ID when a callback is made by the system. For calls to external numbers that are forwarded to the RingCX number, it shows the number where the external number is forwarded as the caller ID.

    Looking to have a feature or option to set the forwarded number (external number) as the caller ID.

    18 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)
  16. Issue Summary:
    Calls are not being routed to the agent with the longest available time. Based on the RingCX Real-time Analytics report, calls are not consistently directed to the agent who has been available the longest.

    Current Behavior:
    RingCX routes calls without correctly prioritizing the agent with the longest AVAILABLE duration. Analytics (“Agent State Change Raw” report) confirmed that when a call arrives, the agent with the longest AVAILABLE state time is not always selected.

    Expected Behavior:
    RingCX should route calls to the agent who has been in the AVAILABLE state the longest.

    Troubleshooting Performed:

    Reviewed “Agent State Change Raw”…

    7 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)
  17. background:
    Customers attempting to access RingCX using mobile devices (iPhone/iPad and Android) via supported browsers such as Chrome, Safari, Firefox, and Edge are encountering an error message stating:
    "You’re using an unsupported browser. Switch to the latest version of Chrome, Firefox or Edge to start a session."

    This occurs even when using updated versions of supported browsers.

    current behavior:

    Users can access the RingCX login page via mobile browsers
    Upon attempting to start a session, the system blocks access
    Error message indicates unsupported browser
    Issue is consistent across all browsers on iOS devices
    Similar limitations may occur on Android devices…

    1 vote

    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)
  18. Summary:
    Request to enhance call control functionality when using "RingCentral Phone" as the selected voice connection within RingCX.

    Description:
    Currently, when "RingCentral Phone" is selected as the voice connection in RingCX, the call control remains within the RingCX platform (ringcx.ringcentral.com). As a result, users are unable to perform call control actions—such as call transfer—directly from the RingCentral App.

    Expected Behavior:
    When "RingCentral Phone" is selected as the voice connection, call control should be enabled within the RingCentral App, allowing users to:

    Perform call transfers
    Access standard call control features (hold, mute, transfer, etc.)
    Seamlessly interact with RingEX features, including voicemail…

    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)
  19. Add an ability or a configuration to have like a whisper greeting for the agent in RingCX on which queue the call came from or the queue their callers chose.

    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)
  • Don't see your idea?