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.