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

1496 results found

  1. When a caller is in the process of requesting a callback or leaving a voicemail, and an agent becomes available, the caller is left in those modules/processes instead of being routed to the agent that became available. Please add an option on a queue that controls what happens when a caller is requesting a callback or leaving a voicemail, so the queue can either be configured to:
    1) Leave the caller to continue with their original operation of requesting a callback or leaving a voicemail.
    2) Abort the original option of requesting a callback or leaving a voicemail, and route…

    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)
  2. When a caller requests a callback, they can choose to receive the callback from the originating phone number, or choose to enter a new phone number. When the caller enters a new phone number, there is a long pause before the caller hears any type of confirmation of the number the callback will occur to. This can make callers believe something has gone wrong with the callback request process, causing them to hang up prematurely. This pause should be reduced in length, or better yet, set to be a configurable value.

    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)
  3. The callback process needs additional functionality and configuration options added to make it more useful. Today the process just prompts to create a callback with the current phone number, or enter a different phone number. The callback process needs to be modified for the following:

    1) Prompt for the caller's name, as outlined in this feature request: https://ideas.ringcentral.com/forums/958496-contact-center-ringcx/suggestions/49775720-inbound-queue-callback-option-to-record-caller-s. This would at least let the agent know who they are calling back, and allow the agent to speak to an operator or navigate an auto attendant at the destination number.
    2) Enable a toggle to prompt the caller to enter…

    11 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. NICE CXone has a "Agent Timeout" setting on each unavailable code. Please add the functionality to toggle on an "Agent Timeout" for each unavailable code. When enabled, and the agent reaches the value set for the timeout, the agent would be logged out of the RingCX system. This is useful for agents that put themselves into an unavailable code like Lunch, without realizing they are taking the rest of the day off. For example, most employees take a one hour lunch break. The "Agent Timeout" for the Lunch available could would be set to 120 minutes (two hours). 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)
  5. We would like the ability for agents to answer a call from a queue that the agent or supervisor is currently not enabled to receive calls from. We have two main use cases:

    1) Support teams are organized by geographic region of the country. Support teams only have the voice queue enabled for the area of the country they serve (provide support for), but we let support teams view what is happening in other queues for call volume. If the team for Region A is receiving many calls leading to extended wait times, we'd like for agents on team that…

    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. I’d like to submit a feature request for RingCX Analytics.

    Currently, when reviewing Interaction Details for Digital SMS interactions, the ANI field displays as "N/A." For better visibility and reporting, it would be highly beneficial if the actual ANI (sending number) were displayed in this field.

    This enhancement would help teams more effectively track and analyze SMS interactions, especially when handling multiple Digital SMS numbers.

    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

    New  ·  0 comments  ·  Digital experience  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. When using the RingCX embedded agent in ServiceNow, and a outbound call is placed with click to dial, the "Name" is not populated in the RingCX agent like it is on an incoming phone call. This would provide a more consistent user experience on inbound and outbound phone calls in the RingCX agent. Additionally, it would assist in finding other open cases that that contact has right within the RingCX agent, so the user does not have to navigate back to ServiceNow to look at the contact's other open cases.

    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)
  8. We would like to request an enhancement to the Supervisor Dashboard in NICE CXone to include visibility into whether an agent has placed a call on hold, along with the status duration—similar to what is currently shown in the Realtime Dashboard.

    Current Behavior:
    The Realtime Dashboard provides clear visibility when an agent places a call on hold, including the timestamp and duration of that status. However, this information is not currently visible in the Supervisor Dashboard, limiting the supervisor's ability to monitor real-time agent behavior effectively within a single interface.

    Requested Enhancement:
    Add the following to the Supervisor Dashboard:

    1.Hold…

    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)
  9. Pediatrics Associates Family of Companies' (UID#185248027, RCX#
    31740001) ServiceNow developer's recommendation/request, after installing the RCX for SNow integration, would be for RC to expand upon their ServiceNow offering to allow for an ITSM-friendly approach for the many ServiceNow clients out there who are just leveraging ITSM and may not have CSM entitlements. I don't think it would take much heavy lifting aside from offering a system property within ServiceNow to indicate whether to leverage CSM or not to leverage CSM. Based on that flag, their softphone iframe can either display Case/Case Task or Interaction lookup capabilities. Also, instead of account,…

    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)
  10. Currently, any agent state configured on an Account will show as (empty) vs what is mapped to the underlying base state.

    We must display the states customers are expecting to see based on their account setup.

    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)
  11. In the Agent Activity report, when the filter is set to all channels, the Interactions Handled metric does not include the digital interactions handled. When the filter is set to voice channels only, the interactions handled are the same as when the filter is set to all channels. And when the filter is set to channels only, Interactions Handled and Acceptance Rate are blank.

    To check the actual digital interactions handled by agents, one must go to Digital Analytics > Activity tracking > Conversations activity.

    It would be a great feature to have a report that can show all interactions…

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

    60 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. 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)
  14. Add a native feature to display Caller ID (name and number) of waiting callers (2nd, 3rd, etc.) within the active call screen in the RingCX Agent interface.

    Current Limitation:
    Agents are currently unable to see Caller ID information for waiting calls unless they leave the active call view and manually navigate to other areas like the Analytics or Supervisor tabs. This creates a disjointed experience and impacts real-time decision-making.

    Use case:
    An agent is currently engaged in a live call. While speaking, they can glance at the interface and see the next caller waiting — “John Smith | (555) 123-4567…

    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)
  15. Make Agent States by Agent and not a global setting.

    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)
  16. Client Feedback on Current Setup:
    - The platform is not intuitive for their team, particularly compared to Gmail
    - Significant training and manual effort required to manage workflows
    - Difficult to gain team adoption due to lack of visibility and increased overhead

    Request
    - More intuitive UI/UX
    - Fewer clicks to perform routine actions (assignment, visibility, filtering)
    - A faster learning curve for new agents

    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)
  17. Current Setup:
    - Only a single basic search bar and limited filter options are available
    - No status indicators (read/unread, responded/unresponded) at-a-glance
    - No quick summary or icons to show assignment or engagement status unless each message is clicked individually

    Request:
    - Easily search email content by name, order number, or keywords
    - Filter messages by response status (read/unread, new/engaged)
    - Allow shift-based filtering (e.g., emails received from midnight–10 AM)

    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)

    Read/Unread by customer or agent?

    For agent: in a collaborative settings, just opening the email, doesn't mean much, the point is to be assigned on the email.

    For responded/unresponded: status_in: New or Replied

    please provide more details what and why is needed for searching, what objective it achieves.

  18. Current Setup:
    - A 12-month thread inclusion is set up, however, new threads are still generated upon recontact
    - Conversations are being stored in separate threads, creating a fragmented customer history

    Request:
    - True conversation threading based on customer email address or ticket ID
    - Ensure replies from customers within a set period are appended to the original thread regardless of closed status
    - Reopened conversations (e.g. customer replies after closure) should rejoin the original thread, not create a new one

    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)
  19. Current Setup:
    - No role-based restriction available for view-only access to digital queues
    - Email Assignment via automatic routing or manual assignment by Supervisors

    Request:
    - Viewing permissions and view email communications without being assigned or able to respond
    - Visibility into email threads by all agents without compromising interaction ownership
    - Auto-assignment by time-slot or agent shift

    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)
  20. Agents using RingCX Engage Digital currently have no control over the system notification sounds, leading to missed or inaudible alerts especially for high-priority events like new interactions or interaction updates. We propose introducing configurable sound notifications per user, similar to what is available in the RingCentral App (RingEX) for message alerts.

    Proposed Functionality

    1. Customizable Notification Profiles (Per Agent): Agents can choose from a preloaded list of sounds (chimes, beeps, alerts, etc.) for: New interaction; Interaction activity (e.g., customer reply, supervisor note); System alerts (e.g., disconnection, transfer, timeout).

    2. Sound Settings Location: Accessible under Agent Settings > Notifications; Options to preview the…

    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

    New  ·  1 comment  ·  Digital experience  ·  Admin →
    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?