13290 results found
-
Native Support and Provisioning for International Peer-to-Peer (P2P) Conversational SMS
Description:
We request that RingCentral expand its global SMS capabilities to fully support regulatory-compliant, two-way Peer-to-Peer (P2P) messaging outside of North America.Currently, business users outside the US and Canada who attempt to engage in normal, 1-on-1 conversational text messaging with international clients experience delivery failures, silently dropped texts, or strict carrier blocking. In many international markets, carriers treat all business platform traffic as commercial spam unless dedicated P2P conversational routing and local geographic virtual number (DID) provisioning are explicitly supported.
Key Requirements:
International P2P Number Provisioning: Enable local geographic virtual numbers (DIDs) in non-US/Canada regions with two-way conversational SMS…
3 votes -
Hotdesk Phone Centralized Credentials
Implement a centralized credential for hotdesk phones so users can log in using a single credential, rather than entering individual extension numbers and PINs for each device.
3 votes -
Have an option to automatically flatten documents when sending faxes
This would be a great help if RingCentral can automatically flatten the faxes before sending the documents out? As we have 4-5 faxes fail everyday, checking them, and having to manually download the documents off our EMR (the third party app integrated with RingCentral), flattening them, and then resending them, is a big time investment, especially for a clinic with a small admin staff that's already overworked up until clock-out time.
3 votes -
Option to Restrict the SMS Server for Metada, logs, and message content to be stored in US based servers only
Ensuring SMS metadata, logs, and message contents are stored physically on US-based servers only to comply with financial, healthcare, or government compliance
3 votes -
Call Queue Templates: Multiple SMS Recipients
Under Call Queue Settings in Templates — a new feature that lets you configure SMS recipients for selected call queue groups directly from the template.
- This makes it easy to assign the same SMS recipients to multiple call queues at once, instead of adding them one by one on each call queue group extension.3 votes -
Voicemail-to-Email Subject Parity for Call Queues
Requesting an update to platform routing architecture to ensure the Call Queue Name is consistently passed as a variable into the Voicemail-to-Email subject line, regardless of whether the call is processed during Business Hours or After-Hours.
The system should retain the Call Queue Name variable during the after-hours routing diversion to voicemail. The subject line should maintain exact parity in and out of hours:
New Voice Message from [QUEUE NAME] - [CALLER ID] on [DATE/TIME]3 votes -
Option to assign the internal extension number ( Video Pro Only) as the caller ID in the custom rule condition
When setting up the conditions for the custom rule I see there is an option called "Caller ID". The only option that you have there is putting a phone number, a contact name or contacts from address book.
Looking for a way to get the Internal Extension number of a user that has no license ( Video Pro Only) to use as a caller ID condition for creating custom rule.
3 votes -
Be able to Shorten the Retention from 90 days to 30 days
I would like to be able to change the retention to a shorter amount. We would like to set it from the default 90 days to 30 days.
3 votes -
Algo Speaker 8160 for Both Ringing Monitor and Paging
They want to use their Algo Speaker 8160 on two separate extensions simultaneously — one for monitoring and one for paging.
The device itself supports this, but RingCentral's platform only allows a device to be assigned to one extension at a time.
3 votes -
Allow owners to share live CX dashboards with any user, role, or department across the entire organization, regardless of hierarchy.
Current Behavior:
Dashboard sharing is restricted strictly to users within the dashboard owner's immediate hierarchical group. Cross-functional leads, agents outside the direct reporting chain, or upper-level stakeholders cannot access these live views unless they are added to that specific group hierarchy.Expected Behavior: Allow owners to share live CX dashboards with any user, role, or department across the entire organization, regardless of hierarchy.
3 votes -
Sync the Caller ID on both the mobile and desktop applications during an ongoing call.
The desktop application should display the caller ID and caller number even when the call is answered through the mobile application.
When the call is answered through the mobile application, the caller ID and caller number are displayed on the mobile app. However, when the user checks the call logs on the desktop application during the ongoing call, only the caller’s number is displayed. The caller ID only appears on the desktop application after the call has ended.
3 votes -
Call Forwarding from IVR Menu going to Call Queue and Transferred to User Extension.
The customer would like to configure a rule where calls to the main number route to the IVR Menu > Call Queue Members. If a queue member transfers the call to an unavailable extension, the call should route to the Key Press option initially selected in the IVR Menu.
3 votes -
Allow Custom IVR Prompt Repetition Settings
It would be very helpful if RingCentral allowed administrators to choose how many times an IVR greeting/prompt should be repeated when a caller does not select an option.
Currently, the system automatically repeats the prompt 3 times, which can make the call flow unnecessarily long.
For example, we would like to have the following option:
Play the greeting/prompt only once
If the caller does not select any option, automatically route the call to a designated extension (for example, Main Office – Extension 4)
Alternatively, allow administrators to choose 1, 2, or 3 repetitions depending on their business needs
This would…3 votes -
Allow Pre-Chat Forms Without the Mandatory "Message to agent" Field
Currently, customers are trying to build frictionless webchat experiences where an end-user simply clicks a predefined radio button (e.g., "New Enquiry" vs. "Existing Enquiry") and hits submit to enter the queue. They do not want the end-user to type out a message to initiate the chat.
Allow admins to successfully save and deploy a pre-chat form that consists solely of a Category, Custom field, or Messaging variable, without the strict requirement of the Message to agent field. The selected radio button/dropdown value should be sufficient to generate the initial interaction payload and place the user in the queue.
3 votes -
Allow SMS autoreply for Miss call from IVR menu or Call queue
Allowing to setup SMS automation/SMS auto reply for miss call from the IVR menu and Call queue
3 votes -
Block a specific carrier
Ability to block a specific carrier such as Google Voice. Been getting a lot of SPAM calls from them and blocking numbers manually can be a hassle.
3 votes -
Assign a user to be notified of a call back request to the AI receptionist
The AI should either have an ability to store the call back request to a folder where a user is assign and has access to or, an assigned user will be notified of the details if the caller requested for a call back
3 votes -
Option to download AI transcriptions
Option to download AI transcriptions of other users via call reports in RingEX
3 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 -
Allow Customizable Callback Request Prompts and In-Queue Callback Audio for Call Queues
Summary
Currently, the Call Queue callback feature relies on standard system prompts. We request the ability to customize the Callback Request greeting or embed custom callback triggers directly into standard Call Queue greetings and Music on Hold (MOH).Use Case & Business Need
Multiple customers want to provide a seamless, branded experience while waiting in a Call Queue. They want to inform callers of expected hold times and offer an automated callback option within their custom queue announcements or hold music rather than relying on standard, uneditable system prompts.Example Scenario:
"Thank you for calling [Company Name]. Please hold while…
3 votes
- Don't see your idea?