WhatsApp API Updates for 2026:
Portfolio Pacing, 100K Messaging Limits, and Usernames (BSUID)
Index
Meta is rolling out major WhatsApp Business Platform (Cloud API) updates across 2026 that affect two things every team relies on: how fast you can scale messaging and who your customer is.
The biggest change is WhatsApp usernames, which may hide phone numbers by default and introduce BSUID (business-scoped user ID) as the identifier delivered via webhooks. Meta is also changing messaging limit tiers and adding business portfolio pacing, which can batch-send large campaigns and pause delivery based on feedback signals.
This article breaks down what changed, who’s affected, and what to prepare so your acquisition and operations don’t get disrupted.
Summary table
| Update | Who is affected | What changes | What to do now |
|---|---|---|---|
| Business portfolio pacing | Newer/suspicious accounts | Large campaigns may be sent in batches; the remaining batch may stop on harmful/policy feedback | Warm-up, segment, monitor quality signals |
| Relaxed messaging limit tiers | Businesses completing verification/quality path | 2K/10K tiers removed; 100K daily messaging limit becomes baseline | Prepare campaigns and features that were tier-blocked |
| Usernames + BSUID | Any Cloud API business | Some customers’ phone numbers may be hidden; BSUID becomes the customer identifier | Store BSUID, update CRM joins |
Business Portfolio Pacing: batched sending + feedback checks
What changed
WhatsApp is pacing large campaigns by sending messages in batches and monitoring feedback before releasing the next batch. If signals suggest harmful content or policy violations, remaining messages may not be sent.
Who is subject to pacing:
- businesses new to the platform (less than 500,000 messages sent in the last year)
- or accounts where suspicious signals are detected
When it triggers: large volume in a short time, regardless of template type.
How it works
WhatsApp releases your send in batches, checks feedback/quality signals, then continues or stops the remaining batch if risk signals appear. The practical outcome is that “having a high messaging limit” does not guarantee instant full delivery.
What to prepare
- Warm up volume: ramp gradually instead of sudden spikes.
- Segment audiences: smaller targeted sends usually generate better feedback signals.
- Monitor quality signals: blocks/reports = faster throttling.
- Design campaigns to be stoppable: if batch #2 pauses, batch #1 should still produce value.
Messaging Limit Update: 2K/10K tiers removed → 100K baseline
What changed
Meta will remove the 2K and 10K daily messaging limit tiers. Once a business completes Business Verification or the Quality messaging scaling path, it will immediately receive a 100K daily messaging limit. Rollout begins with select partners in Q1 2026, with full removal in Q2 2026.
How it works
Instead of gradually stepping through 2K → 10K → 100K tiers, verified/qualified businesses move to 100K/day faster. This reduces “tier planning” and makes scaling campaigns simpler, while pacing (next section) becomes the safety guardrail.
What it means for you
If your WhatsApp use case was blocked by low-tier limits, the shift to a 100K baseline means:
- fewer feature rollouts delayed by tier friction
- larger campaigns become feasible earlier
- Groups API plans that were previously constrained by tier-related access can become realistic once your account hits 100K
What to prepare
If your WhatsApp use case was blocked by low-tier limits, the shift to a 100K baseline means:- Make Business Verification / quality scaling a standard onboarding milestone.
- Update campaign playbooks: with easier access to 100K, your bottleneck shifts from “limit tiers” to deliverability quality + pacing behavior.
WhatsApp Usernames + Business-Scoped User ID (BSUID)
(June – H2 2026)
What changed
WhatsApp is launching usernames to improve phone-number privacy. Once usernames are adopted, some users’ phone numbers may no longer be automatically visible to businesses. To support Cloud API businesses, WhatsApp will rely on a new customer identifier: BSUID (business-scoped user ID).
What you need to know
- Rollout timing: usernames start in test countries in June 2026, then expand gradually.
- Phone numbers are not going away: businesses that already have a user’s phone number from prior interactions can continue sending messages to that number. If a user has not adopted usernames, businesses will receive both their phone number and the business-scoped identifier.
- 30-day transition behavior: WhatsApp will automatically return a user’s phone number for a rolling 30 days after any interaction between a business and that user’s phone number.
What to prepare
- Store BSUID in your customer database: Add BSUID as another field in the customer profile alongside phone/email, and ensure you can join records when phone number is missing.
- Fix anything triggered off CRM Triggered campaigns, chatbots, attribution/measurement, billing……anything that assumes “phone number always exists” needs BSUID logic.
FAQ
If my business gets a 100K messaging limit, will WhatsApp deliver all 100K messages immediately?
Not always. A higher messaging limit is your maximum capacity, but portfolio pacing can still affect delivery by batching sends and pausing remaining batches if feedback signals are negative. Plan campaigns with gradual expansion and segmentation instead of a single sudden blast.
What are WhatsApp usernames, and how do they affect businesses?
Usernames allow people to message businesses without automatically revealing a phone number. For username adopters, phone numbers may not always be shared by default, which changes how businesses identify and route customers.
Will we still see phone numbers after usernames roll out?
In some cases, yes. Meta states businesses that already have a user’s phone number from prior interactions can continue to message that number, and WhatsApp may return phone numbers in certain transition scenarios. But because phone numbers won’t always be available for username adopters, BSUID should be treated as the reliable identifier for automation and CRM syncing.
