Skip to content

JUMP TO ANOTHER FORUM

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

126 results found

  1. RingCX Callback feature_ Enable the ability to upload multiple audio files, or add a feature that informs the caller of the number they should expect the callback from.

    5 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. RingCX Speech Recognition default format
    The customer prefers to use the default RingCX Speech Recognition format rather than manually adding both lowercase and uppercase versions of each 'digit'.

    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. The customer would like to manually add numbers that do not get added back into the callback cycle, and add a time and date for the manual callbacks.

    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. Currently in RingCX, if all agents logged into a queue are busy or unavailable, or if a caller has been on hold for an extended period of time, the system routes callers directly to voicemail (or continues holding until timeout). There is no built-in option to reroute callers to a backup RingEX ring group before voicemail is triggered.

    Current Behavior

    Callers enter a RingCX voice queue.

    If all agents are busy, callers wait in queue until:

    An agent becomes available, or

    A voicemail/timeout rule takes effect.

    There is no ability to configure a conditional overflow to a RingEX ring group.

    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. Include a system-wide phone book. Having a Phone Book per Agent Queue is good, but when I have to add the same Phone Book entry to multiple Agent Queues, it creates unnecessary work.

    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)
  6. Please add logic and verbiage for when a caller has a pending callback request and calls back into the RingCX voice queues from the same ANI. Today, the process does not detect when there is a pending callback request and offer the caller to resume their spot in line. The call is treated like a second contact, and can be misleading when the queue position is read back to the caller. A second callback is allowed to be scheduled, but is then discards the second callback request once the callback request is completed. Please add the following logic to the…

    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 a caller requests a callback, they can choose to receive the callback from the originating phone number, or choose to enter a new phone number. When the caller enters a new phone number, there is a long pause before the caller hears any type of confirmation of the number the callback will occur to. This can make callers believe something has gone wrong with the callback request process, causing them to hang up prematurely. This pause should be reduced in length, or better yet, set to be a configurable value.

    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)
  8. 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)
  9. If a queue event is defined for an action like send the call to voicemail, and the destination is an email address, that value or information should be able to be referenced when creating a business hour override.

    Use case: We have a queue event set with a DTMF tone to route the caller to voicemail. That queue event sends an email to a specific address. If we create a business hour override on that queue to close the queue, we typically send the queue to the same voicemail & email address as defined in the queue event. Today, this…

    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)
  10. Instead of the weblinks attached to access voicemail messages from RingCX, we'd like to attach the exact audio file to the email notification.

    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)
  11. RingCentral should add robocall filtering to CX. I was told it happens on the EX side, but it's not happening in CX. We're getting robocalls that hang up right after they are dropped into our queue, and that's causing our abandoned rate to spike.

    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)
  12. RingCX to support a feature where it can track the status of an inbound call. This will allow the system to automatically send an SMS to the caller's number if their call is abandoned (i.e., they hang up before connecting to an agent).

    This type of functionality is currently available in RingCentral Contact Center (RCCC) and is configured using its Studio tool.

    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. Under their stats it shows "In Queue" and this is where they were seeing the total amount of calls in queue including call backs but now since enabling FiFO it shows them the total of "queued" calls only, not the total of call backs waiting (callback-await-queue) and "queued" calls. Is there a way to change this? They can certainly see the total under "active" but under active it also includes the calls that agents are currently actively on, making it hard to gauge pending volume. 

    In the example below, the "In Queue" says 1 but when you actually look into…

    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)
  14. Request for functionality that allows chat sessions, reinitiated by a client after inactivity, to be reassigned to the original technician instead of being routed back to the queue for random reassignment.

    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. When adding a new Date Time node in the Workflow Studio, the timezone defaults to Eastern Standard Time. This is unexpected.

    Expected behavior would be for the Date Time node to use the same Timezone that is set in Account settings.

    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)
  16. Customer requested that when their clients call in and are given the option to request a call back, they need these requests sorted by timezone so the agents only call people during working hours in their respective timezone.

    5 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. Ringcx

    When creating workflow and costumer like to merge a new created or exciting workflow ,the would like to have to option to merge with other flow
    As for now this option is not available

    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. option for Container Node that allow as to import workflow so that when creating workflow and like to merge a new created or exciting workflow ,the would like to have to option to merge/connect with other flow. As for now this option is not available as function of the Container Node.

    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)
  19. The ability to add an automated message to press the pound key (#) when the their callers are routing to a Callback IVR since this is a system message there is no option to add this automatically. The customer needs to manually add it to the greeting.

    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. Problem:
    Agents must manually log in/out and select/deselect the chat queue to control availability. This creates inefficiency, increases the risk of error, and disrupts their voice queue workflow.

    Solution / Feature Request:
    Add an automated scheduling option for chat queues, similar to voice business hours, that allows:

    Routing chat messages only during defined business hours (e.g., Mon–Fri, 7 a.m.–5 p.m.).

    Holding messages sent outside these hours (weekends, after-hours) until business hours resume.

    Eliminating the need for agents to manually adjust chat queue selection.

    Impact:

    Ensures customer messages are handled promptly and consistently.

    Reduces agent workload and login complexity.

    Prevents disruption…

    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?