Upcoming changes to messaging limits | Developer Documentation

Update an old WhatsApp campaign plan for a shared portfolio limit

If your campaign spreadsheet still assigns a separate messaging allowance to each WhatsApp number, review it before the next send through ChatArchitect. Meta now sets the messaging limit for a business portfolio, and the numbers in that portfolio share it. The transition described in the old version of this article has already happened.

This guide helps you revise a plan made under the former per-number model. Use the current messaging limits guide for the definition of the limit and the checks for a new campaign.

Replace the assumptions in your old plan

Build one coordinated campaign plan

1. Identify the portfolio and numbers. Record which connected numbers belong to the same Meta business portfolio, which teams use them and who coordinates the send. Do not infer portfolio membership just because two numbers appear in the same CRM.
2. Confirm the current limit. Open WhatsApp Manager and look for Account tools → Messaging limits, or ask ChatArchitect support to confirm the limit for the correct portfolio. Record the value and when you checked it. An old screenshot or spreadsheet is a historical record.
3. Collect the overlapping plans. Include campaigns and other planned business-initiated sends from every number sharing the portfolio. Include relevant recent activity when considering the moving 24-hour period. Agree on a time zone so that teams compare the same schedule.
4. Count distinct recipients. The limit concerns different WhatsApp user phone numbers reached outside an open customer service window. Combine the relevant recipient sets across numbers; count an overlapping recipient once in that combined set. A submitted request count or number of template messages is a different measure.
5. Check the audience and other constraints. Apply the permission and withdrawal checklist. Check your ChatArchitect plan and billing separately. The monthly active client allowance does not describe Meta's moving 24-hour allowance.
6. Approve the combined schedule. If the relevant usage or portfolio limit cannot be reconciled, resolve it with support before a large launch. If the plan does not fit, reduce or reschedule the audience and check again before sending. Another team using the same portfolio can affect the plan.

Example: two numbers with overlapping audiences

Suppose number A plans to contact 600 people and number B plans to contact 500 during the same relevant period. If 200 people appear in both lists, the combined planned audience is 900 distinct recipients, not 1,100. These are illustrative audience sizes, not Meta limit tiers.

This calculation alone does not confirm that 900 recipients can be reached. You must account for other relevant activity in the portfolio, check the current limit, and respect each recipient's service window and permission. Sending to the same person from both numbers can also create an unwanted duplicate message even though the person appears only once in the combined audience.

Check old reports and integration references

If a saved report labels a value as a phone-number limit, verify what it measures and when it was collected before using it to authorize a campaign. Ask the owner of the report or ChatArchitect support to reconcile it with the current portfolio limit. Do not treat an old API field, webhook example or upgrade timetable from the imported Meta article as a current customer configuration step.

The standard ChatArchitect customer workflow uses App key and Secret with the connected tool. Checking the campaign plan does not require you to obtain a Meta System User token or configure a Meta webhook yourself.

When the plan and delivery results disagree

Keep the portfolio, sender numbers, checked limit, schedule with time zone, audience calculation and exact error or status together when asking support for help. Follow the sending and retry guide before repeating unsuccessful attempts. If Meta shows a policy notice, use the account restriction guide.

A larger portfolio allowance does not by itself resolve a paused template, a recipient-specific restriction or a sending-rate problem. Confirm the actual cause before changing the schedule.

Meta reference: current messaging limits. The numerical tiers and upgrade criteria can change; the live value for your portfolio is the one to confirm before launch.