Skip to content

JUMP TO ANOTHER FORUM

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

225 results found

  1. Currently; the "Internal" transfer tab results would be utilized to transfer an RCX call to another RCX agent who is logged in to the platform. The "Corporate Directory" transfer tab results would be utilized to transfer an RCX call to a users REX ext.

    The overall ask is to have there be a global directory that shows all results together, rather than have the separation of these results between multiple transfer tab types (Internal Transfer and Corporate Directory being two examples)

    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, REX CNAM settings can override the CNAM showing for REX users, which is typically intentional from a global level to do this; however, some customers have internal support queues that are meant to help users calling from REX to RCX, but the CNAM shows what's configured in REX.

    The goal here would be for the system to recognize an internal caller and display their extension/user info instead of the REX CNAM input for the Main Site.

    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)
  3. When agent makes a manual outbound call, agent needs to be reverted back to an agent's previous state before the manual call was made

    19 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. Internal Chat (ex. from supervisor to agent) inside RingCX. An internal chat can help to solve complex use case and enable multiple advantage:
    - ability for agent to ask for help proactively to their supervisor.
    - ability for supervisor to get involved in a less intrusive way.

    The internal chat developped for Engage Digital standalone is probably very close to what the this potential partner would like.

    39 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)

    Agents can chat with their team mates and colleagues with RingCX in RingCentral application. If you are using standalone RingCX agent web-app we encourage you to try RingCentral app available for Windows and Mac, where RingCX agent is built in so you can enjoy both customer and corporate communications in just one app.


    https://www.ringcentral.com/us/en/blog/ringcx-agent-and-supervisor-capabilities-now-in-the-ringcentral-app/


  5. Would be great to have a feature that allows managers/supervisors to receive text message notifications when agent states are abused. Example, an agent in an RNA state for more than 1 min. Manager would receive a text message alerting them of the agent's state.

    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. Ability to allow the use of the Plantronics hub through RCX.

    Customers who are using the RingCentral Office phone via the RCX and the RC app is integrated with the Teams app should be able to use the Plantronics hub without an issue.

    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)
  7. When agents add information unto the contact card, automatically save those details after the call ends instead of relying on agent to hit "save" button

    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. Here at the City of Bend, some Contact Center team members use their Desk Phones to handle calls, transfers, putting on hold, etc. On RCX, you can "Login with RC Phone" option Logging into RCX, but the receptionists must handle the call through the HTML RCX Interface. We assumed this would allow receptionists to completely handle calls through the physical RC Phone, however, we are being told this does not work at this time. We would like to handle the entire call control from the physical desk phone.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. 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.

    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)
  10. Allow agents who requeue a call to reclaim it if the transfer fails or the call remains active.

    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)
  11. Currently, when agents using RingCX attempt to transfer a call to a RingEX extension via the corporate directory, the system presents a misleading "congestion" error. This message suggests a network or capacity issue when the true cause is that transfers to RingEX extensions are not supported in RingCX.

    This leads to agent confusion, unnecessary troubleshooting, and increased support tickets. We request a clearer, more accurate system message such as "Unsupported transfer destination" or "Transfers to RingEX extensions are not currently supported" to replace the generic "congestion" message in these cases.

    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)
  12. It is not possible to copy/paste numbers containing spaces for the numbering of outgoing calls. This is a time-consuming process for manually entering numbers or deleting spaces. This feature will optimize the processing time.

    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)
  13. Summary:
    We request a feature enhancement for RingCX that allows Wrap-Up settings to function independently, even when Agent Disposition is disabled. Currently, the Disposition prompt is tied directly to Wrap-Up, making both share the same time settings. This limitation restricts operational flexibility and does not align with customer preferences for separate configurations.

    Detailed Description of the Request:
    At present, in RingCX, the Disposition prompt and Wrap-Up are intertwined:

    If Disposition time is set to 30 seconds, the same applies to Wrap-Up time.
    Disabling Disposition entirely also disables Wrap-Up functionality, which is undesirable for customers who prefer one without the other.…

    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)
  14. Add the "Allow Off-Hook Calls" and "permanent connection" functionality from the RingCX web client to the desktop client. This feature currently allows calls to be routed to an agent even when they are in an "Away" status.

    The customer identified that this behavior difference between the two clients caused a support issue. Implementing this feature in the desktop client would provide a consistent user experience and prevent similar issues in the future.

    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. Some agents are inadvertently logging in using the RingCentral App instead of the Integrated Softphone. As a result, calls routed to the RingCentral App are left unanswered and often abandoned. Since Presence Sync is not yet available, the RingCentral App must be set to Do Not Disturb (DND) to prevent calls from being delivered simultaneously.

    This feature should allow administrators to modify the available Voice Connection options for agents, ensuring that calls are routed correctly and reducing missed or abandoned 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)
  16. Request to integrate the RingSense for RingCX icon into the RingCentral app interface to improve accessibility and visibility for users. Currently the icon only shows in the RingCentral app if the account has RingSense for Sales. The icon should be positioned consistently with other app features and allow users to easily launch or access RingSense for RingCX functionality directly from the main app UI. Acceptance Criteria: RingSense for RingCX icon is visible within the RingCentral app UI. Icon links to or opens RingSense for RingCX features. Placement is consistent with existing design standards. Available for users with appropriate permissions.

    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)
  17. Summary:
    Enhance queue logic to allow conditional call routing to supervisors who are part of the same queue but should only receive calls flagged as escalations or transfers from agents, while remaining in Available status.

    Current Limitation:
    In the current setup, any supervisor assigned to a queue and set to Available will receive regular inbound queue calls unless they manually switch to a different status (e.g., Working) to avoid being routed normal contacts. This manual workaround is not ideal, as supervisors must remain Available to handle warm transfers or escalation scenarios from frontline agents.

    Proposed Enhancement:
    Introduce an optional "Escalation-Only…

    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. Add a tag or variable in RingCX "Email Templates" that dynamically inserts AI-generated call summaries. This would enable the system to automatically include the summary of a call in a follow-up email sent to the caller after the call has been dispositioned.

    This enhancement streamlines post-call communication, improves customer experience, and ensures that key conversation details are accurately and consistently conveyed via email without requiring manual input.

    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. Currently, the RingCX home page has a "Quick Access" section. We would like to request the addition of two new, configurable links to this section: "Call Log" and "Reports."

    Having these links readily available on the home page would save time and clicks for our agents and administrators, allowing them to quickly access key information and analytics without navigating through multiple menus. This feature would significantly improve the user experience and overall efficiency when using RingCX.

    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. Currently we use the application Ring CX to overcome the problem of pop-up, however it does not allow to code calls, nor to carry out call transfer. The roll-out of the Ring CX application, as announced later this year, should allow these features to be used.
    Unable to code and transfer on the Ring CX application.

    Currently we perform these tasks (call end coding and call transfer) from the web interface, but this requires switching between tools (Ring CX application lient Ring CX web).

    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)
  • Don't see your idea?