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

383 results found

  1. Please add Total wrap time , total break time , total lunch time , total coaching time that are visable to agents on their stats page

    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)
  2. We would like to be able to change states actively during a call. Our Leads like to track time spent on specific parts of a call (IE. Payments / Flood Insurance ) We have several use cases where our Supervisors want agents to be able to swap mid call so that the team can actively check how long members are taking for various actions while on a call.

    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. "I see that the integration part has been added, is there any way that this could be added by us in the future so that we don't have to create a ticket"

    Description:
    Currently, when a new campaign is created and requires integration setup/configuration, customers must submit a support ticket to have the integration component added or configured.

    We would like to request an enhancement that allows Admins to independently manage and assign integrations to campaigns without requiring assistance from Support or internal teams.

    Requested Functionality:

    Allow Admin users to add, configure, or enable integrations directly within the admin portal/UI.…

    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. Title:
    Allow Admins to Disable Disconnect Scrubbing at the Account Level for RingCX Campaigns

    Description:
    Currently in RingCX, the Disconnect Scrubbing setting can only be configured at the individual Campaign level. Customers managing multiple campaigns must manually disable this setting for each campaign separately, which creates additional administrative overhead and increases the risk of inconsistent configurations.

    We would like to request an enhancement that allows Admins to manage Disconnect Scrubbing at the Account level.

    Requested Functionality:

    Introduce an Account-level setting to enable or disable Disconnect Scrubbing across all RingCX campaigns.
    Allow the account-level configuration to automatically apply to:
    Existing campaigns…

    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. Currently, when a user manually assigns an email interaction that is sitting in the queue, the system's background routing logic does not recognize the manual assignment. The interaction retains its "Queued" status, causing the system to subsequently auto-route the email to a different agent. This creates duplication of work, conflicts in ticket ownership, and inefficiencies in queue management.

    Request:

    Status Update: The interaction's status should immediately transition from "Queued" to "Assigned" (or "In Progress").

    Halt Auto-Routing: The interaction must be automatically excluded from the active routing queue so that it cannot be pushed to another agent.

    Ownership Lock: The manual…

    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. When a callback request is offered to the agent, the agent can reject or answer the call using the RingCX Agent application.

    26 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. When they make changes on agents (e.g. skills, queue). The agent still needs to update their session information.

    It would be better if the changes made to the agent be applied without updating the session information

    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. SPOG Application: The option to manually accept callback request calls when they are routed to the agent.

    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)
  9. Prevent an agent from requeing into a queue with no available agents. This helps ensuring no calls are accidentally sent to a queue with no one available to pick up the phone.

    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. Is there a way to prevent information about customer SLA breaches from appearing in the Engage Digital chat window?
    The customer has noticed that SLA breach information is being displayed, even though the agent has already responded to the chat. The customer does not want another SLA to be applied once the agent has provided an initial response.
    Currently, the system shows that the agent is breaching the customer SLA, even after responding. Ideally, another SLA should not be triggered once the agent has already replied—similar to how calls are handled. If an agent has already answered a call, it…

    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. The ability of the RC app to change its status to DND when a RingCX call comes in, so they won't receive an REX call. The same goes when receiving an RC App call to change the RCX status to Unavailable or Busy.

    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)
  12. RingCX’s default 48-hour call history window feels like trying to solve a puzzle with half the pieces missing. Once you need to review anything older than two days, you’re forced into the Reports rabbit hole (if you even have access), wasting precious minutes and leaving non-admin agents stuck. Let’s fix that by giving every user a simple dropdown or settings toggle to choose their history range: 48 hrs., 7 days, 14 days, or up to 30 days, so you can instantly pull up that crucial call from last week without a detour. This small change supercharges agent productivity (no more…

    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)
  13. 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.

    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. Customers have reported persistent background noise during calls when using the RingCX browser version. Unlike the desktop app, the browser version lacks audio settings such as noise suppression. Implementing audio controls and noise reduction features in the RingCX browser client would enhance call clarity and overall user experience.

    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)
  15. Scenario:

    When agents place outbound calls from the RingCx SPOG, they currently have access to select from all main company numbers as their Caller ID. However, based on operational requirements, each agent typically only needs access to 3 designated caller IDs corresponding to their assigned outbound calling queues.
    Request:

    We would like to request an enhancement to limit or customize the available Caller ID options per agent or per outbound queue assignment. This would help:
    Minimize selection errors,
    Streamline the outbound call process, and
    Ensure compliance with proper Caller ID usage by team.

    Please let us know if this customization…

    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)
  16. Add a new column “Average waiting Time” in the Real-time Agent view.
    This column should display, for each connected agent:

    The average waiting time of client
    Calculated on a time window consistent with real-time data
    Based on ongoing and/or recently handled interactions (same logic as other real-time KPIs)

    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: Improve the agent user experience in RingCX by providing a clearer, more intuitive option to cancel a requeue and return to the original caller before the transfer completes. While the current system allows this via the "Hangup" button and selecting "Cancel transfer," this functionality is not obvious to agents and leads to confusion and call handling issues. A dedicated "Cancel Requeue" or "Return to Caller" button during the transfer process would reduce errors, improve efficiency, and ensure agents can confidently manage live interactions without unintentionally abandoning the member.

    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)
  18. It would be really useful to have an address book in CX to store email address. Our agents frequently forward on emails so without this, it slows them down.

    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. Customers / admins should have the ability to reassign agent group assignment in RingCx. This would be more helpful since not all company have stable agents. Some are multi trained and being moved to different groups.

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

    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 2 … 5 7 9 … 19 20
  • Don't see your idea?