25 results found
-
Improvement with the CX queue voicemail options.
CX queue voicemail is a major issue. It should work exactly like the EX platform, meaning to attach the voicemail as well as the option to transcribe the voicemail in the emailed message. For our users, having a link to another server which does not work. we have already whitelisted it but when logging in you get no voicemail but a option to log in again. We had to transfer the call to an EX queue, then use that queue to save the voicemail to send to a group email.
36 votes -
Add time based variable to holiday configuration
Managing segmented or partial holidays in RingCX Workflows and Administration is difficult. Admins have to create the holiday and then add multiple scheduling objects to the IVR Workflow to split out partial times during a specific date.
Adding the ability to specify times of day for a configured holiday would allow a customer to apply routing logic to a specific time period for a specific date.Example:
- On Oct 1, the service department is closed from 12pm-1pm
- Between 12 and 1 on Oct 1, they want calls to route to the operator instead of the service departmentIn…
64 votes -
Custom callback prompts
We need the ability to use custom audio files for the Callback in queue prompts. It is disruptive for the caller to hear different voices while interacting with the business.
14 votes -
In-Queue-Callback Number Restriction To Prevent Misuse
The RingCX Callback feature currently allows users to enter an alternative number for a callback, with the sole restriction being that the number must originate from the same country as the inbound ANI country code.
However, there is a potential risk of abuse by malicious actors or scammers, who could exploit this feature to generate revenue for themselves by using premium rate numbers for the callback, resulting in financial implications for our customers.
To mitigate this risk, I would like to suggest implementing the ability to restrict specific numbers from being used for callbacks by creating a blacklist.
29 votes -
RingCX Time Based Callback-in-Queue Offering
It is important to use time-based Callback-in-Queue so that when a queue is ending callbacks aren't left waiting until the next day. Time- based Callback offering could turn off callbacks being offered 10, 15 or 30 minutes prior to Queue closing. Phase 2 could be time and "chance of answering" using AI to determine if a callback is offered can it be answered while the Queue is active such as number of agents, active talk time versus time left in Queue before closing.
42 votes -
Callback Queue Languages
The callback queue recording is only available in English. This should be available in multiple languages to account for various language requirements. We have a need for a French version in RingCX.
11 votes -
Agent script disposition element variable support
Agent script element is currently very static in what is displayed (hard coded queue/campaign values). Avantive would like to be able to put show/hid filter logic based on agent script values
2 votes -
AI Optimal Routing based on Last Agent Sentiment, Disposition, etc.
Last Agent Sentiment Advances in AI makes optimal routing possible, routing new interactions based Last Agent Sentiment (if this customer interacted with this agent and it was positive based on agents’ availability direct new interaction to this agent. If the last interaction between this customer and the agent (who is due the next interaction) was negative, redirect to next agent skipping this potential negative conversation. This needs to be reportable that includes customer information like phone number or email for digital, the agent skipped and possibly the actual agent and the interactions sentiment outcome versus last with up/down metric showing…
29 votes -
Add ability to label IVR Studio nodes
Add the ability to label IVR Studio widgets so it's not the NodeID. Current limitation is if you change NodeID value: no spaced allowed and only 9 characters display. Including labels will make complex scripts easier to understand since there won't be the need to edit them to understand the use.
4 votes -
Improve Zoom/Scrolling Behavior
When using a touchpad that supports 2-finger scrolling, the workspace zooms and the position of the items moves to left and up so you have to use the mouse to move things around instead of scrolling. It's very difficult to navigate and the zoom is too granular to be useful.
2 votes -
In Pop-up window, unable to view all options
The edit pop-up windows for nodes gets cut off and forces the user to maximum browser window to see all the options and Save button. The window can't be moved so there is no other way to see all options which adds steps to a user's workflow. This is inconsistent from Script Studio, which only shows a maximized pop-up.
2 votes -
1 vote
-
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 -
API that would allow exporting scripts in JSON format.
Can an API be provided so we can export scripts on our Engage Voice account in the form of JSON?
2 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 -
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 -
Post Call Surveys within the Interface
The request is to bring this functionality into the User Interface. There are ways of doing this with our IVR studio but they are not 'standard'. Users would have to use javascript, agent scripting, and IVR studio scripting to get this accomplished.
8 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 -
Access to web service responses for agent scripting
Currently there is no way to get return data out of a web service to be used in an agent script.
2 votes
- Don't see your idea?