211 results found
-
Update RingCX Agent for ALL Interaction Types
Currently, the RingCX agent only updates an agent's status when a voice interaction is received and not when a chat interaction is received.
When a chat interaction is received, the status of the Agent stays in "Available" even if the "Max number of concurrent interactions" setting is set to '1'.
This makes it difficult for Admins and Supervisors to accurately manage their agents, because this status does not change in the dashboards.
It would make sense to simplify the status changing in the CX agent for all interactions, when the agent is engaged.
58 votes -
Configurable Auto-Resolve Settings for SMS Shared Inbox
Customer is requesting additional configuration options for SMS Shared Inbox conversation management.
Current behavior automatically moves SMS conversations to the “Resolved” folder after a certain period, which the customer reports is causing confusion and inconvenience for users managing ongoing conversations.
Requested enhancements:
Ability to disable automatic movement of SMS conversations to the “Resolved” folder.
Ability to configure or extend the auto-resolve interval before conversations are moved to the “Resolved” folder (e.g., allow longer retention periods such as weeks or months).Customer also noted that replying to a resolved conversation starts a new active thread while previous messages remain in the…
17 votes -
Unified interaction routing: Detect forwards in real time and auto-close the orphaned interactions
Problem Statement:
Currently, when an agent forwards a digital interaction (like an email) to another channel or department, the system behaves differently than a standard requeue. Instead of seamlessly transferring the work, the system leaves the original interaction in an open state and generates a completely new, disconnected interaction for the forwarded item.Business Impact:
-Agent Confusion & Friction: Agents must perform multi-step manual wrap-ups to close the original interaction, increasing Average Handle Time (AHT).
-Fragmented Journey: Splitting the interaction breaks the historical thread, making it harder for the next agent to see the full context.
-Administrative Burden: Our admins…8 votes -
Enable Outlook GAL Search in RingCX Digital Email (To/CC/BCC/Forward Fields)
Business Need:
*Customers using RingCX Digital email interactions require the ability to search and select recipients directly from the Microsoft Outlook Global Address List (GAL) when composing, replying to, or forwarding emails.Current Behavior:
*The"Sync with RingEX Contacts" feature currently supports contact lookup only within the RingCX Integrated Softphone in SPOG for voice-related workflows. Users can search contacts and initiate or transfer calls using synchronized Outlook/GAL contact information. The feature does not provide GAL search capabilities within RingCX Digital email fields (To, CC, BCC, or Forward). As a result, agents must manually enter known email addresses. The upcoming release is…5 votes -
Native Mass Email Campaigns / Broadcasts
Description:
Currently, RingCX handles 1-to-1 email ticketing and interactions excellently, but it lacks the native ability to execute outbound mass email campaigns or broadcasts.Use Case:
Many of our customers frequently need to send mass announcements, policy updates, or marketing emails to large distribution lists directly from their contact center platform.Business Value:
Adding a native mass-email campaign feature within RingCX (Digital experience) would allow businesses to manage both inbound customer service and outbound mass communications in a single, unified platform. This provides a much smoother omnichannel experience and prevents customers from having to purchase and complexly integrate separate third-party…8 votes -
Social Media Comment Threads - Lock Ability
The problem:
- We manage hundreds of social media channels.
- When we run competitions, posts often get thousands of comments.
- Most comments don’t need a reply — but sometimes a customer service–related question appears in the middle of the thread.
- If we completely ignore a comment thread, we could miss those occasional important queries.
The feature request:
Allow us to “lock” a thread when we don’t need to respond further, so that if a new comment is added later, it appears as a new, separate thread — making it easier to spot and respond to.
Why it matters:
Without this, we…
34 votes -
Audit log to show when things are requeued by an agent
Within digital interactions it is not clear when agents have requeued interactions when looking at thread audit logs. This needs to be clear for agent management.
Alongside this it is best practice to show which queue the interaction is in as large accounts such as ours have close to 100 queues to manage. Currently, all we can see is that the interaction has moved to 'triage queue' with no insight into which queue that is.
11 votes -
Chat Popout Window
Allow user to pop chat window out, incase they need to navigate away from the current window.
14 votes -
Unify RingCX Digital Interaction Options To Simplify Agent and Supervisor Workflow.
Interaction Options are inconsistent across "My Messages" and "All Messages" which confuses agents and complicates the workflow.
Within the agent interface on RingCX there are significant differences between the options available within "My Messages" and "All Messages".
The "My Messages" section offers the following options:
-Transfer (to a queue)
-End Message
Extra Actions:
-Recategorize
-Reassign (directly to an agent)
-Mute Author
-View audit log
-Change Language
-Anonymize
-Ask an expertThe "All Messages" section offers the following options:
-Solve (End Message)
-Defer
Extra Actions:
-Recategorize
-Mute Author
-View audit log
-Change Language
-Anonymize
-Ask an expert…
70 votesIn design
-
Add the Polish language (audio CALLBACK)
Add Polish to callback audio messages to enhance the experience for Polish-speaking users by improving message comprehension and the quality of the customer journey in a multilingual context.
4 votes -
Ability to enable presence sync for call queues/groups vs individual users
Currently, presence sync can be enabled either for all users or individual users. For customers enabling presence sync for individual users, every new user will need to have presence sync enabled manually.
Having the ability to control sync for call queues/groups would both reduce the work required for enabling sync (there are less groups than there are users) and ensure future members of that call queue/group will have sync automatically enabled.
2 votes -
change button shape and placement
Ability to change the placement/size/shape of button using visual library. You can do this but the default button shows after interactions.
It doesn't make sense to allow button changes but only before the customer interacts, the change should implement permanently on the chosen URL/site regardless of interaction.
Please see case 28193631 for further information along with a video.
24 votes -
Google Chat as inbound channel for help desk use case
We support MS Teams as a channel for IT desk use case. Some customers asked to support Google Chat in a similar use case.
End user contacts Customer Support through a group in Google Chat and the chat is routed to an agent who is able to reply.
This use case is particularly important for BPOs which handles IT support for their customer (SCC, Sopra, Comearth, fimainfo - only in France)
https://rc.lightning.force.com/lightning/r/Account/001Hr000023vagMIAQ/view
https://rc.lightning.force.com/lightning/r/Opportunity/006TU00000DOMr7YAH/view
https://rc.lightning.force.com/lightning/r/Opportunity/006TU00000DQLXaYAP/view
https://rc.lightning.force.com/lightning/r/Account/0012H00001gHulwQAC/view13 votesThis is not a common channel in CCaaS space, we'll need to gather interest on this
-
RingCX Digital Message Notification Improvements
Digital interaction notifications in "My Messages" appear when an interaction dequeues to an agent.
Requeuing via "Transfer" (within the notification) removes the notification from the handling agent and shows a new notification for the agent to which the interaction dequeues.
However, transferring directly to another agent through "All Messages" keeps the notification with the initial agent, creating a three-party chat scenario.
To address this inconsistency, we propose unifying the behaviour for all transfers: remove the notification from the initial agent and display it for the receiving agent, matching queue transfer behaviour.
48 votes -
Ability to limit SMS channel selection when creating an outbound SMS message
When an agent generates a manual outbound SMS message, you have to select the channel to send the message from. The issue is that it shows every channel in the system, not just the channels/queues that agent is assigned to.
In our use case, agents have their own SMS queue but without the ability to restrict this, an agent can send an outbound SMS from any other agents queue or channel.
It would be ideal if there was a way to set a 'default' outbound channel instead of having to have the agent select a channel.
34 votes -
Ability to limit digital interactions per channel and per user
Is there a way to limit digital interactions? The client would like the ability to set limits for each digital channel per user.
For example:
1 interaction for email
5 interactions for chat8 votes -
SMS Channel Token Lifecycle
The ability to extend the token expiration period beyond the standard system default would be highly beneficial, along with the option to completely disable the token refresh requirement for SMS channels. If disabling the refresh is not feasible, an alternative would be to allow whitelisting of our channel ID or client ID to enable a long-lived access token, helping prevent potential service interruptions.
4 votes -
RingCX Spell Check where can control dictionary and if errors alert agent before sending.
RingCX Spell Check where can control dictionary and if errors alert agent before sending.
5 votes -
Real time agent analytics for when they are engaged in a digital interaction
Have a real time report/widget that will show digital interactions connected to an agent
18 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.
26 votes
- Don't see your idea?