1279 results found
-
Option to retrieved a deleted Custom Greeting
When a user uploads new Custom Greeting, the old one will be automatically deleted. It will be helpful if there is an option to retrieve the previous greeting that has been deleted
2 votes -
Enhanced Administrative & Data Export Audit Logging Across All Platforms
Security / Administration
1 vote -
ability to turn off automatic call recording during calls
Option to turn off the automatic call recording during calls
5 votes -
Remove the deskphone from limited extension easily
Remove the deskphone from limited extension easily
2 votes -
Holiday Template
We're managing 680+ hospital sites across two tenants, and each site has its own after-hours IVR with a unique greeting that includes a local emergency hospital recommendation, plus site-specific voicemail routing. Setting holiday rules one extension at a time across that many sites isn't feasible.
What we're really looking for is something closer to how Zoom Phone handles holiday hours. Specifically:
Holiday Groups: The ability to create a named group of holidays (e.g., "2026 Company Holidays") with specific dates and hours defined once, then assign that group to multiple sites or auto-receptionist extensions in bulk. This way we define the…
7 votes -
Customized CNAM for internal calls without changing user details
We would like to have the ability to customized our caller ID name for internal calls without changing our user details.
7 votes -
Emergency Log In Extension
Emergency contact that can bypass the standard login protocol for emergency purposes.
Allow to put a mobile number that can recieve the OTP for emegency purposes.
2 votes -
RCX Status Update While Handling REX Calls
Under the systems current design for the agents' RCX status to only be updated to an Engaged state while handling REX calls IF the agent was in an "Available" RCX agent state prior to handling the REX interaction. We suggest RCX status updating even when the agent is "Away" prior to handling the REX interaction, as many of our agents prefer to set their RCX status to "Away" to prevent inbound calls from coming in while they are making outbound calls in REX. This current design interferes with our monitoring process.
3 votes -
Retain Call & SMS history for deleted users
Allow call and SMS history to remain accessible after a user account is deleted. This would preserve historical communication records for auditing, reporting, and continuity purposes while ensuring that the data is handled in accordance with applicable privacy and data-retention requirements.
The retained history should remain clearly associated with the relevant records without allowing access to the deleted user’s active account or personal profile.
2 votes -
Call Logs Visibility for Custom Role Users
Request to improve the Call Logs behavior for users assigned with custom roles who have access to multiple sites, enabling automatic population of call logs without requiring manual filtering.
Currently, users with custom roles and site-level access to call recordings are required to manually apply filters (e.g., by site, calling number, or dialed number) before call logs are displayed in the Analytics page.
Most reporting users (e.g., managers or team members) do not always have prior knowledge of specific call details such as the calling or called number. This creates challenges in efficiently locating and reviewing call records for the…
4 votes -
Add the option to route calls to voicemail when blocking calls with no caller ID.
Currently, the only available option is to change the default greeting from "Default" to "Mailbox is full."
It would be beneficial to have an option to route these calls to voicemail. This would allow us to customize the greeting so callers can leave a callback number or an alternate contact method, ensuring it doesn't defeat the purpose of hiding their caller ID in the first place.
2 votes -
Native Visibility for Call Disconnect Initiator & Reason in Admin Portal
Problem Statement
Account administrators currently have no self-service method within the Admin Portal or Analytics to determine which party disconnected a call or why. When users report suspected "call drops," admins must open support tickets to have Tier 2 support pull backend session logs (Sonus-Disconnect-Initiator / Sonus-Call-Disconnect-Reason). In many cases, these inquiries turn out to be normal hangups rather than technical failures, resulting in unnecessary ticket volume and delayed answers for admins.Proposed Feature
Expose call termination telemetry directly within the Admin Portal Call Logs and Analytics detailed view:
1. Disconnect Initiator: A field indicating who ended the call (e.g.,…2 votes -
Include All Phones on the Licenses and Inventory Report
We recommend enhancing the Licenses and Inventory Report to include all provisioned hardware, specifically ensuring that BYOD and manually provisioned devices are captured alongside standard inventory. Currently, the report omits devices lacking pre-registered serial or model numbers, creating critical data gaps for customers performing End-of-Life (EoL) tracking and hardware audits. By ensuring the report consistently exports the model, serial number, phone number, and extension details for every device on the account, RingCentral will provide the comprehensive visibility required for enterprise-level asset management and lifecycle planning.
10 votes -
Tailor SMS Notifications
Customer is requesting a way they can edit the notification and not include the "You can get RingCentral app here" and provide a link, as it does not apply to their environment, and they do not want to encourage their staff to download an app that will not work with their RingCentral account.
3 votes -
Ability to change the area code of numbers directly in the number inventory without needing to assign them to a user first. This will stream
Direct area code changes for unassigned inventory numbers without having to assign them to a user first—reducing process steps and saving time.
2 votes -
Caller ID for sending fax restriction
The customer has 3 fax numbers assigned to message-only extensions within a single site. The customer wants to restrict the users from using all the 3 numbers as a Caller ID when sending a fax, and only use/view the one assigned to their department
6 votes -
Disable automatic call recording announcement, while the call is on hold or from park calls.
When a custom blank recording is configured for the call recording announcement, it should consistently apply across all call scenarios.
Currently, even if a blank recording is set (resulting in no audible announcement during regular inbound or outbound calls), the announcement is still played in certain situations—such as when a user picks up a call or retrieves a parked call.
The expected behavior is that once a blank custom recording is applied, no recording announcement should be heard in any call handling scenario, including direct calls, answered calls, or parked call retrieval. This ensures consistent behavior across all call flows…
8 votes -
Bulk Enable Users With Dummy Email Assigned
Significance:
There are user extensions that does not need email addresses and that dummy emails has been assigned in order to be created and be used for deskphones. Some features won't work if these extensions are not enabled. There's currently no way to bulk enable users without the need to assign credentials, the only current available option is to "Send Invite" by bulk.It will be very helpful to have a function of assigning PIN, security question, and password for bulk of users that won't be using the service web or the admin portal or for those that will be…
2 votes -
Disable forward to voicemail keys for incoming calls
A feature in which allows the admin of the account to disable the short cut keys like * or # to forward calls to voicemail
2 votes -
Caller ID Passthrough on Toll-Free Forwarding Chains
When a fax is transmitted from an originating Toll-Free Number (TFN) to a RingCentral Direct Inward Dialing (DID) local number configured to forward to a secondary destination TFN, the final recipient TFN displays the intermediate RingCentral DID on the Caller ID (ANI) rather than the originating TFN.
This behavior is standard for routed/forwarded legs, as the intermediate DID acts as the billing and originating point for the final call leg to the destination TFN.
Desired Outcome: Preserve and display the originating sender's TFN on the recipient’s inbound Caller ID/header, rather than overriding it with the intermediate forwarding DID.
2 votes
- Don't see your idea?