WhatsApp ban risk matrix by type of use

The classification combines three factors: who receives (do they know you), what they receive (a reply or your initiative) and how it is sent (one to one at a human pace, or bulk and repeated). It is a priority map, not a guarantee. Nothing here is a rule published by WhatsApp; it comes from reading the Terms of Service and from reported practice.

The levels are low, medium and high. Even low exists, because the platform can restrict any account that uses unauthorized automated means. The foundation is in the guide why WhatsApp bans numbers.

The honest reading: what weighs most is not the tool but the combination of cold audience, volume, repetition and lack of an exit. The more items on that list you tick, the higher the risk, with any vendor.

1) Relationship: a contact who has already talked to you reports less than a stranger. 2) Reciprocity: if people reply, the pattern looks like conversation. If nobody replies, it looks like blasting. 3) Repetition: identical texts to many people are easy to recognize. 4) Pace: bursts with no pauses depart from human behavior. 5) Reputation: recent blocks and reports weigh, and a new number has no history yet.

Each factor has practical levers, described in the anti-ban guide and the chip warm-up guide. If you want a ready routine, use the warm-up checklist.

Answer yes or no: has the recipient talked to me before? Did they consent to receive this? Does my text change from person to person? Is there an interval between sends? Does the number already have usage history? Is there an easy exit that I honor? Do I track replies and complaints?

Three or more "no" answers put the case in the high band. The good news is that each "no" is fixable: asking for consent, varying the text, spacing sends and warming up the number change your position on the matrix. No adjustment removes the risk, but they take the case out of the band where restriction is likely.

Watch the reply rate (falling is a warning sign), messages that stay undelivered, "who are you?" replies and blocks reported by support. The API has an endpoint to check the number's current limit of new conversations, described in the reference, useful for tracking warm-up.

If the signs get worse, slow down, pause cold campaigns and go back to talking only to people who reply. Stopping early costs little; insisting costs the number. If the number falls anyway, follow the blocked number step by step.

It does not say how many messages per day are safe, because there is no reliable public number; read how many messages per day. Nor does it say low risk is zero risk: WhatsApp can restrict any account at any time, within its Terms.

For operations where losing the number is unacceptable, the matrix points to Meta's official API, with approved templates and clear rules. See the unofficial API, an honest guide to decide.

Treat the number as consumable: keep a spare number already warmed up, split functions across different numbers (support, sales, collections) and keep contacts and history in your CRM, not only on the device. That way a restriction becomes an annoyance, not an outage.

This is architecture, not a promise: well organized multi-instance isolates the problem. See several numbers in one system.

A clinic confirming appointments: the audience already booked, the message is useful and one to one, and there is a natural reply ("confirmed" or "I need to reschedule"). The matrix puts the case between low and medium. The watch-out is the volume of identical reminders at the same hour: spread sends through the day and vary the wording.

A shop reactivating old customers: the list is yours, but nobody has talked in months. It lands in medium to high. Segmenting by recent buyers, asking for refreshed consent and starting with a small batch changes the position. If the list has contacts from years ago, clean it first with the number check.

An agency blasting third-party lists: this is the highest-risk case on the matrix, because it combines a cold audience, repeated text and no relationship. The honest answer here is to change the model: capture contacts with consent and only then converse. If the agency's client demands this kind of blast, it is worth discussing the official API with approved templates.

Every week, look at five indicators: reply rate per number, number of exit requests, undelivered messages, complaints or blocks reported by the team, and recent changes to text or audience. Note what changed, because almost every problem shows up one or two weeks after a change in behavior.

If two indicators get worse together, halve the pace and go back to talking only to people who replied in recent days. If the drop continues, stop the number and investigate before insisting. This simple habit is worth more than any table of limits copied from third parties.