240 results found

1. Extension dialing between CX and EX

   Extension dialing between EX and CX is needed. Having to route calls between the two platforms with a 10 digit number results in the need for additional phone numbers, and cost for the customer.

   Another problem with 10 digit numbers, is that if routing is built using temporary numbers that will go away after porting, all of those references have to be updated on CX and EX after the port.

   116 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Under Review  ·  22 comments  ·  Agent & supervisor experience  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. 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., system sleep, network timeout, or WebSocket disconnects):

   🔄 Replace “WORKING” with a clearer status such as:

   “Connection Lost”
   “Disconnected”
   “Session Timeout”
   “Network Error”

   This status should only be triggered during system-driven disconnections, not manual agent actions.

   Why This Matters:

   • Improves transparency in real-time dashboards and routing behavior.

   • Helps admins and supervisors immediately identify connection issues vs. assuming the agent is working.

   • Reduces missed or mishandled calls due to misinterpreted statuses.

   • Supports accountability and follow-up (e.g., reaching out to the agent to check if they’re experiencing technical issues).

   • Aligns agent state logic with actual backend session state and improves operational visibility in high-volume contact centers.

   Reproducible Scenarios:

   Agent is logged in and set to AVAILABLE.
   Machine enters sleep mode.
   Upon waking, session reconnects — agent is placed in “WORKING” despite no input.

   OR

   Agent places an outbound call to a disconnected number.
   Call fails; agent transitions to “WORKING” without taking any further action.

   Impact:
   • Frequent confusion among admins.
   • Incorrect routing behavior due to “active” status.
   • Average of 4–5 agents per hour affected.
   • Impacts SLA, productivity, and agent accountability metrics.

   Suggested Implementation:
   • Enhance session reconnection logic to check:

   • If agent is not actively engaged with UI.

   • If the reconnection was system-triggered (e.g., Layer 2 reconnect or socket timeout).

   → Place agent into a descriptive, non-selectable system state that reflects the disconnection reason.

   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.,… more

   75 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Under Review  ·  5 comments  ·  Agent & supervisor experience  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. 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.

   49 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Under Review  ·  2 comments  ·  Agent & supervisor experience  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. transfer

   Include Agent Name on Transfer Segment in Interaction Details Report

   Request Summary:
   When an agent initiates a transfer (especially a warm transfer) during an active call, the Interaction Details Report splits the call into two segments under the same UII. However, the second segment (the transfer attempt) does not display the agent name, resulting in incomplete data when filtering by agent in the report. The customer requests that the agent name be captured for all segments of a call—including transfer attempts—to ensure accurate reporting.

   ---

   Current Behavior:
   • The agent's name is shown for the initial (inbound) segment.
   • During a transfer attempt, the second segment is created but shows Agent Name = N/A.
   • As a result, when filtered by agent, the report omits the transfer segment—causing data discrepancies.

   ---

   Expected Behavior:
   • Both the original and the transfer segments of the interaction should capture and display the initiating agent's name.
   • Filtering the Interaction Details Report by agent should include all call segments initiated by that agent, including canceled or completed transfer attempts.

   ---

   Business Impact:
   • The customer relies heavily on the Interaction Details Report to track individual agent activity.
   • Missing agent data on transfer segments leads to inaccurate call metrics, causing confusion and a lack of confidence in reporting.
   • For instance, OB calls made during active IB calls are not tracked properly, resulting in agent performance being under- or over-represented.

   ---

   Use Case Reproduction (as demonstrated by customer):
   1. Agent places outbound call (OB) to their own cell.
   2. While on call, agent clicks Transfer, dials another number, connects, then cancels the transfer.
   3. Interaction Details shows:
   o 2 call segments (same UII),
   o 1st segment: agent name populated,
   o 2nd segment: agent name = N/A.
   4. Filtering by agent omits the 2nd segment entirely.

   ---

   Supporting Evidence:
   • Multiple test scenarios (UIIs included in case notes).
   • Screenshots, spreadsheets, and logs attached to Case 27382978.
   • Customer provided 4-page Excel document showing discrepancies between reports.
   • Customer's updated report (“Updated Agent Activity Report: Daily”) does not fix the issue due to missing agent name in core data.

   ---

   Requested Solution:
   Modify the data model or reporting logic so that agent information is retained and displayed in all segments of an interaction, especially during transfer attempts (warm or cold), regardless of whether the transfer is completed or canceled.

   Include Agent Name on Transfer Segment in Interaction Details Report

   Request Summary:
   When an agent initiates a transfer (especially a warm transfer) during an active call, the Interaction Details Report splits the call into two segments under the same UII. However, the second segment (the transfer attempt) does not display the agent name, resulting in incomplete data when filtering by agent in the report. The customer requests that the agent name be captured for all segments of a call—including transfer attempts—to ensure accurate reporting.

   ---

   Current Behavior:
   • The agent's name is shown for the initial (inbound) segment.
   • During a… more

   • 

   58 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Under Review  ·  1 comment  ·  Realtime & historical analytics  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Cost Centers built in RCX

   Currently, RCX bills lack a summary page showing agent allocations, similar to RingEX's cost center billing. The customer requests this feature

   37 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Under Review  ·  0 comments  ·  Other  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. call offers for the longest wait time

   RCX system prioritizes agents based on their overall Available Status time for the day, rather than their current Highest Availability:

   -agents who have recently returned from an offline state (such as breaks or lunch) receive calls before those who have been continuously available.

   -to better accommodate the varying preferences of our clients, we kindly request the addition of an option to enable or disable this feature. This adjustment would allow clients to configure their queues according to their specific needs and ensure a more equitable distribution of calls.

   We understand that this behavior aligns with the current design of RCX, where an agent's overall available time is accumulated rather than resetting with each offline period. However, this has led to some challenges for our users, who have noted that agents who have been available continuously are not receiving calls as expected.

   RCX system prioritizes agents based on their overall Available Status time for the day, rather than their current Highest Availability:

   -agents who have recently returned from an offline state (such as breaks or lunch) receive calls before those who have been continuously available.

   -to better accommodate the varying preferences of our clients, we kindly request the addition of an option to enable or disable this feature. This adjustment would allow clients to configure their queues according to their specific needs and ensure a more equitable distribution of calls.

   We understand that this behavior aligns with the current design of RCX,… more

   193 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Under Review  ·  13 comments  ·  Interaction routing, workflow & queuing  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. 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/view

   10 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  Digital experience  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Under Review  ·  AdminGrigori (Product Manager Contact Center, RingCentral) responded

   This is not a common channel in CCaaS space, we'll need to gather interest on this

