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

1612 results found

  1. There is a significant need for the ability to drill down into historical data and filter digital queue KPIs by channel name and ID. This functionality serves multiple purposes and use cases, with a common scenario being the grouping of channels by site, language, or brand. Without the ability to create a more granular channel breakdown of KPIs, RingCX data analysts and supervisors have limited capabilities when it comes to determining and understanding potential customer service performance issues or identifying areas for improvement across different sites, languages, or brands today. Additionally, providing the associated digital thread ID within Historical Reporting…

    32 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. The ability to get a report on surveys both for voice and digitial.

    Ability to see how many surveys were sent, how many answered, results of the replies, overall score etc.

    32 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, if an agent has an inbound queue assigned to them in the 'manual outbound default queue assignment' field, then manual outbound calls made by that agent are counted in analytics as inbound calls against that inbound call queue.

    This causes some confusion in reporting and skews stats related to inbound calls to the given call queue.

    Customers would like an option to differentiate between inbound and outbound calls associated with an inbound queue, or at least manual outbound calls associated with an inbound queue should not be counted on inbound reports & dashboards.

    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)
  4. When callers are waiting in a queue, RingCX can only play back the estimated wait time once. Other phone systems have an option to let callers know the estimated wait time every X seconds, such as once every 45 seconds, so they know how long it is before their call is answered.

    We would like to see RingCX updated so it allows us to teller our callers how long it is before their call is answered more than just one time.

    Also, there is a RingCX configuration that lets the callers know their position in the queue, such as "caller…

    30 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  ·  2 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)
  5. Currently, the only option to transfer an SMS is to reroute to the queue group itself. It would be nice if there was an option for companies to allow agent-to-agent transfers. Our team consists of 8 employees, and rather than reroute a customer looking to speak with a specific agent digitally back to the skill group, it would be nice to be able to transfer directly to the agent to wait. Then the next time this agent would be available, they would be prompted to interact via SMS or Engaged Digital (email).

    30 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. Currently, the callback feature has no caller ID override. By default, it uses the DNIS as the caller ID when a callback is made by the system. For calls to external numbers that are forwarded to the RingCX number, it shows the number where the external number is forwarded as the caller ID.

    Looking to have a feature or option to set the forwarded number (external number) as the caller ID.

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

    29 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 we get RingCentral voicemail email notifications, we cannot move and merge the VM/email to an existing customer profile with out permanently associating the "notify@ringcentral.com" to that one customer account every time another comes in.

    Example:
    Ringcentral sends a VM notification email, sent from notify@ringcentral.com to our email queue.
    The VM call from caller ID is from 734-999-9999.

    That number is associated with John Smith, a customer profile visible from a previous interaction
    with that customer.

    We'd like to move that VM over to the John Smith profile manually (or via a workflow if possible by using the…

    29 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. I would like to suggest a couple of feature enhancements to simplify the use and management of the following:

    • Phonebook (Agent Tools and Voice queues and skills)
    • Special ANI (Voice queues and skills)
    • Blocked ANI (Channels)
    1. Currently, we can only add a name and note to individual Phonebook entries in Agent Tools. It would be highly beneficial if we could add this functionality Special ANI and Blocked ANI to allow customers to better manage and identify phone numbers.

    2. We can currently only import numbers natively through the RingCX admin portal for Special ANI. It would be helpful if we had…

    29 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  ·  0 comments  ·  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)
  10. The RingCX Callback feature currently allows users to enter an alternative number for a callback, with the sole restriction being that the number must originate from the same country as the inbound ANI country code.

    However, there is a potential risk of abuse by malicious actors or scammers, who could exploit this feature to generate revenue for themselves by using premium rate numbers for the callback, resulting in financial implications for our customers.

    To mitigate this risk, I would like to suggest implementing the ability to restrict specific numbers from being used for callbacks by creating a blacklist.

    29 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 request is for RingCX to have a Customer Journey Cradle-to-Grave Report, showing the start to finish and reporting on Pivots between channels. If it is a telephone call the detail should focus on the contact, even if the call is transferred between agents, put on hold, etc. If it pertains to a phone call and also includes digital channels, then the digital channel information can be added as a follow up from the call.

    29 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. Last Agent Sentiment Advances in AI makes optimal routing possible, routing new interactions based Last Agent Sentiment (if this customer interacted with this agent and it was positive based on agents’ availability direct new interaction to this agent. If the last interaction between this customer and the agent (who is due the next interaction) was negative, redirect to next agent skipping this potential negative conversation. This needs to be reportable that includes customer information like phone number or email for digital, the agent skipped and possibly the actual agent and the interactions sentiment outcome versus last with up/down metric showing…

    29 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. Have a feature to restrict the access of an admin to the analytics based on the team/department/group they are only managing.

    This is an issue as Admins should not be able to see other departments data via report.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Currently, in the RingCX Agent Interface, the Stats tab (specifically under the 'Inbound' and 'Blended' views) provides a single column for "Presented" calls. This metric is an aggregate that combines both Inbound and Outbound presented calls into one figure.

    In contrast, the RingCX Analytics Real-Time Dashboards (e.g., the People Services Dashboard) already provide a granular breakdown with separate columns for "Pres. IB" (Inbound) and "Pres. OB" (Outbound).

    This discrepancy creates a lack of visibility for agents who need to distinguish between their reactive (inbound) and proactive (outbound/manual dial) performance within their primary workspace.

    Proposed Solution
    Update the Table Settings within…

    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)
  15. 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…

    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)
  16. Not having park in the CX platform creates a large problem for our users. Having the ability for CX users be able to park calls for both CX users as well as EX users would make the pain of switching to Ringcentral much easier. I have been told that call centers simply do not use park but I think that is not a true statement. We have 80 employees and several queues. some queues are on the EX side and some on the CX. We are not the typical call center but we wanted the Queued callback and the ability…

    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)
  17. Ability to display user extension number of the transferring agent when a call is being transferred from RingCX to RingEX users.

    Whenever an agent from RingCX transfers a call to a RingEX agent, the RingEX user would like to see who internally from RingCX agents are calling them helping them easily identify who from the RingCX agent are calling them.

    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)
  18. Many customers would like to have a warm transferred call automatically put the far end on hold. This functionality is available within agent scripting. However, some customers use the RingEX extension integration which would require the agent scripting to use webservices. This change would give customers the ability to choose how they would like to handle warm transfers on a queue/campaign level and would alleviate the lift required to mimic this functionality.

    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. Suggestion is to offer simultaneous ring capability in RingCX, similar to what is available in the MVP call queue. In RingCX, the current routing options are Round Robin, Sequential, Percent Allocation and Geo Location.

    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)
  20. Customer is requesting additional configuration options for SMS Shared Inbox conversation management.

    Current behavior automatically moves SMS conversations to the “Resolved” folder after a certain period, which the customer reports is causing confusion and inconvenience for users managing ongoing conversations.

    Requested enhancements:

    Ability to disable automatic movement of SMS conversations to the “Resolved” folder.
    Ability to configure or extend the auto-resolve interval before conversations are moved to the “Resolved” folder (e.g., allow longer retention periods such as weeks or months).

    Customer also noted that replying to a resolved conversation starts a new active thread while previous messages remain in the…

    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

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