356 results found

1. Call controls for RingCX calls with desk phone pairing

   RingCX Voice Connection (RingCentral Phone + Deskphone Pairing) Call Control Enhancement

   Summary:
   Request to enhance call control functionality when using "RingCentral Phone" as the selected voice connection within RingCX paired with Deskphone

   Description:
   Currently, when "RingCentral Phone" is selected as the voice connection in RingCX, the call control remains within the RingCX platform (ringcx.ringcentral.com). When Deskphone Pairing is enabled, it allows RingCX calls to be answered through the Deskphone. As a result, users are unable to perform call control actions—such as call transfer, hold and mute— directly from the Deskphone.

   Expected Behavior:
   When "RingCentral Phone" is selected as the voice connection and RingCentral App is Paired to a Deskphone, users should not be limited to using Deskphone as Media Endpoint. Agents should be able to manage call control on the Deskphone to:

   Perform call transfers
   Access standard call control features (hold, mute, transfer, etc.)
   Seamlessly interact with RingCX features, including voicemail routing

   Business Impact:
   This limitation affects agent workflow and efficiency, especially for organizations transitioning from Integrated Softphone to RingCentral Phone. It prevents agents from utilizing familiar and centralized call handling using their Deskphone

   Use Case:
   RingCX Agents would like to utilize full call handling capabilities using deksphone buttons, including the ability to transfer calls, put callers on hold or mute. The current behavior results in failed transfers, hold reflecting possible audio issues and operational friction.

   Requested Enhancement:
   Enable full call control using Deskphone when "RingCentral Phone" is used as the voice connection in RingCX and RingCentral App is Paired to the Deskphone.

   RingCX Voice Connection (RingCentral Phone + Deskphone Pairing) Call Control Enhancement

   Summary:
   Request to enhance call control functionality when using "RingCentral Phone" as the selected voice connection within RingCX paired with Deskphone

   Description:
   Currently, when "RingCentral Phone" is selected as the voice connection in RingCX, the call control remains within the RingCX platform (ringcx.ringcentral.com). When Deskphone Pairing is enabled, it allows RingCX calls to be answered through the Deskphone. As a result, users are unable to perform call control actions—such as call transfer, hold and mute— directly from the Deskphone.

   Expected Behavior:
   When "RingCentral Phone" is selected as the voice… more

   64 votes

   Vote 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

   Planned  ·  9 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. 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.

   169 votes

   Vote 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

   Future Consideration  ·  24 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. Add Busy Tone and Announcement options for RingEX calls during active RingCX sessions

   Current Behavior: The "Send RingEX calls to voicemail" feature currently routes all direct calls to the user’s personal voicemail while they are on a RingCX call. There is no alternative for organizations that do not use voicemail or want to avoid agents managing a personal inbox backlog.

   Proposed Solution: Expand the current "Send to Voicemail" permission into a selectable menu with three additional handling options:

   • Busy Tone: Disconnect with a busy signal to indicate the agent is occupied.

   • Announcement Only: Play a "User is busy" recording and disconnect without allowing a voicemail to be left.

   • Forwarding: Route the direct call to a prefered destination.

   Business Value:

   • Agent Efficiency: Prevents REX personal voicemail clutter for agents in high-volume CX environments.

   • Improved CX: Callers get immediate feedback (Busy/Announcement) rather than leaving messages that may not be checked for hours.

   • Flexibility: Supports business workflows where personal voicemail is disabled or not used.

   Benefits:

   • Eliminates administrative overhead for agents.

   • Provides more professional call handling options during active CX sessions.

   • Allows for "Active" rather than "Passive" call management.

   Current Behavior: The "Send RingEX calls to voicemail" feature currently routes all direct calls to the user’s personal voicemail while they are on a RingCX call. There is no alternative for organizations that do not use voicemail or want to avoid agents managing a personal inbox backlog.

   Proposed Solution: Expand the current "Send to Voicemail" permission into a selectable menu with three additional handling options:

   • Busy Tone: Disconnect with a busy signal to indicate the agent is occupied.

   • Announcement Only: Play a "User is busy" recording and disconnect without allowing a voicemail to be left.

   • Forwarding: Route the direct call… more

   20 votes

   Vote 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

   New  ·  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

