WhatsApp is replacing phone numbers. And you need to adapt your integration now. Users can now adopt a username. And when they do, their phone number eventually stops arriving in your webhooks. The replacement is the Business-scoped User ID (BSUID). If your WhatsApp integration depends on phone numbers, you... may be losing messages already. We created: 1️⃣ A live chart of the % of messages arriving without a phone number 2️⃣ A complete guide on this changeshow more

Full guide: Percentage of messages arriving without a phone number:

Mi duda es: Si envias un template con el numero y el webhook whatsapp te devuelve si respondio el mensaje con el numero o solo el BSUID? Si es solo el BSUID como vinculas el numero con el BSUID? El output de cuando envias un template tampoco te da el BSUID, solo el wa_id.

después de enviar un template al número, el status webhook trae wa_id y BSUID

Sii, pero va a ser siempre asi o van a eliminar el wa_id en algun momento?

con la info que tenemos hasta hoy: wa_id se va a mantener

Gracias

found kapso thru x ad. and fully switched from a previous provider for indian numbers. fantastic so far

🙌

Losing messages if you rely on phone numbers, good heads up for devs

I noticed the msisdn field disappearing from incoming webhooks and the BSUID appearing instead. I built a simple mapping store and backfilled historic contacts. A dual key migration path saves the headache later

the nasty part is identity stitching during rollout: the same user may show up with msisdn in older events and BSUID in newer ones. if your CRM keys on phone, you need a dual-write migration path plus backfill before usernames go mainstream.

Lets chat