1320 results found
-
Separate Off Hook mode/ permanent connection management options for inbound and dialer-campaigns calling
customers would like to be able to manage answer mode in different ways depending on the type ( inbound/manual outbound VS dialers/campaigns ) :
have the ability to enable/disable the off hook / permanent connection for inbound calls separately from the dialer/campaigns off hook / permanent connection mode.so even if you disable the permanent connection/off hook for inbound, you can still have the dialer calls (as when you start dialing it switches you to off hook mode automatically).
or the other way around if you start the dialer - it would switch to off hook for the dialer -…
30 votes -
RCX - Realtime Dashboard Access
RingCX agents should have the option to view the dashboard to see the other agent's status in the RingCX Agent platform, not in Analytics, regardless if they are just an Agent or an Admin.
12 votes -
6 votes
-
User greeting in RingCX Agent.
Ability to personalize the greeting before answering the call per agent user.
33 votes -
Screen Calling for Outbound Dialer
Title: Screen Calling Feature for RCX Outbound Dialer for leads with Google Assistant
Use Case: If the agent gets routed to a lead with Google Assistant, the agent will hear a prompt asking to say their name and reason for calling before the call gets routed to the actual lead so the name and reason for calling is initially what the lead with Google Assist would hear.
8 votes -
RingCX Agent: Ability to Modify Voice Connection Options for Agents
Some agents are inadvertently logging in using the RingCentral App instead of the Integrated Softphone. As a result, calls routed to the RingCentral App are left unanswered and often abandoned. Since Presence Sync is not yet available, the RingCentral App must be set to Do Not Disturb (DND) to prevent calls from being delivered simultaneously.
This feature should allow administrators to modify the available Voice Connection options for agents, ensuring that calls are routed correctly and reducing missed or abandoned calls.
9 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.
-
- Susan reports they are receiving inappropriate chat - The wanted to confirm if its the same person that is pretending to be a 30 different
- They are receiving inappropriate chat
- The wanted to confirm if its the same person that is pretending to be a 30 different people
- That chat is being received in their Chat Channel
2 votes -
RingCX Audit Log Feature – Agent Status
RingCX Audit Log Feature – Agent Status
The customer is requesting an option to view the audit log that identifies which Supervisor manually changed a user's status.9 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 -
SPOG Application: The option to manually accept callback request calls when they are routed to the agent.
SPOG Application: The option to manually accept callback request calls when they are routed to the agent.
12 votes -
Using the Local Bucket for Manual Outbound Calling
Customer wants to use the Local Bucket for Manual Outbound Calling as it would be beneficial for them instead of using it from their dialing. Customer mentioned that since 5x9 has it that it make sense to have it here as well.
Any tips/advice/workaround for this would be appreciated.
8 votes -
RingCX Voice Queue Call Distribution
The customer is requesting to have a call routing feature that will route the call based on the number of calls each agent has received, to ensure a more balanced distribution.
16 votes -
base state
Need the ability to have additional "Base States" added for reporting purposed for account added "State Names".
Currently, there are the Base States of:
Available
On Break
Away
Lunch
Break
Training
WorkingThe added custom states fall under one of those categories.
Either additional Base States need to be able to be configured or the reporting for the agent state needs to include the custom Agent States that are configured on the account.
11 votes -
Feature Request – Distinct “Invalid Number” Result for Manual Outbound Calls
Description:
Currently, in RingCX historical reports, manual outbound calls to invalid numbers are recorded as “No Answer” in the Call Results column. This makes it impossible to differentiate between genuine no-answer calls and invalid-number attempts in reporting.
Business Impact:
Agents and managers cannot accurately track list quality or outbound performance.
Invalid numbers are not flagged for clean-up, reducing operational efficiency.
Reporting and analytics on manual outbound campaigns are incomplete.
Requested Feature:
Introduce a distinct call result/disposition such as “Invalid Number” for manual outbound calls.
Ensure this result is visible in historical reports, dashboards, and exported data.
(Optional) Include this disposition…
3 votes -
QA Reviews for Email Interactions in RingSense
We currently leverage RingCX and RingSense to perform quality assurance (QA) reviews, coaching, and performance analysis for agent phone calls. These tools provide valuable insights such as call recordings, transcripts, sentiment, and AI-driven scoring. However, we have a significant number of agents who primarily handle customer interactions via email, and there is currently limited visibility or structured QA oversight for those interactions.
Requested Enhancement
We are requesting enhanced email interaction analysis and QA functionality within RingCX and/or RingSense, comparable to what is available for voice interactions.Desired capabilities include (but are not limited to):
Visibility into agent email conversations within…
4 votes -
Inbound Queued Callback option in Queue Events, it's only in DTMF sub-Queue Events options which is limiting
For some reason you can set a DTMF Queue event to be an Inbound Queue Callback, but you can't do it from the Queue Event itself. Every other option is there, but that one is missing. It seems a bug or missed item since it would only enhance the options available?
There are many reasons for a queue event to go to Callback rather than requiring a DTMF selection to do it.
17 votes -
Allow for Web Service DTMF Queue Event to fire off without changing callers status in queue
Allow for Web Service DTMF Queue Event to fire off without changing callers status in queue.
We are attempting to configure a queue event with DTMF enabled where we offer the caller an option to press X key and receive a text message with a link to our website while the caller waits in queue. Currently, the only way we can get this working without forcing the caller to drop from the queue after receiving the text is to use the requeue option in conjunction with an external web service. This does keep the caller in the same queue, however,…
3 votes -
RingCX for Salesforce integration to RingCentral Desktop App
Customer wants to integrate RingCX for Salesforce to RingCentral desktop app so that when agent receives a call in RingCX, agent can retrieve Salesforce data or have popup in the RingCentral desktop app.
8 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…
24 votes
.png){kind=link}
.png){kind=link}
- Don't see your idea?