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

319 results found

  1. Customer is using SPoG and an agent script to present the IB call's Queue Name when call is connected. They don't want their agents to know what IB Queue calls are ringing and prefer to intentionally NOT disclose the IB queue name in the SPoG visual IB call notification. Agents are in a Sales group and answer calls for Home and Auto Sales and want these queue names to be discreet until the agent is connected.

    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. Add "Not Live Person" flag and option for pre-recorded message for Manual calls.
    In disposition this is not available now and only available in the auto dialer outbound calls.

    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)
  3. the Agent Disposition Notes field is present in order to complete call disposition. With the ability for agents to now edit and update the Summary field, this requirement often results in duplicated information and increased after-call work.
    We understand that the Agent Disposition Notes field is a core product design element and cannot currently be disabled at the account level. However, for many customers, the Summary field is sufficient—and preferred—for capturing call outcomes and context.
    Requested enhancement:
    Add an account-level configuration option that allows customers to disable the Agent Disposition Notes field, enabling teams to rely solely on the Summary…

    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. Aligning the REX interface with the RCX layout is essential for operational consistency. Having a uniform design minimizes the learning curve for supervisors and reduces navigation errors when switching between platforms.

    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. When transferring a call, and clicking the Ask First button, the system creates a blind conference call with the caller still on the line.

    Expected behavior is to put the caller on hold, while the agent speaks with the person to which they are trying to transfer the call.

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

    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)
  7. We would like to implement a feature in RingCX that prevents our agents from muting any ongoing interactions. This option should ensure that all communications remain audible and transparent, thereby enhancing accountability and ensuring that all parties are fully engaged in the conversation. This could help minimize misunderstandings and promote a higher level of service quality.

    0 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. 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. Display a message to the agent informing that a call is part from a callback campaign.

    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. Feature Request Documentation

    Customer statement:
    We had some agents who wanted to have the incoming call/email notifications to play over their speakers but have all other audio play into their headset.

    Requested functionality:

    Ability to separate notification audio (ring tones, alerts for calls or emails) from regular media/audio (calls, music, system sounds).

    Notification audio should be configurable to play through device speakers, while regular call/audio continues through headset.

    Use case / rationale:

    Agents can be notified of incoming calls or messages without removing their headset or interrupting ongoing work.

    Helps improve awareness of incoming communications while maintaining audio privacy 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)
    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)
  11. 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)
  12. Allow the ability to control the call recording of the supervisor when they barge in, Monitor, and take over the call regardless of the call recording settings of the Voice Queue.

    Currently when the supervisor takes over the call the call recording stops if the Voice Queue call recording settings is set to Do Not Record On transfer.

    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)
  13. 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)
  14. An option and/or default behaviour being to auto-hold the external caller / customer when an agent initiates a warm transfer / three-way call to a user on the REX system?

    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. Ensure RingCX search behavior and UI visibility is consistent with RingEX UI behavior for lookups
    Investigate whether the RingCX search result display can be improved (e.g., visual indicator for scrollable content or removal of the result limit).
    If not currently supported, please escalate as a feature request to address search usability and parity.

    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)
  16. 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)
  17. 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)
  18. 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)
  19. 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)
  • Don't see your idea?