Description of the Idea:
Currently, when creating or managing BYOC phone numbers via the API (endpoint:
/restapi/v2/accounts/~/byoc-carriers/{byoccarrierid}), there is no way to assign a display name or label to a number.

This omission leads to confusion and manual overhead, especially when Caller ID numbers are selected by end-users — since names are visible in the UI, but not assignable via API.

Problem Statement:

• Numbers created or provisioned via API have no associated label.
• In the RingCentral admin portal or apps, these numbers appear unnamed, making it difficult for admins and users to identify their purpose.
• This increases the risk of selecting incorrect numbers for outbound calls and makes large-scale number management more error-prone.

Suggested Improvement:

• Extend the /byoc-carriers/{byoccarrierid} API to support a "name" or "label" field when creating or updating phone numbers.
• This would allow developers and provisioning systems to assign meaningful, human-readable names to numbers (e.g., “Support Line – East”, “Sales DIDs Europe”, etc.).

Use Case Example:

• An integration provisions 50 numbers via the BYOC API.
  • Without labels, admins and users see only raw numbers (e.g., +1 415 123 4567).
  • With a name attribute, numbers appear as: +1 415 123 4567 – [Marketing Team], making them easy to identify and assign in caller ID selections or routing.

Expected Enhancement:

POST /restapi/v2/accounts/~/byoc-carriers/{byoccarrierid}/phone-numbers

{
"phoneNumber": "+14151234567",
"name": "Support Queue West",
...
}

Benefits:

• Enhances clarity and usability in the admin portal and apps
• Improves accuracy when selecting Caller ID or assigning numbers
• Supports automation and better number lifecycle tracking
• Reduces risk of misidentification in environments with large number pools

Priority:
Medium, but impactful for large-scale or automated BYOC deployments — should be addressed ASAP to avoid operational confusion.

Conclusion:
Adding a "name" attribute to phone numbers created via the BYOC Carrier API will bring consistency between API and UI, improve number management, and enhance the overall user and admin experience.

Let me know if you need an OpenAPI spec draft or example payload to support the request.