WhatsApp will let users add, manage, and save contacts via usernames, removing the phone number as the mandatory identifier for initiating conversations or calls, the company announced on its official blog in October 2024.

The mechanics are straightforward: a WhatsApp username functions as a portable, user-chosen handle that can be shared in place of a phone number. Two people can begin messaging or call each other with nothing more than that handle — no SIM-linked digits exchanged. The practical upshot is that users can compartmentalise their WhatsApp presence from their phone identity, choosing which contacts, communities, or contexts ever see their number.

For privacy, this is a meaningful structural change. A phone number is sticky in ways a username is not. It connects to carrier records, is frequently used as a 2FA recovery method, and can be reverse-looked-up across data brokers with varying degrees of ease. A username that is independent of that number narrows the surface area considerably. WhatsApp has positioned the feature explicitly as an additional layer of privacy and security.

The comparison that comes to mind is Signal's usernames rollout, which the privacy-focused messenger completed in early 2024 after a multi-year development cycle. Signal's implementation allowed users to hide their phone numbers from contacts entirely — a deliberately more aggressive privacy posture than what WhatsApp is describing here, where the number remains the underlying account anchor. The distinction matters. WhatsApp's username is a contact-discovery and sharing convenience that also provides privacy benefits; it does not, at least as announced, sever the account's dependence on a phone number at the registration layer.

That said, the scale differential between the two platforms is orders of magnitude apart. WhatsApp operates at roughly two billion active users; Signal's user base, while substantial, is a fraction of that. A username option reaching two billion people — even if architecturally shallower than Signal's — has a broader practical effect on how many individuals can conduct private communications without phone-number exposure.

Worth flagging for enterprise and developer audiences: contact management by username has implications beyond end-user convenience. Business API integrations, customer support pipelines, and B2C messaging flows on WhatsApp have historically been anchored to phone number lookup. If usernames become a first-class routing primitive in the platform, that changes how contact records are stored, deduplicated, and matched across CRM systems. WhatsApp has not, as of this writing, detailed how usernames will interact with the Business API or the broader platform ecosystem — that gap will matter to the organisations running production workloads on the platform.

The broader pattern here, across end-to-end encrypted messengers, is a gradual decoupling of communication identity from telecommunications infrastructure. Phone numbers were an inherited constraint, not a deliberate design choice — they became the de facto login credential for messaging apps largely because SMS verification was cheap and universally available in the early smartphone era. The industry has been walking that back, slowly, as the security liabilities of SMS-based auth have become undeniable and as users have grown more attuned to data minimisation.

WhatsApp's username feature is one more step in that direction. Whether it goes far enough depends on what users and regulators ultimately demand of the platform — and on whether Meta extends the capability into the account-layer architecture or keeps it as a contact-sharing convenience. The feature's announced scope is genuinely useful. Its ceiling, for now, is still determined by a phone number sitting underneath it.