211 results found
-
Feature Request: Option to Remove uiicall1 Column from RingCX Survey Report
Description:
Currently, the uiicall1 column in the Survey Input section of the RingCX survey report is mandatory and cannot be removed. Some customers have requested the ability to customize the report layout, including the option to remove this column if it is not relevant to their reporting needs.Proposed Feature:
Allow users to optionally hide or remove the uiicall1 column from the survey report.
Ensure that removing the column does not affect report functionality or data integrity.
Include an admin setting or report customization option for this purpose.
Business Justification:
Providing this flexibility will improve the usability of RingCX survey…1 vote -
Feature Enhancement Request – Token-Based Access for RingCX Historical Reports
Subject: Feature Enhancement Request – Token-Based Access for RingCX Historical Reports
Description:
Currently, RingCX Analytics provides token-based access for Realtime Dashboards, enabling secure external display. However, this functionality is not available for Historical Reports, which limits the ability to securely and selectively share historical data with authorized users.Use Case / Business Impact:
Organizations need access to historical RingCX data to generate reports and analyze trends.
Without token-based access, exporting historical reports requires manual CSV/XLS downloads or scheduled email/FTP deliveries, increasing operational overhead and delaying reporting.
Token-based access would allow only specific users to view these reports, preventing unrestricted access…
1 vote -
Agent acceptance rate in Inbound Queue Overview report
For the Inbound Queue Overview report (in the standard historical reports), I would suggest that the agent acceptance rate in the entire column shall display or show the actual percentage of staff's performance in decimal point or digit number, instead of rounding up the tenth digit to whole number. For example, if the interactions handled (7416) is divided by the interactions assigned (7438), then the agent acceptance rate should be 7416/7438 = 99.7 % (not 100% by rounding it up ). Hope Ring Central team can consider this idea and modify the data accordingly to meet our business's need. Thank…
2 votes -
Feature Enhancement Request – Support for Dynamic Number Insertion (DNI)
Summary:
Requesting the addition of Dynamic Number Insertion (DNI) support within RingCentral to improve call tracking and marketing attribution capabilities.Details:
Current Status:
No native support or KB documentation found for DNI on the RingCentral support site.
A workaround exists by leveraging third-party solutions (e.g., CallRail) that integrate with RingCentral.
Enhancement Value:
DNI enables businesses to assign unique phone numbers to website visitors based on their traffic source (ads, search, referrals, etc.).
Improves marketing analytics and ROI tracking by linking inbound calls to specific campaigns.
Reduces dependency on third-party tools and ensures more seamless workflows if supported natively.
Request:
Enhance…2 votes -
Agent dashboards
Would like agents to be able to see other agents on their dashboard so they can see who is at lunch, who is currently on a call..etc..
5 votes -
Add Queue Time In Interaction Time if the Call Became Abandoned
Please add the queue time in the interaction time for calls that resulted to abandoned.
2 votes -
Feature that links DID and CX data in one report
Current Challenge: Currently, DID number analytics are available in the EX report, while CX analytics are shown in a separate CX report. This separation makes it difficult to identify participants in a DID call when reviewing the CX report.
To resolve this, is it possible to consolidate both datasets into a single report? Ideally, we should be able to pull both DID and CX analytics from one unified source or report, enabling a more comprehensive view of call activity and participant details.
3 votes -
SLA % calculations - create inbound presented or remove outbound from calculations
Currently IB queue SLA% is calculated using the "Presented" metric -- "Presented" is calculated using both IB calls presented to an agent AND OB session/Agent Leg connection calls. -- This inherently skews SLA% as the OB session/Agent Leg connection calls are not true/real calls "presented" to the agent. The SLA% should calculate only IB calls; e.g. if a customer has a 30 second SLA set and 100 calls come into a queue (90 are answered prior to 30 seconds) their SLA% (adherence) would be 90%.
4 votes -
Able to customize the header of the columns | Custom Columns on the RingCX Analytics page
Wanted to be able to customize the names of the columns on the RingCX Analytics page. To be able to edit the names of the columns or allow the customers to be able to change the label of the columns on their RingCX analytics page
2 votes -
RingCX Agent list_The customer want to pull up lists of active agents using the RingCX platform.
The customer is looking for an option to pull up lists of active agents using the RingCX platform.
2 votes -
product name
Customer wants to associate Phone NumbersDNIS to the Product Name attribute. Currently, Product Name is tied up to the Product Type: IVRs and Voice Queue only.
Historical Dashboard > Billing Period Account Usage > Usage Details
1 vote -
real time dashboard to show outbound calls
In the past I was able to create a widget on my real time dashboard that showed how many outbound calls an agent made. That option is no longer available and is needed for me to measure productivity in real time.
3 votes -
Adding the "Live" metric on the custom dashboards On RCX Analytics Live Dashboards
When you create a Real Time dashboard in RCX Analytics for product IVR, you can find the IVR widget including few data fields like "Live", "Presented", Connected", etc...
If you want to add a custom widget displaying IVR data fields
- Widget type = Number
- Product = IVR
When you want to select Data fields, the field "Live" is not included in the list, you can find ONLY, all the others like "Connected", "Presented" but not "Live"
Otherwise you can find "Live" data field when you configure rules after widget creation.1 vote -
Display ANI Location (City and State) in RingCX Real-Time Dashboard
Request to display the caller's location (city and state) based on ANI in the RingCX Real-Time Dashboard to help agents and supervisors gain better context during live interactions.
3 votes -
Robust Wallboard Functionality
Add more comprehensive capabilities in the RingCX Dashboards and allow them to be shared externally.
RingCX Wallboard is required to have the below features added:
Images (i.e. Brand Logo)
Scrolling / Static Text Boxes (Manual Announcements / Information updated)
Individual Agent Statistics (Not Table View) – (Offered, Answered, Outbound, Status, Time etc)
Calculated Statistic Values (Example: Presented – Deflected)
Coloured/Alerting Boxes based on Statistics (Number or Text)
7 votes -
1 vote
-
SMS Historical Reporting
Would like the the ability to see History of all texts sent and received from a specific dispatcher.
Today: you can pull by channel but not on an individual basis.3 votes -
Real time dash board for dialing campaign
We need a real time dashboard where we can find the phone number that's being dialed out by our outbound campaign and for it to display the actual DNIS.
1 vote -
RingCX_Improvement for Country ANI / Country Geolocation ANI Metric
Goal: Customer needs to have a report where it can indicate how many calls they received for each country
-We tried to use Country ANI and Country Geolocation ANI Metric, however, it is only counting the number of call from a specific international ANI and not the total number of calls per country.
-We also tried to filter by ANI using wildcard but it is a limitation in RingCX
What we're trying to resolve: To get a custom reporting to classify calls and get total number of calls outside US
2 votes -
RCX Real time Long Abandon Metrics
When looking at the Analytics in the Real-time Dashboard, Long Abandons is not available as a field for us to report on, only Short Abandons. Reporting on Short Abandons is not very useful, as we would be reporting on the number of customers that called us, then quickly put the phone down, which is not useful data. Long Abandons, however, would give us a report showing how many people waited in the queue and then left, signifying that they waited too long.
It would be more useful to add in the "Long Abandons" field so we can show the number…
4 votes
.png){kind=link}
.png){kind=link}
- Don't see your idea?