WhatsApp API numbers banned despite compliance?

logan-lifecycle

Almost lost the business last year to bans on the regular WhatsApp Business app. Migration to the official API was the obvious next step. Tried WATI-priced me out of the market and still got flagged there. Eventually found a local platform that ran in coexistence mode with my existing app. Since January, smooth sailing. Approve templates through Meta, send utility messages, leads opt in, then I nurture them toward purchase. Clean, controlled logic branch.

Then we onboarded a second number for my business partner. Same platform, identical setup. But last week we tested a different niche-cold leads scraped from public groups, not our own database. That number got banned within days. Mine stayed clean until a few minutes after his went down. Coincidence? Both under the same Business Manager, so the correlation is obvious.

Appeals went through, both numbers restored. This morning I sent a single test message-fine. Partner only replied to inbound messages, no outbound campaigns, and got banned again hours later. I then sent ₁₂₀ warm leads a standard flow and got banned too.

So what's the actual trigger? Is it the cold lead source? The fact the numbers share a BM? or the platform itself getting flagged? The platform dev says other clients are seeing the same pattern. My money's on a combination: using non-owned data sets combined with correlated numbers inside the same manager. That's a logic branch Meta's abuse detection hits hard. but the fact that just replying to incoming messages triggered a ban suggests something deeper-maybe the phone hardware fingerprint? We've already requested another review. This feels systemic, not a single botched send.

zoecreative

it's the API correlation that flags them every time. spread across 15-20 devices, cap at a handful of new chats per phone daily. Keep everything off the Business API entirely if you want them to stick

maya-b2b

it sounds like your partner's messages were flagged as spam. In my experience, the core issue is using a third-party list rather than building your own opt-in database. Focusing on quality engagement from the start would help prevent those bans

justauser

honestly, I don't think you're getting proper lead analytics from whatever WhatsApp API service you're using. If your number got banned, it's almost certainly because a few of the contacts you sent cold messages to reported it. And if you don't know exactly who did it, you're basically sending the same junk to the same people who already flagged you once. of course they'll keep reporting your alt numbers - it's spam, plain and simple. Imagine reporting someone for an unwanted message and then getting the exact same rubbish from their backup numbers. anyone would be furious. 😤

weekendhustle

Ugh, that's a tricky one. Sounds like someone (or a few people) have been actively reporting the number. If it's getting flagged repeatedly, it's usually down to spam complaints or people marking messages as unwanted. Might be worth checking the opt-in flow and making sure the consent message is crystal clear.

jamesaso

Is your business actually verified on the WhatsApp Business API? Without it, you're capped at 1,000 conversations per day - and any spike in volume or unusual behaviour flags the number instantly.

copycat

I've seen this happen a fair bit, and it's almost always down to how the number was onboarded or the message templates triggering Meta's spam filters. Happy to chat through it in DMs - I can share what's worked for me - but the quick fix is usually tightening your opt-in flow.

davidsearch

Nope, the ban is entirely down to the age of the numbers. Fresh WhatsApp accounts hitting sudden lead volume get flagged as spam-WhatsApp's algo sees high inbound activity with zero history and assumes phishing. Even after unbanning, the pattern repeats, and soon the whole IP range gets cooked.

We ran into the exact same issue. Solution is brutal but necessary: buy aged numbers, then warm them up gradually over 3-4 weeks. Start with 5-10 outbound messages a day, then slowly scale. CPC doesn't matter if you can't even keep a number live. Treat it like a quality score for WhatsApp-ramping too fast kills your CPA.

localpack

Yeah, this is painfully familiar. 😞 Once one number gets the axe, the whole Business Manager seems marked. Happened to me twice - tried appealing, but WhatsApp support is basically a black hole. No way to talk to a human.

My fix? Had to spin up an entirely new Business Manager from scratch: fresh email, separate browser profile, different admin accounts. Absolutely tedious, but it worked.

Critical rule: do not blast cold leads. That's the fastest way to burn a number. Warm up slowly, only message people who've opted in. Ignore this at your own risk.

trendspotter

The exact same pattern keeps cropping up in these ban stories - always scraped groups rather than the channel itself. Meta threads every number under a single Business Manager like some invisible spiderweb, which is why your primary dropped within minutes of your partner's. One report triggers a domino effect across the entire BM.

Warming up a number helps in theory, but it's cosmetic. It doesn't touch the raw nerve: unsolicited messages to people who never opted in get flagged, and the report rate is the one metric that actually seals your fate. If your genuine daily volume sits south of a few hundred warm or inbound conversations, driving the actual WhatsApp desktop app - your real number, your real WhatsApp session - dodges the whole template-and-BSP machinery entirely. There's nothing for Meta to correlate across a Business Manager that way.

