Description of the Idea:
When assigning a phone number during user creation, RingCentral currently shows only the phone number itself, with no label or name indicating its current usage or purpose. This can lead to accidental assignment of numbers that are already in use for redirects, call queues, auto-receptionists, or external routing, potentially disrupting existing call flows.

Problem Statement:
- Admins cannot easily distinguish between numbers that are reserved, actively used, or intended for specific services.
- As a result, it's possible to mistakenly assign a number used for redirection to a new user.
- This introduces unexpected behavior and can break existing call routing configurations without warning.

Suggested Improvement:
- When selecting a phone number during user creation (in the Admin Portal or via API), display the associated name/label next to the number.
- If the number is assigned to a queue, receptionist, or external rule, display that context as well (e.g., "Support Queue Redirect", "Sales IVR Entry", "Marketing Campaign").

Use Case Example:
- An admin sees number +1 (555) 123-4567 in the available list.
- It’s currently used to redirect calls to a Call Queue for the support team.
- With no label shown, the admin mistakenly assigns it to a new user.
- Support calls are now misrouted, causing confusion and service disruption.

Expected Behavior:

• Display: +1 (555) 123-4567 – [Support Queue Redirect]
• Or: +1 (555) 123-4567 – [Marketing IVR Inbound]
• Include this in both the Admin UI dropdowns and API metadata responses.
• Include this in both the Admin UI dropdowns and API metadata responses.

Benefits:

• Prevents accidental number reassignment
• Protects existing routing configurations
• Saves time troubleshooting post-deployment issues
• Improves administrative visibility and clarity
• Supports error-free user provisioning

Priority:
- Medium, with high operational impact — ideally implemented ASAP to improve provisioning accuracy.

Conclusion:
Displaying the label or assigned purpose of phone numbers during user creation will prevent configuration mistakes, enhance visibility, and reduce risks of disrupting critical call flows.

Let me know if you'd like to provide real-world impact scenarios or admin interface mockups to support this feature request.