334 results found
-
Replace Default “WORKING” State with More Accurate Status When Agents Lose Connection (e.g., Sleep/Idle Timeout)
Description:
• Currently, when an agent's machine goes to sleep, loses network connection, or resumes after a period of inactivity, the platform automatically places the agent into the "WORKING" state. This is a default system state, and cannot be removed or reconfigured, similar to NCX.
However, this behavior creates confusion for supervisors and admins monitoring real-time agent states. The “WORKING” label implies that the agent is actively engaged in tasks, even though they may have lost connectivity or walked away from their machine.
Feature Request:
• We propose introducing a more appropriate default system state for these specific conditions (e.g.,…56 votes -
Transferring calls to RingEX Extensions via corporate directory
To enable the ability to transfer calls via the corporate directory using RingEX extension numbers instead of typing the user's name and selecting it from the list.
Currently, the system does not recognize extension numbers when attempting to transfer a call. It only displays results when typing the name of the user or agent.
42 votes -
MVP & Max Launch As One
Currently MVP does not automatically launch, which causes the CRs to refuse a call. We would like to implement and have MVP launch as soon as you open Max. The two should work together as one. We should not have to log into two separate systems to get Ring Central running.
26 votes -
Answer Calls through MVP
The challenges we are having are the following: When receiving a call we are answering from the MVP. We would like to implement receiving call notifications through Max. Answer calls directly through Max’s interface. This adds control to answer the call, giving the CRs more time and avoiding calls from being sent to abandon queue.
26 votes -
Add Hold & Transfer Funcitonality to MVP
The challenges we are having are the following: We have to answer the call on the MVP, yet it does not allow us to place on hold or transfer from within the MVP. We would like to implement Hold and Transfer functionality in MVP. These are core features for your product, especially if it's related to communication, customer service, or call management
26 votes -
Function to Disable Extensions
We would like to implement a functionality to disable the extensions for certain Representatives from receiving external calls or direct transfers. We want to ensure the only calls received are through a skill.
25 votes -
hashtag # in RCX (IVRs and queue events)
customers would like to have the Hashtag in the list of possible DTMF codes in IVRs and Queue events.
38 votes -
Have search option of dial group added to Ring Sense
We would like the ability to search by campaign dialing groups in Ringsense
38 votes -
Filter by Voice/Digital Queue in RingSense for RingCX
Currently, the filter panel only pulls in queues when tied to RingSense for Sales (RingEX) and doesn't pull in queues when tied to RingCX. This is a request to be able to also filter by RingCX queues in RingSense.
31 votes -
All Messages Conversation Search Enhancement
There should be a way the system understands the different ways a TN can be displayed/formatted and searched, but at present, it seems it needs to be exactly the same as the interaction shows in the history.
Please see the screenshots.
If a number is formatted in 3 different ways as it's used in RCX:
(734) 279-2221
17342792221
734-279-2221When you search by these formats, you only get see the exact format the text is searched as, instead of all instances in which the number can be formatted as. This causes an issue as you search for a customer's info and/or…
19 votes -
Last Called Agent (LCA) Functionality Required for Engage Messaging and Email Channel Types
We require the same “Last Called Agent” (LCA) capability for Engage Messaging and Email channels within Digital Queues as currently exists for Voice Queues. This will significantly improve customer experience by providing more efficient and personalised resolution to issues.
By reducing the need for clients to repeat information and details from previous interactions, this feature would potentially lower interaction durations. Furthermore, this capability is also essential in scenarios where agents receive commissions for successful sales, ensuring clients are routed back to the initial agent who provided consulting prior to the purchase of services or goods.
18 votes -
RingCX needs to display inbound callerID for calls coming into our Voice Queues.
Currently, all inbound calls to our RingCX Queues will only show the callerID as, "UNKNOWN."
Meanwhile, callerID works just fine for all inbound calls coming into RingEX.
This function needs to exist so that our Agents can better identify our customers as the call in.
16 votes -
Quality of Service (QoS) Portal for RingCX Calls
Implementing a Quality of Service (QoS) Portal in RingCX would allow visibility into whether call quality issues originate from the agent’s side or the caller’s side.
11 votes -
Ability to Set Skill Weight/Proficiency
Currently, RingCX does not provide the capability to define individual skill weight or proficiency for each agent individually. This capability is essential because it will:
- Reduce the need to create a separate skill ("Sales Proficiency 1", "Sales Proficiency 2", "Sales Proficiency 3" and so on) for each weight or proficiency level.
- Simplify and reduce the level of effort when creating and assigning skill profiles to agents.
- Streamline skill assignment within queue routing by enabling the selection of a required skill and the definition of a specific weight or proficiency range and order (high to low or low to high).
15 votes -
Save last number used when using "External Phone" as voice connection in RingCX salesforce and standard ( and other) web apps
when a user in RingCX uses "External Phone" as their Voice connection, save the last number used here. should be an easy change and it would save a LOT of "we ended up in an RNA state" support tickets...
21 votes -
Inbound Queued Callback option in Queue Events, it's only in DTMF sub-Queue Events options which is limiting
For some reason you can set a DTMF Queue event to be an Inbound Queue Callback, but you can't do it from the Queue Event itself. Every other option is there, but that one is missing. It seems a bug or missed item since it would only enhance the options available?
There are many reasons for a queue event to go to Callback rather than requiring a DTMF selection to do it.
13 votes -
Need Wrap Time to also apply to manual outbound calls
Within current functionality, wrap time only applies to inbound calls. Because of this, we are running into the issue where agents disconnect from a manual outbound call and immediately receive an inbound call.
The suggested workaround to make the "Post Call State" an unavailable state is not a feasible or sustainable solution for our company. Relying on agents to manually adjust their status to available introduces too much room for inconsistency and leadership has identified several issues with this manual process:
-Inconsistency: Relying on manual actions introduces a high risk of agents forgetting to update their status, leading to inconsistent…10 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.
10 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
10 votes -
Outbound Default and Custom Lead Field Order/Ranking
Clients need the ability to define the order in which standard and custom lead fields show within the agent interface. When creating custom lead fields "One", "Two", and "Three", the order shown to the agent is identical to the order in which custom fields were created (most likely by chance); however, when adding "six", "five", and "four", the order in which fields show has no logic as these show in the order "six", "four", "One", "Two", "five," and "Three." Generally, customers want and need the ability to set a rank in the same way as exists for disposition.
13 votes
- Don't see your idea?