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

211 results found

  1. 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)
  2. 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)
  3. 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.

    17 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. 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)
  5. 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)
  6. Looking for the ability to just use the Same phone number for the voice queue and for the SMS channel. This is to avoid adding multiple numbers to an agent in EX.

    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)
  7. I would like to suggest several improvements to the way RingCX handles queue events. Currently, managing these is somewhat complicated. The following changes would bring the platform in line with industry standards and significantly simplify the user experience.

    1. Queue Event “Duration”
      Currently, having to manually set a "Duration" for queue events is not ideal, as the event time must precisely match the audio file length. Most competitor solutions play prompts from start to finish, with the duration automatically defined by the audio file itself. Removing the manual duration requirement would prevent prompts from being cut off or leaving awkward silences.

    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)
  8. Allow for Web Service DTMF Queue Event to fire off without changing callers status in queue.

    We are attempting to configure a queue event with DTMF enabled where we offer the caller an option to press X key and receive a text message with a link to our website while the caller waits in queue. Currently, the only way we can get this working without forcing the caller to drop from the queue after receiving the text is to use the requeue option in conjunction with an external web service. This does keep the caller in the same queue, however,…

    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)
  9. The customer is requesting to have a call routing feature that will route the call based on the number of calls each agent has received, to ensure a more balanced distribution.

    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)
  10. For some reason you can set a DTMF Queue event to be an Inbound Queue Callback, but you can't do it from the Queue Event itself. Every other option is there, but that one is missing. It seems a bug or missed item since it would only enhance the options available?

    There are many reasons for a queue event to go to Callback rather than requiring a DTMF selection to do it.

    19 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. 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”…

    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)
  12. Description:
    In the legacy Engage Digital platform, there was a valuable capability called Agent Capacity Profiles, allowing administrators to define how many asynchronous conversations (e.g. email, Apple Business Chat, WhatsApp, social messaging) an agent could handle simultaneously, while also reserving capacity for real-time channels such as webchat or voice.

    RingCX currently lacks an equivalent mechanism, making it difficult to manage agent workload across mixed interaction types.

    Pain Point:
    Without agent capacity control:

    Agents supporting both async and real-time channels can easily be over-allocated, leading to missed SLA targets or delayed responses.

    Supervisors cannot reserve a portion of agent availability for…

    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)
  13. 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.…

    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)
  14. ummary:
    Enhance JavaScript nodes in the Workflow Editor to support “Error” and “Default” routing options to prevent calls from getting stuck in the node when an issue occurs with the script execution.

    Details / Description:
    Currently, the only way to move a call through a JavaScript node is by explicitly setting a connection using ivr.setConnection("go"); and then mapping the connection ? to the value of "go" (or whichever name is assigned).

    If for any reason the script fails to set the connection properly (e.g., a runtime error, variable not found, or unexpected input), the call will remain stuck in the…

    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)
  15. We would like to request a feature that enables the use of a custom alphanumeric verification code for callers entering a call queue. The length and format of this code should be configurable by the customer.

    Proposed Functionality:

    Allow callers to input a unique alphanumeric verification code before or during entry into a call queue
    Enable administrators to define the length and format of the code (e.g. numeric only, alphanumeric, fixed or variable length)
    When a valid code is entered, automatically bypass standard IVR menu selections and route the caller directly into the appropriate queue
    Integrate with CRM systems so…

    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)
  16. Feature Request: Call Park for RingCX
    Summary:

    Enable Call Park functionality within RingCX to allow agents to place a call on hold in a shared "parking spot" and retrieve it from any other device or extension.

    Details:

    Currently, RingCX does not support call parking, which limits flexibility for teams handling calls across multiple devices or locations. Call Park is a critical feature in traditional PBX and UC systems, and its absence in RingCX creates workflow inefficiencies.

    Proposed Functionality:

    Agents can park an active call into a designated slot.

    The system generates a unique park number or code.

    Any agent or…

    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)
  17. CX queue voicemail is a major issue. It should work exactly like the EX platform, meaning to attach the voicemail as well as the option to transcribe the voicemail in the emailed message. For our users, having a link to another server which does not work. we have already whitelisted it but when logging in you get no voicemail but a option to log in again. We had to transfer the call to an EX queue, then use that queue to save the voicemail to send to a group email.

    36 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)
  18. Currently the ability to park and offer paging is only available on the EX side. In Healthcare, paging on call doctors is a daily aspect of their jobs and not being able to page in RCX has prevented the adoption of RCX. Having the option for an agent to place the caller on hold while they page an office to find a doctor and then hand them directly to the doctor is severely needed on the RCX platform.

    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)
  19. Currently, RingCX does not provide the capability to define individual skill weight or proficiency for each agent individually. This capability is essential because it will:

    • Reduce the need to create a separate skill ("Sales Proficiency 1", "Sales Proficiency 2", "Sales Proficiency 3" and so on) for each weight or proficiency level.
    • Simplify and reduce the level of effort when creating and assigning skill profiles to agents.
    • Streamline skill assignment within queue routing by enabling the selection of a required skill and the definition of a specific weight or proficiency range and order (high to low or low to high).
    17 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)
  20. Description:
    We would like to request a feature in RingCX that allows administrators to block incoming calls based on country or area code, rather than manually adding individual numbers.

    Current Behavior:
    At present, the only available method to block unwanted calls is through Blocked ANI, which requires manually entering each phone number. This approach is not scalable, especially when dealing with high volumes of international spam or unwanted calls from multiple numbers within the same country or region.

    Requested Enhancement:
    Introduce a configuration option within RingCX (e.g., under Channels > Blocked ANI) that allows:

    Blocking calls by country code (e.g.,…

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