466 results found
-
WhatsApp Outbound API
Would like to be able to send outbound WhatsApp messages by means of an API or via UI to one or multiple users. Outbound WhatsApp message will use Facebook templates API (regular + interactive templates).
15 votesRingCX has an API that facilitates this
-
Pulse: Get Pulse for Engage (Digital / Voice / Omni)
Extend "Pulse" to all Contact Center solutions.
3 votes -
2 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.
22 votes -
Set of RingCX inbound ports to be minimized
RingCX requires many ingress firewall ports to be opened.
4 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 -
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.
7 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 -
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 -
5 votes
-
Allow supervisor to move agent into available status.
Request is the ability for a supervisor to move an agent into available status.
13 votes -
Upgrade LumenVox ASR
The current Automated Speech tool works well for 'dictionary' based speech recognition, but is not as successful with multi-word or phrases (good at, press or say 1, say billing, etc). The ask is to improve the automated speech tool to utilize more advanced feature sets that will better satisfy IVR requirements.
2 votes -
RingCX account creation automation + Import/Export Functionality
The ability to quickly spin up templated accounts and have self-service import/export would be very helpful.
2 votes -
Support agent availability for Live Agent handover
The request is to Support agent availability for Live Agent handover based on category in EDF (Native google dialog flow adaptor).
For example, to support channels like Live-chat, which is real-time. No single API that would look at the category and find the agents for the category, then return info on whether an agent is available or not. Note that the request is to avoid using any APIs and leverage current native connector.3 votes
- Don't see your idea?