1022 results found
-
QM - Request Further Review - Shouldn't Go Back to the Evaluator
If an agent submits a ‘Request Further Review’, this means they are ‘Challenging’ the score and want it re-reviewed. Currently, the dispute routes back to the Evaluator. This shouldn’t go back to the Evaluator but to a third-party person, like the QM Manager or Supervisor.
3 votes -
QM - Evaluation Notifications – Need Via Email
When a user submits an evaluation, only the person who was evaluated receives a notification, and it’s via the system, but not via email. I’d like to request that the system email the user an email notification that a new evaluation is ready to review.
12 votes -
QM – Evaluation Notifications – More Than One User
When a user submits an evaluation, only the person being evaluated receives the notification via the QM Tool that a new evaluation is ready to review. We should be able to choose additional people to receive a notification, like the agent's supervisor, for example. More than one person should be able to receive the notification.
15 votes -
Suppression Scripts
Some customers use 'agent flag' on outbound leads to reserve lead 'x' for that agent. Should another agent search for a lead, they would have the ability to dial this lead whether or not it is theirs. Something like suppression scripts, where the system does a check at the moment of dial attempt against some sort permissions list, would help manage this solution. Suppression scripting could be used in numerous ways within RingCX especially around manual dialing.
2 votes -
Automatic hold for warm transfers using integrated phone
Many customers would like to have a warm transferred call automatically put the far end on hold. This functionality is available within agent scripting. However, some customers use the RingEX extension integration which would require the agent scripting to use webservices. This change would give customers the ability to choose how they would like to handle warm transfers on a queue/campaign level and would alleviate the lift required to mimic this functionality.
20 votes -
Set of RingCX inbound ports to be minimized
RingCX requires many ingress firewall ports to be opened.
4 votes -
To allow a user to have the InContact SalesForce agent “lightning” dialer open and functional in multiple Salesforce browser tabs.
When using the SalesForce “Classic” dialer, a user could open a new (Chrome) browser tab with the same Salesforce session, and then open the “Classic” SalesForce Agent InContact dialer on each active Salesforce tab. It is common for our users to open additional Salesforce browser tabs to complete different functions within SalesForce (ex: A customer record, a Gantt chart, an inventory record, Geo Portal, and potentially others)This was not an issue with the “Classic” Dialer However, with the “Lightning” dialer, the first instance of the dialer opens normally – And when a user opens a second (and additional) Salesforce browser…
5 votes -
Reporting for Contact Center Numbers in RCO
ability to track usage and trends of phone numbers that are assigned to contact center services, today we do not have this ability and cannot monitor usage for CC services easily.
19 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 -
3rd Party Connector for Non-Native Messaging Channels and High Volume SMS (International)
Specific improvements in terms of 3rd party messaging channels:
WeChat support
LINE support
Telegram Support
High Volume SMS API for international customersInternational customers have requested a few 3rd party channels (listed above) not natively supported on RingCX. The request is to use a 3rd party service for a connector.
4 votes -
Addition to Dynamic Address Book
Agent's utilizing MAX agent address book would like to provide the DID / digital line number for external callers ahead of transferring to the employee.
3 votes -
Combine both mandatory disposition & ACW time
At present, you can either set a disposition in a skill to be mandatory, or provide a timer for after call work. Some customers have requested the ability to make a disposition mandatory & also count down the ACW rather than one or the other. The ability to provide a default disposition to be used if timer ends before a disposition is entered would be helpful as well. Ideal Scenario: Agent is mandated to provide a disposition, but after call work is timed.
1 vote -
Agent personal queue - Easy UI feature
Currently within RingCX, if a customer has a need for customized caller experience per agent, various routing requirements for agents, or something similar, they have to create an individual queue for every agent. This becomes cumbersome for a manager and reporting is not set up for this when wanting a wholistic view. Many customers see this as a requirement. Having a simple checkbox, drop down menu, or something similar associated at the agent level that allowed for simple management and reporting of direct agent routing would solve many issues for customers, new and old.
5 votes -
RingCentral Office Call Deflection into Engage Digital
The request is for RingEX IVR/call queue standalone to have the native ability to configure deflection into RingCX whatsapp/FB messenger/via SMS. For Example, in the IVR configuration, press 2 to receive an SMS with the whatsapp/FB Messenger link to start a digital conversation with agents.
5 votes -
Multi-lingual support
The ability to support other languages beyond English not just within features, but at the interface level.
7 votes -
Allow More Dialing Options for Outbound
The RingCX approach to outbound dialing is unique to the industry. There is a lot of value in this style of dialing (dial groups with campaigns, with only one dial group dialing at a time for an agent), but there are multiple markets with the style of dialing (example being insurance) that would allow agents to be a part of multiple campaigns across dial groups, support skills based routing (like on ACD), and take into account agent rank would also be helpful.
5 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 -
Default Manual Dialing to not be recorded
The default setting for a manual dial is not to record the agent call in RingCX. Within RingCX, Manual dialing is expected to be a circumvention of the system. This may go against some clients expectations of how a manual call should be managed. While there is a work around to tie the manual call to an inbound queue, some would find value in allowing a simple option to enabled recording and recording management by the agent for manual dials.
5 votes -
Better digital support for bank branches
The ask is for Engage Digital to better support digital interactions, which are becoming critical to many banks' business.
3 votes -
Ask an expert v2
The goal is to link Contact Center teams with rest of organizations to "ask an expert", outside of the agent-customer discussion. V1 had 1-way communication (RingCX->RingEX message and the response from expert not visible in RingEX). This would be helpful for customers who are interested in both RingCX and RingEX.
4 votes
- Don't see your idea?