1234 results found
-
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 -
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 -
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 -
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 -
Productized Lead Loader API / Speed2Lead
Productized Lead Loader api / Speed2lead.
On the old chat form you can create a form and send leads to dialer campaign.
To include this option in the new chat form and set as subscription option for customer.
7 votes -
Extend RingCX Call History View to 30 Days
RingCX’s default 48-hour call history window feels like trying to solve a puzzle with half the pieces missing. Once you need to review anything older than two days, you’re forced into the Reports rabbit hole (if you even have access), wasting precious minutes and leaving non-admin agents stuck. Let’s fix that by giving every user a simple dropdown or settings toggle to choose their history range: 48 hrs., 7 days, 14 days, or up to 30 days, so you can instantly pull up that crucial call from last week without a detour. This small change supercharges agent productivity (no more…
16 votes -
Retain Originating Caller ID During RingEX to RingCX Transfers
Enable RingEX Receptionist to preserve the original caller's number (Originating Caller ID) when transferring calls to RingCX.
Current behavior:
When a call is transferred from RingEX to RingCX, the original caller’s number is not retained. Instead, RingCX displays the Caller ID of the RingEX user who performed the transfer.10 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 -
Ability to Set Skill Weight/Proficiency
Currently, RingCX does not provide the capability to define individual skill weight or proficiency for each agent individually. This capability is essential because it will:
- Reduce the need to create a separate skill ("Sales Proficiency 1", "Sales Proficiency 2", "Sales Proficiency 3" and so on) for each weight or proficiency level.
- Simplify and reduce the level of effort when creating and assigning skill profiles to agents.
- Streamline skill assignment within queue routing by enabling the selection of a required skill and the definition of a specific weight or proficiency range and order (high to low or low to high).
17 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.8 votes -
Add two more drop-down menus in RingCX Digital Disposition (for a total of three) alongside the existing “Notes” text field.
Add two more drop-down menus in RingCX Digital Disposition (for a total of three) alongside the existing “Notes” text field.
Use Case: This will allow agents to categorize interactions more effectively with:
Notes (text field)
Disposition (drop-down)
Category 1 (drop-down)
Category 2 (drop-down)
10 votes -
Allow Hiding Metrics on a Historical Report
Ability to hide a metric on a report. For example, I use 2 metrics to calculate a custom metric, but I don't want those visible on the finished report.
7 votes -
Caller ID Override for Callbacks in RingCX
Currently, the callback feature has no caller ID override. By default, it uses the DNIS as the caller ID when a callback is made by the system. For calls to external numbers that are forwarded to the RingCX number, it shows the number where the external number is forwarded as the caller ID.
Looking to have a feature or option to set the forwarded number (external number) as the caller ID.
11 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 -
Automatic Call Recording Pause When Agents Begin Payment Collection (PCI Auto-Protection)
Title:
Automatic Call Recording Pause When Agents Begin Payment Collection (PCI Auto-Protection)Summary:
Requesting a RingCX feature that automatically pauses call recordings the moment an agent initiates payment collection, without relying on DTMF detection or manual agent actions.Details:
Currently, RingCX requires agents to manually pause the call recording when collecting customer credit/debit card information. This introduces human error and increases PCI compliance risk.In other platforms (e.g., Dialpad), recording can automatically stop during payment collection flows. The trigger comes from workflow context, not customer DTMF digits.
Issue:
RingCX does not have a trigger or system event that identifies when…5 votes -
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 -
Improve Historical Reporting: Exclude Deleted Agents and Queues past their deletion date
When an agent or queue is deleted, the historical data associated with them should ideally no longer be displayed or should be clearly marked as inactive past their deletion date.
If multiple agents are leaving and are removed from RingCX, manually filtering them out from historical dashboards is indeed very difficult and inefficient.
Hence, the agent and queue details should be cleared off after the date they are deleted from the portal
12 votes
.png){kind=link}
.png){kind=link}
- Don't see your idea?