Sagicc Updates: Full support for WhatsApp BSUID 💬🆕 🚀

Hi there! 👋🏻 At Sagicc, we evolve at the same pace as the platforms your team uses every day, adapting to changes so your operation never comes to a halt.
WhatsApp is transforming the way it identifies people. Since July of this year, Meta has been migrating to a new scheme called BSUID (Business-Scoped User ID), driven by its new usernames feature. Usernames allow people to message you without needing to share their phone number. So, when a new customer or contact writes to you, their number no longer travels within the message and, instead, Meta delivers a BSUID: a unique identifier, generated specifically for your business, that replaces the phone number to recognize whoever is reaching out to you.
💡 Important: The Username and the BSUID are not the same thing. The Username is the public name the user chooses and sees on their profile (like an @username on social media); the BSUID is a technical, internal identifier generated by Meta. The username can't be used to send messages, it only allows the customer to write to you. To reply, Sagicc automatically uses their BSUID or their phone number, if they've already shared it.
To keep your operation running with complete normalcy, we've built native and full BSUID support into the WhatsApp channel, made up of two major improvements:
New "WhatsApp BSUID" contact data type 🆔
We've added the new "WhatsApp BSUID" contact data type, with which Sagicc detects, associates, and stores the identifier Meta assigns to each user. The platform always prioritizes the phone number when available and stores the BSUID as complementary data, so a single customer can have their phone number and their BSUID coexisting without conflict. This means:
- When an existing customer writes to you, Sagicc will associate their BSUID with the customer's profile, keeping their number as the primary identifier.
- When it's a new contact arriving with a Username only, their profile will be created using the BSUID as the primary identifier, so they won't have a phone number associated until the customer chooses to share it.
This will allow your team to maintain a unified and reliable customer database, ensuring that every conversation is linked to the right person even when their number doesn't travel within the message.
New "Request Contact Information" button 📲
Getting your customers' real phone numbers will be simple and straightforward. We've added a new button type called "Request Contact Information", which you'll be able to include both in your approved template messages and in your interactive session messages. With a single tap, the customer will be able to share their phone number voluntarily and securely, and Sagicc will automatically link it to their record. This will allow your team to enrich the profiles of customers who arrived with a BSUID only, enable future outreach that requires a verified number, and open new contact channels whenever you need them most.
With BSUID support, Sagicc keeps you one step ahead of Meta's changes, protecting the continuity of your conversations and the integrity of your customers' information on WhatsApp. And the best part is that everything works automatically: you don't need to modify your current flows or operation to take advantage of it. Very soon we'll bring more news about our integration with Meta. See you next time! 🚀









