The message_template_quality_update webhook

What it is measuring

How people react to messages sent with one particular template, rather than to the number as a whole. Blocks and reports weigh heaviest, and not engaging at all counts for something too.

That per template scope is what makes it useful. A number can be healthy overall while one template quietly poisons its own audience, and this is the event that separates the two. Without it, the first signal is that template failing to send while everything else on the number works normally.

Why acting early is the whole point

Because every state after this one is worse and harder to undo.

Quality falling far enough pauses the template, which returns error 132015 on every attempt and lifts only after a period Meta does not publish. Repeated pauses disable it permanently, at which point the content has to be rebuilt as a new template under a new name.

A quality signal arriving while the template still sends is the only moment where editing costs nothing. Once it is paused, editing is still the right move, but a send path has already been broken for however long nobody noticed.

What usually causes it

Content and audience, in that order, and the second is the one people forget.

• Promotional language inside a template declared as utility, which recipients did not expect.
• A message that does not make clear which business is writing.
• Sending to a list rather than to people who have engaged recently.
• The same template going out at volume to an audience that never asked for it.

Common mistakes

• Treating it as informational. It is the last signal that arrives while the template still works.
• Reading it as a problem with the number. It is scoped to one template.
• Editing the wording and keeping the same audience. Who it goes to produces the same signals as what it says.

Frequently asked questions

Keep reading