4. Align RingCX Agent 'Stats' Tab with Real-Time Analytics: Split 'Presented' into Inbound & Outbound

   Currently, in the RingCX Agent Interface, the Stats tab (specifically under the 'Inbound' and 'Blended' views) provides a single column for "Presented" calls. This metric is an aggregate that combines both Inbound and Outbound presented calls into one figure.

   In contrast, the RingCX Analytics Real-Time Dashboards (e.g., the People Services Dashboard) already provide a granular breakdown with separate columns for "Pres. IB" (Inbound) and "Pres. OB" (Outbound).

   This discrepancy creates a lack of visibility for agents who need to distinguish between their reactive (inbound) and proactive (outbound/manual dial) performance within their primary workspace.

   Proposed Solution
   Update the Table Settings within the Agent 'Stats' view to allow for more granular metric selection. Specifically, we request that the single "Presented" checkbox be replaced or supplemented with:

   Presented Inbound (Pres. IB)

   Presented Outbound (Pres. OB)

   This change should be reflected in both the Stats Table columns and the Summary Tiles at the top of the interface.

   Key Benefits
   Consistency: Aligns the Agent UI with the existing Real-Time Analytics/Supervisor reporting structure, providing a "single source of truth" across the platform.

   Performance Tracking: Allows agents to clearly see how many manual dials or outbound campaign calls have been presented versus inbound queue volume.

   Accuracy: Prevents confusion when an agent's "Presented" count is high, but their "Answered" count looks low because they were performing manual dials that are currently being lumped into the same stat.

   Operational Efficiency: Reduces the need for agents to ask supervisors for a breakdown of their activity, as they can self-serve this data directly from their RingCX workspace.

   Supporting Documentation
   Refer to attached: JLP RCX Agent Stats Settings.jpg – Shows the current limitation in the Table Settings.

   Refer to attached: JLP RCX Real Time Dash.jpg – Shows the existing functionality in Analytics that we wish to see mirrored in the Agent view.

   Currently, in the RingCX Agent Interface, the Stats tab (specifically under the 'Inbound' and 'Blended' views) provides a single column for "Presented" calls. This metric is an aggregate that combines both Inbound and Outbound presented calls into one figure.

   In contrast, the RingCX Analytics Real-Time Dashboards (e.g., the People Services Dashboard) already provide a granular breakdown with separate columns for "Pres. IB" (Inbound) and "Pres. OB" (Outbound).

   This discrepancy creates a lack of visibility for agents who need to distinguish between their reactive (inbound) and proactive (outbound/manual dial) performance within their primary workspace.

   Proposed Solution
   Update the Table Settings within… more

   •  

   •  

   •  

   •  

   26 votes

   Vote 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  ·  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

5. ring CX call id

   When receiving an incoming call from an employee their name is not displayed unless they are on the ex side only. This causes confusion on who is calling. We would like for the employees name that is calling any internal extension to be displayed on the incoming call whether they are cx or ex

   19 votes

   Vote 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

   New  ·  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

6. RCX AGENT DIALPAD

   RCX Agent Dialpad should be added on Agent Tab in RingCentral App.
   This means that the Dialer/Dialpad within RingCX Tab has RingCX CallerID's by default and will have no option to use RingEX lines as OB Caller ID. This will enhance and minimize agent errors when making an outbound call.

   •  

   12 votes

   Vote 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

   New  ·  3 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

