Settings and activity
85 results found
-
1 vote
Christopher
shared this idea
·
-
1 vote
Christopher
shared this idea
·
-
2 votes
Christopher
shared this idea
·
-
4 votesNew · 0 comments · AI Conversation Expert (ACE, formerly RingSense), AIR & AVA » ACE for RingCX · Admin →
Christopher
shared this idea
·
-
35 votes
Christopher
supported this idea
·
-
14 votes
An error occurred while saving the comment -
1 voteNew · 0 comments · Developer Platform, APIs, & Integrations » Integrations: Microsoft Teams · Admin →
Christopher
shared this idea
·
-
2 votes
Christopher
shared this idea
·
-
1 vote
Christopher
shared this idea
·
-
1 vote
Christopher
shared this idea
·
-
1 vote
Christopher
shared this idea
·
-
2 votes
Christopher
shared this idea
·
-
1 vote
Christopher
shared this idea
·
-
2 votes
Christopher
shared this idea
·
-
2 votes
Christopher
shared this idea
·
-
1 vote
Christopher
shared this idea
·
-
10 votes
Christopher
shared this idea
·
-
1 vote
Christopher
shared this idea
·
-
1 vote
Christopher
shared this idea
·
-
32 votesNew · 1 comment · AI Conversation Expert (ACE, formerly RingSense), AIR & AVA » ACE (AI Conversation Expert) · Admin →
Christopher
shared this idea
·
This feature request is also applicable to a similar RingCX Analytics use case involving deleted Queues and Workflows.
Once a Queue or Workflow is deleted, it can no longer be edited or renamed in the CX Admin Center. However, historical records associated with these entities may continue to appear in Analytics reports, making it difficult to distinguish obsolete/test entities from current production data.
For historical reporting purposes, it would be helpful to provide an option to either:
Exclude deleted Queues and Workflows from standard/current reports after their deletion date;
Clearly identify deleted entities as inactive/archived;
Provide an "Include Deleted" or similar filter in Analytics; or
Allow the names of deleted entities to be edited for historical reporting purposes.
This would help administrators maintain cleaner Analytics reports while still retaining historical data for auditing and reporting when needed.
Workflows should also be considered alongside Agents and Queues in this enhancement.