1180 results found
-
Manual Outbound SMS
Other than from Inbox mode, the ability to send manual outbound sms messages. Additionally, the ability to escalate a phone call with a manual SMS/email and to create outbound campaign for SMS / email / chat or messaging notifications.
5 votes -
Wrap Time / After Contact Work
After Contact Work – Display and Reports. Currently when a voice interaction ends, the agent state changes to Available and the timer restricts another call until the timer expires. Optimally, we have an actual after contact state that has an expiration timer and an agent override. The ACW would need to be reportable for time in this state, especially useful if agent can end early ( for example, to be able to see that they were allocated 30 seconds and only used 8 seconds. ACW would ideally be programmable for Voice only and Voice, SMS, Email etc.
ACW status should…
128 votes -
Include Name & Number in Caller ID
Request is to have both the Name and Number appear. Currently, the name only shows if the number is in a Campaign.
24 votes -
3 votes
-
Admin portal Payment Processor
The current Payment Processor solutions require a custom IVR/agent script to be built. Having a RCX, admin portal supported, payment processor feature which would 'automatically' handle agent's availability, call routing, and necessary reporting via a configuration page would be monumental in making this particular experience a good one.
1 vote -
AI-based automated translation tool in RingCX digital channels
Idea is for RingCX to detect participants' languages and translates Q&A posts, similar to option in RC Webinar.
7 votes -
RingCentral for SalesForce/RingCX : Supervisors to monitor Agent activity w/in SFDC (using salesforce tools)
The request is for the ability to monitor Agent activity w/ SFDC (using native salesforce tools).
1 vote -
RingCentral for SalesForce/RingCX improvement BYOT to provide Dynamic Voice Routing in SFDC
The request is for BYOT to provide Dynamic Voice Routing w/in SFDC.
2 voteshttps://support.ringcentral.com/article-v2/using-ringcx-for-service-cloud-voice.html?brand=RingCentral&product=RingCX&language=en_US
-
Call journey report for RCX
Currently within RCX we do not have the option to trace a call and show the call journey details like we are able to in MVP. For this specific prospect the ask was for a call journey reports that shows transfer detail, however, from a demo and overall competitive point of view it would be great if RCX can match the call journey report we have on MVP as it is a missing feature today.
41 votes -
Improve ability to remove widget link
It is difficult to select a widget link to remove it. The selection hot spot is limited to the arrowhead and there is no visual indication it was selected nor is there any indication that you can delete or move it.
2 votes -
Ability to switch language for Text to Speech
It would be helpful to have the ability to switch language for Text to Speech so users make their own recordings to support multilingual IVRs.
3 votes -
Improve Text to Speech w/o requiring recording audio prompts and calling APIs via JavaScript
Goal is to extend the use of Text to Speech for Get input and Play audio widgets. Current use is limited to Say var. This would give an option that doesn't require recording audio prompts and would improve speed to deploy script changes on deployment and in production.
2 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.
3 votes -
Correct inconsistent experiences in Agent Scripting Editor
Several areas of the agent scripting editor are not consistent with the UI of IVR scripting. Editing properties of a widget window, widget naming, JavaScript editor window, etc.
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 -
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 -
More clear to quicklinks and help pages
It is unclear how to get back to the Quick Links & Help page seen when first logging in. Users have to click on the logo on the top of the window to get there. Links on that page should also be available on the left navigation bar. The current experience forces the user to remember where to go to access something not found in the left navigation menu. There needs to be a single source of resources for users to access and needs to be consolidated.
2 votes -
Ability to set holidays without JavaScript
There is no way to set holidays in a schedule without adding JavaScript code to an IVR to check if the queue is closed. This code needs to be manually added to each IVR and if there's a change in holiday date (like Thanksgiving), someone has to manually edit code on each and every IVR for each calendar year. This will lead to errors and extra overhead in managing the system.
5 votes -
Notify user if other user already editing IVR (and other IVR editor improvements)
There should be a visible indication if you open IVR Studio and someone else has it open already. The current UI shows Cancel and Save buttons disabled which does not necessarily indicate that another user has it open. The page should display a message indicating it's being edited and by whom. All configuration changes should also be included in the Audit log records.
2 votes -
Improve Knowledgebase Usability
The article editor is limited in features and can't be resized. That makes it difficult to create/edit more complex articles.
2 votes
- Don't see your idea?