1153 results found
-
RCX Feature Request: Auto-Assign Supervisor Access Based on Group Membership
Currently, it is not possible to automatically grant Supervisor access when an agent is added to a specific Group of Agents in RingCX. At present, enabling Supervisor access requires manual configuration through the Agent profile:
Navigate to: Agents > General > Agent Type
Change the type to Supervisor to allow monitoring capabilities while retaining agent functionality.
Then, under Supervisor Settings, manually assign which agents they will supervise by checking names under Supervises > All.
We recognize that automating Supervisor access based on group membership would significantly streamline onboarding and role management processes. As such, I’ve submitted this as a Feature…
1 vote -
Hide SFTP credentials in the RingCX Recording Delivery
Currently, SFTP credentials are visible to anyone with admin or RC admin access, which poses a security risk. Hide or restrict the visibility of the SFTP Credentials and be only accessible to the users who created them
7 votes -
5 votes
-
Ability to allow Litify objects to mapped on RCx SF embedded agent
We need the ability to screenpop Intake or Matter and have the ability to create call logs unto those objects as well
4 votes -
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 -
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 -
Block RingCentral App (EX) Calls While Agent Is on RingCX Call
Currently, when an agent is on a RingCX call, incoming RingCentral (EX) app calls can still come through, causing interruptions. This request is to enable call status sync in the reverse direction—so that when an agent is active on a CX call, their status is reflected in the EX app, and EX calls are either blocked or suppressed accordingly.
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
-
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 -
Please modify current UI for transfers to allow for usage of only corporate directory.
Currently; the "Internal" transfer tab results would be utilized to transfer an RCX call to another RCX agent who is logged in to the platform. The "Corporate Directory" transfer tab results would be utilized to transfer an RCX call to a users REX ext.
The overall ask is to have there be a global directory that shows all results together, rather than have the separation of these results between multiple transfer tab types (Internal Transfer and Corporate Directory being two examples)
2 votes -
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 -
Show REX User Extension on internal RCX calls
Currently, REX CNAM settings can override the CNAM showing for REX users, which is typically intentional from a global level to do this; however, some customers have internal support queues that are meant to help users calling from REX to RCX, but the CNAM shows what's configured in REX.
The goal here would be for the system to recognize an internal caller and display their extension/user info instead of the REX CNAM input for the Main Site.
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
- Don't see your idea?