7. Feature Request: Configurable Agent “Working” State Timeout

   Feature Request: Configurable Agent “Working” State Timeout
   Summary

   Enable RingCX administrators to configure a maximum duration that agents can remain in the Working status. When an agent reaches the configured timeout—for example, one hour—RingCX should automatically perform an administrator-selected action.

   Problem Statement

   • Agents may unintentionally remain in the Working status for extended periods, making them unavailable to receive new interactions. This can reduce queue coverage, affect service levels, and require supervisors to identify and correct agent statuses manually.

   Proposed Solution

   • Add an Agent State Timeout setting to the RingCX Admin Portal. Administrators should be able to:

   1. Enable or disable the timeout for the Working status.
   2. Configure the timeout duration.
   3. Select the action RingCX performs when the threshold is reached. Timeout Actions

   Administrators can choose one of the following actions:

   1. Sign out of RingCX • Completely sign the agent out of RingCX.
   2. Sign out of all queues • Remove the agent from every assigned queue while keeping them signed in to RingCX.
   3. Change status to Available • Automatically change the agent’s status from Working to Available so they can receive new interactions.
   4. Do nothing Keep the agent in Working status. The timeout event may still be recorded for reporting or monitoring purposes.

   Functional Requirements
   • The timeout duration must be configurable by an authorized administrator.
   • The timer starts when an agent enters the Working status.
   • The timer resets whenever the agent exits and later re-enters the Working status.
   • The configured action is performed only if the agent remains continuously in Working status for the entire timeout period.
   • If the agent changes status before the threshold is reached, no timeout action is performed.
   • The setting may be configured globally and, if supported by RingCX’s configuration model, overridden for specific teams or agent groups.
   • Only users with the appropriate administrative permissions can change the timeout configuration.
   • Configuration changes should be recorded in the administrative audit log.

   Each timeout event should record:
   • Agent name or ID
   • Time the agent entered Working status
   • Configured timeout duration
   • Time the threshold was reached
   • Action performed

   Result of the action

   Agent Experience

   • RingCX should optionally notify the agent before performing the configured action. For example:

   "You have been in Working status for 55 minutes. Your status will automatically change in 5 minutes."

   When the action is performed, the agent should receive a confirmation explaining what happened and why.

   Acceptance Criteria

   1. Given that the Working State Timeout is enabled, when an agent remains continuously in Working status for the configured duration, then RingCX performs the selected timeout action.

   2. Given that the selected action is Sign out of RingCX, when the timeout is reached, then the agent is signed out of RingCX.

   3.Given that the selected action is Sign out of all queues, when the timeout is reached, then the agent is removed from all queues but remains signed in to RingCX.

   1. Given that the selected action is Change status to Available, when the timeout is reached, then the agent’s status changes to Available.

   2. Given that the selected action is Do nothing, when the timeout is reached, then the agent remains in Working status and no automatic status change or sign-out occurs.

   3. Given that an agent exits Working status before reaching the timeout, then no timeout action is performed and the timer is cleared.

   4. Given that an agent later re-enters Working status, then a new timeout period begins.
      Given that an automatic timeout action occurs, then the event and its result are recorded in the audit or activity log.

   5. Given that a pre-timeout notification is enabled, then the agent receives a warning at the configured time before the action occurs.

   Business Value

   This feature would help organizations:

   • Prevent agents from remaining unavailable unintentionally.
   • Improve queue coverage and workforce availability.
   • Reduce manual monitoring by supervisors.
   • Improve the accuracy of agent-state reporting.
   • Maintain service levels through consistent status management.

   Feature Request: Configurable Agent “Working” State Timeout
   Summary

   Enable RingCX administrators to configure a maximum duration that agents can remain in the Working status. When an agent reaches the configured timeout—for example, one hour—RingCX should automatically perform an administrator-selected action.

   Problem Statement

   • Agents may unintentionally remain in the Working status for extended periods, making them unavailable to receive new interactions. This can reduce queue coverage, affect service levels, and require supervisors to identify and correct agent statuses manually.

   Proposed Solution

   • Add an Agent State Timeout setting to the RingCX Admin Portal. Administrators should be able to:

   1. Enable or… more
   7 votes

   Vote 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

   New  ·  0 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

8. INTERCEPT

   Subject: Feature Request: Improve Granularity of "INTERCEPT" Call Disposition Code

   Currently, the INTERCEPT call disposition is used as a generic status for multiple distinct call failure scenarios, including invalid numbers, carrier blocks, and user rejections.

   This lack of specificity makes it difficult for administrators and end-users to quickly diagnose the root cause of a failed call. While backend codes may differentiate these events, that information is not exposed on the front end, forcing admins to perform manual investigations to understand the true outcome.

   We propose replacing the single INTERCEPT disposition with more granular and descriptive statuses that reflect the actual reason for the call failure. Examples would include:

   Invalid Number

   Blocked by Carrier

   Rejected by User or Declined

   Implementing this change would provide immediate, actionable insight into call failures directly within the user interface. This would significantly improve the user experience, reduce administrative overhead, and allow for much faster troubleshooting.

   Subject: Feature Request: Improve Granularity of "INTERCEPT" Call Disposition Code

   Currently, the INTERCEPT call disposition is used as a generic status for multiple distinct call failure scenarios, including invalid numbers, carrier blocks, and user rejections.

   This lack of specificity makes it difficult for administrators and end-users to quickly diagnose the root cause of a failed call. While backend codes may differentiate these events, that information is not exposed on the front end, forcing admins to perform manual investigations to understand the true outcome.

   We propose replacing the single INTERCEPT disposition with more granular and descriptive statuses that reflect the actual… more

   67 votes

   Vote 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

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

   132 votes

   Vote 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  ·  8 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

