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

165 results found

  1. 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)
  2. 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)
  3. 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)
  4. 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)
  5. Problem Statement
    In the current SPOG (RingCX in RingCentral app) setup, agent presence is not fully synchronized between RingEX and RingCX.

    When a user is actively engaged in a RingEX call, their RingCX status may still appear as Available. As a result, RingCX continues to route inbound CX calls to the agent, leading to overlapping interactions and unintended call interruptions.

    This creates a conflict in blended environments where both RingEX and RingCX are actively used.

    Current Behavior

    Agent receives or is on an active RingEX call
    RingCX (SPOG) status remains Available
    RingCX continues routing inbound CX calls to the same…

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

    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)
  9. 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)
  10. 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)
  11. 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)
  12. 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)
  13. 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)
  14. 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)
  15. 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)
  16. 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)
  17. RingCX > Admin > Agent Scripts > Button > Button Configuration > Actions > Button Action: Call Control / Call Action: Cold Transfer

    We had an issue when attempting to use an agent script button to perform a cold transfer to a 10 digit RingEX phone number where the tag configuration of {{model.call.ani}} was not being respected. On the EX side, the transfer recipient would see our main RingEX phone number as opposed to the callers ANI.

    After a support ticket was opened for months, a support agent finally stated that we needed to use {{model.call.aniE164}}. This tag does not…

    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. 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)
  19. Existing functionality: RingCX can have set hours of operation at the queue level. For agents that need to log in and out of different queues throughout the day, they can log in and out manually by updating their current session or have a supervisor reassign via real time dashboard.

    Desired functionality: Allow the ability to configure what time of day an agent is allocated to specific queues. For example, Agent One should be in queues A and B from 8:00am - 11:00am, then queues B and C from 11:00am - 5:00pm. Meanwhile, Agent Two may need to be in queues…

    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)
  20. Request to enhance Priority Events in RingCX by allowing DTMF (keypad input) interaction for callers when a queue reaches defined thresholds (e.g., max queue size or wait time).

    Current Behavior:
    Priority Events currently allow actions such as routing or prioritization when thresholds are met. However, they do not support DTMF input, which limits the ability to offer interactive options (e.g., callback requests) directly within this flow.

    Problem:
    Customers who want to manage high queue volume cannot provide callers with real-time options (such as requesting a callback or leaving voicemail) when a queue is full or wait time is excessive. This…

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