Skip to content

JUMP TO ANOTHER FORUM

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

1180 results found

  1. We would like to have an audible notification or push notification when receiving messages from SMS queue in RingCX. This would be helpful for us to manage our company SMS within RingCX.

    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)
  2. Currently, RingCX does not provide the capability to define individual skill weight or proficiency for each agent individually. This capability is essential because it will:

    • Reduce the need to create a separate skill ("Sales Proficiency 1", "Sales Proficiency 2", "Sales Proficiency 3" and so on) for each weight or proficiency level.
    • Simplify and reduce the level of effort when creating and assigning skill profiles to agents.
    • Streamline skill assignment within queue routing by enabling the selection of a required skill and the definition of a specific weight or proficiency range and order (high to low or low to high).
    16 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. We require the same “Last Called Agent” (LCA) capability for Engage Messaging and Email channels within Digital Queues as currently exists for Voice Queues. This will significantly improve customer experience by providing more efficient and personalised resolution to issues.

    By reducing the need for clients to repeat information and details from previous interactions, this feature would potentially lower interaction durations. Furthermore, this capability is also essential in scenarios where agents receive commissions for successful sales, ensuring clients are routed back to the initial agent who provided consulting prior to the purchase of services or goods.

    21 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. To use the progressive/preview dialer, which we want to be able to do, you must upload a list to RingCentral. This means that RingCentral and Salesforce are only syncing one way (Call log activity through RingCentral to Salesforce)

    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. RingCX queues do not follow the holiday schedule set up under Voice>Account Settings>Holidays and consequently holidays need to be setup manually as a business hours overdrive which is a long and tedious process.
    Having a RingCX holiday queue event added under the queue's "queue events" menu that would follow the holidays setup under the account settings and allow admin to configure where to route the calls to if a holiday would be a tremendous setting addition and a total gain of time for admins.

    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

    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)
  6. 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)
  7. Disable the "ding sound/sound notification" on the customer's browser. Whenever the customer opens a new page, the customer keeps hearing the "ding sound". It creates unnecessary sounds with their customer.

    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

    New  ·  1 comment  ·  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)
  8. It would be helpful if RingCX allowed users to manually pick up or recover calls not progressing on the dashboard.

    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)
  9. Extension dialing between EX and CX is needed. Having to route calls between the two platforms with a 10 digit number results in the need for additional phone numbers, and cost for the customer.

    Another problem with 10 digit numbers, is that if routing is built using temporary numbers that will go away after porting, all of those references have to be updated on CX and EX after the port.

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

    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. At the moment, agents can search leads without issue.

    However, if they need to search leads that is uploaded in a different campaign and dial group the agent is not assigned into. They cannot do that.

    It would be better if we have a feature that can allow agents to search leads globally so that they have idea if this customer will be called by other agent.

    8 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. It would be better to have a "today" button in the interaction details instead of going to the static date and change the date manually as this is ineffiicient and requiring more steps.

    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)
  13. Currently when a lead detail was shown to the agent. They have to scroll down at the very bottom making it difficult in finding important lead information right away.

    It would be better if we have a feature where we can customize which lead detail will be shown at the very top so that the agent's wont have difficulty finding certain information specially if there are a lot of lead details being shown to agents.

    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. Agent would see a pop-up on the right side of the app showing the contact information during an inbound call.
    They would update it but when the same customer call back in, the information won't show their name, just showing the number and unknown
    Customer suggested that if possible to show the contact information so that the agents would be notified whether the caller is a VIP or not.

    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)
  15. Request: Improve the agent user experience in RingCX by providing a clearer, more intuitive option to cancel a requeue and return to the original caller before the transfer completes. While the current system allows this via the "Hangup" button and selecting "Cancel transfer," this functionality is not obvious to agents and leads to confusion and call handling issues. A dedicated "Cancel Requeue" or "Return to Caller" button during the transfer process would reduce errors, improve efficiency, and ensure agents can confidently manage live interactions without unintentionally abandoning the member.

    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. Remove or reconfigure the "Total" on the RT dashboard. It appears to be misleading in terms of the total availability count.

    The client thinks there are 7 available agents, but the actual number is higher than it should be because agents are assigned to multiple queues, causing them to be counted more than once.

    The total number of available agents (boxed in orange) shown in the dashboard is based on the sum of the "Avail" column. Since some agents are assigned to multiple queues, they are counted more than once, which leads to a higher total than the actual headcount.

    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. In the corporate directory, display RingCX presence for agents and RingEX presence for non-agents side by side.

    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)
  18. Allow agents who requeue a call to reclaim it if the transfer fails or the call remains active.

    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)
  19. Display the name or extension of the requeueing agent in the receiving agent’s interface or call history.

    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, when agents using RingCX attempt to transfer a call to a RingEX extension via the corporate directory, the system presents a misleading "congestion" error. This message suggests a network or capacity issue when the true cause is that transfers to RingEX extensions are not supported in RingCX.

    This leads to agent confusion, unnecessary troubleshooting, and increased support tickets. We request a clearer, more accurate system message such as "Unsupported transfer destination" or "Transfers to RingEX extensions are not currently supported" to replace the generic "congestion" message in these cases.

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