188 results found
-
2 votes
-
Feature Enhancement Request: Generate Post-Call State for Bad Number Calls
Feature Request
Enhance RingCX to generate and update the appropriate post-call state when an outbound call is classified as a Bad Number, instead of ending the call without a standard post-call state.
Current Behavior
Engineering confirmed that the current behavior is expected. When a destination number is identified as a Bad Number—such as an invalid, unreachable, disconnected, or otherwise non-callable number—the call does not proceed through the normal call flow.
Because the call is terminated or classified at an earlier stage, the normal post-call processing is not triggered, and no post-call state is generated or updated.
Customer Impact
The absence…
2 votes -
Ring CX Place in Queue announcement to be able to play multiple times
Currently, the "Place in Queue" announcement plays only once when the "Route to Agent" queue event is first triggered. The desired functionality is to have an option for this announcement to loop and repeat at adjustable intervals. Ideally, the position in queue should be recalculated and announced each time, without the need to chain multiple "Route to Agent" events sequentially.
4 votes -
Improved Callback Reporting and Functionality for Early Caller Disconnects
In the current RingCX callback flow, if a caller disconnects before the system successfully queues the callback, the interaction is categorized as “Inbound ACD Callback Incomplete” in Analytics reporting. This occurs even in cases where the caller has already expressed intent to receive a callback.
Problem:
This classification does not accurately reflect customer intent or agent workload. From a business perspective, these interactions often represent valid callback requests that were interrupted due to timing or user behavior, rather than true failures. As a result:
1) Callback demand may be underreported
2) Metrics may not align with actual customer experience
3)…3 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.
30 votes -
terminate calls in CX queue at end of business hours
Our call center agents leave at 5pm. On high volume days, we may have 10 calls waiting in queue at 5pm when our agents logout for the day. We find that many of these calls will continue to remain in queue without accepting the callback option because they are unaware no one is going to be available until 8am the next morning. If we configure a queue event to disconnect calls when there are No Agents Signed In, we run the risk of disconnecting calls during the middle of the day when agents are leaving and returning from lunch. There…
2 votes -
SMS Conversation Assigned to Different Agent During Active Voice Call with Same Customer
We would like to know if there is a way to keep SMS interactions with the same agent who is currently handling an active voice call with the customer.
Workflow:
- An agent is on an active voice call with an install partner
- During the call, the agent asks the customer to send photos via SMS
- When the customer sends the SMS, the new SMS conversation is automatically assigned to a different available agent instead of the agent currently handling the voice callOur goal is to have the SMS conversation remain with the same agent handling the…
2 votes -
Ability to control playback speed for variable audio that is captured in a workflow
Need the ability to control playback speed for variable input audio that is captured in a workflow, e.g. credit card number. We want to make the playback slower so that the caller can clearly understand the number.
1 vote -
Route Calls to the Agent With the Longest Time in AVAILABLE State
Issue Summary:
Calls are not being routed to the agent with the longest available time. Based on the RingCX Real-time Analytics report, calls are not consistently directed to the agent who has been available the longest.Current Behavior:
RingCX routes calls without correctly prioritizing the agent with the longest AVAILABLE duration. Analytics (“Agent State Change Raw” report) confirmed that when a call arrives, the agent with the longest AVAILABLE state time is not always selected.Expected Behavior:
RingCX should route calls to the agent who has been in the AVAILABLE state the longest.Troubleshooting Performed:
Reviewed “Agent State Change Raw”…
11 votes -
Option to Route Unanswered External Phone Connections to Next Available Agent
Option to Route Unanswered External Phone Connections to Next Available Agent
When a RingCX agent uses an external phone number for their voice connection, the system currently treats the handoff like a call forward. If the agent does not answer, the call falls to the external phone's ring settings, and RingCX marks it as answered. We need a configuration option for RingCX to pull the call back to the queue if it is not physically answered by the agent, allowing it to route to the next available agent rather than ending up in a personal external mailbox.
1 vote -
Include Audio File Attachments on RingCX Voicemail Notifications
Instead of the weblinks attached to access voicemail messages from RingCX, we'd like to attach the exact audio file to the email notification.
19 votes -
RingCX Feature Request: Native Integration for RingEX Call Queue Transfers
When an agent is using the RingCX application, they have the ability to transfer calls to RingEX users and see their extensions in the corporate directory. However, there is no native integration that allows RingCX agents to transfer calls directly to RingEX call queues. The customer is currently using a workaround where they manually upload the DIDs of the RingEX call queues into the RingCX phone book, which allows for transfers as if it were an external contact. This is a time-consuming and inefficient process that requires manual maintenance whenever a call queue is changed or added. The customer would…
20 votes -
Enable Automated Disposition Email Generation for Manual Outbound Calls
RingCX currently supports automated email generation for inbound calls based on the disposition selected by the agent, through custom workflow. This feature has already been designed, presented, demo’d, and validated for inbound workflows.
However, during UAT, customers requested that this same functionality be extended to manual outbound calls, which is not currently supported.
Current Limitation:
Automated disposition-triggered emails only work for inbound calls
Manual outbound calls do not generate emails, even when dispositions are applied
Agents must perform follow-up communications manually, leading to inconsistent workflows between inbound and outbound callsRequested Enhancement
Enable automated email generation for manual outbound calls,…2 votes -
Callback Flow Improvement
There should be a way in RingCX to enhance the callback experience by allowing callback requests to be honored immediately after the caller’s initial input, without requiring a second confirmation—even if the caller disconnects early.
Current Behavior
1) Callers press “1” to request a callback.
2) A second confirmation (“press 1 again”) is required before the callback is officially queued.
3) If the caller disconnects before completing the second confirmation or before system disconnect, the interaction is marked as “Inbound ACD Callback Incomplete.”
4) No callback is generated, even if the caller already indicated intent.Problem Statement
• The two-step…4 votes -
Deleting a phone book entry should delete them automatically for all queues
At the moment, deleting an entry in the phone book page doesn't delete it from the voice queues. We are requesting that this functionality be updated. Deleting a phone book entry should delete it from all queues.
1 vote -
callback feature only when calls are waiting or wait time reaches a set threshold
Feature Request: Create a feature that can dynamically determine when a callback queue event should be offered based on specific thresholds (i.e SLA, elapsed time (currently in place), abandoned rates, # of calls waiting, etc.)
5 votes -
Import RingEX IVRs to RingCX
- Executive Summary As customers migrate from RingEX to RingCX (or adopt a hybrid setup), reconstructing complex Interactive Voice Response (IVR) menus manually in RingCX is a major pain point. It is time-consuming, prone to human error, and delays the onboarding process.
This feature will allow administrators to export an existing RingEX IVR configuration and import it directly into RingCX, automatically mapping menus, prompts, audio files, and key presses (extensions) to the corresponding RingCX queues, scripts, or flows.
Problem Statement
"Rebuilding a 5-level IVR menu with dozens of audio prompts in RingCX takes hours of manual labor and requires dual-monitoring both…
3 votes -
Digital Routing "Longest Idle" should not treat an agent actively on a voice call as more idle than a truly available agent
When a Longest-Idle style routing algorithm selects an agent for a new digital interaction (chat/email) and multiple agents tie on every other ranking factor (skill profile, rank, role), the routing engine falls back to comparing how long each agent has been idle since their last interaction ended.
The issue is that idle time appears to be tracked using a single timestamp that only updates at the start or end of an interaction — and for voice calls, this timestamp seems to update only when the call ends, not when it begins. Digital interactions, by contrast, appear to update the timestamp…
1 vote -
hashtag # in RCX (IVRs and queue events)
customers would like to have the Hashtag in the list of possible DTMF codes in IVRs and Queue events.
46 votes -
Need a native feature equivalent to Amazon Connect’s flow resumption capability
This feature request for RingCX asks to implement the ability to resume an IVR contact flow after an external PSTN transfer, a capability currently supported by competitors like Amazon Connect.
Key summary points:
The Problem: Currently, RingCX terminates the contact flow when a call is transferred externally. If the external party hangs up, the caller is disconnected.
The Solution: Allow RingCX to anchor the call so that when the external party disconnects, the original caller is returned to the RingCX IVR.
The Value: This is essential for routing callers to post-call CSAT surveys after speaking with an outsourced agent, using…
1 vote
- Don't see your idea?