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

290 results found

  1. SMS Delayed Send allows users to compose a message and choose a specific date and time for it to be sent automatically, rather than delivering it instantly.
    This feature gives teams more control, consistency, and professionalism in how they communicate—especially in time-sensitive or customer-facing operations.

    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)
  2. 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)
  3. We need an enhancement to our call‑handling interface that adds a real‑time hold‑duration timer for agents. Currently, agents can see the total call time but cannot see how long a caller has been on hold, leading to compliance gaps, inconsistent customer experience, and unintentionally long hold times. I would like to request A secondary timer that: Displays real‑time hold duration (HH:MM:SS) Resets each time hold is removed Remains visible at all times If possible, and alerts agent when hold exceeds a set threshold

    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)
  4. Subject: Feature Request: Add Filter for “Has Coaching Moment” in RingSense

    Hi Team,

    I’d like to submit a feature request related to RingSense analytics and call review capabilities.

    Request:
    Add a filter option for “Has Coaching Moment” within RingSense so users can easily locate calls that contain coaching moments, even if no scorecards or feedback were set up at the time the calls were recorded.

    Customer Need:
    Some customers have historical calls that include coaching moments generated before managers were fully trained or before scorecards were configured. Currently, there is no UI filter available for them to pull or isolate…

    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)
  5. CX users have the EX dialpad populating when selecting the dialpad. This is creating a discrepancy with their CX functionality and reporting of outbound calls. The call detail is capturing in their EX history instead of in their CX history, and the associated reporting in CX is not capturing the details. Desired functionality is that if the user is in CX mode, the only dialpad that will populate is the CX dialpad. Seems this is occurring when disposition window is open and dial pad is selected, and/or if disposition is not selected and subsequent outbound call is attempted.

    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)
  6. Write back Disposition and notes to RCX Contact Card

    Enterprise Account ID: UID: 813377035
    Feature Request Summary: Write back Disposition and notes to RCX Contact Card
    Current Functionality: only support AI Summaries
    Ideal Functionality: Write back Disposition and notes to RCX Contact Card
    Opp Link: SFDC Opp Link: https://rc.lightning.force.com/lightning/r/Opportunity/006TU00000Eg3B7YAJ/view

    Business Justification -- Since we dont support all integration this willl help the agent identify the last reason for call aside from AI Summaries

    https://jira.ringcentral.com/browse/INIT-25003

    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)
    1. Additional details for the feature that you are requesting:
    2. What is your use case for this feature request? Agents with multiple roles leave their desk throughout the day.
    3. What problem are you trying to solve or what problems does the current functionality cause? If agents forget to check status they do not receive calls when needed.
    4. How do you want the feature/product to work (proposed solution)? Have a setting in the Agent Roles or Queue general settings to disable the RNA status and/or set a timer.
    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)
  7. At the moment, agents show as "Available" even though they are handling digital contacts. We would like to request a feature to show the digital state of agents in the supervisor page and analytics.

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

    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. We would like to see an option to only "require" Dispositions/Notes/Scripts for Inbound calls only. Current situation is that a script runs with required categories to populate, this is appropriate for inbound calls, but not outbound calls. If there could be an option to decide what direction the call is for a requirement that would solve this, or an ability to create a custom rule to circumvent the requirement.

    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. It would be extremely valuable for RingCX alert notifications to be pushed directly into Microsoft Teams chats and channels via a native integration.

    Currently, the workaround requires:
    Alert → Email → Power Automate → Microsoft Teams

    This introduces unnecessary complexity, additional maintenance, and potential points of failure.

    A native Teams integration would:

    • Reduce technical overhead

    • Improve reliability and speed of alert delivery

    • Eliminate dependency on third-party automation tools

    • Increase adoption of real-time operational alerts

    Ideally, this would allow alerts to be sent to:

    • Individual user chats

    • Group chats

    • Specific Teams channels

    This would significantly strengthen real-time operational visibility for supervisors…

    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. In order to allow our agents working in shared contexts to prepare for their calls, we would like to be able to set a delay for automatic call response in RingCX or SPOG.

    The two main objectives are as follows:
    - to make the agent's work less “oppressive”;
    - to allow the agent to prepare to welcome the user.

    Ideally, we would like to have the same configuration as that available on RingEX, with the queue name displayed in advance and a countdown timer showing the time remaining before the call is automatically answered.

    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. Chat and email interactions should not include the agent's last name for their safety. This is true in the actual interactions occurring real-time, and in any subsequent transcripts. Please provide an option that allows agent profiles to include their full name, however that also allows an option to remove their last name from customer facing interactions, reports and transcripts

    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. Create a Supervisor Security setting to restrict changes to Queue SLA settings by Supervisors

    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)
  14. Description/Business Use Case:

    Currently, RingCX users (specifically Agents working from home) who attempt to view a Live Wallboard while simultaneously logged into the Agent Interface experience session token conflicts. This occurs because modern browsers share a single "cookie jar" per domain.

    When a refresh token for a Wallboard login is processed, it can overwrite the Agent’s digital messaging token, causing the "Messages" function to intermittently disappear.

    Requested Change:

    Enhance the RingCX authentication architecture to allow for isolated session tokens. This would enable a single browser profile to maintain both an Agent session and a Wallboard/Admin session concurrently without credential crosstalk…

    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 would like to request for a feature that allow agents to handle multiple calls simultaneously.

    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. *Summary

    Introduce a platform-level capability to enforce conditional Caller ID behavior for internal calls during warm transfers and consultations, ensuring consistent Caller ID presentation across RingCX and RingEX environments.

    *Problem Statement

    During warm transfers or consult calls—whether between RingCX agents or from RingCX to RingEX users—Caller ID presentation may vary and display RingEX Born Super Admin name, queue numbers, site numbers, or system-generated identifiers. This inconsistency creates confusion during internal collaboration. However, once a call is fully transferred or taken over, the receiving party must see the original customer identity to preserve service continuity.

    *Proposed Capability

    Implement call-state–aware Caller ID…

    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)
  17. Requested Enhancements:
    Rich Text / Formatting Support
    Allow basic formatting in case descriptions and replies, including:
    Bullet points and numbered lists
    Paragraph spacing
    Bold / italics / headings
    Inline code or monospaced text (where relevant)

    This would significantly improve clarity when describing technical issues, test results, timelines, or step-by-step findings.

    Ability to Add External or Internal Parties to the Case Thread
    Enable customers to:
    Add additional participants (e.g. colleagues, partners, or vendors) to the case communication thread
    CC or notify relevant stakeholders without forwarding emails manually
    Maintain a single, auditable communication trail within the case
    Improved Communication Chain Visibility
    Ensure…

    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)
  18. Feature Request: “Mask Audio” Button in RingCX Dialer

    Title:
    Add a “Mask” button in the RingCX Dialer to temporarily hide or block sensitive audio from being recorded or monitored.

    Description:
    Agents occasionally need to capture sensitive customer information (e.g., credit card numbers, SSNs, or account verification data). Currently, RingCX records the entire call without a built-in way to exclude these segments.

    We propose adding a “Mask” button directly in the RingCX Dialer interface, allowing agents to manually pause or mask the call audio.

    When the agent activates the Mask button:

    Recording and monitoring streams are replaced with white noise, silence,…

    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)
  19. We should have the ability to view only the agents that we need to in the real-time Agent Dashboard. Currently, you have to view all agents, and when your organization has A LOT of agents, that is a lot of scrolling and hunting to find the agents you need to see. I would think it should be easy to implement a drop-down menu showing all the RingCX queues, and you should be able to just select the queue(s) you want to monitor.

    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?