Skip to content

JUMP TO ANOTHER FORUM

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

1319 results found

  1. Issue:
    The system is not configured to check the holiday schedule, causing it to send alerts that a queue is open even when it is closed for a holiday.

    Proposed Solution:
    Add a filter option to the alert system that allows it to check the holiday schedule. This filter would prevent "queue is open" alerts from being sent on scheduled holidays, ensuring the alerts accurately reflect the operational status of the queue.

    85 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. Extension dialing between EX and CX is needed. Having to route calls between the two platforms with a 10 digit number results in the need for additional phone numbers, and cost for the customer.

    Another problem with 10 digit numbers, is that if routing is built using temporary numbers that will go away after porting, all of those references have to be updated on CX and EX after the port.

    143 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. Currently, the RingCX agent only updates an agent's status when a voice interaction is received and not when a chat interaction is received.

    When a chat interaction is received, the status of the Agent stays in "Available" even if the "Max number of concurrent interactions" setting is set to '1'.

    This makes it difficult for Admins and Supervisors to accurately manage their agents, because this status does not change in the dashboards.

    It would make sense to simplify the status changing in the CX agent for all interactions, when the agent is engaged.

    28 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)
  4. RingCX supports last agent routing only if a call has connected to an agent previously.
    Request for a feature enhancement - include outbound dialer attempts in which a lead is calling back in after missing the call, and route to the last agent who called out to them utilizing the Route to Last Agent queue event.

    34 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. Implementing a Quality of Service (QoS) Portal in RingCX would allow visibility into whether call quality issues originate from the agent’s side or the caller’s side.

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

    113 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 implement a call status synchronization between the RingCentral Desktop application and RINGCX. When you are on a call using your RingCentral desktop application, this status should be reflected in real time to RINGCX preventing the RingCX app from present you an additional incoming call.

    Key Points:
    1. Real Time Status Updates: Both RingCentral Desktop and RingCX should be able to communicate real time call statuses to each other. When you answer or make a call on one platform, the other should recognized that you're on an active call.

    1. Presence Integration: Leverage the user presence feature to reflect an…

    306 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. When you are in RingCX and on a call, if you requeue a call and select stay on the call, it will put the customer on hold. Taking the customer off hold does not end the requeue and causes the agent to hear a beeping until the requeue is either successful or the call has ended. There is no option anywhere to end the requeue.
    This has been replicated on RingCentral’s internal RingCX account.

    Functionality wanted: To be able to cancel the requeue without having to fully end the call.

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

    43 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. Some supervisors have requested that the Realtime inbound display dashboard shows queue times in minutes and seconds (MM:SS) rather than just seconds to make viewing these at a glance simpler.

    Max Q, Avg Q etc.

    98 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. The problem:

    • We manage hundreds of social media channels.
    • When we run competitions, posts often get thousands of comments.
    • Most comments don’t need a reply — but sometimes a customer service–related question appears in the middle of the thread.
    • If we completely ignore a comment thread, we could miss those occasional important queries.

    The feature request:

    Allow us to “lock” a thread when we don’t need to respond further, so that if a new comment is added later, it appears as a new, separate thread — making it easier to spot and respond to.

    Why it matters:

    Without this, we…

    33 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. Complete tally of all Dispositions per Agent. Please list all Dispositions in the Analytics>Historical Report>Standard>Dispositions>Agent Disposition. Currently, it is only showing the ones the agent is been using, we would like also to have the data of the ones the agent is not using.

    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)
  13. To enable the ability to transfer calls via the corporate directory using RingEX extension numbers instead of typing the user's name and selecting it from the list.

    Currently, the system does not recognize extension numbers when attempting to transfer a call. It only displays results when typing the name of the user or agent.

    59 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:

    Currently, in RingCX, the only way to enable Call Monitoring/Listening functionality is by changing an Agent's role to Supervisor. However, this creates a significant data visibility issue, as it grants Supervisors access to queues and information beyond their designated team or group, which may include sensitive data from other departments or companies.

    Request:

    We would like to request the implementation of a granular permission setting that allows users with the Agent role to be granted Call Monitoring privileges for a specific group of agents or queues only, without the need to elevate them to a Supervisor role.

    Proposed Solution…

    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)
  15. When an agent goes to requeue a call they get a list of queues available. While there is a search field at the top to type in the name of the queue you are looking for it does not actually perform a search. The agent must scroll down through the list of queues find the one they are looking for. In order to improve agent efficiencies making this truly searchable would be greatly beneficial.

    14 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. Currently, permissions for requeue and cross-queue requeue are managed at the agent level. We are requesting an enhancement to migrate these settings to the queue level.

    This change would provide greater granularity by allowing us to define permissions based on the specific requirements of a queue. This would enable agents to requeue calls on certain queues while being restricted on others, which is essential for improving operational flexibility and security governance.

    14 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. Meta released the Cloud API Calling allowing user to call companies through WhatsApp. Companies have to be registered as WhatsApp business
    https://developers.facebook.com/docs/whatsapp/cloud-api/calling
    This "API" was on beta in Brazil, Indonesia,etc. It is now globally available.
    It is a highly requested feature, due to the public availability on WhatsApp.
    It is important to associate this idea to another one "outbound whatsapp with RCX UI" https://ideas.ringcentral.com/forums/966594-ringcx/suggestions/48515087-outbound-whatsapp-within-rcx-agent-ui
    it will allow to send messages directly to a customer while on call. (in this case, template are not required)
    user initiated calls to business are free and there is a cost for business initiated. The…

    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)
  18. Within digital interactions it is not clear when agents have requeued interactions when looking at thread audit logs. This needs to be clear for agent management.

    Alongside this it is best practice to show which queue the interaction is in as large accounts such as ours have close to 100 queues to manage. Currently, all we can see is that the interaction has moved to 'triage queue' with no insight into which queue that is.

    10 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  ·  2 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)
  19. Allow user to pop chat window out, incase they need to navigate away from the current window.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Add Opt-In Surveys at Call Start, Auto-Prompted at Call End

    As a head of a centralized call center with agents that support multiple businesses and call queues, I’d love to see RingCentral add a simple but powerful feature:

    When a customer calls in, they could press a key at the beginning of the call to opt-in to a quick survey. After the agent disconnects, the system would automatically play the survey.

    Here’s why it matters:
    - Seamless customer experience: No agent involvement, no awkward “Would you like to stay on the line?” interruptions.
    - Accurate feedback: Surveys are tied directly…

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
← Previous 1 3 4 5 65 66
  • Don't see your idea?