WhatsApp has launched a long-awaited revolutionary update aimed at eliminating the classical constraints of needing to reveal phone identities to communicate with others.
Table of contents
- Introduction to the new feature and public name reservations
- Operational activation mechanism and identifier creation conditions
- Additional username key feature and protection layers
- Brand, organization, and public figure protection rights
- Frequently asked questions about WhatsApp usernames
Introduction to the new feature and public name reservations
The popular global instant messaging platform WhatsApp, owned by Meta Platforms, has announced the opening of pre-reservations for unique usernames for all of its subscribers, totaling over 3 billion users worldwide. This security and privacy feature is one of the most anticipated and requested features in the application’s history, as it allows subscribers and businesses for the first time to connect, message, and conduct shared chats without ever needing to reveal or share personal and private phone numbers with new contacts.
Operational activation mechanism and identifier creation conditions
The company explained via an official post and tech blog that the new additional feature will begin rolling out progressively to all users worldwide across sequential phases during the current week, giving them the opportunity and head start to reserve and secure their preferred identifiers and names before the full rollout planned for later this year 2026. To activate the feature and reserve a name, the user must go to the settings menu, then account, and then the username option available in the latest digital versions of the app, provided that the identifier length is between a minimum of 3 characters and a maximum of 35 characters while strictly adhering to the rules.
Additional username key feature and protection layers
Although creating a new account on the WhatsApp platform will still rely on and comply with the requirement of having an active and valid phone number, setting a custom username will prevent this number from appearing to contacts and businesses messaging for the first time. The app will not include any public directories or open indexes for searching usernames, nor will it offer automatic name suggestions while typing; instead, the other party must know and possess the exact correct identifier to start the conversation. Additionally, a username key feature is introduced as an extra secondary authentication code that must be entered to send messages.
Brand, organization, and public figure protection rights
Regarding business sectors, companies, organizations, and content creators who already have official and verified accounts across other Meta platforms such as Instagram and Facebook, the platform will grant them priority and a head start to reserve and confirm the same identifiers on the WhatsApp application to prevent overlap. To combat and avoid impersonation and digital forgery attacks, Meta stated that it has proactively and beforehand blocked and reserved wide lists of identifiers for government entities, institutions, celebrities, public figures, and major global companies, while providing users with options to change or deactivate identifiers at any time.
Frequently asked questions
Question: Does setting a username in WhatsApp eliminate the need for a phone number to establish an account?
Answer: No, having a real and active phone number remains a fundamental and mandatory requirement for creating and activating the account, but the identifier hides the number from strangers.
Question: What are the specific limits and conditions for creating and formatting a username in the new update?
Answer: The chosen identifier and name must consist of at least 3 letters or characters, and its total length must not exceed a maximum of 35 characters.
Question: Does WhatsApp currently allow public search options or scanning codes to connect with identifiers?
Answer: Public search directories are not available to protect privacy, and quick QR codes cannot currently be used to connect with the identifier; it must be shared textually instead.
