phone_number_quality_update webhook reference | Developer Documentation

Review a throughput change for your connected WhatsApp number

A notice about increased platform throughput is a reason to review the sending plan for the affected business number. Confirm what changed and how your connected tool sends messages before increasing its request rate. The throughput guide explains sending speed and rate-limit troubleshooting.

Identify what the notice describes

Meta's field phone_number_quality_update has a historical name: its current reference describes changes to a business phone number's throughput level. Read the actual notice and confirm its scope with support. The event name alone does not establish a change in a message template's quality rating.

Confirm the change for this connection

1. Record the business number, notice wording and time with time zone. Match the number to the connection used in your CRM, help desk or custom service.
2. Ask ChatArchitect support to confirm the current platform throughput and any applicable limits. An old number from a different account or an imported API example is not a campaign target rate.
3. Check the sending workflow with its owner: planned audience, timing, request rate, any visible queue and existing retry rules. If the tool does not expose those controls, ask its administrator or support what can be changed.
4. Check the portfolio recipient allowance and your ChatArchitect plan separately before increasing the campaign volume.

Review existing attempts before adjusting the rate

List attempts already submitted and inspect their available outcomes using the delivery-status guide. A throughput upgrade does not prove that earlier queued or pending messages were delivered. Check previous results and planned retries with the workflow owner before sending to the same recipients again.

If Meta has held messages for quality assessment or paused the selected template, follow the held-message guide or pause guide. Raising the request rate does not establish that those messages can proceed.

After support confirms an appropriate change for the workflow, use an agreed small test with permitted recipients and inspect the final results before releasing a larger batch. The availability of automatic queues, retries or rate adjustments varies with the connection and has not been confirmed as a universal ChatArchitect feature.

Example: platform capacity increased while the CRM schedule is unchanged

You receive confirmation of higher throughput for a number, but its CRM campaign still has the same schedule. Review that workflow's settings and current outcomes with its owner. Establish an appropriate rate and test it before increasing the batch. The platform notice alone does not establish that the CRM has changed its queue or retry behavior.

Information for support and API applications

Provide the connected number and tool, notice and check times, planned audience and schedule, observed request rate if available, and affected attempt references with exact errors. Keep Secret values out of screenshots.

The current ChatArchitect API quick start does not document forwarding phone_number_quality_update to customer callbacks. Confirm the supported event contract with support before using a notice to change a sending process automatically. The webhook overview covers documented message events.