Skip to content

JUMP TO ANOTHER FORUM

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

1180 results found

  1. Driver calls Dispatch, Dispatch calls customer, Driver hangs up. Need two separate elapsed times: One for driver and one for customer... another phrasing: when dispatcher makes secondary call, WM needs the elapsed time for the call with the driver and the elapsed time for the second call to the customer.

    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. Driver calls Dispatch, Dispatcher goes to call customer. Need the keypad to pop up automatically to allow less clicks.

    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. Ability to show the Customer's Phone Number on the dispatcher's screen when the driver calls. Looking for an additional RCX field to pull from the API to show the customer's number.

    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)
  4. WM would like adhoc downloadable report with the following columns of data:
    First/Last Name
    Voice Queue Name
    Rank Within Queue
    Digital Queue Name

    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. Ability to turn off or on list of text queues for dispatchers.

    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. Ability to log internal calls (calls made from RingCX for Salesforce to RingEX extensions)
    The current CRM app only supports logging calls for external contacts, but not for the corporate directory (RingEX extension).

    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. Currently IB queue SLA% is calculated using the "Presented" metric -- "Presented" is calculated using both IB calls presented to an agent AND OB session/Agent Leg connection calls. -- This inherently skews SLA% as the OB session/Agent Leg connection calls are not true/real calls "presented" to the agent. The SLA% should calculate only IB calls; e.g. if a customer has a 30 second SLA set and 100 calls come into a queue (90 are answered prior to 30 seconds) their SLA% (adherence) would be 90%.

    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

    Implemented  ·  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)
  8. Currently, when an agent is on a RingCX call, incoming RingCentral (EX) app calls can still come through, causing interruptions. This request is to enable call status sync in the reverse direction—so that when an agent is active on a CX call, their status is reflected in the EX app, and EX calls are either blocked or suppressed accordingly.

    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)
  9. In RingCX, create additional call events in which When a missed call occurs or When a callback is initiated or completed, the system will send automated emails to a specified recipient or distribution list based on these triggers.

    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. in RingCX outbound dialer, it would be better to have the ability to merge/combine old lead that was dialed before to the same lead that is being uploaded like 6 weeks ago.

    By doing this, the history of the previous lead are visible to the agent that will take the new lead.

    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. RingCX’s default 48-hour call history window feels like trying to solve a puzzle with half the pieces missing. Once you need to review anything older than two days, you’re forced into the Reports rabbit hole (if you even have access), wasting precious minutes and leaving non-admin agents stuck. Let’s fix that by giving every user a simple dropdown or settings toggle to choose their history range: 48 hrs., 7 days, 14 days, or up to 30 days, so you can instantly pull up that crucial call from last week without a detour. This small change supercharges agent productivity (no more…

    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)
  12. SPOG Application: The option to manually accept callback request calls when they are routed to the agent.

    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)
  13. Currently, when a customer initiates a digital chat from a website, there is no straightforward way within RingCX Digital analytics to identify the specific webpage URL they were on.

    The use case has been generated by a customer that has circa 2-million digital interactions a month spread across multiple websites and multiple pages.

    This lack of data creates a blind spot and the account cannot correlate chat volume with specific website and web pages. This hinders their ability to optimize their website, measure marketing campaign effectiveness, provide the most efficient customer support and more importantly they cannot provide reports to…

    6 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. When searching the Phonebook directory in RingCX, both the queue extension and the associated phone number should be displayed—even if the number is directly linked to the RingEX Call Queue group extension. The customer requests that the RingCX directory experience mirror the behavior and data visibility currently provided in the RingEX directory.

    Current Behavior:
    In RingCX, when users search the Phonebook directory, only the call queue name and extension are displayed. The associated phone number is not shown, even if one exists.

    Expected Behavior:
    While using the keypad in the RingCX app, as users begin typing a queue name, 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)
  15. Live Chat with Switch Video Enable - Analytics Recordings

    As of now, the recordings of the video meeting are not available in the RingCX Analytics, once the visitor or the agent in the live chat requested or jumped on the video meeting.
    For the reporting purposes, the video recordings are still needed.

    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)
  16. Have the ability to keep the main phone number but change the dial to number. Sometimes a customer wants us to call them on their cell phone but we need to keep the associated phone number with the account.

    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. Currently today, we are able to hide a queues extension on the EX side but this does not translate over to CX. When searching for a contact, we see all of our queues extensions on the CX side. It would be so helpful if CX behaved like EX in this case where it follows the setting in EX to hide that information.

    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. customize the visibility of the message bar on a per-user basis

    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. customize the visibility of the message bar on a per-user basis on RingCx

    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. There should be a way the system understands the different ways a TN can be displayed/formatted and searched, but at present, it seems it needs to be exactly the same as the interaction shows in the history.

    Please see the screenshots.
    If a number is formatted in 3 different ways as it's used in RCX:
    (734) 279-2221
    17342792221
    734-279-2221

    When you search by these formats, you only get see the exact format the text is searched as, instead of all instances in which the number can be formatted as. This causes an issue as you search for a customer's info and/or…

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