1449 results found
-
Local bucket/connect based RingCX analytics report
Local bucket/connect based RingCX analytics report. A kind of report/custom report that will show the usage of their local connect/bucket.
9 votes -
Qualified Dispositioned Break out/Drop Down Report
Dialer: They would want a complete list of positively dispositioned lead that generated. Customer stated that they would want a separate list/stand alone reporting (Specified Qualified disposition excel/.csv file).
8 votes -
Warm Transfer Calls From RingEX USers to RingCX Agents
To allow warm transfer calls from RingEX users to RingCX agents. Currently, it only works with Cold transfers.
4 votes -
To Have Start and End Time Attributes in RingCX for Salesforce
We would like to request the addition of attributes in RingCX for Salesforce that capture both start and end times. This functionality would provide better tracking, reporting, and integration with workflows, ultimately improving visibility and efficiency for users.
7 votes -
Allow RingCX alerts to be sent to multiple selected users
It would be highly beneficial if RingCX alerts allowed Admins to select multiple users as recipients within a single alert configuration.
At present, alert routing appears to require either:
Single-user targeting, or
Separate configurations per user
This increases administrative overhead and makes alert management more difficult at scale.
Enhancing this to support multi-user selection would:
Reduce duplication of alert configurations
Improve scalability for larger teams
Ensure consistent notification distribution
Simplify ongoing maintenance
This is especially important for operational alerts that need to notify multiple Supervisors or stakeholders simultaneously.
2 votes -
Automatic Queue Log Out After Configurable Inactivity / Time Threshold
It would be highly beneficial to introduce a configurable automatic log-out feature for agents after a specified time threshold (e.g. end of shift or defined inactivity period).
Key requirements:
Admin-defined time threshold
Agents on an active call at the time of trigger would not be interrupted
Once the active call ends and the agent submits the disposition, they should not return to Available, instead, they should automatically be logged out of all queues
This would:
Improve queue governance and SLA integrity
Prevent agents remaining accidentally logged in after shifts
Reduce manual supervision effort
Support stronger adherence and workforce management controls
…
2 votes -
Allow transfer of interactions to a specific agent (RingCX)
In RingCX, interaction transfer is currently only possible to a specific queue (requeue).
Unlike Engage Digital, it is not possible to transfer an interaction directly to a dedicated / named agent.
This limitation is blocking for some operational use cases (expert handling, continuity of service, supervisor routing), where transferring to a specific agent is required.Expected evolution:
Enable the ability to transfer an interaction directly to a selected agent by name, in addition to the existing skill-based and queue-based transfers.1 vote -
Simultaneous Ring option for Call Queues/Skill
It would be nice to have an option to ring all agents simultaneously under a Call Queue. This would:
• Provide the possibility of a shorter wait time for callers
• Avoid caller abandons
• Help in user data analyzation on who picks up the most/least calls19 votes -
Feature Request: Display Call Recording Storage Usage in RingCX
Customers currently cannot view the total disk space used by call recordings within RingCX, as storage is managed only by retention timeframe. Providing a feature that shows the actual storage size (in gigabytes) of call recordings per account would help customers better manage their storage, forecast costs (especially when archiving offsite), and optimize retention policies. This visibility would improve transparency and enhance customer experience.
8 votes -
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 -
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 -
RingCX - Option not to count outbound queue calls within inbound reporting stats
Currently, if an agent has an inbound queue assigned to them in the 'manual outbound default queue assignment' field, then manual outbound calls made by that agent are counted in analytics as inbound calls against that inbound call queue.
This causes some confusion in reporting and skews stats related to inbound calls to the given call queue.
Customers would like an option to differentiate between inbound and outbound calls associated with an inbound queue, or at least manual outbound calls associated with an inbound queue should not be counted on inbound reports & dashboards.
30 votes -
Enhanced Playback Controls & Dual-Channel Visualization for RingCX Recordings.
Please consider an update to the RingCX Call Recording interface to include advanced playback navigation (Fast Forward/Rewind) and a visual "Dual-Channel" waveform. Currently, the playback experience requires manual scrubbing and active listening to distinguish between speakers, which slows down the auditing and coaching process.
Key Feature Requests
Granular Playback Controls: Add dedicated "Skip Forward" and "Skip Backward" buttons (e.g., in 5 or 10-second increments). This allows users to quickly bypass hold music or repetitive disclosures without losing their place.Split-Track Visualization (Agent vs. Customer): Implement a visual waveform or timeline that clearly distinguishes the Agent's audio from the Customer's audio.
…
3 votes -
RingCX callback in queue
Significantly improve the RingCX callback in queue experience for callers. Here's a breakdown of the issues and how to address them, focusing on making the text-to-speech (TTS) more natural:
Key Issues Identified:
Mixed Gender Voices: The callback message currently starts with a male voice and switches to a female voice. This can be jarring and unprofessional.
Outdated/Robotic Text-to-Speech: The TTS used to read and verify the phone number sounds old and unnatural, which negatively impacts the caller experience.
Solutions and Recommendations:- Unify and Improve Voice Consistency:
Custom Audio Recordings: The most direct way to ensure consistent and natural-sounding voices is…
13 votes -
Integration of RCS (Rich Communication Services) as a Communication Channel in RingCX
Summary:
We formally request the addition of RCS (Rich Communication Services) as a supported communication channel within the RingCX platform. This feature would enable businesses to deliver a next-generation mobile messaging experience, significantly enhancing digital engagement capabilities beyond traditional SMS and MMS.What is RCS?
RCS is a modern messaging protocol designed to replace SMS and MMS, offering rich media capabilities and real-time interaction features within a user’s native messaging app. Unlike SMS, which is limited to plain text and dependent on cellular networks, RCS operates over IP (internet protocol), allowing for a more robust and versatile communication experience via…11 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 -
-
Outbound Default and Custom Lead Field Order/Ranking
Clients need the ability to define the order in which standard and custom lead fields show within the agent interface. When creating custom lead fields "One", "Two", and "Three", the order shown to the agent is identical to the order in which custom fields were created (most likely by chance); however, when adding "six", "five", and "four", the order in which fields show has no logic as these show in the order "six", "four", "One", "Two", "five," and "Three." Generally, customers want and need the ability to set a rank in the same way as exists for disposition.
14 votes -
Add time based variable to holiday configuration
Managing segmented or partial holidays in RingCX Workflows and Administration is difficult. Admins have to create the holiday and then add multiple scheduling objects to the IVR Workflow to split out partial times during a specific date.
Adding the ability to specify times of day for a configured holiday would allow a customer to apply routing logic to a specific time period for a specific date.Example:
- On Oct 1, the service department is closed from 12pm-1pm
- Between 12 and 1 on Oct 1, they want calls to route to the operator instead of the service departmentIn…
63 votes
.png){kind=link}
- Don't see your idea?