1496 results found
-
Update Documentation – Remove/Revise “Global Audio” Instructions
Article Reference:
https://support.ringcentral.com/article-v2/Uploading-an-audio-file-in-RingCX.html?brand=RingCentral&product=RingCX&language=en_USSummary:
Request to update the existing support documentation for uploading audio files in RingCX by removing or revising references to the “Global Audio” option to prevent confusion for users who do not have access to this feature.Problem Statement:
Customers following the current documentation encounter confusion when instructed to use the “Add Global Audio” option, as this feature is not visible or available in all accounts or environments. This leads to:Misalignment between documentation and actual UI
Increased support inquiries
Delays in customer configurationCurrent Behavior:
The article includes steps referencing the Global Audio feature, which is…1 vote -
RCX Allow Agent to Open the Queue when they are Logged In
RCX Allow Agent to Open the Queue when they are Logged In. We do not want them to configure business hours but something that can be managed on their end once given a permission by an Admin.
2 votes -
Export DNC list
Add the option to download/export the DNC list in RingCX
2 votes -
Visibility of Pending Messages Count per Conversation
Requested Evolution / Expected Outcome
Restore or introduce the ability for agents to see the number of pending/unread messages directly at the conversation level, for example by:displaying the pending message count in the conversation bubble in task mode,
or exposing a clear indicator within the conversation list or header,
ensuring the count updates in real time as messages are processed.Business Impact
Without this evolution:task prioritization is less efficient,
workload balancing across conversations and agents is more difficult,
overall handling time and agent efficiency may be negatively impacted.Providing clear visibility of pending message counts would significantly improve…
1 vote -
Consistent Conversation Identification Between Historical Exports and New Reporting
Expected Outcome / Requested Evolution
Provide a solution that enables reliable conversation matching between historical exports and the new reporting, for example by:exposing a stable and persistent conversation/thread identifier shared across legacy exports and the new reporting module, or
providing a mapping mechanism between historical contentthreadid values and the new conversation identifiers (UID / UUID), or
adding a field in the new reporting that explicitly references the historical conversation identifier.Business Impact
Without this evolution:historical vs. current conversation analyses cannot be reconciled,
longitudinal KPIs and trend analysis are not reliable,
manual and error-prone reconciliation is required.1 vote -
Consistent Agent Identification Across Historical and New Livechat Reporting
Expected Outcome / Requested Evolution
Provide a solution enabling reliable agent matching across historical and new reporting data, for example by:exposing a stable and unique agent identifier shared across legacy exports and the new reporting module, or
providing a mapping table between historical agent IDs and the new identifiers (UID / UUID), or
exposing an additional field in the new reporting that allows reconstruction of this mapping.Business Impact
Without this evolution:agent-level historical analyses are incomplete or inaccurate,
trend analysis before vs. after the reporting migration is not reliable,
manual reconciliation work is required, with a high risk…1 vote -
Ring CX Place in Queue announcement to be able to play multiple times
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.
4 votes -
Callback Flow Improvement
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 -
Expose API data when a call is connected
We recently ran into an issue where a configured Start Recording node in an Agent Script was triggering before the ADD SESSION event. This caused the recording event to fail, and the call would not be recorded. We solved this by adding a half second forced wait in the agent script. It would be beneficial to expose this information in Audit Logs or similar when the call connects, so that if this were to happen again it would be easily diagnosable.
3 votes -
Improved Callback Reporting and Functionality for Early Caller Disconnects
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)…3 votes -
Agent Script: Allow configuration to limit the width of an agent script, so agent script takes up less screen space
When using Agent Scripts with the Embedded Agent within a CRM (e.g. Salesforce), you cannot limit the width of the RCX Agent Script panel. In Salesforce, specifically, with the Embedded Agent adaptor in "Docked" mode, the Agent Script panel takes up like, a third of the screen real estate - even if your script only consists of a tiny, 30-pixel "HANGUP" button. If you switch to "Undocked" mode, as soon as you answer the call, the size of the Agent adaptor window expands radically to accommodate the extra-wide Agent Script - again, even if the only script element is a…
-
Answering%20a%20call%20in%20Salesforce%20-%20undocked%20-%20agent%20can%20manually%20shrink%20down%20call%20window%20after%20answer%20(problem%20happens%20again%20on%20next%20call).png 159 KB -
Answering%20a%20call%20in%20Salesforce%20-%20undocked%20-%20upon%20answering%20call%2C%20agent%20script%20expands%20to%20take%20up%20half%20the%20screen.png 132 KB -
Answering%20a%20call%20in%20Salesforce%20-%20undocked%20-%20before%20receiving%20a%20call.png 250 KB -
Answering%20a%20call%20in%20Salesforce%20-%20docked%20-%20agent%20script%20takes%20up%20left%20third%20of%20screen.png 153 KB
1 vote -
-
Digital interaction routing to next available agent
Route digital interactions to the longest available agent, regardless of how many concurrent interactions each agent can handle. For example, we have agents set to two concurrent digital interactions, and when two come in they both go to the same agent. We would want one to go to the first, then the second to go to the next available agent. An additional option to choose to have this work for voice interactions as well could also be useful.
2 votes -
Call queue notifications
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.
5 votes -
Admins do not have access to users' AI notes or transcripts.
current limitation with AI notes and transcripts is that, while we store them securely and do not share them externally, Admins do not have access to users' AI notes or transcripts.
6 votes -
Add Digital Interaction Details Report with Media/Attached Files
We are requesting a report for Digital Interactions (such as chat, SMS, email) that gives us a full view of the details of the interaction, which includes transcripts, media, and other attachments.
1 vote -
Ability to Customize AI Compliance Prompts
Summary:
Request to introduce the ability to customize AI compliance prompts within the RingCX Admin Portal.Current Behavior:
At present, AI compliance prompts can only be enabled or disabled via:
Admin → Settings → Accounts → Compliance PromptsThe available prompts include:
Recording Announcement
AI Quality Management Announcement
AI Processing AnnouncementThere is no option to modify or customize the content of these prompts.
Problem Statement:
Organizations have varying legal, regulatory, and branding requirements depending on their location and industry. The inability to customize compliance prompts limits flexibility and may result in:Misalignment with local legal wording requirements
Inconsistent customer…2 votes -
Dispositions-based Purge Management
Dispositions are not attached to messages, conversations, or threads in the same way as categories were in Engage Digital. As a result, it is currently not possible to apply retention or purge rules based on Dispositions.
We would therefore like to submit an evolution request to enable the ability to:Use Dispositions as criteria for data retention and purge policies
Apply selective purges based on specific Dispositions, similarly to what was previously possible with Engage Digital categoriesThis evolution is critical to ensure:
Compliance with data retention requirements
Operational continuity compared to Engage Digital
Better control over data lifecycle management…1 vote -
Disposition for manual outbound calls
Please add the option to add dispositions to manual outbound calls where "default" is selected on the "queue" dropdown
2 votes -
AI Notes & Transcript data retention policy
We would like to have a separate data retention policy for AI Notes & Transcripts
3 votes -
RCX AGENT DIALPAD
RCX Agent Dialpad should be added on Agent Tab in RingCentral App.
This means that the Dialer/Dialpad within RingCX Tab has RingCX CallerID's by default and will have no option to use RingEX lines as OB Caller ID. This will enhance and minimize agent errors when making an outbound call.12 votes
.png){kind=link}
- Don't see your idea?