211 results found
-
Timeout codes for Web Services and WWW Nodes
When a WWW node times out there is no reason code in the debug. It would be helpful to see the reason code so that it can be determined why it’s not working.
2 votes -
Check Queue Status Nodes
The ability to check queue status (available agents, number of calls waiting, average wait time, etc) from the IVR will help greatly in some of the routing scenarios customers have.
3 votes -
2 votes
-
Access to debug logs for web services and agent scripts
Troubleshooting would be made easier with access to the debug results for web services and agent scripts
2 votes -
Track number destination search
Within the "track numbers" section of the RingCX platform, we have the ability to ring multiple destinations in parallel or sequential. This is a great tool, since there isn't a 'technology cap,' limiting the amount of destinations can be run simultaneously. However, from a management perspective, there is little ability to search/filter on the assigned number destinations. For customers who wish to use both RingCX as well as RingEX features, having the ability to use the track number feature for high volume 'ring groups' would be advantageous. One example would be when a customer hits the ring-group limitation of RingEX.
4 votes -
Conditional Queue Events - Engage Voice
The 'modular' nature of Engage Voice is helpful. However, with this design, some feature-sets of one routing component are not found in others. Having a if/and feature enhancement to inbound queue events would bridge this gap. Example: Play audio file 'A' for normal conditions. If wait time is 'x' then play audio file 'B'. This idea could be expanded to any queue event type.
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.
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 -
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)…2 votes -
Digital interaction routing to next available agent
Route digital interactions to the longest available agent, regardless of how many concurrent interactions each agent can handle. For example, we have agents set to two concurrent digital interactions, and when two come in they both go to the same agent. We would want one to go to the first, then the second to go to the next available agent. An additional option to choose to have this work for voice interactions as well could also be useful.
2 votes -
Call queue notifications
We would like an option we can set to send notifications to users logged in when there are calls in queue as well as notifications when a call has reached a certain time in queue. Agents are busy dialing at times and since they are constantly dialing w/o having direct view on the call queue they do not see that there is a call in queue and they continue to outbound dial causing an abandoned call. This would be on the CX dialing.
4 votes
- Don't see your idea?