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

363 results found

  1. The customer would like the historical call view in Agent RingCX to display call results differently—for example, using different text colors for successful calls versus missed calls (RNA). They would also like the ability to filter call history by All Calls, Missed Calls, Incoming Calls, and Outgoing Calls, similar to what is available in RingEX.

    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)
  2. When agents make internal calls on the SPOG, their caller ID shows the RingCX caller ID Setup. It would be helpful if the system preserved the agent’s actual Extension as caller ID so colleagues can easily recognize who is calling.

    16 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. Configurable alert to the agent based on time in call.

    We have an guideline for our agents of approximately how long they should be on a call, would be nice if a supervisor/admin could set an alert for an agent or groups of agents. So if an agent is on a call for X minutes, they get a pop-up alert on the screen, or ideally a separate pop-up window in case they've switched focus to another system, letting them know they should consider escalating the call to a higher level.

    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. Enable RingEX Receptionist to preserve the original caller's number (Originating Caller ID) when transferring calls to RingCX.

    Current behavior:
    When a call is transferred from RingEX to RingCX, the original caller’s number is not retained. Instead, RingCX displays the Caller ID of the RingEX user who performed the transfer.

    20 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. If an agent is initially unavailable and receives an internal call or makes an outbound call, do not automatically change agent status to Available once the call is over.

    44 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. The customer does not want users to access or connect to the Agent icon or SPOG when they are logged into their RingCentral application. However, some users are still attempting to connect to SPOG/RingCX through the Agent icon.

    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)
  7. Description
    In the RingCX SPOG App, when users initiate a call transfer and search for a contact, the system currently returns only 10 results.

    This limitation makes it difficult for agents to locate the correct contact, particularly in environments with large directories or when contacts have similar names.

    Steps to Reproduce
    1. Initiate or receive a call
    2. Attempt to transfer the call
    3. Use the contact search function
    4. Observe that only 10 contacts are returned, even when more matches exist

    Actual Result
    Search results are limited to 10 contacts.

    Expected Result
    Search should return more results (e.g., 50–100)…

    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)
  8. RingCX currently does not provide live closed captioning or real‑time transcription visibility for agents handling voice calls in the RingCentral desktop app. This creates a meaningful accessibility gap, especially given that live captions are available in RingEX and that RingCX already performs real‑time transcription behind the scenes for analytics and AI features.
    This appears to be a product parity and accessibility issue, not a technical limitation.

    Why This Matters
    Live closed captioning is a recognized accessibility accommodation, not merely a convenience feature. Its absence in RingCX directly impacts:

    Deaf or hard‑of‑hearing agents
    Agents with auditory processing disorders
    Neurodivergent agents who…

    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. Hi Team,

    I am submitting a high-impact Feature Request on behalf of a RingCX customer who manages a high-volume Customer Service Representative (CSR) team.

    Customer Use Case & Workflow
    The customer’s team frequently handles multi-purpose interactions where a single customer call covers multiple distinct topics (e.g., spending the first few minutes on a billing dispute, then transitioning to processing a payment).

    The customer wants supervisors to be able to monitor exactly what an agent's current call is about in real time and track how long they spend on each specific task within that single live interaction.

    Proposed Feature / Ideal…

    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)
  10. I would really appreciate having more theme options, as this is the primary platform I use throughout the day, and it is nice being able to change things up. Especially, since I am prone to migraines and so are some members of my team, and there are limited options for both light and dark modes.

    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)
  11. Currently, when a customer sends a PDF file via digital channels, agents are forced to download the file locally to their machine every time they need to view it. This creates unnecessary friction in the agent workflow, clutters local storage, and can introduce potential security compliance risks depending on the data handling policies of the organization.

    I would like to suggest adding a built-in PDF previewer directly inside the RingCX workspace.

    If that is not possible, I'd like to have the option for a "Save as" dialog box to open so we can select to open the file instead of…

    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)
  12. Customer Request:
    Allow agents to access and review their call history for at least the previous 7 days.

    Current Behavior:
    There is currently a product limitation on the available agent call history period, and administrators do not have an option to extend the agent call history view to 7 days.

    Customer Requirement:
    The customer would like agents to be able to review their historical calls from the previous 7 days for operational and call review purposes.

    Business Use Case:
    Agents may need to review previous calls to identify specific customer interactions, verify call activity, reference previous conversations, or assist with…

    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)
  13. When a call comes through the ability to allow the ring tone to come through the laptop audio as well as the headset audio should be allowed to allow agents to hear a call coming through even if they do not have their headset on at the time a call is coming in so they can be alerted.

    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)
  14. Request:
    Please consider adding support for reliable Canada-to-Canada call transfers without requiring the use of a non-Canadian caller ID or a Canadian carrier workaround.

    Customer Impact:
    The customer reports that Canada-to-Canada transfers previously worked but are now inconsistent, with some transfers completing successfully while others fail. This is impacting their ability to reliably transfer calls to external Canadian numbers and has raised significant concerns about the viability of the service.

    Requested Enhancement:
    Provide a supported and reliable routing solution for Canada-to-Canada call transfers, regardless of whether the destination is another RingCentral customer, while maintaining the appropriate Canadian caller ID and…

    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)
  15. We have last agent routing for Voice Queues, but it would be very helpful to have this for digital queues as well. Example:
    A customer responds to an email thread a couple of days later, but the original agent had closed the interaction due to lack of response or the interaction had timed out. Since the original agent had been working the email thread directly, we should have the option to attempt to route the interaction to them first.

    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. Problem Description:
    RingCX currently does not automatically change an agent's state from the configured post-call state (such as ACW) to Available after the configured Wrap Time has elapsed.

    Current Behavior:
    Wrap Time only determines how long before another call can be presented to the agent after the previous call has ended. It does not automatically transition the agent's state to Available.

    For example, if Wrap Time is set to 30 seconds and the post-call state is ACW, the agent remains in ACW after the 30 seconds have elapsed unless they manually change their state to Available.

    Expected Behavior / Feature…

    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. Request:
    Please submit a feature enhancement to prevent incoming CX queue calls from being presented to an agent who is already engaged in an active EX call.

    Current Behavior:
    When an agent is on an active EX call and an incoming CX queue call is received, the CX call may interrupt the ongoing call, place the active call on hold, and cause the agent's status to change to RNA.

    Requested Behavior:
    When an agent is already engaged in an active EX call, incoming CX queue calls should be blocked or prevented from being offered to that agent until the agent…

    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. Problem:
    Previous provider would allow a certain wrap-up time before putting agents back into availability using a ""wrap-up"" code, not available code. Supervisors see multiple people in available but calls queuing, as the current setup shows agents as ""available"" when they're actually in their wrap up time.

    The feature request:
    Wrap-up time allowance, which then puts the agent back to available after the countdown. At a queue level, theres a ""Wrap time"" at a queue level, but it shows agents as available to supervisors which is misleading when managing a large amount of people and queues.

    Why it matters:
    This…

    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)
  19. For incoming calls into CX, can it automatically pull the CNAM and put it as the Caller Name when the call pops?

    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. Problem Description
    When a RingCX agent (Party A) places a manual outbound call to Party B, then adds Party C to create a 3-way conference (Agent + Party B + Party C), if the agent (Party A) disconnects, the entire conference call is dropped for all participants (Party B and Party C).


    Expected Behavior
    If the agent (Party A) disconnects from a 3-way conference, the call should continue between Party B and Party C. This is expected in standard call conferencing logic where the initiator disconnecting does not necessarily terminate the call for all participants.

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