8. Dashboard for agents in RingCX | Agent platform.

   RingCX agents should have the option to view the dashboard to see the other agent's status in the RingCX Agent platform, not in Analytics, without the need to change the agent type to Supervisor.

   45 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Under Review  ·  5 comments  ·  Agent & supervisor experience  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Unexpected Call Drop: Entire 3-Way Conference Ends When Agent Disconnects in RingCX

   Problem Description
   When a RingCX agent (Party A) places a manual outbound call to Party B, then adds Party C to create a 3-way conference (Agent + Party B + Party C), if the agent (Party A) disconnects, the entire conference call is dropped for all participants (Party B and Party C).

   ---

   Expected Behavior
   If the agent (Party A) disconnects from a 3-way conference, the call should continue between Party B and Party C. This is expected in standard call conferencing logic where the initiator disconnecting does not necessarily terminate the call for all participants.

   • 

   31 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Under Review  ·  1 comment  ·  Agent & supervisor experience  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. 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.

    24 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Under Review  ·  2 comments  ·  Digital experience  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Separate Off Hook mode/ permanent connection management options for inbound and dialer-campaigns calling

    customers would like to be able to manage answer mode in different ways depending on the type ( inbound/manual outbound VS dialers/campaigns ) :
    have the ability to enable/disable the off hook / permanent connection for inbound calls separately from the dialer/campaigns off hook / permanent connection mode.

    so even if you disable the permanent connection/off hook for inbound, you can still have the dialer calls (as when you start dialing it switches you to off hook mode automatically).

    or the other way around if you start the dialer - it would switch to off hook for the dialer - but it would not force the off hook for inbound calls (the auto answer will not be forced).

    I attached a screenshot to show what features I'm referring to.

    thanks

    customers would like to be able to manage answer mode in different ways depending on the type ( inbound/manual outbound VS dialers/campaigns ) :
    have the ability to enable/disable the off hook / permanent connection for inbound calls separately from the dialer/campaigns off hook / permanent connection mode.

    so even if you disable the permanent connection/off hook for inbound, you can still have the dialer calls (as when you start dialing it switches you to off hook mode automatically).

    or the other way around if you start the dialer - it would switch to off hook for the dialer -… more

    •  

    30 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Under Review  ·  1 comment  ·  Other  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Add the existing (warm) "Transfer" call control functionality to the "Requeue" feature. "

    When using the (warm) "Transfer" feature, agents are given call controls for both calls independently. This allows agent to switch between both calls as needed by placing one leg on hold. It also provides options to disconnect certain legs, their leg only, or the entire call.

    In contrast when using the (Stay on call) "Requeue" feature agents do not have any ability to switch between both calls.

    If an agent needs to reconnect the voice path to the original while utilizing "Requeue", they must hit "Resume". By doing the Requeue is effectively cancelled and agents would need to restart the process if they wish to continue with requeue, losing their original place in line from the first attempt.

    Agents are also unable to drop from the call once it has begun "requeuing" to the secondary queue until it is answered by an agent from the secondary queue. If agent chooses to hang up while waiting in the secondary queue, the entire call drops.

    We need to add the ability to control both calls independently when utilizing "Requeue" and "Stay on call" option just like a warm transfer would allow.

    When using the (warm) "Transfer" feature, agents are given call controls for both calls independently. This allows agent to switch between both calls as needed by placing one leg on hold. It also provides options to disconnect certain legs, their leg only, or the entire call.

    In contrast when using the (Stay on call) "Requeue" feature agents do not have any ability to switch between both calls.

    If an agent needs to reconnect the voice path to the original while utilizing "Requeue", they must hit "Resume". By doing the Requeue is effectively cancelled and agents would need to restart the… more

    15 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Under Review  ·  0 comments  ·  Interaction routing, workflow & queuing  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. RingCX Voice Queue Call Distribution

    The customer is requesting to have a call routing feature that will route the call based on the number of calls each agent has received, to ensure a more balanced distribution.

    14 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Under Review  ·  0 comments  ·  Interaction routing, workflow & queuing  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. RingCX bulk upload on phonebook

    Requesting to have the bulk upload on directories under RingCX. Uploading new contacts on directories have only one option to upload one by one. If needing to upload hundreds of contacts, that will take time.

    Creating global phone book entries in RingCX screenshots of options attached.

    •  

    •  

    14 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Under Review  ·  3 comments  ·  Admin experience  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. To Have Start and End Time Attributes in RingCX for Salesforce

    We would like to request the addition of attributes in RingCX for Salesforce that capture both start and end times. This functionality would provide better tracking, reporting, and integration with workflows, ultimately improving visibility and efficiency for users.

    6 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Under Review  ·  0 comments  ·  Integrations & APIs  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Cancelling a requeued call

    Currently, if you requeue a call and select say on the call, there is not a way to take the call back. If you click end call, it will disconnect the call. There is no option to cancel the requeue. With transferring calls, you can cancel the transfer, but you cannot cancel a requeue.

    19 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Under Review  ·  4 comments  ·  Interaction routing, workflow & queuing  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. 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.

    6 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Under Review  ·  1 comment  ·  Digital experience  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. Increase Historical Report Capacity

    RingCX Historical Reporting is limited to 60k lines per RC Support site. Customer is making around 200K OB dials per day, and wants to be able to report on every interaction in one report. With current limitations, customer will have to download 4 separate reports.

    6 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Under Review  ·  2 comments  ·  Realtime & historical analytics  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. RingCX - Play Remaining Esimated Wait Time to Callers in Queues (More than just once)

    When callers are waiting in a queue, RingCX can only play back the estimated wait time once. Other phone systems have an option to let callers know the estimated wait time every X seconds, such as once every 45 seconds, so they know how long it is before their call is answered.

    We would like to see RingCX updated so it allows us to teller our callers how long it is before their call is answered more than just one time.

    Also, there is a RingCX configuration that lets the callers know their position in the queue, such as "caller number 20 in the queue". RingCX only plays this back once. It would also make sense to advise callers as this number changes, so they know how many callers are ahead of them before their call is answered.

    When callers are waiting in a queue, RingCX can only play back the estimated wait time once. Other phone systems have an option to let callers know the estimated wait time every X seconds, such as once every 45 seconds, so they know how long it is before their call is answered.

    We would like to see RingCX updated so it allows us to teller our callers how long it is before their call is answered more than just one time.

    Also, there is a RingCX configuration that lets the callers know their position in the queue, such as "caller… more

    24 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Under Review  ·  2 comments  ·  Other  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Mark email that did not have an agent reply as "Solved" rather than "Ignored"

    Whenever an agent solves an interaction without responding to the message, the interaction is being tagged as "Ignored". This cause confusion as the agent actually accepted the interaction but it just didn't require a reply thus the agent is marking them as solved. It should be tagged "Solved" or something else other than "Ignored"

    9 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Under Review  ·  1 comment  ·  Digital experience  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating