What would you like?
Add an internal-only VIP designation in the name admin UI for reserved names associated with celebrities, public figures, notable brands/orgs, high-profile creators, and other high-risk impersonation targets. The VIP designation should appear as a visible label on the reserved-name card/details popup, support search/filtering so admins can pull a list of all VIP names, show a separate VIP count in the system, and ideally display a warning before edit/revoke actions on VIP records. If feasible, access to edit/revoke VIPs should be more restricted than ordinary reserved names.
How would this be useful for you?
This helps admins distinguish the actual protected/reserved VIP name from lookalike names, reduces the risk of accidentally editing or revoking sensitive reserved names, and makes internal review/management of high-sensitivity reservations faster. It is mainly an internal ops safeguard rather than a public verification feature.
When would you use this?
When reviewing or managing reserved names in the admin UI—especially for celebrity/public-figure/high-profile creator accounts, notable brands/orgs, or any reserved names with elevated impersonation risk. Also when an admin needs to audit VIP reservations as a group or understand how many VIP reservations currently exist.
Anything else?
- Scope: internal admins only.
- Existing
reserved reason field likely already covers the reason; no need to turn this into a CRM.
- Useful metadata: who marked the name as VIP.
- Nice-to-have: warning before revoke/edit on VIP names.
- Nice-to-have: stronger permissions so not everyone can edit/revoke VIPs.
- Screenshot/mock reference exists from Alice Chan showing a red "VIP" example on the name details popup.
- Non-goal / open question: this may correlate with external verification in the future, but this request is primarily for internal admin tooling.
What would you like?
Add an internal-only VIP designation in the name admin UI for reserved names associated with celebrities, public figures, notable brands/orgs, high-profile creators, and other high-risk impersonation targets. The VIP designation should appear as a visible label on the reserved-name card/details popup, support search/filtering so admins can pull a list of all VIP names, show a separate VIP count in the system, and ideally display a warning before edit/revoke actions on VIP records. If feasible, access to edit/revoke VIPs should be more restricted than ordinary reserved names.
How would this be useful for you?
This helps admins distinguish the actual protected/reserved VIP name from lookalike names, reduces the risk of accidentally editing or revoking sensitive reserved names, and makes internal review/management of high-sensitivity reservations faster. It is mainly an internal ops safeguard rather than a public verification feature.
When would you use this?
When reviewing or managing reserved names in the admin UI—especially for celebrity/public-figure/high-profile creator accounts, notable brands/orgs, or any reserved names with elevated impersonation risk. Also when an admin needs to audit VIP reservations as a group or understand how many VIP reservations currently exist.
Anything else?
reserved reasonfield likely already covers the reason; no need to turn this into a CRM.