1511 results found
-
Main Screen Functionality
Need the ability to see MISSED Calls on the main agent screen and be able to click and call them back.
3 votes -
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 -
Dynamic Caller ID from RCX Front
We’d like to request a change to support displaying the caller ID dynamically from the RCX front, instead of using a static value. It should display a more generic value like "Internal RCX Call" or the actual caller ID of the RCX agent, depending on their configuration.
Currently we are seeing random numbers (027837475)
2 votes -
In-Queue-Callback Number Restriction To Prevent Misuse
The RingCX Callback feature currently allows users to enter an alternative number for a callback, with the sole restriction being that the number must originate from the same country as the inbound ANI country code.
However, there is a potential risk of abuse by malicious actors or scammers, who could exploit this feature to generate revenue for themselves by using premium rate numbers for the callback, resulting in financial implications for our customers.
To mitigate this risk, I would like to suggest implementing the ability to restrict specific numbers from being used for callbacks by creating a blacklist.
29 votes -
RingCX Additional Call Events
In RingCX, create additional call events in which When a missed call occurs or When a callback is initiated or completed, the system will send automated emails to a specified recipient or distribution list based on these triggers.
3 votes -
Compliance - Remove my data email button
California, Virginia, Colorado, Connecticut, Texas, Oregon, Delaware, Maryland all have comprehensive data deletion requirements, and it would be helpful to have a standardized 'button' that allows for an email to be sent to a specific defined email address that can be actioned by supervisors/staff. The email would contain the lead data needed: Account, Campaign, date time stamp, lead phone, name, address, city, st, zip. notes. Similar to an email that is generated off of a disposition notification but without having to have a gazillion dispositions created for this.
1 vote -
Ability to Assign Company Main Number Directly to RingCX Call Queues
Currently, the company’s main phone number cannot be directly assigned to RingCX call queues, requiring a workaround by forwarding calls to a different number. This creates additional setup complexity and potential for misrouting. Requesting a feature to allow direct assignment of the company main number to RingCX call queues for simplified configuration and improved call handling efficiency.
1 vote -
Enable Recording for Dialer Calls that are detected as Machine Answered
Request to enable call recording for Dialer Calls that are detected as machine answered.
1 vote -
1 vote
-
API Support for Retrieving Agent Availability and Offhook State Without Event Subscriptions
Request to add a new RingCX API endpoint that allows retrieval of agent availability and offhook state directly, without the need to use event subscription mechanisms. This feature would enable easier and more flexible integration for monitoring agent statuses in real-time.
2 votes -
Complete Call Handling Through Physical RC Phone
Here at the City of Bend, some Contact Center team members use their Desk Phones to handle calls, transfers, putting on hold, etc. On RCX, you can "Login with RC Phone" option Logging into RCX, but the receptionists must handle the call through the HTML RCX Interface. We assumed this would allow receptionists to completely handle calls through the physical RC Phone, however, we are being told this does not work at this time. We would like to handle the entire call control from the physical desk phone.
11 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 -
Native CRM Integration for Lead Interaction History
Currently, preserving a permanent record of all lead interactions requires a complex API integration to push logs to the client’s CRM, creating administrative overhead and potential for data gaps.
This feature request proposes a native CRM integration within RingCentral to automatically sync all lead interaction history, enabling:
Seamless tracking of communications across platforms.
Reduced dependency on custom API development.
Improved data accuracy and accessibility for reporting and compliance.The goal is to simplify CRM management, enhance data integrity, and improve workflow efficiency for agents and admins.
1 vote -
Integrated Messaging Within the Dialer
Currently, agents must leave the dialer to send SMS messages, navigate to a separate section, and manually copy-paste phone numbers, disrupting workflow and reducing efficiency.
This feature request proposes integrating SMS and other digital communications directly within the dialer interface, allowing agents to:
Send messages without leaving the dialer.
Maintain context on the lead or customer they are engaging with.
Reduce time spent switching between screens, improving productivity and user experience.The goal is to streamline agent workflows, minimize errors, and enhance communication efficiency within the RingCentral platform.
1 vote -
Enhanced Dialer & Voicemail Control for Agents
Currently, RingCentral’s dialer and voicemail functionalities limit agent flexibility and efficiency. Personalized voicemail drops require an admin to create a separate campaign-level disposition for each agent’s custom recording, making it unscalable for teams. Additionally, in Progressive Dialer mode, agents cannot stop or cancel a call once the system begins dialing, which disrupts workflows and reduces operational control.
This feature request proposes enhancements to provide agents with:
Scalable, agent-specific voicemail options without needing manual admin configuration.
The ability to cancel or stop calls in progress within the Progressive Dialer to improve responsiveness and control.These improvements aim to streamline agent workflows,…
1 vote -
Enhanced Lead & Campaign Management for Improved Agent Efficiency
Currently, RingCentral’s campaign and lead management capabilities limit agents and admins in several key ways: leads expire unpredictably, there are only five campaign priority levels, and re-uploading lead lists creates duplicate records while losing historical interaction data. Agents cannot filter leads within an active campaign to target calls effectively, and campaign assignment is entirely manual, preventing the system from automatically distributing leads to available agents.
This feature request proposes a comprehensive upgrade to the lead and campaign management experience, including:
Expanded and configurable campaign priority levels.
Ability to merge duplicate leads while preserving historical interaction data.
In-campaign lead filtering for…
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 agent have the ability to select which campaign to work.
In RingCX, agent do not have the ability to choose which campaign they can work on if in case there are more campaigns in the dial group they are working on.
It would be better if agent have the ability to choose which campaign they will be working on for the day since it is also tidious in creating different dialgroup per campaign.
2 votes -
RingCX: Ability to implement interaction restrictions on a digital inbox for a team of agents
I have a use case with an existing client that the heavily uses digital interactions. They have a requirement to be able to restrict access to interactions associated with specific channels to a team of people.
In RingCX currently, by design, the digital inboxes are just filters for interactions - they are not permissive or restrictive. Although the inbox can be filtered to display certain interactions, an agent can use the search facility to be able to search and view interactions across all channel.
The use case is that an client may wish to create a channel that is used…
2 votes -
RingCX Add Bulk Disposition
Add bulk or add the same disposition on different queues to avoid manually adding disposition to match the other queues and to save time
4 votes
- Don't see your idea?