140 results found
-
RingCX Chat Channel_Option to transfer chat directly to the agent
RingCX Chat Channel_Option to transfer chat directly to the agent
The customer is requesting the following options: When they reply to an email initiated by an agent, the response should be routed directly back to that agent. Alternatively, they would like the ability to manually transfer the email to the agent who originally contacted them."1 vote -
When logging out of RCX or refreshing: digital tasks are immediately sent back to the queue.
When logging out of RCX or refreshing: mails in task mode assigned to an agent move to the Inbox instead of being kept on the task mode. the idea is to "keep" digital tasks assigned for a certain time with the same agent even if he refreshes the browser or disconnect from RingCX.
5 votes -
Feature Request: Reopen and Return Chats with No Customer Activity to Queue Instead of Direct Agent Assignment
Currently, chats with no customer activity are being directly routed and assigned to agents. Ideally, these chats should be automatically reopened and returned to the general queue instead of being assigned to individual agents. This change would help ensure that agents are only assigned active or relevant chats, improving efficiency and customer experience.
Additionally, if chats closed by customers and then routed to agents is the expected behavior, this request aims to provide an alternative flow for organizations preferring a different process.
We recommend considering this feature for future updates to offer more flexible chat routing options.
4 votes -
Chats with no customer activity being routed to agents – Ideally, these should be reopened and returned to the queue instead of being direct
Currently, chats with no customer activity are being directly routed and assigned to agents. Ideally, these chats should be automatically reopened and returned to the general queue instead of being assigned to individual agents. This change would help ensure that agents are only assigned active or relevant chats, improving efficiency and customer experience.
Additionally, if chats closed by customers and then routed to agents is the expected behavior, this request aims to provide an alternative flow for organizations preferring a different process.
We recommend considering this feature for future updates to offer more flexible chat routing options.
2 votes -
Add two more drop-down menus in RingCX Digital Disposition (for a total of three) alongside the existing “Notes” text field.
Add two more drop-down menus in RingCX Digital Disposition (for a total of three) alongside the existing “Notes” text field.
Use Case: This will allow agents to categorize interactions more effectively with:
Notes (text field)
Disposition (drop-down)
Category 1 (drop-down)
Category 2 (drop-down)
9 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…
29 votes -
Digital interactions handled from "All messages" inbox no longer remain in triage queue.
For many companies, multiple agents work across multiple channels often using "all messages" tab to complete queries inbetween tasks rather than setting as available.
Currently, even when a query has had a response through "all messages" it remains in the queue to be accepted through "my messages". If an agent assigns a conversation to themselves through "all messages" then responds, this should remove it from the queue.
It isn't productive to need to accept conversations through "my messages" which have already been responded to by another member of the team.
2 votes -
Ability to reduce the auto-lock of conversations that have had no response from 4 days to required number.
Ability to reduce the auto-lock of conversations that have had no response from 4 days to required number.
Allowing conversations to stay open for 4 days does not work for businesses that use automation to resolve customer issues if the customer does not go to the end of the flow and leaves the conversation to later come back and restart. E.g. a customer contacts today regarding delivery and is advised that they need to allow 2 working days using AI. Customer comes back in 2 working days to query a missing item/damaged item and is greeted with the same conversation,…
4 votes -
1:1 SMS per agent
Currently, RingCX supports SMS communication only through queue-based messaging, which does not allow representatives to send and receive SMS messages individually. This limits the ability of reps to engage in personalized, one-on-one SMS conversations with prospects and customers.
We request the addition of a feature that enables each agent to have their own SMS-enabled Direct Inward Dial (DID) number. This would allow reps to send and receive SMS messages individually, improving direct communication, customer engagement, and tracking at the agent level.
Key benefits of this feature would include:
- Enhanced personalization and customer experience through 1:1 messaging
- Clearer accountability…2 votes -
Display Digital SMS ANI in RingCX Analytics Interaction Details
I’d like to submit a feature request for RingCX Analytics.
Currently, when reviewing Interaction Details for Digital SMS interactions, the ANI field displays as "N/A." For better visibility and reporting, it would be highly beneficial if the actual ANI (sending number) were displayed in this field.
This enhancement would help teams more effectively track and analyze SMS interactions, especially when handling multiple Digital SMS numbers.
1 vote -
Efficiency in Searching and Retrieving Customer Correspondence
Current Setup:
- Only a single basic search bar and limited filter options are available
- No status indicators (read/unread, responded/unresponded) at-a-glance
- No quick summary or icons to show assignment or engagement status unless each message is clicked individuallyRequest:
- Easily search email content by name, order number, or keywords
- Filter messages by response status (read/unread, new/engaged)
- Allow shift-based filtering (e.g., emails received from midnight–10 AM)3 votes -
Maintaining Cohesive Threads with Individual Customers
Current Setup:
- A 12-month thread inclusion is set up, however, new threads are still generated upon recontact
- Conversations are being stored in separate threads, creating a fragmented customer historyRequest:
- True conversation threading based on customer email address or ticket ID
- Ensure replies from customers within a set period are appended to the original thread regardless of closed status
- Reopened conversations (e.g. customer replies after closure) should rejoin the original thread, not create a new one3 votes -
Flexibility in Assigning and Managing Email Communications
Current Setup:
- No role-based restriction available for view-only access to digital queues
- Email Assignment via automatic routing or manual assignment by SupervisorsRequest:
- Viewing permissions and view email communications without being assigned or able to respond
- Visibility into email threads by all agents without compromising interaction ownership
- Auto-assignment by time-slot or agent shift3 votes -
turn off chat during after hours
To have an option in queue events that will automatically turn off the chat during after hours.
1 vote -
Configurable Notification Sounds for RingCX Engage Digital
Agents using RingCX Engage Digital currently have no control over the system notification sounds, leading to missed or inaudible alerts especially for high-priority events like new interactions or interaction updates. We propose introducing configurable sound notifications per user, similar to what is available in the RingCentral App (RingEX) for message alerts.
Proposed Functionality
Customizable Notification Profiles (Per Agent): Agents can choose from a preloaded list of sounds (chimes, beeps, alerts, etc.) for: New interaction; Interaction activity (e.g., customer reply, supervisor note); System alerts (e.g., disconnection, transfer, timeout).
Sound Settings Location: Accessible under Agent Settings > Notifications; Options to preview the…
1 vote -
Digital Condition - From/CC/To Fields
There is no condition for Digital contacts to check who the message is From, who was CC, or who the message is To (if outgoing). There exists a Digital Condition for Content, such as searching the Message Body or Message Subject, but not other details of the message. This condition would need to accept wildcards, as so that you could search for domains rather than a specific email address.
2 votes -
Chat send to email
Ability to email a chat transcript with contact details.
8 votes -
Copying an alphanumeric value from Engage Digital should not automatically format it as a phone number or trigger click-to-dial functionalit
Copying alphanumeric values should preserve the original formatting and not trigger or apply click-to-dial behavior unless the value is a valid phone number.
9 votes -
"Accept" and "Accept and Go" do the same thing when no active Interaction
In Ring CX, the "Accept" and "Accept and Go" buttons function the same when the Agent has no interaction currently in My Messages. However, this is contrary to the user expected behaviour. The user clicks the button "Accept" when they want to only accept the Interaction when it is offered to them, rather than accepting the Interaction and being take to it. However, when you click the "Accept" button and you have no current Interaction in My Message, the system will both accept the message and take you to the message.
I purpose to amend the design to fall within…
5 votes -
RingCX: Ability to implement interaction restrictions on a digital inbox for a team of agents
I have a use case with an existing client that the heavily uses digital interactions. They have a requirement to be able to restrict access to interactions associated with specific channels to a team of people.
In RingCX currently, by design, the digital inboxes are just filters for interactions - they are not permissive or restrictive. Although the inbox can be filtered to display certain interactions, an agent can use the search facility to be able to search and view interactions across all channel.
The use case is that an client may wish to create a channel that is used…
1 vote
- Don't see your idea?