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

1443 results found

  1. Supervisors currently cannot filter real‑time indicators by team in the “Real‑Time Digital” and “Real‑Time Agent” views. This limits operational monitoring and makes it difficult to analyze performance and workload at team level.

    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. have the ability to track who made changes in the Audio Library

    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)
  3. Add the number of customers in queue to the Supervisor view
    Provide supervisors with a real‑time view of the number of customers currently waiting in each queue directly from the Supervisor interface.

    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. We have an opportunity to improve agent efficiency for bilingual (or other) accounts by reconfiguring the call-display hierarchy. Currently, the Caller ID dominates the interface, but for this client, the 'To:' field (Language Indicator) is the higher-priority data point. I propose we allow for a dynamic display toggle that allows the customer to elevate the 'To:' title to the primary position, ensuring agents can instantly identify the required language before even answering the call.

    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. With Microsoft Dynamics, phone calls are logged but are in an "Open" status by default. This skews reporting in Dynamics if an agent forgets to take the extra step of marking the call as complete. In a high volume or fast paced environment, agents may receive a another call right after dispositioning/wrapping up the previous call and forget to mark as complete later. If we can have a setting to enable or disable calls to auto-complete at the account level based on preference, that would help keep Dynamics reporting accurate and simplify the agent workflow

    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)
  6. Make the Name and Related To fields on the RC widget on Salesforce mandatory

    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)
  7. The customer would like to have the option to have a delay of at least 20 seconds before the call was forwarded to an external 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  ·  Call & screen recording  ·  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. Today, an agent can see the summary of each interaction. It would be highly valuable to agents if they could see at the top of the list of historical interactions a summary of the previous several interactions to see what's been talked about overall, without having to review every interaction. A paragraph summary including topics discussed will save agents a huge amount of time and improve customer satisfaction.

    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)
  9. Write back Disposition and notes to RCX Contact Card

    Enterprise Account ID: UID: 813377035
    Feature Request Summary: Write back Disposition and notes to RCX Contact Card
    Current Functionality: only support AI Summaries
    Ideal Functionality: Write back Disposition and notes to RCX Contact Card
    Opp Link: SFDC Opp Link: https://rc.lightning.force.com/lightning/r/Opportunity/006TU00000Eg3B7YAJ/view

    Business Justification -- Since we dont support all integration this willl help the agent identify the last reason for call aside from AI Summaries

    https://jira.ringcentral.com/browse/INIT-25003

    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)
  10. It would be helpful for our customers to have an option to setup a temporary greeting without creating a new workflow or adjusting their current workflow.

    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. The customer is requesting enhanced visibility for callback queues within the RingCX Real-Time Dashboard. Currently, while the Real-Time Inbound widget provides an overview of total queued interactions, it does not distinguish between active queued calls and callback-queued requests. As a result, both interaction types are grouped together, limiting the ability to accurately monitor callback activity in real time. The customer is specifically looking for a configurable widget or dashboard enhancement that allows callback-queued requests to be displayed separately from active calls, enabling clearer insights into queue distribution (e.g., distinguishing how many are active vs. callback requests at any given 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Description
    The current automatic transcription quality in English within RingCX is not accurate enough for operational use. Users frequently encounter incorrect or incomplete transcripts, which limits the usefulness of the feature in daily workflows.
    Because of these inaccuracies, users often need to manually recreate tasks, notes, or summaries to save time—defeating the purpose of automated transcription. This reduces efficiency and impacts the overall user experience.
    Request
    We would like to request improvements to the automated transcription engine, specifically for RingCX, including:

    Higher accuracy in recognizing spoken English/French/Italien/Spanish/German (various accents, speeds, and environments)
    Better handling of technical or domain-specific vocabulary
    More…

    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)
  13. Feature Request: Persistent Login for RingCX Salesforce Agent
    Description:
    The RingCX Salesforce Agent logs users out whenever they switch tabs or applications within Salesforce, requiring repeated logins and disrupting workflow.

    Current Behavior:

    Users must log in again after navigating to a different tab or application.
    This causes delays and frustration.
    Proposed Enhancement:

    Maintain login sessions while users switch tabs or applications.
    Keep authentication valid for the duration of the Salesforce session unless manually logged out.
    Business Impact:

    Reduces login fatigue and improves efficiency.
    Minimizes workflow disruptions.

    17 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. the customers would like to be able to manage answer mode in different ways depending on the direction :
    have the ability to enable/disable inbound auto answer
    in parallel have the ability to enable/disable outbound auto answer

    so even if you disable the autoanswer for inbound, you can still "autoanswer" outbound calling

    the impact:
    when receiving a call they should be able to manually answer (1 click)
    when initiating the call they should be able to dial the number without the need to click on 2 different buttons (the dial button + answer button) (1 click - the wished behavior-…

    52 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. When a call enters wrap up time, set the status to Wrap Up, then when wrap up time ends, set the agents stats to Available. Its misleading to have the status as Available during wrap up time thats set on the back end.

    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)
  16. *Summary

    Introduce a platform-level capability to enforce conditional Caller ID behavior for internal calls during warm transfers and consultations, ensuring consistent Caller ID presentation across RingCX and RingEX environments.

    *Problem Statement

    During warm transfers or consult calls—whether between RingCX agents or from RingCX to RingEX users—Caller ID presentation may vary and display RingEX Born Super Admin name, queue numbers, site numbers, or system-generated identifiers. This inconsistency creates confusion during internal collaboration. However, once a call is fully transferred or taken over, the receiving party must see the original customer identity to preserve service continuity.

    *Proposed Capability

    Implement call-state–aware Caller ID…

    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)
  17. Need a way to query data to identify what % of calls are recorded.

    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)
  18. The German localization for the "Post Call State" setting in the Admin interface is currently nonsensical.

    Current Label: "Anrufstatus veröffentlichen" (Literal translation: "Publish call status")

    Context: This field determines the agent's status immediately following a call (e.g., "AVAILABLE"). The current translation is misleading and does not align with standard telephony terminology.

    Please update the German string to accurately reflect the function of the field.

    Proposed Translation: "Status nach dem Anruf" (Status after the call)

    Location: Routing > Voice queues and skills > [Queue Name] > General

    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)
  19. Have the ability to see to which ext the call was transferred if the user will transfer the call from RingCX to RingEX. Instead of showing UC Voice or UC.

    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. When callers are waiting in a queue, RingCX can only play back the estimated wait time once. Other phone systems have an option to let callers know the estimated wait time every X seconds, such as once every 45 seconds, so they know how long it is before their call is answered.

    We would like to see RingCX updated so it allows us to teller our callers how long it is before their call is answered more than just one time.

    Also, there is a RingCX configuration that lets the callers know their position in the queue, such as "caller…

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