132 results found
-
RingCX Agent voicemail greeting
A feature that lets them set a voicemail greeting for RingCX Agent's voicemail.
6 votes -
Enable Direct Association of Workflows with Queues for Outbound Calls in RingCX
In RingCX, outbound workflows that trigger actions such as automated emails are currently tied to workflows that are triggered through dispositions. These workflows are manually assigned at the agent level. At present, agents can be assigned to only one manual outbound workflow, and this assignment can be configured only by administrators. Agents do not have the ability to select, switch, or apply different workflows on a per-call or per-queue basis.
This creates a significant limitation for organizations that manage multiple clients, queues, and outbound scenarios. The customer requirement is for agents to be able to select the appropriate workflow based…
2 votes -
6 votes
-
Allow change of state for RC CX Agents
We would like to be able to change states actively during a call. Our Leads like to track time spent on specific parts of a call (IE. Payments / Flood Insurance ) We have several use cases where our Supervisors want agents to be able to swap mid call so that the team can actively check how long members are taking for various actions while on a call.
1 vote -
Allow Admin Self-Service Management of Campaign Real-Time DNC Integration Without Support Intervention
"I see that the integration part has been added, is there any way that this could be added by us in the future so that we don't have to create a ticket"
Description:
Currently, when a new campaign is created and requires integration setup/configuration, customers must submit a support ticket to have the integration component added or configured.We would like to request an enhancement that allows Admins to independently manage and assign integrations to campaigns without requiring assistance from Support or internal teams.
Requested Functionality:
Allow Admin users to add, configure, or enable integrations directly within the admin portal/UI.…
1 vote -
Allow Admins to Disable Disconnect Scrubbing at the Account Level for RingCX Campaigns
Title:
Allow Admins to Disable Disconnect Scrubbing at the Account Level for RingCX CampaignsDescription:
Currently in RingCX, the Disconnect Scrubbing setting can only be configured at the individual Campaign level. Customers managing multiple campaigns must manually disable this setting for each campaign separately, which creates additional administrative overhead and increases the risk of inconsistent configurations.We would like to request an enhancement that allows Admins to manage Disconnect Scrubbing at the Account level.
Requested Functionality:
Introduce an Account-level setting to enable or disable Disconnect Scrubbing across all RingCX campaigns.
Allow the account-level configuration to automatically apply to:
Existing campaigns…1 vote -
Manual Assign digital In-Queue interaction
Currently, when a user manually assigns an email interaction that is sitting in the queue, the system's background routing logic does not recognize the manual assignment. The interaction retains its "Queued" status, causing the system to subsequently auto-route the email to a different agent. This creates duplication of work, conflicts in ticket ownership, and inefficiencies in queue management.
Request:
Status Update: The interaction's status should immediately transition from "Queued" to "Assigned" (or "In Progress").
Halt Auto-Routing: The interaction must be automatically excluded from the active routing queue so that it cannot be pushed to another agent.
Ownership Lock: The manual…
1 vote -
ability to apply the changes made to the rcx users without them updating their session information
When they make changes on agents (e.g. skills, queue). The agent still needs to update their session information.
It would be better if the changes made to the agent be applied without updating the session information
1 vote -
Another SLA is being triggered even though the agent has already responded to the chat in Engage Digital.
Is there a way to prevent information about customer SLA breaches from appearing in the Engage Digital chat window?
The customer has noticed that SLA breach information is being displayed, even though the agent has already responded to the chat. The customer does not want another SLA to be applied once the agent has provided an initial response.
Currently, the system shows that the agent is breaching the customer SLA, even after responding. Ideally, another SLA should not be triggered once the agent has already replied—similar to how calls are handled. If an agent has already answered a call, it…1 vote -
option to assign direct number to agents
It would be helpful to assign a direct number to agents in RingCx. Since RingCX customers would mainly use RIngCX instead of EX. So they would like an option to assign the direct number of agents from EX to CX as well to have SMS capabilities for the numbers being assigned in RingCX Agents
1 vote -
Hide EX Caller IDs when logged in to CX
CX users have the EX dialpad populating when selecting the dialpad. This is creating a discrepancy with their CX functionality and reporting of outbound calls. The call detail is capturing in their EX history instead of in their CX history, and the associated reporting in CX is not capturing the details. Desired functionality is that if the user is in CX mode, the only dialpad that will populate is the CX dialpad. Seems this is occurring when disposition window is open and dial pad is selected, and/or if disposition is not selected and subsequent outbound call is attempted.
2 votes -
Last Agent Routing with Digital Queues
We have last agent routing for Voice Queues, but it would be very helpful to have this for digital queues as well. Example:
A customer responds to an email thread a couple of days later, but the original agent had closed the interaction due to lack of response or the interaction had timed out. Since the original agent had been working the email thread directly, we should have the option to attempt to route the interaction to them first.5 votes -
Add “Average waiting Time” column to Real-time Agent view
Add a new column “Average waiting Time” in the Real-time Agent view.
This column should display, for each connected agent:The average waiting time of client
Calculated on a time window consistent with real-time data
Based on ongoing and/or recently handled interactions (same logic as other real-time KPIs)1 vote -
An email address book in CX
It would be really useful to have an address book in CX to store email address. Our agents frequently forward on emails so without this, it slows them down.
4 votes -
ability to transfer agent assignment in RingCx
Customers / admins should have the ability to reassign agent group assignment in RingCx. This would be more helpful since not all company have stable agents. Some are multi trained and being moved to different groups.
1 vote -
RingCX Default as outbound caller ID
It would be helpful and beneficial if we didn't need to select the RingCX Default as the mycaller ID every time when using the RC App. This feature is working as expected when using the RingCentral web.
3 votes -
Allow extension dialing within RingCX SPOG
Currently within RingCX SPOG, once you start your session and go to the dial pad and enter an extension in the dial pad with "RingCX Default" set as your caller ID, and then press enter and select the option "Dial" or press "Enter" on your keyboard, it will prompt an error "The number is invalid, please check it carefully and try again"
When you have a session started but select a RingEX caller ID, you can type the extension and then hit "Enter" or "Dial" and it will connect.
What we want is the ability to dial a RingEX extension…
3 votes -
Single Pane of Glass | Both EX and RCX call logs should appear on the same page
Wanted to be able to see the voicemails for both EX and CX, and similarly have the call logs for both EX and CX displayed on the same page
2 votes -
Allow RingCX alerts to be sent to multiple selected users
It would be highly beneficial if RingCX alerts allowed Admins to select multiple users as recipients within a single alert configuration.
At present, alert routing appears to require either:
Single-user targeting, or
Separate configurations per user
This increases administrative overhead and makes alert management more difficult at scale.
Enhancing this to support multi-user selection would:
Reduce duplication of alert configurations
Improve scalability for larger teams
Ensure consistent notification distribution
Simplify ongoing maintenance
This is especially important for operational alerts that need to notify multiple Supervisors or stakeholders simultaneously.
2 votes -
Automatic Queue Log Out After Configurable Inactivity / Time Threshold
It would be highly beneficial to introduce a configurable automatic log-out feature for agents after a specified time threshold (e.g. end of shift or defined inactivity period).
Key requirements:
Admin-defined time threshold
Agents on an active call at the time of trigger would not be interrupted
Once the active call ends and the agent submits the disposition, they should not return to Available, instead, they should automatically be logged out of all queues
This would:
Improve queue governance and SLA integrity
Prevent agents remaining accidentally logged in after shifts
Reduce manual supervision effort
Support stronger adherence and workforce management controls
…
2 votes
- Don't see your idea?