Skip to content

JUMP TO ANOTHER FORUM

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

1180 results found

  1. Queue Events, Business Hours, and Business Hour overrides all allow calls to be transferred. These transfers rely on DID transfers with 10 digit phone numbers being used. We have a large number of call queues set up on RingEX that do not have a DID assigned, and we do not want DIDs on those call queues. Today, we are unable to transfer calls from a RingCX queue back to a RingEX extension without the use of a workflow. We'd like RingCX to support call transfers to a phone number + extension. Example: Queue Event DTMF key press 1 would perform…

    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)
  2. When a caller is in the process of requesting a callback or leaving a voicemail, and an agent becomes available, the caller is left in those modules/processes instead of being routed to the agent that became available. Please add an option on a queue that controls what happens when a caller is requesting a callback or leaving a voicemail, so the queue can either be configured to:
    1) Leave the caller to continue with their original operation of requesting a callback or leaving a voicemail.
    2) Abort the original option of requesting a callback or leaving a voicemail, and route…

    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)
  3. The callback process needs additional functionality and configuration options added to make it more useful. Today the process just prompts to create a callback with the current phone number, or enter a different phone number. The callback process needs to be modified for the following:

    1) Prompt for the caller's name, as outlined in this feature request: https://ideas.ringcentral.com/forums/958496-contact-center-ringcx/suggestions/49775720-inbound-queue-callback-option-to-record-caller-s. This would at least let the agent know who they are calling back, and allow the agent to speak to an operator or navigate an auto attendant at the destination number.
    2) Enable a toggle to prompt the caller to enter…

    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)
  4. NICE CXone has a "Agent Timeout" setting on each unavailable code. Please add the functionality to toggle on an "Agent Timeout" for each unavailable code. When enabled, and the agent reaches the value set for the timeout, the agent would be logged out of the RingCX system. This is useful for agents that put themselves into an unavailable code like Lunch, without realizing they are taking the rest of the day off. For example, most employees take a one hour lunch break. The "Agent Timeout" for the Lunch available could would be set to 120 minutes (two hours). The agent…

    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)
  5. I’d like to submit a feature request for RingCX Analytics.

    Currently, when reviewing Interaction Details for Digital SMS interactions, the ANI field displays as "N/A." For better visibility and reporting, it would be highly beneficial if the actual ANI (sending number) were displayed in this field.

    This enhancement would help teams more effectively track and analyze SMS interactions, especially when handling multiple Digital SMS numbers.

    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

    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)
  6. When using the RingCX embedded agent in ServiceNow, and a outbound call is placed with click to dial, the "Name" is not populated in the RingCX agent like it is on an incoming phone call. This would provide a more consistent user experience on inbound and outbound phone calls in the RingCX agent. Additionally, it would assist in finding other open cases that that contact has right within the RingCX agent, so the user does not have to navigate back to ServiceNow to look at the contact's other open cases.

    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)
  7. Add a native feature to display Caller ID (name and number) of waiting callers (2nd, 3rd, etc.) within the active call screen in the RingCX Agent interface.

    Current Limitation:
    Agents are currently unable to see Caller ID information for waiting calls unless they leave the active call view and manually navigate to other areas like the Analytics or Supervisor tabs. This creates a disjointed experience and impacts real-time decision-making.

    Use case:
    An agent is currently engaged in a live call. While speaking, they can glance at the interface and see the next caller waiting — “John Smith | (555) 123-4567…

    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. Make Agent States by Agent and not a global setting.

    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)
  9. We’d like to request a change to support displaying the caller ID dynamically from the RCX front, instead of using a static value. It should display a more generic value like "Internal RCX Call" or the actual caller ID of the RCX agent, depending on their configuration.

    Currently we are seeing random numbers (027837475)

    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)
  10. When some potential customers mention that they know someone who is looking for or needing our services and want to give us their number, or when they indicate that their spouse is the one we need to speak to and volunteers their number - it would be ideal and a great aid if we were actually able to use that information to take advantage of the presented opportunity and cease the moment and get referred customers.

    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)
  11. Request to add a new RingCX API endpoint that allows retrieval of agent availability and offhook state directly, without the need to use event subscription mechanisms. This feature would enable easier and more flexible integration for monitoring agent statuses in real-time.

    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

    New  ·  0 comments  ·  Integrations & APIs  ·  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. A customer has requested the ability to configure a pre-call workflow that prompts callers to input key details such as:

    Name

    Address

    Phone number

    Email

    Product type

    Issue description

    The goal is to collect this information before the call is connected to a representative, so that it can automatically populate the agent’s interface. This would reduce call handling time, improve agent preparedness, and enhance the overall customer experience.

    Business Value:

    Reduces time spent on data collection during live calls

    Increases first-contact resolution likelihood

    Improves accuracy and consistency of captured customer information

    Enhances agent efficiency and customer satisfaction

    Suggested Implementation:

    Interactive…

    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)
  13. I have a use case with an existing client that the heavily uses digital interactions. They have a requirement to be able to restrict access to interactions associated with specific channels to a team of people.

    In RingCX currently, by design, the digital inboxes are just filters for interactions - they are not permissive or restrictive. Although the inbox can be filtered to display certain interactions, an agent can use the search facility to be able to search and view interactions across all channel.

    The use case is that an client may wish to create a channel that is used…

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

    I’d like to submit a feature request regarding how RingCentral handles call signaling when a terminating carrier fails to return an intercept message.

    Current Behavior:
    When calls are placed to numbers that are unassigned, disconnected, or otherwise unreachable, and the terminating carrier does not return a proper intercept message (e.g., “This number is not in service”), RingCentral simply passes through the signaling it receives. This may result in endless ringing or silence, causing confusion for users.

    Requested Enhancement:
    Implement a mechanism or fallback behavior to better handle cases where no intercept message is returned—such as:

    Playing a generic…

    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. the client would like a feature to be added that allows users to sort message threads so that older interactions can appear at the top of the inbox in "All messages". This would be particularly helpful for:

    -Quickly revisiting important past conversations without scrolling or searching.

    -Managing long-term projects where older threads remain relevant.

    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

    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)
  16. RingCX for Zoho Embedded Agent >Due to limited space, Digital Email seen in window is not large enough and cannot scroll to the edge of the email...Need the capability to scroll and see the full email either vertically or horizontally in some manner

    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)
  17. Ability to access Cloud Destination outside RingCX to modify or configure

    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

    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)
  18. Ability to assign the email interaction to a group instead of manually selecting agents. Right now, we can only assign email interaction manually to an agent, but there is no option to create a group to assign the email interaction instead.

    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

    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)
  19. Backup / export and restore / import options for
    - voice queues
    - digital queues with agent mappings,
    - roles,
    - user with queue mapping including rank or skills
    - time settings.
    the existing export functions, e.g. flows covers only a small part of settings.

    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 for a voice queue in the integration section, you can only have one web service endpoint selected for an event like De-Queue Webservice, Agent Connect Webservice and Agent Termination Webservice. It would be nice to be able to send those events to two different environments - production and staging endpoints for testing.

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