1362 results found
-
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 -
Spam detection for chats
Addition of a Spam Detection feature to chat channel. This feature will help identify and filter out unwanted or malicious content from users, ensuring a safer and more pleasant experience for all participants. The system should be capable of detecting spam messages such as repeated text, irrelevant links, offensive language, and other behaviors that typically indicate spam.
28 votes -
Move from generic email profile to existing or new Customer Profile
When we get RingCentral voicemail email notifications, we cannot move and merge the VM/email to an existing customer profile with out permanently associating the "notify@ringcentral.com" to that one customer account every time another comes in.
Example:
Ringcentral sends a VM notification email, sent from notify@ringcentral.com to our email queue.
The VM call from caller ID is from 734-999-9999.That number is associated with John Smith, a customer profile visible from a previous interaction
with that customer.We'd like to move that VM over to the John Smith profile manually (or via a workflow if possible by using the…
28 votes -
RingCX - Play Remaining Esimated Wait Time to Callers in Queues (More than just once)
When callers are waiting in a queue, RingCX can only play back the estimated wait time once. Other phone systems have an option to let callers know the estimated wait time every X seconds, such as once every 45 seconds, so they know how long it is before their call is answered.
We would like to see RingCX updated so it allows us to teller our callers how long it is before their call is answered more than just one time.
Also, there is a RingCX configuration that lets the callers know their position in the queue, such as "caller…
28 votes -
When a callback request is offered to the agent, the agent can reject or answer the call using the RingCX agent application.
When a callback request is offered to the agent, the agent can reject or answer the call using the RingCX Agent application.
26 votesThis issue has been resolved and callback calls now provide option to the agent to answer or reject, as expected.
-
Name or number of the RingCX user should show as caller ID if they call RingEX internally
Currently when RingCX user calls RingEX internally, the name of the (main) Super Admin is showing up as the caller ID
26 votes -
ringcx analytics restrict
Have a feature to restrict the access of an admin to the analytics based on the team/department/group they are only managing.
This is an issue as Admins should not be able to see other departments data via report.
26 votes -
AI Optimal Routing based on Last Agent Sentiment, Disposition, etc.
Last Agent Sentiment Advances in AI makes optimal routing possible, routing new interactions based Last Agent Sentiment (if this customer interacted with this agent and it was positive based on agents’ availability direct new interaction to this agent. If the last interaction between this customer and the agent (who is due the next interaction) was negative, redirect to next agent skipping this potential negative conversation. This needs to be reportable that includes customer information like phone number or email for digital, the agent skipped and possibly the actual agent and the interactions sentiment outcome versus last with up/down metric showing…
26 votes -
Automatic hold for warm transfers using integrated phone
Many customers would like to have a warm transferred call automatically put the far end on hold. This functionality is available within agent scripting. However, some customers use the RingEX extension integration which would require the agent scripting to use webservices. This change would give customers the ability to choose how they would like to handle warm transfers on a queue/campaign level and would alleviate the lift required to mimic this functionality.
26 votes -
Add Opt-In Surveys at Call Start, Auto-Prompted at Call End
Add Opt-In Surveys at Call Start, Auto-Prompted at Call End
As a head of a centralized call center with agents that support multiple businesses and call queues, I’d love to see RingCentral add a simple but powerful feature:
When a customer calls in, they could press a key at the beginning of the call to opt-in to a quick survey. After the agent disconnects, the system would automatically play the survey.
Here’s why it matters:
- Seamless customer experience: No agent involvement, no awkward “Would you like to stay on the line?” interruptions.
- Accurate feedback: Surveys are tied directly…25 votes -
Preserve Caller ID When Transferring from RingCX to RingEX
Product Area(s):
RingCX (Contact Center)
RingEX (Phone System / MVP)
Call Handling & Caller ID Display
Current Behavior:
When an external call is routed through a RingCX queue and answered by an agent, and the agent then transfers the call to a RingEX user (via warm or blind transfer), the RingEX recipient currently sees the original external caller’s phone number as the caller ID.There is no visibility into which RingCX agent initiated the transfer. This can lead to confusion, lack of internal context, and inefficiencies in how the transferred call is handled.
Requested Enhancement:
Introduce a configurable caller ID…25 votes -
Last Called Agent (LCA) Functionality Required for Engage Messaging and Email Channel Types
We require the same “Last Called Agent” (LCA) capability for Engage Messaging and Email channels within Digital Queues as currently exists for Voice Queues. This will significantly improve customer experience by providing more efficient and personalised resolution to issues.
By reducing the need for clients to repeat information and details from previous interactions, this feature would potentially lower interaction durations. Furthermore, this capability is also essential in scenarios where agents receive commissions for successful sales, ensuring clients are routed back to the initial agent who provided consulting prior to the purchase of services or goods.
25 votes -
RingCX needs to display inbound callerID for calls coming into our Voice Queues.
Currently, all inbound calls to our RingCX Queues will only show the callerID as, "UNKNOWN."
Meanwhile, callerID works just fine for all inbound calls coming into RingEX.
This function needs to exist so that our Agents can better identify our customers as the call in.
25 votes -
Ability for Any Admin to Modify, Disable, or Delete RCX Historical Report Schedule Regardless of Ownership
Currently, a RingCX admin can only modify and delete Historical Report Schedules that they own.
I would like to suggest a feature enhancement to allow an admin to delete any Historical Report Schedule, regardless of ownership. This is particularly useful for Historical Report Schedules no longer owned by off-boarded admins or users whose admin access has been revoked.
This capability can also be important if a situation arises where an employee is absent from the business due to unforeseen circumstances and the schedule needs to be modified, disabled, or deleted. Furthermore, if an admin is deleted, the schedule will show…
25 votes -
RingCX Audit Logs Queue Event Elements For Voice and Digital Queues Lack Sufficient Detail
The RingCX audit log fails to capture details regarding digital queue events (ChatQueueEvent) and their associated queues. As a result, we cannot determine which digital queue was involved when an event was created, updated, or deleted.
This lack of information prevents administrators from quickly understanding where and what changes were made. The challenge becomes more significant when dealing with multiple queues and hinders our ability to restore previous states if a queue event is inadvertently deleted or modified by an administrator
While queue details are captured for voice queue events (GateQueueEvents), we urgently need the same level of detail to…
25 votes -
Give possibility to calculate the SLA on FB Messenger over all responses, not only the on the first response.
I'd like to know the service level from the first response to the last response. How quick are we to respond to the customer requests. Actually, I can get from Dimelo the Average Time of Response, but I'd like to know how many responses were given within 30 seconds, and how many responses are given after the treshold of 30 seconds. And I want this information on all messages, not only on the first response. Is it possible to display this calculation of the SLA?
25 votes -
Feature Request: Granular Call Monitoring Permissions for Agent Role
Description:
Currently, in RingCX, the only way to enable Call Monitoring/Listening functionality is by changing an Agent's role to Supervisor. However, this creates a significant data visibility issue, as it grants Supervisors access to queues and information beyond their designated team or group, which may include sensitive data from other departments or companies.
Request:
We would like to request the implementation of a granular permission setting that allows users with the Agent role to be granted Call Monitoring privileges for a specific group of agents or queues only, without the need to elevate them to a Supervisor role.
Proposed Solution…
24 votes -
change button shape and placement
Ability to change the placement/size/shape of button using visual library. You can do this but the default button shows after interactions.
It doesn't make sense to allow button changes but only before the customer interacts, the change should implement permanently on the chosen URL/site regardless of interaction.
Please see case 28193631 for further information along with a video.
24 votes -
Enable Call Controls in RCX Agent UI when dialing Mobile Numbers
When placing a call through the RCX Agent UI, Agent Call Controls are only shown when a 200 OK is returned. This is standard for landline numbers, however when dialing a cell, we do not get a 200 OK until the called party picks up. Customer would like to enable Agent Call Controls to show when a 180 RINGING or 183 SESSION PROGRESS is returned. This would allow Agent Call Controls to show when dialing Mobile numbers as well.
24 votes -
Include Name & Number in Caller ID
Request is to have both the Name and Number appear. Currently, the name only shows if the number is in a Campaign.
24 votes
.png){kind=link}
.png){kind=link}
- Don't see your idea?