The official API is the right tool when you genuinely need templates and scale, but it won't rescue a cold-outreach motion. Nothing will. It's a fundamental mismatch of brand trust and permission.

logan-lifecycle

So you're thinking about scaling horizontally across multiple API numbers to distribute the send volume and reduce the per-number ban risk? That's the classic "split the load" trigger, and theoretically it should work-each number stays under the abuse threshold, so the platform doesn't flag it.

But the real bottleneck isn't the numbers, it's the licensing cost per number. Each additional phone number means another WhatsApp Business API account, and most providers charge per-number monthly fees plus per-conversation charges. the cost compounds fast. I've seen teams burn through budget just trying to stay ahead of bans, only to find that the root cause (message quality, opt-in hygiene, outbound velocity spikes) is still there-it just gets distributed.

If you do go the multi-number route, treat each number as a separate journey node with its own send limits and retry logic. use a round-robin or least-recently-used allocation per contact segment. but you're right-the tooling cost stings. some platforms offer bundled pricing for multiple numbers, so worth asking your provider if they have a multi-number plan rather than paying per license. Even then, it's still a workaround, not a fix.

ctrjunkie

Honestly, swapping phones won't fix it if the real problem is poor consent and cold leads. Meta isn't just looking at volume per number - they track block rates, report rates, and patterns across your whole Business Manager. Spreading the same dirty data across twenty phones just makes the same mistake twenty times over. Your partner's number getting banned for cold group leads? That poisons the entire BM.

As someone who runs campaigns through the official API and some third-party tools, the golden rule is warm list only. Cold leads are a ticking time bomb. That's what keeps numbers clean in the long run.

logan-lifecycle

Sounds like a classic trigger-loop scenario. If his number got banned again with zero outbound activity, Meta's backend likely still sees a prior violation flag on that account. In journey terms, his number is a contaminated node-it's still firing risk signals even when idle.

I'd recommend isolating it from your account completely. Treat it as a separate branch: spin up a clean WhatsApp Business Account with a fresh number, and keep your own number on a different API key or business manager. The real question is whether the ban propagates through shared cloud API tokens or just phone number association. If it's the former, you might need to regenerate tokens too.

Are you both under the same Meta Business Manager?

funnelhacker

Exactly the same issue here. Cold leads hammering the spam report button slaughters your sender reputation.

Short-term fix? Rethink your initial template entirely. Build a proper engagement flow-don't just blast a message and hope. Measured a 40% drop in spam flags on one account after we switched from a generic outreach to a two-step opt-in sequence.

If you're not warming those leads before the first WhatsApp touch, the platform will keep burning your numbers.

localpack

good question - are they perma-banned or just restricted? Makes a big difference for recovery. i've seen both

zoecreative

Honestly, this whole WhatsApp API ban situation is driving me up the wall. Been seeing it wreck automated flows for a few client campaigns-nothing spammy, just standard order confirmations and cart recovery. The official API's forgiveness level seems to be zero.

Are you doing any kind of automated outreach, or is this more for broadcast-style messaging? If it's the former, I'd strongly suggest dropping the official API and running with something like whatsmeow or baileys. Less overhead, way fewer false positives, and you keep full control over your number reputation. The API's machine learning model is frankly too aggressive for anything that isn't strictly human-paced.

zoecreative

Exactly this. WhatsApp's anti-spam systems aren't checking creative quality or engagement patterns - they're essentially looking at raw send counts and flagging anything that looks like mass messaging without a warm sender reputation.

The platform treats high throughput as a proxy for spam, regardless of intent. So if your API is pumping out hundreds of conversations from a fresh number without building a proper engagement history, you're asking for a ban. It's a volume game, but only once you've earned the right to scale.

Most people miss the warm-up phase entirely.

ctrjunkie

Ditching his number might not solve the issue if both numbers are still sitting under the same Business Manager account.

What probably happened: his number got flagged from that cold leads campaign a while back. WhatsApp doesn't always ban straight away. The ban hit delayed, and because both numbers share the same BM, yours got dragged into it.

For what it's worth, I've seen this exact playbook before. One number burns, the BM itself takes a quality score hit. Any other number under it becomes a target for a while, even if it did nothing wrong.

Don't drop his number just yet. Try warming both numbers slowly with only reply-based traffic for a couple of weeks. Let the BM cool off.

Are both numbers registered under the same legal business entity in the BM?

logan-lifecycle

scaling to hundreds of messages a day without the API is asking for a trigger-happy ban-it's a logic node failure waiting to happen. Account hygiene doesn't stand a chance at that volume without proper routing

zoecreative

honestly, doesn't matter how clean your copy looks or how slick the creative is - if you're cold outreaching or touching unofficial APIs, they flag you regardless. Best I've seen is splitting volume across devices and capping new chats at fifteen a day max. Still not bulletproof.