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

211 results found

  1. We have a CX Queue called RPS.  On Fridays, the queue closes at about 4:30pm.  The agents log off and go home.  Sometimes there is a requested callback still waiting to happen.  The next morning, the RPS agent arrives at 6:45am for our 7:00am opening of the rehabilitation department.  The agent needs to log in to receive any calls concerning the 7am appointments, like late arrive or cancelling the appointment.  This agent then at 6:45am fields the callback that was left the previous night.  This is too early to be calling patients.  We would like that callback to start at…

    23 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. Issue:
    The system is not configured to check the holiday schedule, causing it to send alerts that a queue is open even when it is closed for a holiday.

    Proposed Solution:
    Add a filter option to the alert system that allows it to check the holiday schedule. This filter would prevent "queue is open" alerts from being sent on scheduled holidays, ensuring the alerts accurately reflect the operational status of the queue.

    88 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 you are in RingCX and on a call, if you requeue a call and select stay on the call, it will put the customer on hold. Taking the customer off hold does not end the requeue and causes the agent to hear a beeping until the requeue is either successful or the call has ended. There is no option anywhere to end the requeue.
    This has been replicated on RingCentral’s internal RingCX account.

    Functionality wanted: To be able to cancel the requeue without having to fully end the call.

    43 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. Ability for agents to manually schedule a callback for a customer without using dialer with the following requirements:
    1. The agent needs to have the ability to set the date and time the callback has to be scheduled.
    2. The callback has to be scheduled to the agent's "queue" and not to the agent specifically
    3. At the time of the callback, the agent has to be notified and the agent has to have a way to decline the scheduled callback.

    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)
  5. option for either an automated change from RNA to Available or the ability to set a specific duration for RNA before the status automatically changes to Available.

    14 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, permissions for requeue and cross-queue requeue are managed at the agent level. We are requesting an enhancement to migrate these settings to the queue level.

    This change would provide greater granularity by allowing us to define permissions based on the specific requirements of a queue. This would enable agents to requeue calls on certain queues while being restricted on others, which is essential for improving operational flexibility and security governance.

    14 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. Meta released the Cloud API Calling allowing user to call companies through WhatsApp. Companies have to be registered as WhatsApp business
    https://developers.facebook.com/docs/whatsapp/cloud-api/calling
    This "API" was on beta in Brazil, Indonesia,etc. It is now globally available.
    It is a highly requested feature, due to the public availability on WhatsApp.
    It is important to associate this idea to another one "outbound whatsapp with RCX UI" https://ideas.ringcentral.com/forums/966594-ringcx/suggestions/48515087-outbound-whatsapp-within-rcx-agent-ui
    it will allow to send messages directly to a customer while on call. (in this case, template are not required)
    user initiated calls to business are free and there is a cost for business initiated. The…

    23 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. Add Opt-In Surveys at Call Start, Auto-Prompted at Call End

    As a head of a centralized call center with agents that support multiple businesses and call queues, I’d love to see RingCentral add a simple but powerful feature:

    When a customer calls in, they could press a key at the beginning of the call to opt-in to a quick survey. After the agent disconnects, the system would automatically play the survey.

    Here’s why it matters:
    - Seamless customer experience: No agent involvement, no awkward “Would you like to stay on the line?” interruptions.
    - Accurate feedback: Surveys are tied directly…

    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)
  9. We would like an option we can set to send notifications to users logged in when there are calls in queue as well as notifications when a call has reached a certain time in queue. Agents are busy dialing at times and since they are constantly dialing w/o having direct view on the call queue they do not see that there is a call in queue and they continue to outbound dial causing an abandoned call. This would be on the CX dialing.

    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)
  10. RCX system prioritizes agents based on their overall Available Status time for the day, rather than their current Highest Availability:

    -agents who have recently returned from an offline state (such as breaks or lunch) receive calls before those who have been continuously available.

    -to better accommodate the varying preferences of our clients, we kindly request the addition of an option to enable or disable this feature. This adjustment would allow clients to configure their queues according to their specific needs and ensure a more equitable distribution of calls.

    We understand that this behavior aligns with the current design of RCX,…

    230 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, the "Place in Queue" announcement plays only once when the "Route to Agent" queue event is first triggered. The desired functionality is to have an option for this announcement to loop and repeat at adjustable intervals. Ideally, the position in queue should be recalculated and announced each time, without the need to chain multiple "Route to Agent" events sequentially.

    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. When an agent is using the RingCX application, they have the ability to transfer calls to RingEX users and see their extensions in the corporate directory. However, there is no native integration that allows RingCX agents to transfer calls directly to RingEX call queues. The customer is currently using a workaround where they manually upload the DIDs of the RingEX call queues into the RingCX phone book, which allows for transfers as if it were an external contact. This is a time-consuming and inefficient process that requires manual maintenance whenever a call queue is changed or added. The customer would…

    20 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. RingCX currently supports automated email generation for inbound calls based on the disposition selected by the agent, through custom workflow. This feature has already been designed, presented, demo’d, and validated for inbound workflows.

    However, during UAT, customers requested that this same functionality be extended to manual outbound calls, which is not currently supported.

    Current Limitation:
    Automated disposition-triggered emails only work for inbound calls
    Manual outbound calls do not generate emails, even when dispositions are applied
    Agents must perform follow-up communications manually, leading to inconsistent workflows between inbound and outbound calls

    Requested Enhancement
    Enable automated email generation for manual outbound calls,…

    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. There should be a way in RingCX to enhance the callback experience by allowing callback requests to be honored immediately after the caller’s initial input, without requiring a second confirmation—even if the caller disconnects early.

    Current Behavior
    1) Callers press “1” to request a callback.
    2) A second confirmation (“press 1 again”) is required before the callback is officially queued.
    3) If the caller disconnects before completing the second confirmation or before system disconnect, the interaction is marked as “Inbound ACD Callback Incomplete.”
    4) No callback is generated, even if the caller already indicated intent.

    Problem Statement
    • The two-step…

    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)
  15. In the current RingCX callback flow, if a caller disconnects before the system successfully queues the callback, the interaction is categorized as “Inbound ACD Callback Incomplete” in Analytics reporting. This occurs even in cases where the caller has already expressed intent to receive a callback.

    Problem:
    This classification does not accurately reflect customer intent or agent workload. From a business perspective, these interactions often represent valid callback requests that were interrupted due to timing or user behavior, rather than true failures. As a result:
    1) Callback demand may be underreported
    2) Metrics may not align with actual customer experience
    3)…

    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)
  16. Feature Request: Create a feature that can dynamically determine when a callback queue event should be offered based on specific thresholds (i.e SLA, elapsed time (currently in place), abandoned rates, # of calls waiting, etc.)

    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. Currently, RingCX supports agent priority ranking for voice skills, allowing administrators to route interactions to the most qualified agent first, with automatic fallback to other available agents. This same capability does not exist for digital skills.

    We are requesting the ability to assign priority rankings to agents within digital skills, enabling digital interactions to route to the highest-ranked available agent before cascading to others. This would support proficiency-based routing, improve efficiency, and provide consistency across voice and digital channel configuration.

    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)
  18. customers would like to have the Hashtag in the list of possible DTMF codes in IVRs and Queue events.

    45 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. Ability to filter the numbers added in route properties for all workflows instead of checking them manually. It will be efficient and time-saving if there's an option for this. In this way, we can change the number added to another number we prefer and resolve the issue as soon as possible.

    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)
  20. Manager would like the option to assign out callback to agents and then have agents pick up those calls once available

    12 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)
← Previous 1 3 4 5 10 11
  • Don't see your idea?