1258 results found
-
Preserve Agents’ extension as Caller ID for Internal Calls
When agents make internal calls on the SPOG, their caller ID shows the RingCX caller ID Setup. It would be helpful if the system preserved the agent’s actual Extension as caller ID so colleagues can easily recognize who is calling.
12 votes -
Retain Originating Caller ID During RingEX to RingCX Transfers
Enable RingEX Receptionist to preserve the original caller's number (Originating Caller ID) when transferring calls to RingCX.
Current behavior:
When a call is transferred from RingEX to RingCX, the original caller’s number is not retained. Instead, RingCX displays the Caller ID of the RingEX user who performed the transfer.12 votes -
RCX - Realtime Dashboard Access
RingCX agents should have the option to view the dashboard to see the other agent's status in the RingCX Agent platform, not in Analytics, regardless if they are just an Agent or an Admin.
12 votes -
Improve Historical Reporting: Exclude Deleted Agents and Queues past their deletion date
When an agent or queue is deleted, the historical data associated with them should ideally no longer be displayed or should be clearly marked as inactive past their deletion date.
If multiple agents are leaving and are removed from RingCX, manually filtering them out from historical dashboards is indeed very difficult and inefficient.
Hence, the agent and queue details should be cleared off after the date they are deleted from the portal
12 votes -
Make the Knowledge Base for Agent Assist available on demand
Not all clients use RingCX for all interaction types. Make the knowledge base available to be searched/reviewed regardless of if there is an active interaction.
12 votes -
RingCX callback in queue
Significantly improve the RingCX callback in queue experience for callers. Here's a breakdown of the issues and how to address them, focusing on making the text-to-speech (TTS) more natural:
Key Issues Identified:
Mixed Gender Voices: The callback message currently starts with a male voice and switches to a female voice. This can be jarring and unprofessional.
Outdated/Robotic Text-to-Speech: The TTS used to read and verify the phone number sounds old and unnatural, which negatively impacts the caller experience.
Solutions and Recommendations:- Unify and Improve Voice Consistency:
Custom Audio Recordings: The most direct way to ensure consistent and natural-sounding voices is…
12 votes -
SPOG Application: The option to manually accept callback request calls when they are routed to the agent.
SPOG Application: The option to manually accept callback request calls when they are routed to the agent.
12 votes -
RingCX- Ability to upload Audio File and change the system default audio
RingCX- Ability to upload an Audio File and change the system default audio
12 votes -
Agent States Transition
Agent States Transition report presented as a bar graph, displaying the duration and frequency of each status.
12 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.
12 votes -
Add Voicemail Transcription for Contact Center
Currently there is no voicemail transcription offered in RingCX like we are provided with RingEX. This would be a massive time saver for high volume Contact Centers.
12 votes -
Real Time Inbound dashboard widget - Need to include Callback request count
Currently there is not option to add Callback Requests under the Real Time Inbound widget on the real time dashboard.
It is better to have this metric added as well so that customers can check the total count of contacts requesting for callback and if those callback requests were dialed.
12 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 -
Admin State Change
Ring Central Engage Voice admins should be able to change the state of an agent as needed through the admin platform. Currently, we are only able to remove someone from the queue.We should be able to change someone's state when required.
12 votes -
Replace busy signal from carriers with announcement(s)
Currently there are several situations where carriers can provide response messages and these are collectively returned as busy signals. This can be seen with the provider Outreach.
12 votes -
Ability to Move or Reposition Admin Users in RingCX Admin
Currently, when creating a new admin user in RingCX Admin by clicking the plus sign next to an existing user, the new admin is automatically created as a child under that user. There is no option to move or reposition the admin user afterward. This feature request is to add the ability to move or reassign admin users within the hierarchy to allow better organization and management of users in RingCX Admin.
11 votes -
Recordings Delivery Audio Format
Currently Recording Delivery Tasks only send the standard Recording URL. Customer is looking to deliver Perspective Recordings instead of Standard. An option on Task creation to choose which Recording is delivered would accomplish this.
11 votes -
View RingCX Dashboards in Softphone-Client
It should be possible to display the created dashboards from Analytics directly in the client, preferably via an additional selection, so that the website does not have to be open in parallel for the display.
11 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.
11 votes -
Mark email that did not have an agent reply as "Solved" rather than "Ignored"
Whenever an agent solves an interaction without responding to the message, the interaction is being tagged as "Ignored". This cause confusion as the agent actually accepted the interaction but it just didn't require a reply thus the agent is marking them as solved. It should be tagged "Solved" or something else other than "Ignored"
11 votes
- Don't see your idea?