10. Automatically log the RingCX agent out after they stay idle for a certain period of time

    To have a settings where they can set an idle time to automatically log out RingCX agent.
    New status "Auto Logged Off" to track in reporting.
    Option to schedule log outs, e.g. in the end of the day.

    13 votes

    Vote 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

11. Hold timer ringback

    Request to add the following feature, "Hold Timer Ringback"

    Feature that automatically rings the agent’s phone or forces the call to pop back into an active state after a set duration defined in the admin portal.

    8 votes

    Vote 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

    New  ·  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

12. Post call status to remain the same as the pre-call status for the agents/supervisors

    When an agent or supervisor's pre-call state is Working, their status should remain the same after every inbound call or outbound call.

    13 votes

    Vote 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

    Implemented  ·  3 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

13. Feature Request: Scheduled Callbacks for Voice Queue Dispositions

    Feature Request Title: Scheduled Callbacks for Voice Queue Dispositions

    Product Area: RingCX — Voice Queues / Dispositions / Queue Callback Lists

    Feature Request:

    Add a Schedule Callback option to Voice Queue dispositions. When an agent selects this disposition, they should be able to specify the callback date, time, phone number, and optional notes.

    The scheduled callback should then appear in the Queue Callback Lists tab and notify the appropriate agent when it becomes due.

    Requested notification and dialing options:

    • Display an alert, banner, or persistent notification telling the agent that a scheduled callback is due and needs to be completed.

    • Optionally allow RingCX to automatically dial the scheduled callback when the assigned agent’s state changes to Available.

    • If the original agent is unavailable, optionally allow the callback to be handled by another eligible agent in the queue.

    • Show the callback’s status, such as Scheduled, Due, In Progress, Completed, Missed, or Rescheduled.

    • Allow authorized users to reschedule, reassign, or cancel a pending callback.
    Record the callback activity in the interaction history and reporting.

    Example Workflow:

    1. An agent completes a Voice Queue interaction.
    2. The customer requests a callback at a specific date and time.
    3. The agent selects Schedule Callback as the Voice Queue disposition.
    4. The agent enters the callback schedule and saves it.
    5. The callback is added to the Queue Callback Lists tab.
    6. When the callback becomes due, RingCX displays an alert or banner to the agent.
    7. Depending on the configured behavior, the agent can manually start the call, or RingCX automatically dials the customer when the agent becomes available.
    8. The callback result is recorded and the item is removed from, or marked completed in, the callback list.

    Business Need:

    Voice Queue agents often receive requests to call customers back at a specific time. Without a native scheduling workflow, agents must rely on external calendars, notes, or manual reminders. This creates a risk of missed callbacks, inconsistent customer experiences, and incomplete reporting.

    Adding scheduled callbacks directly to Voice Queue dispositions would centralize callback management, improve agent accountability, reduce missed customer commitments, and provide better operational visibility.

    Important Distinction:

    This request is specifically for Voice Queue dispositions. It is separate from the existing scheduled-callback functionality associated with Campaign Dialer dispositions. The requested feature should work for inbound or Voice Queue interactions and integrate with the Queue Callback Lists workflow.

    Acceptance Criteria:

    • Agents can schedule a callback from a Voice Queue disposition.
    • The callback date, time, time zone, phone number, and notes can be captured.
    • The scheduled callback appears in the Queue Callback Lists tab.
    • The assigned agent receives a visible notification when the callback becomes due.
    • Administrators can configure manual dialing or automatic dialing when the agent becomes available.
    • RingCX prevents multiple agents from calling the same callback simultaneously.
    • Missed or overdue callbacks remain visible and can be escalated or reassigned.
    • Callback attempts and final outcomes are included in interaction history and reporting.

    Feature Request Title: Scheduled Callbacks for Voice Queue Dispositions

    Product Area: RingCX — Voice Queues / Dispositions / Queue Callback Lists

    Feature Request:

    Add a Schedule Callback option to Voice Queue dispositions. When an agent selects this disposition, they should be able to specify the callback date, time, phone number, and optional notes.

    The scheduled callback should then appear in the Queue Callback Lists tab and notify the appropriate agent when it becomes due.

    Requested notification and dialing options:

    • Display an alert, banner, or persistent notification telling the agent that a scheduled callback is due and needs to be… more

    5 votes

    Vote 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

    New  ·  0 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

