217 results found
-
Blind Transfer Option in the Route Node
Ability to make the route node in IVR Studio to be a simple blind transfer. There are situations when transferring to an external IVR where the receiving carrier doesn't signal the platform that the call has been picked up, resulting in the call being pulled back. The workaround is to build queues that are used purely to forward calls, which is time consuming, clumsy, and restrictive if the forwarding number needs to be dynamic.
5 votes -
Call streaming IVR audio
Current Call streaming is capable of streaming audio of Queues and Campaign calls in Engage Voice. https://developers.ringcentral.com/engage/voice/guide/workforce/call-streaming/getting-startedNew idea is the capability of Call streaming dual audio in IVR product as well. This will help in building products related to Virtual agents.
2 votes -
Object support in call baggage
When passing data from IVR Studio to Scripting Studio a limitation was found that the call baggage cannot contain an object with multiple values. Allowing for objects to be passed from one part of the platform for another would allow users to have a single web service up front that could provide all of the data necessary for the life of the call.
2 votes -
1 vote
-
Ring All Phones
My branches currently don't like using IVR's and only want all phones to ring in the branch. It would be nice to have a way to have all User Phones, Limited Phones and Apps ring at once when the main Branch number is called. Currently we can't use Call Queues as they don't allow Limited Phones and if I setup a user as a ring all, I can get user and limited phones to ring, but not app. This would be a great solution for small locations that don't need an IVR.
1 vote -
Potential Spam
Automated system wide blocking of spam numbers to all extensions requiring no action by customers.
6 votes -
AI/NLU for Voice Bots (IVR)
AI/NLU integration to drive Voice Bot (IVR) solutions using Google AI/NLU engines (or other AI/NLU engines available) to create a similar experience as a chatbot.
12 votes -
Create a Repeat Queue Event option
Create an option to select “Repeat Event” and “Number of Repeats” (a specified number or indefinite). This would allow the ability to have the programmed event in the Queued Event Configuration to repeat indefinitely or for a specified number of times for the interval time as configured in that Queue Event. This option would prevent the administrator from having to create duplicate events.
9 votes -
6 votes
-
Ability to "Cherry Pick" callers out of a queue
Though there are other ways to accomplish this, many customers would like to have this functionality.
5 votes -
Ability to assign more than one web service to an event
Many APIs require an initial authentication call in order to make the main API request, which requires two API calls for an event.
3 votes -
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.
3 votes
- Don't see your idea?