1450 results found
-
Allow extension dialing within RingCX SPOG
Currently within RingCX SPOG, once you start your session and go to the dial pad and enter an extension in the dial pad with "RingCX Default" set as your caller ID, and then press enter and select the option "Dial" or press "Enter" on your keyboard, it will prompt an error "The number is invalid, please check it carefully and try again"
When you have a session started but select a RingEX caller ID, you can type the extension and then hit "Enter" or "Dial" and it will connect.
What we want is the ability to dial a RingEX extension…
3 votes -
RingCX Inbound Queue Reconciliation & Unclassified Exit Visibility
We request a native, system-calculated metric in RingCX Analytics that automatically reconciles the total Queue Inbound Interactions (Presented) against all final outcomes (Answered, Abandoned, Callback, and Deflected). Currently, a significant volume of interactions falls into a catch-all "Other" bucket due to system-level disconnects or unclassified IVR exits, requiring complex manual reconciliation. This enhancement should provide a clear, granular breakdown of Unclassified Queue Exits and a pre-calculated "Total Outcomes" column to ensure every presented call is accounted for with 1:1 accuracy without manual spreadsheet work.
3 votes -
Add inbound caller ID normalization to E.164 format (+61XXXXXXXXX) for Australian numbers so that inbound call logs and desk phones (e.g., Y
Add inbound caller ID normalization to E.164 format (+61XXXXXXXXX) for Australian numbers so that inbound call logs and desk phones (e.g., Yealink T54) correctly resolve names from the RingCentral Company Directory.
3 votes -
Disable phone number recognition
Disable phone number recognition.
Currently, the RingCX Email interface automatically injects a Telephone Icon and click-to-dial hyperlink onto all numerical strings in email replies. This behavior is overly aggressive and frequently misidentifies non-phone data (such as Reference IDs, SKU numbers, and currency) as dialable numbers.3 votes -
Transcriptions for voicemail email notifications in RingCX
Current Behavior:
When a call routed to a workflow or voice queue is sent to voicemail, the email notification received contains only the voicemail recording as an attachment. There is no voicemail transcription included in the email body.Requested Enhancement:
Enable voicemail transcriptions to be included directly in the email notifications sent when a voicemail is left for a workflow or voice queue.This functionality already exists in the RingEX platform, and we would like to have the same capability available in RingCX for consistency and usability.
Important Clarification:
This request is not related to the Queue Voicemail Channel feature.…
3 votes -
Enhanced Playback Controls & Dual-Channel Visualization for RingCX Recordings.
Please consider an update to the RingCX Call Recording interface to include advanced playback navigation (Fast Forward/Rewind) and a visual "Dual-Channel" waveform. Currently, the playback experience requires manual scrubbing and active listening to distinguish between speakers, which slows down the auditing and coaching process.
Key Feature Requests
Granular Playback Controls: Add dedicated "Skip Forward" and "Skip Backward" buttons (e.g., in 5 or 10-second increments). This allows users to quickly bypass hold music or repetitive disclosures without losing their place.Split-Track Visualization (Agent vs. Customer): Implement a visual waveform or timeline that clearly distinguishes the Agent's audio from the Customer's audio.
…
3 votes -
Feature Request – Distinct “Invalid Number” Result for Manual Outbound Calls
Description:
Currently, in RingCX historical reports, manual outbound calls to invalid numbers are recorded as “No Answer” in the Call Results column. This makes it impossible to differentiate between genuine no-answer calls and invalid-number attempts in reporting.
Business Impact:
Agents and managers cannot accurately track list quality or outbound performance.
Invalid numbers are not flagged for clean-up, reducing operational efficiency.
Reporting and analytics on manual outbound campaigns are incomplete.
Requested Feature:
Introduce a distinct call result/disposition such as “Invalid Number” for manual outbound calls.
Ensure this result is visible in historical reports, dashboards, and exported data.
(Optional) Include this disposition…
3 votes -
Feature Request: Conditional Caller ID Enforcement for Warm Transfers and Consultations Across RingCX and RingEX
*Summary
Introduce a platform-level capability to enforce conditional Caller ID behavior for internal calls during warm transfers and consultations, ensuring consistent Caller ID presentation across RingCX and RingEX environments.
*Problem Statement
During warm transfers or consult calls—whether between RingCX agents or from RingCX to RingEX users—Caller ID presentation may vary and display RingEX Born Super Admin name, queue numbers, site numbers, or system-generated identifiers. This inconsistency creates confusion during internal collaboration. However, once a call is fully transferred or taken over, the receiving party must see the original customer identity to preserve service continuity.
*Proposed Capability
Implement call-state–aware Caller ID…
3 votes -
Identify percentage of RingCX calls that are recorded
Need a way to query data to identify what % of calls are recorded.
3 votes -
Option to apply Campaign Criteria Custom Fields when setting Lead Search filters.
It would be helpful if admins had an option to include the Custom Field from Campaign Criteria Plan when filtering the reports in Lead Search Criteria.
3 votes -
Feature Request: Embedded Integration for RingCX + Zoho
I’d like to submit a feature request regarding the current RingCX integration with Zoho.
At present, the only available method for connecting RingCX to Zoho is through the Chrome extension. Several customers have expressed the need for a more seamless workflow by having this functionality embedded natively within RingCX instead of relying on the extension.
Requested Enhancement:
Add support for a native or embedded RingCX–Zoho integration, removing the dependency on the browser extension.
Goal: Improve agent workflow efficiency, reduce extension-related issues, and provide a more streamlined user experience.
This enhancement would greatly improve usability and stability for customers leveraging Zoho…
3 votes -
IVA Custom Role Toggle
Arrowhead would like the ability to lock down the AI Tools section of the platform. Currently, there is no toggle within the Custom Role creation tool to limit Admins ability to change/ or view only AI Knowledge Base, IVA Integrations or the AI Engine. Any Admin can modify this section of the platform. Their desire is only a select few admins have the ability to change that area of their platform and filter all changes through their IT department.
Proposed Solution: Create Toggle within Custom Roles to "View only" or completely hide that section of the RingCX Admin.
3 votes -
Salesforce for RingCX - allow login sessions to be kept active even when browser refresh so agents do not log out.
Allow login sessions to be kept active even when browser refresh so agents do not log out.
3 votesRelease 25.4.2 (December)
RingCX for Salesforce - Persistent Login Across Browser Refreshes:
Agents using the integrated softphone will now remain logged into the adapter even after refreshing a browser page. This eliminates a major point of friction, prevents workflow interruptions, and provides a more stable and reliable user experience, especially for agents working in complex Salesforce environments.
-
Enhanced Agent Dashboards for Queue Visibility and Custom Statuses
Currently, RingCX agents have limited visibility into calls across queues, agent availability, and overall queue activity. While supervisors can see more detailed information, agents themselves cannot access this data without compromising security. Existing workarounds, such as using JWT tokens, are not viable as they grant access to admin settings and analytics, creating a significant security risk.
Agents would benefit from a dedicated dashboard that provides real-time visibility into calls, queue status, and agent availability without exposing KPIs or sensitive information from other agents. This would also support coordination among agents for breaks, shift changes, and coverage planning.
We request the…
3 votes -
option and/or default behaviour being to auto-hold the external caller / customer when an agent initiates a warm transfer / three-way call t
An option and/or default behaviour being to auto-hold the external caller / customer when an agent initiates a warm transfer / three-way call to a user on the REX system?
3 votes -
Allow Callback Requests to Include Country Code
Requesting a feature that enables or requires clients to input their full phone number including the country code when requesting a callback.
Business Need:
Many global businesses use call forwarding (e.g., +1) to route calls to different tenants or regions. Currently, the callback form or IVR flow only accepts local numbers, meaning international clients cannot accurately request a callback. This leads to missed opportunities and forces teams to implement workaround solutions that don’t fully meet operational or compliance requirements.Benefits:
Ensures international clients can successfully request callbacks.
Improves accuracy and efficiency of callback routing.
Reduces manual handling or missed return…
3 votes -
RingCX Domo Integration (For Analytics)
Would like a direct integration built between RingCX and Domo Analytics, instead of having to SFTP
3 votes -
Email Digital Topology Routing Control
Overview:
Our current email digital topology system attempts to route incoming email threads to the agent who previously engaged with the customer. While this behavior supports continuity and customer experience, the underlying logic lacks transparency and configurability.Current Limitations:
-The system’s decision-making process for agent assignment is unclear.
-There is no administrative control over how long the system attempts to route to the original agent before reassigning.
This can lead to inefficiencies, especially when the original agent is unavailable, resulting in delayed responses or inconsistent customer experiences.Proposed Enhancement: Introduce a configurable routing control feature that allows administrators to:
-Set…3 votes -
UC and RCX call recording report
Currently, when calls are made in RingEX using a RingCX-provisioned number as the caller ID, the call appears in the Interaction Details report in RingCX. However, since the call is initiated from the UC side, the corresponding recording isn’t visible within RingCX.
The customer is requesting the ability to include these UC-originated calls — along with their recordings — in RingCX reporting for better visibility and tracking.
3 votes -
Outbound Dialing Should Use Updated Phone Number After Agent Lead Update
Description:
Currently, when an agent updates the phone number in a lead record (Agent Lead Update), the system continues to dial the old phone number during the outbound call process. Although the lead information reflects the new number in both the Lead Search and Lead View pages, the dialing logic still references the outdated number.Expected Behavior:
When a lead’s phone number is updated by an agent, the system should immediately reference and use the updated number for any subsequent outbound dialing attempts, without requiring the lead to be re-passed or refreshed.Actual Behavior:
Updated lead details display correctly in…
3 votes
- Don't see your idea?