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

165 results found

  1. Make a way to automatically block Robocalls from different numbers without manually adding them to the Blocked ANI List

    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)
  2. 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)
  3. 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)
  4. 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)
  5. 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)
  6. 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)
  7. 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)
  8. on the call queue, we have 2 direct numbers, we want to generate a report like how many number of calls came in on each of those direct number, because only option here is for the whole call queue.

    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)
  9. Expand on the "Cross queue requeue" setting to allow agents to requeue calls to ALL queues not just queues they are assigned to.

    8 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. Please allow inbound queue call back requests to play "This call is being recorded for quality and training purposes" on caller's end whenever the system triggers an outbound call for an agent

    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. The customer requested that there must be an option to copy the template from his existing workflow from one RingCentral account to another. So they could save more time when creating a workflow.

    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)
  12. To allow warm transfer calls from RingEX users to RingCX agents. Currently, it only works with Cold transfers.

    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)
  13. It would be nice to have an option to ring all agents simultaneously under a Call Queue. This would:

    • Provide the possibility of a shorter wait time for callers
    • Avoid caller abandons
    • Help in user data analyzation on who picks up the most/least calls

    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)
  14. Significantly improve the RingCX callback in queue experience for callers. Here's a breakdown of the issues and how to address them, focusing on making the text-to-speech (TTS) more natural:

    Key Issues Identified:

    Mixed Gender Voices: The callback message currently starts with a male voice and switches to a female voice. This can be jarring and unprofessional.
    Outdated/Robotic Text-to-Speech: The TTS used to read and verify the phone number sounds old and unnatural, which negatively impacts the caller experience.
    Solutions and Recommendations:

    1. Unify and Improve Voice Consistency:

    Custom Audio Recordings: The most direct way to ensure consistent and natural-sounding voices is…

    13 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. Incoming caller ID within Canada only shows phone number and location but not caller name (CNAM) it would be good to have the CNAM displayed.

    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. We have an opportunity to improve agent efficiency for bilingual (or other) accounts by reconfiguring the call-display hierarchy. Currently, the Caller ID dominates the interface, but for this client, the 'To:' field (Language Indicator) is the higher-priority data point. I propose we allow for a dynamic display toggle that allows the customer to elevate the 'To:' title to the primary position, ensuring agents can instantly identify the required language before even answering the call.

    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. It would be helpful for our customers to have an option to setup a temporary greeting without creating a new workflow or adjusting their current workflow.

    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. Enhancement suggestion for the "Route to Last Agent" (LCA) functionality in voice queue events.

    Current Behaviour: The current LCA queue event employs a strict policy, exclusively routing a call to the last-contacted agent. A key issue arises when this agent is unavailable (e.g., busy, away, or offline), as the call remains queued for the event's duration. This results in preventable delays and extended customer wait times.

    Suggested Improvement: The LCA functionality should be enhanced to be more flexible. It should still first attempt to route the call to the last-contacted agent; however, if that agent is unavailable, the system should…

    8 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. One of my queues behaviors is to have a call send over to another workflow if no agents are available or if the queue is closed. It supposed to play a warm message then send the call over. In my test environment, it never plays the message and just cold transfers the call over to the workflow.

    We need to have the ability within the queue event to have prioritize a behavior. I want to make sure an audio plays before it does the expected main queue event behavior. I can add a separate queue audio event before i send…

    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)
  20. Currently, the only possibility is to add a priority event No Agents Signed In that will requeue calls to another queue when agents are not signed in to the queue. However, it would be interesting to add a new event based on the agents' busyness/availability on the queue.

    Expected behavior:
    If all agents are busy with other calls, new calls should not be waiting in the queue for the next available agent. What we need is for this call to be requeued to another queue

    We used the Max Queued Calls and tried setting it to 1 but if agents…

    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?