14. Sync RingCentral Desktop Application With RingCX

    RingCentral should implement a call status synchronization between the RingCentral Desktop application and RINGCX. When you are on a call using your RingCentral desktop application, this status should be reflected in real time to RINGCX preventing the RingCX app from present you an additional incoming call.

    Key Points:
    1. Real Time Status Updates: Both RingCentral Desktop and RingCX should be able to communicate real time call statuses to each other. When you answer or make a call on one platform, the other should recognized that you're on an active call.

    1. Presence Integration: Leverage the user presence feature to reflect an "on -call" status across all platforms. This willhelp ensure that RingCX acknowledges when you are engaged on a call via the RingCentral Desktop app.

    2. Unified Call Management: By integrating call management across RingCentral and RINGCX you can avoid duplicate call notifications, ensuring a seamless experience regardless of which platform you are using.

    3. APIs or SDKs: if not available RingCentral could introduce APIs or SDKs that allow for better communication between the desktop application and the RingCX system, allowing both to update each other in real time when calls are initiated or received.

    RingCentral should implement a call status synchronization between the RingCentral Desktop application and RINGCX. When you are on a call using your RingCentral desktop application, this status should be reflected in real time to RINGCX preventing the RingCX app from present you an additional incoming call.

    Key Points:
    1. Real Time Status Updates: Both RingCentral Desktop and RingCX should be able to communicate real time call statuses to each other. When you answer or make a call on one platform, the other should recognized that you're on an active call.

    1. Presence Integration: Leverage the user presence feature to reflect an… more

    329 votes

    Vote 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

    Planned  ·  27 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

15. Preserve Caller ID When Transferring from RingCX to RingEX

    Product Area(s):

    RingCX (Contact Center)

    RingEX (Phone System / MVP)

    Call Handling & Caller ID Display

    Current Behavior:
    When an external call is routed through a RingCX queue and answered by an agent, and the agent then transfers the call to a RingEX user (via warm or blind transfer), the RingEX recipient currently sees the original external caller’s phone number as the caller ID.

    There is no visibility into which RingCX agent initiated the transfer. This can lead to confusion, lack of internal context, and inefficiencies in how the transferred call is handled.

    Requested Enhancement:
    Introduce a configurable caller ID display option for calls transferred from RingCX to RingEX, allowing the receiving RingEX user to see:

    The transferring RingCX agent’s name and/or extension

    The original external caller ID

    Or both, depending on the administrator's preference

    This setting should be manageable at the admin level, and ideally configurable per queue or user group, to align with various business workflows.

    Business Justification / Use Case:
    Many RingCX customers operate in high-volume, multi-agent environments where external calls are frequently transferred to subject matter experts, team leads, or support departments using RingEX extensions.

    The current behavior limits visibility into who initiated the transfer. This causes issues such as:

    RingEX users answering calls with no internal context, unsure if it’s a direct customer call or a handoff.

    Delays in handling the call properly due to lack of warm introduction cues.

    Difficulty in tracking agent performance or follow-up responsibility, as the handoff origin is not visible.

    Missed opportunity to personalize the response or acknowledge the agent who transferred the call.

    With the requested feature, organizations can streamline their workflows, reduce miscommunication, and provide a smoother, more professional customer experience.

    Benefits:

    Enhances internal communication clarity during transfers

    Enables faster and more informed call handling

    Supports accountability and training, especially in customer support or sales teams

    Aligns with existing behaviors seen in some legacy PBX or call center solutions

    Adds flexibility for businesses to define how caller ID should appear in hybrid RingCX–RingEX environments

    Priority:
    Medium to High – This enhancement would significantly improve day-to-day operational efficiency, particularly for businesses that rely on frequent call transfers between RingCX and RingEX users.

    Workaround (if any):
    There is currently no workaround to modify caller ID presentation on RingEX when calls are transferred from RingCX. Some customers attempt to inform the RingEX user via chat or email, but this is not scalable or reliable in real-time.

    Product Area(s):

    RingCX (Contact Center)

    RingEX (Phone System / MVP)

    Call Handling & Caller ID Display

    Current Behavior:
    When an external call is routed through a RingCX queue and answered by an agent, and the agent then transfers the call to a RingEX user (via warm or blind transfer), the RingEX recipient currently sees the original external caller’s phone number as the caller ID.

    There is no visibility into which RingCX agent initiated the transfer. This can lead to confusion, lack of internal context, and inefficiencies in how the transferred call is handled.

    Requested Enhancement:
    Introduce a configurable caller ID… more

    45 votes

    Vote 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

    Future Consideration  ·  3 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

