Try Omnifox free 7 days free. No credit card required.
Guides

WhatsApp User Reports and Blocks: The Metric Meta Checks First

Every report or block from a customer counts against your number. How the signal works, what triggers it and how to lower it with opt-in and templates.

September 06, 2026
WhatsApp User Reports and Blocks: The Metric Meta Checks First
In this article

    Every time a customer taps "Block" or "Report" on a chat with your business, WhatsApp records it against your number. Of all the signals that feed into whether a number gets limited, WhatsApp user reports and blocks are the most direct: customers telling Meta, in one tap, that they did not want what you sent. Volume, timing and templates all matter, but this is the metric Meta checks first, because it comes straight from the people you are messaging.

    Most businesses never see the number. On the WhatsApp Business app there is no dashboard; you learn about it when the account is limited. On the official API the signal surfaces as a quality rating on the number and on each template, and as a phone status you can watch move. This article focuses on that one signal: what triggers it, how to lower it, where to see it, and how it differs from the general quality rating.

    How the signal works

    WhatsApp offers "Block" and "Report" when a user opens a chat from a number not in their contacts, and in every chat's menu. When a user reports, WhatsApp receives recent messages from that chat; when a user blocks, the business can no longer reach them. Both count against the sending number.

    Meta has said publicly that user feedback, including blocks and reports, feeds the quality rating, and that a low rating can lead to reduced messaging limits or restrictions. Meta does not publish thresholds. What businesses observe is consistent: a burst of blocks is followed within a day or two by a quality drop, a paused template, or, on the app, a warning. The signal is per number (ten campaigns from one number accumulate on it), recent-weighted (a bad week matters more than a bad month six months ago), relative (blocks as a share of messages sent, not the raw count) and fast (the taps happen within minutes of delivery).

    What triggers reports and blocks

    The triggers are not mysterious. Ask yourself when you last blocked a business.

    Practice Risk Alternative
    Messaging people who never opted in (purchased lists, scraped numbers) Highest; these users report most Only contacts with a recorded opt-in; capture consent in the first exchange
    The same promotion repeatedly High; blocks rise with each repeat Frequency cap per contact; stop after one follow-up without reply
    Odd hours (late night, early morning, Sundays) High; the notification itself annoys Business hours in the customer's time zone
    No way to opt out High; blocking becomes the opt-out "Reply STOP to unsubscribe" in every marketing message, honored immediately
    Generic "Hi! Any questions?" to a whole list Medium; ignored by most, reported by some Segment by interest and send something specific
    Marketing template while the customer waits for an order update Medium; they wanted utility, got a pitch Utility first; marketing after the need is met
    Messaging after the customer said no Very high, and a policy breach Log the opt-out in the CRM and exclude the contact
    Replying to a wave of inbound chats days late, in bulk Medium; people already moved on Reply inside the 24-hour window, with an AI agent for the first response

    None of these is about the content being "spammy" in the classic sense. Reports come from context: who, when, how often, and whether the person had a choice.

    How to lower it, in order of impact

    1. Real opt-in, recorded. Not a pre-ticked box. A clear question the customer answered, stored against the contact with date and source. This is also what TCPA in the US and UK GDPR and PECR in the UK expect, in general terms; confirm the specifics with your own counsel.
    2. An opt-out in every marketing message. "Reply STOP" costs one line and turns a block into an unsubscribe. A block counts against you; an unsubscribe does not.
    3. Frequency caps. Decide the maximum marketing messages a contact receives per month, and enforce it in the platform, not in someone's memory.
    4. Segmentation by interest. A promotion for running shoes to people who bought running shoes gets replies; the same message to everyone gets blocks.
    5. Utility over marketing. Order updates, confirmations and payment reminders are messages people asked for. They build a positive history that cushions the occasional promotion.
    6. Respect the 24-hour window. Inside it, reply to what the customer asked. Outside it, use an approved template specific to why you are writing.
    7. Measure blocks per campaign. On the API you can see template quality and delivery failures such as 131026 (undeliverable, which includes users who blocked you) per send. Kill the pattern that generates blocks.

    A marketing template that follows all of the above, sent to an opted-in segment during business hours:

    Hi {{1}}, the trail shoes you looked at in June are back in your size ({{2}}).
    Free returns until the end of the month. Reply YES for a link, or STOP to unsubscribe.
    

    Where you see the signal on the API versus the app

    On the WhatsApp Business app, you do not. There is no metric, no per-message feedback, no warning until the account is limited. On the official API, the same signal is visible in three places, and a platform surfaces all of them in the channel's health panel:

    • Quality rating of the phone number (green, yellow, red): the aggregate of user feedback in the recent period.
    • Quality per template. Each approved template carries its own rating; one that generates reports gets paused by Meta, independently of the others.
    • Phone status and messaging tier. A number whose quality stays low can be moved down a tier or flagged; one with good quality and growing volume moves up.

    There is a fourth, indirect place: error codes on failed messages. Error 131026 (undeliverable) on a contact who used to receive your messages usually means they blocked you; error 131048 (spam rate limit) means the aggregate has crossed a line. Both are described in WhatsApp API error codes explained. On the API you find out about a bad campaign the next morning; on the app you find out when the number is limited.

    Reports and blocks versus the quality rating

    The quality rating is the outcome; reports and blocks are the main input. Other inputs exist (delivery patterns, template category accuracy), but user feedback is the one you can influence most directly and the one that moves fastest. The shortest path to a better rating is to stop generating blocks. The overall ban picture, including the inbound side most guides skip, is in why WhatsApp restricts numbers for receiving too many messages.

    A weekly routine that keeps the signal low

    For a team running campaigns on the API, this takes about twenty minutes a week:

    • Monday: check the number's quality rating and phone status; note any template whose quality dropped.
    • Before each campaign: confirm the segment is opted in, the send time is within business hours, and STOP is in the body.
    • After each campaign: count 131026 failures and replies; if failures rose against a similar previous send, find out why before sending again.
    • Monthly: purge contacts who opted out or never replied to three consecutive marketing messages.

    Omnifox shows quality rating, phone status and messaging tier on the channel, records opt-in and opt-out on the contact, and runs WhatsApp broadcasts to segments built from CRM tags rather than to the whole list.

    Frequently asked questions

    Does one customer block really affect my WhatsApp number?

    One block is noise; a pattern of blocks across a send is the signal. Meta looks at user feedback as a share of what you sent in a recent period.

    Can I see who blocked my business on WhatsApp?

    Not directly. On the API, a contact who used to receive your messages and now returns error 131026 (undeliverable) has most likely blocked you. On the app, messages simply stop being delivered.

    Is "reply STOP" required on WhatsApp marketing messages?

    Meta's policies require that users can opt out and that you honor it; an explicit STOP instruction is the clearest way. Consumer messaging rules in the US and UK point the same way in general terms; confirm with your own counsel.

    How quickly does a bad campaign show up in the quality rating?

    Typically within a day or two: a lower quality rating, a paused template or delivery failures. Meta does not publish exact timings.

    Give people a way out, and they will not block you

    Reports and blocks are customers voting with one tap. Real opt-in, an opt-out in every message, frequency caps, segmentation and utility-first messaging keep that vote positive, and the API lets you watch the score move before it costs you a tier. Start a 7-day free trial and run your next campaign from a channel that shows you the signal.

    Ready to try it in your business?

    Bring WhatsApp, Instagram, Messenger, email and calls into one inbox, and let AI handle the first reply. Set it up today.

    7 days free. No credit card required.

    Comments (0)

    No comments yet. Be the first to share your thoughts.

    Leave a comment

    Your email is never published. Comments are moderated before appearing.

    Markdown supported. HTML is stripped.

    Read more

    Message us on WhatsApp