Skip to content

JUMP TO ANOTHER FORUM

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

1096 results found

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

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

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

    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)
  4. customers would like to be able to manage answer mode in different ways depending on the type ( inbound/manual outbound VS dialers/campaigns ) :
    have the ability to enable/disable the off hook / permanent connection for inbound calls separately from the dialer/campaigns off hook / permanent connection mode.

    so even if you disable the permanent connection/off hook for inbound, you can still have the dialer calls (as when you start dialing it switches you to off hook mode automatically).

    or the other way around if you start the dialer - it would switch to off hook for the dialer -…

    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

    Under Review  ·  1 comment  ·  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. 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.

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

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

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

    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

    New  ·  0 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)
  9. 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.

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

    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

    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)
  11. Need the ability to export Agent Script from Studio so they can be shared and imported.

    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

    Planned  ·  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)
  12. It is important to use time-based Callback-in-Queue so that when a queue is ending callbacks aren't left waiting until the next day. Time- based Callback offering could turn off callbacks being offered 10, 15 or 30 minutes prior to Queue closing. Phase 2 could be time and "chance of answering" using AI to determine if a callback is offered can it be answered while the Queue is active such as number of agents, active talk time versus time left in Queue before closing.

    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)
  13. This will enable Supervisors to see the Wrap status in their dashboard during the set wrap up time after each call.

    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)
  14. We would like to implement a functionality to disable the extensions for certain Representatives from receiving external calls or direct transfers. We want to ensure the only calls received are through a skill.

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

    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)
  16. Currently, RCX bills lack a summary page showing agent allocations, similar to RingEX's cost center billing. The customer requests this feature

    25 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)
  17. If an agent is initially unavailable and receives an internal call or makes an outbound call, do not automatically change agent status to Available once the call is over.

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

    25 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. I'd like to know the service level from the first response to the last response. How quick are we to respond to the customer requests. Actually, I can get from Dimelo the Average Time of Response, but I'd like to know how many responses were given within 30 seconds, and how many responses are given after the treshold of 30 seconds. And I want this information on all messages, not only on the first response. Is it possible to display this calculation of the SLA?

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

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