16. Agent DND state

    True, do not disturb state where agents can place themselves in, and even transferred calls are not possible to be delivered to them.

    7 votes

    Vote 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

    New  ·  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

17. Feature Request: Granular Call Monitoring Permissions for Agent Role

    Description:

    Currently, in RingCX, the only way to enable Call Monitoring/Listening functionality is by changing an Agent's role to Supervisor. However, this creates a significant data visibility issue, as it grants Supervisors access to queues and information beyond their designated team or group, which may include sensitive data from other departments or companies.

    Request:

    We would like to request the implementation of a granular permission setting that allows users with the Agent role to be granted Call Monitoring privileges for a specific group of agents or queues only, without the need to elevate them to a Supervisor role.

    Proposed Solution Features:

    Add a "Call Monitoring" permission toggle to the Agent role settings.

    Allow Admins to assign monitoring access to specific queues or agent groups.

    Prevent monitored Agents from viewing or accessing unrelated queues or data.

    Benefits:

    Maintains strict data segmentation and confidentiality.

    Enables team leads or quality assurance agents to monitor calls without overreaching permissions.

    Supports compliance and auditing policies more effectively.

    Improves operational flexibility without compromising security or visibility boundaries.

    This enhancement would greatly improve our ability to manage teams efficiently while maintaining data integrity and access control within the RingCX platform.

    Description:

    Currently, in RingCX, the only way to enable Call Monitoring/Listening functionality is by changing an Agent's role to Supervisor. However, this creates a significant data visibility issue, as it grants Supervisors access to queues and information beyond their designated team or group, which may include sensitive data from other departments or companies.

    Request:

    We would like to request the implementation of a granular permission setting that allows users with the Agent role to be granted Call Monitoring privileges for a specific group of agents or queues only, without the need to elevate them to a Supervisor role.

    Proposed Solution… more

    27 votes

    Vote 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  ·  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

18. Omit country and area codes when dialing in RingCX

    When dialing via the RingCX application, please omit the country code and area code.
    The customer is asking whether RingCX can automatically omit country and area codes when dialing.

    4 votes

    Vote 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

    New  ·  0 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

19. RingCX SPOG Debugging Tool for Log Collection

    It would be nice to have a built in debugging tool to collect the necessary logs to open support cases for intermittent issues with SPOG. It's difficult to collect HAR and Console logs for issues that happen sporadically. A tool that runs in the background to collect this kind of data for hard to reproduce issues would be very helpful.

    8 votes

    Vote 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

    New  ·  0 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

20. Standalone Agent Notes Field Within Agent Script (Live Call Mode)

    Provide agents with a clean, simplified interface to enter notes during live calls by enabling a standalone Agent Notes field within the Agent Script → Agent Disposition section—without exposing other fields such as Disposition or AI Summary.

    Agents need a quick and distraction-free way to capture notes during live interactions. However, the current Agent Disposition section includes multiple elements (e.g., Disposition dropdown, AI Summary field), which:

    *Adds unnecessary clutter during active calls
    *Slows down note-taking while agents are engaged with customers
    *Increases cognitive load when only note-taking is required

    Key Capabilities

    1. Isolated Notes Input Field: Agent Notes can be displayed independently within the script
    2. Script-Level Configuration: Admins can control which disposition elements are shown per workflow/use case
    3. Real-Time Usability: Optimized for quick note entry during live conversations

    Provide agents with a clean, simplified interface to enter notes during live calls by enabling a standalone Agent Notes field within the Agent Script → Agent Disposition section—without exposing other fields such as Disposition or AI Summary.

    Agents need a quick and distraction-free way to capture notes during live interactions. However, the current Agent Disposition section includes multiple elements (e.g., Disposition dropdown, AI Summary field), which:

    *Adds unnecessary clutter during active calls
    *Slows down note-taking while agents are engaged with customers
    *Increases cognitive load when only note-taking is required

    Key Capabilities

    1. Isolated Notes Input Field: Agent Notes can be displayed… more
    4 votes

    Vote 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

    New  ·  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