245 results found
-
Increase the maximum capacity limit for RingCX Analytics Historical Reports beyond the current platform limitation of 80,000
Request: Increase the maximum capacity limit for RingCX Analytics Historical Reports beyond the current platform limitation of 80,000 rows, 80,000 columns, or 80,000,000 cells. According to the current RingCX Analytics platform capacity documentation, reports exceeding this limit only display partial results, with the option to export the full dataset as a raw CSV file.
Business Justification: The customer generates large volumes of historical analytics data and is reaching the current reporting limits. The existing capacity restricts their ability to view and analyze complete datasets directly within RingCX Analytics, resulting in additional manual effort to export, process, and review data externally.
…
2 votes -
Realtime reporting to report on Categories
Placeholder to provide more details...
2 votes -
transfer
Include Agent Name on Transfer Segment in Interaction Details Report
Request Summary:
When an agent initiates a transfer (especially a warm transfer) during an active call, the Interaction Details Report splits the call into two segments under the same UII. However, the second segment (the transfer attempt) does not display the agent name, resulting in incomplete data when filtering by agent in the report. The customer requests that the agent name be captured for all segments of a call—including transfer attempts—to ensure accurate reporting.
Current Behavior:
• The agent's name is shown for the initial (inbound) segment.
• During a…70 votes -
Enhanced Call Termination Attribution with Contextualized Termination Reason
Summary:
Improve call reporting by clearly separating true disconnect source attribution from termination reason (routing/system event context), ensuring customers can accurately interpret why a call ended and what system event preceded it.Problem Statement:
The current “Termination” field in the Inbound Call Detail Report can reflect an internal routing or system event rather than the actual disconnect source. This creates confusion because the same field is often interpreted as the definitive reason the call ended.In many cases, customers cannot distinguish between:
- the actual disconnect event (who ended the call), and
- the system/routing event that occurred immediately prior…5 votes -
Include Customer DTMF Inputs in RingCX Queue Reporting
Business Need / Context:
We currently have reporting visibility for DTMF (keypad) inputs while a caller is navigating the initial IVR/Workflow. However, once a call enters a queue, any DTMF inputs made by the customer (e.g., pressing a digit to request a callback, change priority, or trigger an automated action) are not captured in any standard, pullable reports.Currently, our team can only verify queue DTMF inputs by running a manual backend trace on individual calls using internal tools. This is highly inefficient, delays troubleshooting, and limits our ability to track customer behavior and queue performance at scale.
User Persona…
3 votes -
Support Combining Agent State and Call Metrics in a Single Custom Analytics Report
Enable Agent State and Call/Interaction Metrics to Be Combined in a Single RingCX Custom Analytics Report
Product Area
RingCX Analytics / Custom Analytics
Request Type
Feature Enhancement
Customer Request
Customers would like the ability to create a single custom analytics report containing both Agent State metrics and Call/Interaction metrics.
Currently, when creating a custom analytics report, the available metrics/KPIs are dependent on the underlying data source. Agent State data and Call/Interaction data are derived from different datasets, preventing users from combining metrics from both sources within the same custom report.
Current Limitation
When creating a custom analytics report:
Selecting Agent…
2 votes -
Fix Inverted ANI / DNIS Mapping on Outbound Reports in RingCX
In RingCX Interaction Details reports, outbound call records invert standard telephony definitions:
-The ANI column displays the customer/lead number called.
-The DNIS column displays the outbound Caller ID presented by the dialer.
-Under industry standards, ANI is the calling party (Caller ID), while DNIS is the number dialed.Business Impact :
-Compliance Confusion: Auditing tools and compliance teams check the DNIS column to ensure calls are within legal daytime hours; inverted columns make fully compliant calls look like illegal curfew violations.
-Wasted Support Time: Administrators and engineers spend weeks troubleshooting non-existent dialer bugs simply because the report mislabels the lead's…1 vote -
User list actually includes all users
Currently, the User List historical report does not include all of our users. I'm unclear on why that is the case, but we are about 20% short when running the report.
I suggest that the user list historical report actually include all the users on the tenant.
1 vote -
Delete agent's old name from the agent full name filter
When an agent's name is edited, the old name stays on the CX analytics agent full name filter. All interactions associated to the agent will be associated to the new name which makes the old name useless.
2 votes -
RingCX Feature Request: Historical HAR and Console Log Capture for Intermittent Issue Troubleshooting
Summary
• Enhance the diagnostic tooling to allow capture and retrieval of historical browser logs, including HAR (HTTP Archive) and browser console logs, to help investigate intermittent issues that cannot be reproduced on demand.
Problem Statement
• Currently, our troubleshooting tools primarily capture agent logs in real time. However, they do not include browser-level diagnostic data, such as:
HAR (network request logs)
Browser console logs
• When customers report intermittent issues, the following challenges arise:
The issue occurs randomly and cannot be predicted.
HAR and console logs must be manually enabled before the issue occurs.
In many cases, the issue…
6 votes -
RCX | Increase data download
have the ability to increase the data download in RingCX analytics from 80,000 to higher.
5 votes -
Reporting Enhancement Request – Identification of Manually Rejected Inbound Calls
I would like to request a reporting enhancement to identify instances where an agent has manually rejected an inbound call.
The existing RNA (Ring No Answer) report provides visibility of calls that were not answered; however, it does not differentiate between calls that timed out and calls that were deliberately rejected by an agent. Having access to this information would improve call handling analysis, provide greater transparency, and support agent accountability.
RNA calls recorded in less than 30 seconds cannot automatically be assumed to be caller-abandoned calls. The RNA metric includes both missed calls and calls that have been actively…1 vote -
ajouter un filtre permettant d'exclure de la visibilité des superviseurs certains échanges
Objectif métier :
Améliorer la pertinence des tableaux de supervision en masquant les conversations n’ayant reçu aucune réponse utilisateur. Cela permet d’éviter que les superviseurs soient exposés à des tâches non traitées ou non traitables, qui n’apportent pas de valeur au suivi opérationnel.Résultat attendu :
Exclure les échanges dont userrepliescount = 0.
Afficher uniquement les conversations ayant fait l’objet d’au moins une réponse utilisateur.
Réduire le bruit dans les tableaux de bord.
Faciliter le suivi des activités réellement engagées et améliorer l’efficacité de la supervision opérationnelle.1 vote -
Show Who Has Clicked "Start Dialer" on the Real-Time Dashboard
Issue :
The problem is that the real-time supervisor dashboard does not show whether a user or agent has clicked on the "Start Dialer" button or not.What is the Proposed Solution?
We want to add a new column to the Real-Time Agent Monitoring Dashboard called "Dialer Status." This column will track whether an agent has initiated their dialing session or not based on backend indicators:
Dialer Clicked: The system tracks that the agent has actively clicked the button to initiate the dialer workflow, indicating they are actively participating in the campaign.
Dialer Not Clicked: The agent is logged in…3 votes -
Restore Historical Dashboard Report Scheduling
Product:
RingCX – Historical Dashboard / AnalyticsRequest:
Bring back the ability to schedule and automatically deliver reports generated from the RingCX Historical Dashboard.Current Behavior:
The RingCX Historical Dashboard currently does not provide a Schedule option for dashboard reports. Users can view and analyze historical data, but they cannot configure the dashboard to automatically generate and deliver a report on a recurring schedule.Expected Behavior:
Provide a Schedule option within the Historical Dashboard that allows users to configure recurring report delivery.Suggested Scheduling Options:
Daily
Weekly
Monthly
Selected days of the week
Configurable time and timezone
Recipient email addresses…1 vote -
Add Caller's Name for Inbound Call Details Report
To add a column or filter that would show the name of the contact number they saved through the contact information section in the Inbound Call Details report.
There's an existing Caller's Name column available for Interaction Details, but it only shows the CNAM of the phone number and not the one saved through the contact information section.
5 votes -
check what number given by the customer in the call back request
A report to check what number given by the customer in the call back request
Additional details for the feature that you are requesting:
There is no way to continue to track a call if the caller requests a call back to a number that they didn’t call from.What is your use case for this feature request?
To figure out what happened to a certain call/s without having to ask the caller what number they used when they enter it into the system.What problem are you trying to solve or what problems does the current functionality cause?
Streamlining…
2 votes -
Real-Time Dashboard Refresh
Allow the users to see the real-time data of the dashboard in any circumstances (e.g, forgot to logout properly) they should still see updated real-time dashboard.
4 votes -
Feature Request: Add Reporting for Abandoned Chats in RingCX
Feature Request: Add Reporting for Abandoned Chats in RingCX
Summary:
Request to introduce a reporting feature in RingCX that captures and displays metrics for abandoned chats — similar to how abandoned calls are tracked in voice queues.Details / Description:
Currently, RingCX does not provide any native reporting or metrics that log abandoned chat interactions, such as when a customer initiates a chat but disconnects before an agent accepts or responds.
This limits visibility for contact center managers who need to measure missed engagement opportunities and optimize staffing and response strategies.Use Case:
Supervisors and analysts need the ability to…8 votes -
Retrieve deleted RingCX Custom Report
Implement a deleted folder or archive system when removing custom reports from the Historical Reports/Dashboard in RingCX Analytics.
6 votes
- Don't see your idea?