147 results found
-
Allow Hiding Metrics on a Historical Report
Ability to hide a metric on a report. For example, I use 2 metrics to calculate a custom metric, but I don't want those visible on the finished report.
7 votes -
Improve Historical Reporting: Exclude Deleted Agents and Queues past their deletion date
When an agent or queue is deleted, the historical data associated with them should ideally no longer be displayed or should be clearly marked as inactive past their deletion date.
If multiple agents are leaving and are removed from RingCX, manually filtering them out from historical dashboards is indeed very difficult and inefficient.
Hence, the agent and queue details should be cleared off after the date they are deleted from the portal
12 votes -
Interaction Search
Interaction Search feature like on CXOne. Instead of pulling up a report and manually look for the interaction.
4 votes -
Business Hours Filter in RingCX Analytics
Summary:
- We would like to request the ability to apply filters in RingCX Analytics that limit data to business hours only, in addition to the existing date-based filters.Current Limitation:
- At present, Analytics filters in RingCX can be applied based on date ranges, but there is no option to restrict reports to specific hours of the day (e.g., business operating hours). This makes it difficult to generate accurate performance reports that reflect true operational hours.Requested Enhancement:
- Add a filter option that allows users to:
- Apply reports to defined business hours (e.g., 8:00 AM – 5:00…2 votes -
RingCX Inbound Queue Reconciliation & Unclassified Exit Visibility
We request a native, system-calculated metric in RingCX Analytics that automatically reconciles the total Queue Inbound Interactions (Presented) against all final outcomes (Answered, Abandoned, Callback, and Deflected). Currently, a significant volume of interactions falls into a catch-all "Other" bucket due to system-level disconnects or unclassified IVR exits, requiring complex manual reconciliation. This enhancement should provide a clear, granular breakdown of Unclassified Queue Exits and a pre-calculated "Total Outcomes" column to ensure every presented call is accounted for with 1:1 accuracy without manual spreadsheet work.
3 votes -
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 -
Include Dispositions in “All Categories” field in conversation exports
In RingCX, Dispositions have replaced Post-Qualifications previously used in Engage Digital.
With Engage Digital, Post-Qualification values were correctly included in conversation/thread exports via the “All Categories” field.
The selected Disposition by agent should appear in the “All Categories” field, exactly as Post-Qualifications did previously in Engage Digital.1 vote -
External Agent ID missing from agent export files (CSV / Excel) and reporting
The External Agent ID field is correctly configured and populated in agent profiles within RingCX Admin, but it is not included in agent export files (CSV / Excel).
This prevents the use of exported agent data for downstream systems and reporting.1 vote -
Forced logout or manual logout reporting
To have a report on whether an agent was forced to log out by a supervisor or system log out due to a network issue, or manually log out on their own.
4 votes -
Add team filter to “Real‑Time Digital” and “Real‑Time Agent” views
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 -
Identify percentage of RingCX calls that are recorded
Need a way to query data to identify what % of calls are recorded.
3 votes -
RCX | Same day caller reports
Looking for a way to pull up a reporting solely for Same day callers that separates the new/potential callers with the callers that are calling multiple times in a day.
4 votes -
Historical Reports for Callback Requests for the next day
Ability to have a Historical Reports for Callback Requests for the next day. The current reports only show callback requests already made
1 vote -
Dashboard Sharing
Please add the option to edit a real-time dashboard for all users it's shared with, and a way to view whom a dashboard has been shared with. This would greatly improve the experience for admins and make it easier for them to create and share dashboards with supervisors.
4 votes -
Consolidation of REX and RCX Analytics
Currently, data is fragmented across two platforms, creating a disconnected view of agent performance. Consolidating these reports is essential to ensure a single source, eliminate manual data reconciliation, and provide leadership with a holistic view of inbound/outbound calling productivity.
2 votes -
Feature Request: Custom Survey Dashboard (Simplesat-like Experience)
• Summary
Request the development of a Custom Survey Dashboard to provide a simple, centralized, and actionable view of survey performance, similar to the functionality offered by Simplesat. The goal is to make it easy for stakeholders to quickly understand what data is available, how surveys are performing, and to drill down into individual feedback.
• Business Objective
Improve visibility into survey results across multiple support groups
Reduce time required to interpret survey data
Enable data-driven decisions through clear metrics and accessible feedback
• High-Level Requirements
- Dashboard Overview
A top-level Overview that summarizes all groups being measured
At-a-glance visibility into…
2 votes -
Backup
Backup / export and restore / import options for
- voice queues
- digital queues with agent mappings,
- roles,
- user with queue mapping including rank or skills
- time settings.
the existing export functions, e.g. flows covers only a small part of settings.7 votes -
Analytics Real-Time Dashboards - Add a Real-time Agent Widget Organized by Queues
It would be helpful to be able to create a widget/tile for individual inbound queues. Each row of the widget would show the agent name and their interaction data just like in the Real-time agent widget. Except we'd be able to instantly see the names of all the agents signed into each queue as these widgets would dynamically update as agents are assigned/unassigned to the queues.
There is an existing "Inbound" widget which only "provides a row of overall metrics for each inbound queue"
1 vote -
Enhanced Agent Dashboards for Queue Visibility and Custom Statuses
Currently, RingCX agents have limited visibility into calls across queues, agent availability, and overall queue activity. While supervisors can see more detailed information, agents themselves cannot access this data without compromising security. Existing workarounds, such as using JWT tokens, are not viable as they grant access to admin settings and analytics, creating a significant security risk.
Agents would benefit from a dedicated dashboard that provides real-time visibility into calls, queue status, and agent availability without exposing KPIs or sensitive information from other agents. This would also support coordination among agents for breaks, shift changes, and coverage planning.
We request the…
3 votes
- Don't see your idea?