business_capability_update webhook reference | Developer Documentation

Review a changed WhatsApp account limit before your next campaign

If Meta or support reports a change to your account's messaging allowance or phone-number capacity, check the affected account and your current campaign plan before increasing sends or adding a number. The messaging-limit guide explains recipient allowances; this checklist helps you act on a change notice.

Identify the affected account and allowance

1. Record the notice wording, the account or business portfolio it concerns, and the time you received it with time zone. Keep any stated effective time separately.
2. Identify the connected WhatsApp Business numbers in that portfolio. A limit notice for one portfolio does not establish the allowance of another connection.
3. Check the current Meta allowance in WhatsApp Manager or ask ChatArchitect support to confirm it. Specify whether you are checking the recipient messaging limit or the ability to add business phone numbers.
4. Compare the current value with a previous observation only if both refer to the same allowance and scope. A notice that an account was created does not establish an increase for an existing account.

Recheck a campaign that was already planned

For a recipient-limit change, coordinate the campaign owners across the numbers in the affected portfolio. Use the portfolio campaign planning guide to review distinct recipients and overlapping audiences in the applicable rolling period. Check the available allowance with support before releasing additional batches.

• If the current allowance is lower than the plan requires, review the schedule and audience with the workflow owners. Use the controls available in each sending tool to revise future sends.
• If an allowance has increased, check template status, consent and the sending tool's behavior before increasing the campaign. An account allowance does not establish a particular processing speed; see the throughput guide.
• For attempts already submitted, inspect their results using the delivery-status guide. A changed limit does not establish the outcome of an earlier message.
• For an account policy notice or restriction, use the restriction response guide and ask support to identify the applicable issue.

Check the commercial plan and additional numbers separately

Your ChatArchitect plan has its own monthly active client allowance. Check it in your account and against ChatArchitect's current terms. A Meta limit notice does not establish that the ChatArchitect plan or its billing terms have changed.

If a notice concerns the capacity to add business numbers, confirm which account and portfolio it applies to before preparing another connection. Follow the number connection checklist. If the supported form refuses the additional number, preserve the exact error and affected account details for support.

Example: a larger allowance while two teams share a portfolio

Support confirms a larger recipient allowance for the portfolio used by two business numbers. Compare both teams' planned audiences and previous sends before releasing the next batch. Keep the ChatArchitect tariff check and the processing rate of each connected tool as separate parts of the plan.

Information for support and API applications

Provide the affected account or portfolio, connected numbers and tools, notice wording and times, current allowance if visible, and planned campaign or number-connection step. Keep Secret values, PINs and verification codes out of screenshots.

Meta names its direct developer event business_capability_update. Its official reference concerns account and portfolio capability changes. The current ChatArchitect API quick start does not document forwarding this event to a customer callback. Confirm availability, scope and the event contract with support before automating campaign decisions. The webhook overview covers documented message events.