Yes. BSUID will be stored alongside the phone number in the Sprinklr user profile, and the platform will support publishing via both BSUID and phone number. Sprinklr mirrors Meta's approach — both identifiers will remain active simultaneously rather than transitioning to BSUID as the sole primary identifier.

• BSUID stored as a new field in social profiles alongside wa_id / phone number

• Outbound publishing will support both to (phone number) and recipient (BSUID) parameters

• User_ID and username fields will be consumed from webhooks and stored at profile level

• If both to and recipient are supplied in a publish request, Meta's rule applies: to (phone number) takes precedence

Sprinklr will add support for consuming all new webhook fields introduced by Meta, storing them at the profile level. As Meta will continue sending both BSUID and phone number in webhooks, profiles will store both. Existing profiles will be updated with BSUIDs as they arrive through incoming webhooks.

New webhook fields being ingested and stored:

• from_user_id

• recipient_user_id

• username

Backward compatibility is maintained — existing profiles and conversation history linked to phone numbers will continue to function normally. Publishing via phone number remains fully supported.

Username rollout is expected in late 2026. Conversation continuity depends on prior interaction history:

• If a user interacted with the business before phone number masking: the existing profile will be updated with the BSUID and conversation history will be mapped to the same profile.

• If a user adopts a username with no prior interaction: a new conversation will be opened. It is architecturally not possible for Meta to retroactively link this to a prior profile.

BSUID will be added as a new dedicated field in Sprinklr social profiles, enabling CRM mapping on this identifier.

Key considerations:

• Profile imports into Sprinklr will support BSUIDs as a field

• If using Parent BSUIDs – you can update profiles using the parent BSUIDs obtained externally

• Audit your current CRM mapping logic to understand reliance on phone number as a sole identifier.

• Ensure your integration is prepared to receive and store new webhook fields (from_user_id, username, parent_user_id) without breaking existing pipelines.

• Plan profile schema updates to accommodate BSUID as a supplementary identifier.

Yes. Sprinklr will support the Request Contact Info button in supported templates, with publishing available across all Sprinklr publishing channels:

• Bot flows

• Journey Facilitator (JF)

• Guided Workflows

• Rules Engine

This is targeted for 26.10. When a user shares their phone number through this mechanism, Sprinklr will support ingesting that contact info and updating the user profile accordingly.

We will integrate support for parent BSUID based on client requests. Sprinklr will support Parent BSUID in the same way phone numbers are currently used for cross-WABA identity resolution. External profiles can be imported and leveraged for unified identity purposes. Parent_user_id will be available upon eligibility – if the business has WABAs shared across multiple BSPs which they would like to streamline, we will apply for the eligibility check with out Meta Partnership team.

BSUIDs are scoped per business portfolio, so a user will have different BSUIDs for each WABA they interact with. The Parent BSUID is the mechanism Meta provides to correlate these across a parent Business Portfolio.