Skip to content

JUMP TO ANOTHER FORUM

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

1180 results found

  1. The Issue:
    Right now, when agents log out and back in, the system defaults to showing the RingCX caller ID. This is how it’s designed, but it means agents have to remember to switch to their RingEX extension before making a call if they want their extension to show. It’s easy to forget and leads to the wrong caller ID being used.

    Suggested Feature:
    Make the system automatically pick the right caller ID based on the kind of call:

    If it’s a call from a RingCX queue, show the queue or company main number.

    If it’s an internal call (extension…

    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. Currently, a RingCX admin can only modify and delete Historical Report Schedules that they own.

    I would like to suggest a feature enhancement to allow an admin to delete any Historical Report Schedule, regardless of ownership. This is particularly useful for Historical Report Schedules no longer owned by off-boarded admins or users whose admin access has been revoked.

    This capability can also be important if a situation arises where an employee is absent from the business due to unforeseen circumstances and the schedule needs to be modified, disabled, or deleted. Furthermore, if an admin is deleted, the schedule will show…

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

    42 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. Description:

    • Currently, when an agent's machine goes to sleep, loses network connection, or resumes after a period of inactivity, the platform automatically places the agent into the "WORKING" state. This is a default system state, and cannot be removed or reconfigured, similar to NCX.

    However, this behavior creates confusion for supervisors and admins monitoring real-time agent states. The “WORKING” label implies that the agent is actively engaged in tasks, even though they may have lost connectivity or walked away from their machine.

    Feature Request:
    • We propose introducing a more appropriate default system state for these specific conditions (e.g.,…

    101 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 a caller requests a callback but doesn't confirm the caller ID, RingCX will not be able to process the callback request.
    This shows in RingCX Analytics as Callback Interactions Unaccepted (Call Result of Inbound ACD Queue Callback Incomplete). This definition would show that the system tried to initiate the callback but was not answered where as it was not actually triggered.
    Suggest to expand the Callback results to include more granular scenarios such as
    "Inbound ACD Callback Unconfirmed CallerID"
    "Inbound ACD Callback Duplicate Request"
    This will allow contact centres to have a significantly better understanding if they are accurately…

    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

    Under Review  ·  0 comments  ·  Other  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Ability to add the ability to specify a particular area code when setting up or managing the Local Connect Bucket? This feature would help in targeting specific geographical regions more effectively.

    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)
  7. RingCentral should add robocall filtering to CX. I was told it happens on the EX side, but it's not happening in CX. We're getting robocalls that hang up right after they are dropped into our queue, and that's causing our abandoned rate to spike.

    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)
  8. We have a Central Office and many Satellite Sites, we need to enable a few specific staff members to be able to set their CallerID to any of the Satellite Sites, at the moment this is a site by site feature and needs to be a user feature.

    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)
  9. 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)
  10. Additionally, the customer requested the following feature:

    If a broadcast-detected live answer is routed to an agent, and the agent fails to answer,

    They want the call to be automatically forwarded to a RingEX AI Agent (or another fallback destination), instead of being missed entirely.

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

    I'd like to submit a feature request regarding enhancements to the Broadcasting functionality in RingCX.

    1. DTMF/IVR Option After Recorded Message The customer would like the ability for contacts to interact with the system after a live answer broadcast. Specifically:

    Once the recorded message plays (e.g., "If you want to speak with an agent, press 1, otherwise hang up"),

    The system should allow the contact to press a DTMF key (e.g., 1) to be routed to an IVR or queue.

    Upon reviewing the current Campaign > Sales > General Settings > Live Answer options, we confirmed that:

    This functionality…

    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. Increase the attachment limit for the customer and their clients to attach files more than MB

    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)
  13. The RingCX audit log fails to capture details regarding digital queue events (ChatQueueEvent) and their associated queues. As a result, we cannot determine which digital queue was involved when an event was created, updated, or deleted.

    This lack of information prevents administrators from quickly understanding where and what changes were made. The challenge becomes more significant when dealing with multiple queues and hinders our ability to restore previous states if a queue event is inadvertently deleted or modified by an administrator

    While queue details are captured for voice queue events (GateQueueEvents), we urgently need the same level of detail to…

    24 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

    Planned  ·  1 comment  ·  Admin 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)
  14. When caller is on hold by the agent, RingCX will be able to notify both agent and supervisor about the ongoing hold duration that can be set on the hold settings.
    Notification that can be configured as pop up or email.

    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)
    • When logging in, agent has visibility to all queues and they have to unclick all markets queues that not assigned to so only see the ones actually assigned to
    • Don't want to take away the ability to access all the other market area queues (example: FL dispatchers don't have internet due to hurricane, need to be able to select the FL queues to help them out)
    • By default only see the queues the agents are assigned to
    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. All deflected calls to be presented on the dashboard with details of calls (driver name and telephone number)
    Feature request - Feature modification of existing abandoned campaign mapping to fit the ask

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

    31 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. Whenever an agent transfers the digital interaction to another queue, the category does not automatically change with the associated queue. Therefore, if a customer replies to the thread, the interaction is routed back to the last assigned queue instead of the transferred queue.

    Use Case:
    1. The customer selects the incorrect queue (Customer Service).
    2. Customer Service transfers the interaction to the Sales queue.
    3. The Sales agent ends the conversation.
    4. The customer replies to the same thread.
    5. The interaction is routed back to Customer Service.

    Desired Behavior: The interaction should be routed back to the Sales queue…

    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)
  18. Addition of a Spam Detection feature to chat channel. This feature will help identify and filter out unwanted or malicious content from users, ensuring a safer and more pleasant experience for all participants. The system should be capable of detecting spam messages such as repeated text, irrelevant links, offensive language, and other behaviors that typically indicate spam.

    27 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 need to be able to separate CIDS in Outbound caller ID by client so we can have agents working for one client not see or be able to pick caller Ids for another client when doing manual calling

    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

    Under Review  ·  0 comments  ·  Other  ·  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?