Settings and activity
13 results found
-
1 vote
Nicolas
shared this idea
·
-
1 voteNicolas
shared this idea
·
-
1 voteNicolas
shared this idea
·
-
8 votesNicolas
supported this idea
·
-
212 votesNeeds More Information ·
AdminJessica Hernandez
(Community and Social Media Engagement Manager, RingCentral)
responded
Hello everyone, this has been implemented in 22.3.1. This version of the app was rolled out to all accounts over 8/25-8/31. No additional action is required to initiate the feature on the app, please confirm you are on at least 22.3.1.
This feature allows for caller ID to transfer in these scenarios.
Warm/Consultative Transfer:
- Incoming call from PSTN/RC # to RingCentral and transferred to RC number
Blind Transfer:
- Incoming call from PSTN/RC # to RingCentral and transferred to RC number
- Incoming call from PSTN/RC # to RingCentral and transferred to RC voicemail
The feature requires the following endpoints to work successfully. This applies to both the user invoking the transfer as well as the user who is the destination of the transfer.
Desk phones: Any Poly, Avaya or Unify models.
RingCentral App: Version 21.4.30 or later
RingCentral Mobile App: Version 22.1.10 or later
RingCentral Phone App: Version…
Nicolas
supported this idea
·
-
1 voteNicolas
shared this idea
·
-
1 voteNicolas
shared this idea
·
-
1 voteNicolas
shared this idea
·
-
3 votes
An error occurred while saving the comment Nicolas
supported this idea
·
-
1 voteNicolas
shared this idea
·
-
1 voteNicolas
shared this idea
·
-
3 votes
An error occurred while saving the comment Nicolas
commented
More global context:
Description of the Idea:
When a user updates their email address in their profile (User Details), RingCentral should automatically reflect this updated email in the notification settings used for alerts and reports.Suggested Improvement:
- Implement automatic synchronization between the email address set in the user profile and the email used for notifications.
- Maintain the ability to manually override the notification email address when needed, in cases of specific user requests or operational exceptions.Why it Matters:
- Today, updating a user’s email in their profile does not propagate to notification settings, leading to missed alerts or inconsistencies.
- This causes confusion, extra administrative overhead, and increased risk of communication failure.
- Having email synchronization with a manual override provides a best-of-both-worlds approach: automation for simplicity and flexibility when needed.Expected Benefits:
- Reduced administrative effort when updating user contact information
- Improved reliability and consistency of email notifications
- Better user experience and fewer support tickets regarding missed alertsConclusion:
Automatically aligning the notification email address with the user’s profile email — while preserving the option to manually override it — would improve usability, reliability, and efficiency across the platform.Let me know if you’d like an example scenario or further clarification.
Nicolas
supported this idea
·
-
2 votesNicolas
shared this idea
·
More context :
Description of the Idea:
When an incoming call targets a Site Number, RingCentral currently displays the main company or main user name as the caller destination. This behavior is misleading and causes confusion for users, especially in multi-site organizations.
Problem Statement:
- The display does not reflect the actual target site, even though the call was placed to a specific site number (X Number).
- Users are shown the main tenant name rather than the name of the site being contacted.
- This prevents staff from identifying which site the caller is trying to reach, impacting call handling, routing, and response efficiency.
Suggested Improvement:
Update the incoming call display logic to:
- Show the name of the site when a site number (X Number) is used for inbound or outbound calls.
- Ensure the site name replaces the generic main user or tenant name in all relevant RingCentral apps, devices, and logs.
Use Case Example:
- A customer calls the Paris office’s site number.
- The receptionist sees the incoming call labeled as “Main Tenant – HQ,” which is incorrect.
- Expected behavior: Display “Paris Office” to correctly reflect the called destination.
Implementation Suggestion:
- Automatically map X Numbers to their associated site name.
- Modify the call presentation layer to prioritize site name over main user name when the call is made to or from a site number.
Benefits:
- Improves clarity for end users
- Reduces misrouting and confusion during call handling
- Enhances multi-site support and professionalism
- Aligns system behavior with user expectations and real-world operations
Priority:
Medium, but important for multi-site deployments — ideally implemented ASAP to prevent operational errors.
Conclusion:
Displaying the correct site name for calls using site numbers will improve usability, accuracy, and the overall call experience, especially in organizations operating across multiple locations.
Let me know if you'd like this backed by example call logs, screenshots, or user impact metrics.