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

1384 results found

  1. Currently, the RingCX agent only updates an agent's status when a voice interaction is received and not when a chat interaction is received.

    When a chat interaction is received, the status of the Agent stays in "Available" even if the "Max number of concurrent interactions" setting is set to '1'.

    This makes it difficult for Admins and Supervisors to accurately manage their agents, because this status does not change in the dashboards.

    It would make sense to simplify the status changing in the CX agent for all interactions, when the agent is engaged.

    54 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. We have a CX Queue called RPS.  On Fridays, the queue closes at about 4:30pm.  The agents log off and go home.  Sometimes there is a requested callback still waiting to happen.  The next morning, the RPS agent arrives at 6:45am for our 7:00am opening of the rehabilitation department.  The agent needs to log in to receive any calls concerning the 7am appointments, like late arrive or cancelling the appointment.  This agent then at 6:45am fields the callback that was left the previous night.  This is too early to be calling patients.  We would like that callback to start at…

    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)
  3. Issue:
    The system is not configured to check the holiday schedule, causing it to send alerts that a queue is open even when it is closed for a holiday.

    Proposed Solution:
    Add a filter option to the alert system that allows it to check the holiday schedule. This filter would prevent "queue is open" alerts from being sent on scheduled holidays, ensuring the alerts accurately reflect the operational status of the queue.

    88 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. Extension dialing between EX and CX is needed. Having to route calls between the two platforms with a 10 digit number results in the need for additional phone numbers, and cost for the customer.

    Another problem with 10 digit numbers, is that if routing is built using temporary numbers that will go away after porting, all of those references have to be updated on CX and EX after the port.

    152 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. Currently, in the RingCX Agent Interface, the Stats tab (specifically under the 'Inbound' and 'Blended' views) provides a single column for "Presented" calls. This metric is an aggregate that combines both Inbound and Outbound presented calls into one figure.

    In contrast, the RingCX Analytics Real-Time Dashboards (e.g., the People Services Dashboard) already provide a granular breakdown with separate columns for "Pres. IB" (Inbound) and "Pres. OB" (Outbound).

    This discrepancy creates a lack of visibility for agents who need to distinguish between their reactive (inbound) and proactive (outbound/manual dial) performance within their primary workspace.

    Proposed Solution
    Update the Table Settings within…

    24 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. RingCX supports last agent routing only if a call has connected to an agent previously.
    Request for a feature enhancement - include outbound dialer attempts in which a lead is calling back in after missing the call, and route to the last agent who called out to them utilizing the Route to Last Agent queue event.

    37 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. Implementing a Quality of Service (QoS) Portal in RingCX would allow visibility into whether call quality issues originate from the agent’s side or the caller’s side.

    76 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. Description:

    • Currently, when an agent's machine goes to sleep, loses network connection, or resumes after a period of inactivity, the platform automatically places the agent into the "WORKING" state. This is a default system state, and cannot be removed or reconfigured, similar to NCX.

    However, this behavior creates confusion for supervisors and admins monitoring real-time agent states. The “WORKING” label implies that the agent is actively engaged in tasks, even though they may have lost connectivity or walked away from their machine.

    Feature Request:
    • We propose introducing a more appropriate default system state for these specific conditions (e.g.,…

    124 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. Ability to see the weighted mean on Real Time Dashboards
    Currently, on the Total Row in the Real Time Dashboard, if the data is regarding Average SOA or Average Queue, it only calculates by adding the Average SOA per queue then dividing it by the total number of queues disregarding the amount of calls answered by each queue. It would be benificial to change the logic to weighted mean for data that involves average.

    15 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. Subject: Feature Request: Improve Granularity of "INTERCEPT" Call Disposition Code

    Currently, the INTERCEPT call disposition is used as a generic status for multiple distinct call failure scenarios, including invalid numbers, carrier blocks, and user rejections.

    This lack of specificity makes it difficult for administrators and end-users to quickly diagnose the root cause of a failed call. While backend codes may differentiate these events, that information is not exposed on the front end, forcing admins to perform manual investigations to understand the true outcome.

    We propose replacing the single INTERCEPT disposition with more granular and descriptive statuses that reflect the actual…

    54 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. When you are in RingCX and on a call, if you requeue a call and select stay on the call, it will put the customer on hold. Taking the customer off hold does not end the requeue and causes the agent to hear a beeping until the requeue is either successful or the call has ended. There is no option anywhere to end the requeue.
    This has been replicated on RingCentral’s internal RingCX account.

    Functionality wanted: To be able to cancel the requeue without having to fully end the call.

    41 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. RingCentral should implement a call status synchronization between the RingCentral Desktop application and RINGCX. When you are on a call using your RingCentral desktop application, this status should be reflected in real time to RINGCX preventing the RingCX app from present you an additional incoming call.

    Key Points:
    1. Real Time Status Updates: Both RingCentral Desktop and RingCX should be able to communicate real time call statuses to each other. When you answer or make a call on one platform, the other should recognized that you're on an active call.

    1. Presence Integration: Leverage the user presence feature to reflect an…

    320 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. Complete tally of all Dispositions per Agent. Please list all Dispositions in the Analytics>Historical Report>Standard>Dispositions>Agent Disposition. Currently, it is only showing the ones the agent is been using, we would like also to have the data of the ones the agent is not using.

    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)
  14. To have a settings where they can set an idle time to automatically log out RingCX agent.
    New status "Auto Logged Off" to track in reporting.
    Option to schedule log outs, e.g. in the end of the day.

    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)
  15. We would like the ability to be able to disposition a number that gets added to the DNC list, but only for a certain amount of time.

    For example, we place an OB call, and disposition it to go on the DNC list for 7 days. Once the 7days is up, the number can be called again.

    The timer will help allow for us to not have to remove numbers manually from the DNC list.

    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)
  16. Some supervisors have requested that the Realtime inbound display dashboard shows queue times in minutes and seconds (MM:SS) rather than just seconds to make viewing these at a glance simpler.

    Max Q, Avg Q etc.

    99 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. Product Area(s):

    RingCX (Contact Center)

    RingEX (Phone System / MVP)

    Call Handling & Caller ID Display

    Current Behavior:
    When an external call is routed through a RingCX queue and answered by an agent, and the agent then transfers the call to a RingEX user (via warm or blind transfer), the RingEX recipient currently sees the original external caller’s phone number as the caller ID.

    There is no visibility into which RingCX agent initiated the transfer. This can lead to confusion, lack of internal context, and inefficiencies in how the transferred call is handled.

    Requested Enhancement:
    Introduce a configurable caller ID…

    37 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. Summary
    Enable the ability to pass lead-level information from an outbound campaign when a call is transferred to an internal queue, ensuring that internal agents can view key lead details (e.g., name, date of birth, and other lead fields) during the interaction.

    Problem Statement
    When agents transfer calls from an outbound campaign to an internal queue, the lead information associated with the original outbound campaign is not consistently presented to the receiving agents. As a result, internal queue staff may not have visibility into important customer details tied to the lead record, such as name, date of birth, or other…

    9 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. Summary
    Introduce a report or dashboard view that predicts the number of outbound dial attempts expected for each campaign on a given day, based on the current lead pool and retry logic. This would provide campaign managers with a concise forecast of dialing activity per campaign and help with operational planning.

    Problem Statement
    Currently, the system provides the Next Dial Time field at the lead level, which indicates the timestamp for the next scheduled attempt based on dispositions, retry rules, and timezone settings. However, there is no aggregated view that summarizes these upcoming dial attempts at the campaign level.

    Operational…

    9 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. The problem:

    • We manage hundreds of social media channels.
    • When we run competitions, posts often get thousands of comments.
    • Most comments don’t need a reply — but sometimes a customer service–related question appears in the middle of the thread.
    • If we completely ignore a comment thread, we could miss those occasional important queries.

    The feature request:

    Allow us to “lock” a thread when we don’t need to respond further, so that if a new comment is added later, it appears as a new, separate thread — making it easier to spot and respond to.

    Why it matters:

    Without this, we…

    34 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)
← Previous 1 3 4 5 69 70
  • Don't see your idea?