Settings and activity
22 results found
-
1 vote
An error occurred while saving the comment -
8 votes
Travis
supported this idea
·
-
8 votesTravis
supported this idea
·
-
4 votesTravis
supported this idea
·
-
4 votesTravis
supported this idea
·
An error occurred while saving the comment Travis
commented
Critical Security/Fraud Use Case:
The current request for forwarded call visibility is not just a UI preference; it is a vital requirement for Fraud Detection and Security Auditing.Currently, an administrator cannot search the account's history using an external PSTN number as the primary criteria to see if any internal extension is forwarding traffic to it. If an employee (or a compromised account) sets up a "rogue" forward to an expensive or unauthorized external number, that traffic is invisible in a global destination search.
Required Capability: Global "Destination Number" search that returns all call legs, whether they were direct outbound dials or the terminal leg of a forwarded call.
-
3 votes
-
2 votes
An error occurred while saving the comment Travis
commented
Please ensure this enhancement includes adding the Unique Interaction Identifier (UII) to every digital audit log entry.
The UII is currently missing, making it impossible for administrators to effectively troubleshoot and correlate audit logs with full analytics reports (a major pain point observed in Case 29329851). Without the UII, the log remains a manual, time-consuming research tool.
-
1 vote
An error occurred while saving the comment Travis
commented
This request can be withdrawn.
-
18 votesTravis
supported this idea
·
-
171 votesTravis
supported this idea
·
-
4 votes
An error occurred while saving the comment Travis
commented
CORRECTION: The metric fields being requested are: Total Talk Time
Average Talk Time
Max Wait Time
Avg Wait time
-
142 votesTravis
supported this idea
·
-
15 votesTravis
supported this idea
·
-
2 votesTravis
supported this idea
·
-
15 votesTravis
supported this idea
·
-
25 votesTravis
supported this idea
·
-
36 votesTravis
supported this idea
·
-
330 votesTravis
supported this idea
·
-
33 votesTravis
supported this idea
·
-
14 votes
An error occurred while saving the comment Travis
commented
See attached
An error occurred while saving the comment Travis
commented
This should also apply to displayed time as well, not just exported data.
NOTE: This is a request to implement granular, immutable administrative audit logging across RingEX, RingCX, and associated platform interfaces. Administrators currently lack sufficient audit trail visibility to determine who downloaded, exported, or viewed specific data sets or system files, as well as the exact scope and timestamp of those actions. For regulated enterprise customers (such as credit unions and financial institutions), detailed auditability is a critical compliance and incident response requirement. The platform must log and report on 1) Who performed the action (User ID / Admin email) 2) What specific data set, report, or file was exported or downloaded, 3) Scope of the data affected and 4) Timestamp and originating IP address