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

   153 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

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

   •  

   •  

   •  

   •  

   24 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

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

   124 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

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

   54 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

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

   321 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

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

   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

   Under Review  ·  4 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. 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

   37 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

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

   25 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

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

   62 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

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

    6 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

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

    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

12. Requeue Shorcuts Searchable

    When an agent goes to requeue a call they get a list of queues available. While there is a search field at the top to type in the name of the queue you are looking for it does not actually perform a search. The agent must scroll down through the list of queues find the one they are looking for. In order to improve agent efficiencies making this truly searchable would be greatly beneficial.

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

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

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

14. Dashboard for agents and supervisors in RingCX

    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.

    79 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  ·  11 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. Audible notification for incoming call & DTMF support

    Our agents must use "RingCentral Phone" as their device type in RingCX because RingCX does not provide an audible indicator for incoming calls, when using Integrated Phone. When they do this, they are not able to enter DTMF tones while in the RingCX UI when conferencing in a third party translator service. The DTMF tones must be entered via the RingCentral softphone app. This is incredibly confusing for our agents, as they perform all other call functions such as hold, transfer, etc in the RingCX web interface. It will be great if we can disbale the diapad in RingCX in this instance to lessen the confusion

    Our agents must use "RingCentral Phone" as their device type in RingCX because RingCX does not provide an audible indicator for incoming calls, when using Integrated Phone. When they do this, they are not able to enter DTMF tones while in the RingCX UI when conferencing in a third party translator service. The DTMF tones must be entered via the RingCentral softphone app. This is incredibly confusing for our agents, as they perform all other call functions such as hold, transfer, etc in the RingCX web interface. It will be great if we can disbale the diapad in RingCX in… more

    9 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

16. Ability to remove suggested email addresses in RingCX

    We’d like an option for agents and supervisors to manually remove or delete suggested email addresses in the RingCX application.
    During testing, an email was sent to one of our team member’s personal address. Now, when users type the last name in the To field, both the personal and work addresses appear, and the personal address often gets selected because it appears first. We can’t find a way to delete or suppress that suggestion.

    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

    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

17. Track and report on agents' geo-location

    For Better Agent management, it will be helpful if we can have geolocation in RingCx as well like what we have in Analytics of RingEX

    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

    Under Review  ·  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

18. Call Waiting notification

    If a user is in an outbound call with a customer and another call comes into their queue, an incoming call notification pop-up should appear, notifying them of the incoming call.

    The agent should have the ability to put the first call on hold and then answer the second call.

    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

    Needs More Information  ·  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 Voice Agent - Enhanced Call History: Visual Differentiation and Filtering Options

    The customer would like the historical call view in Agent RingCX to display call results differently—for example, using different text colors for successful calls versus missed calls (RNA). They would also like the ability to filter call history by All Calls, Missed Calls, Incoming Calls, and Outgoing Calls, similar to what is available in RingEX.

    •  

    •  

    •  

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

20. Preserve Agents’ extension as Caller ID for Internal Calls

    When agents make internal calls on the SPOG, their caller ID shows the RingCX caller ID Setup. It would be helpful if the system preserved the agent’s actual Extension as caller ID so colleagues can easily recognize who is calling.

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