Resultados Exponenciais
I got banned from WhatsApp: a month without my main channel

I got banned from WhatsApp: a month without my main channel

Meta has been blocking and banning numbers that use the unofficial WhatsApp API, even without bulk messaging, and today small volumes can already take an account down. My main number stayed banned for a month.

Daniel ValladaresNovember 10, 20265 min read

Quick answer: Meta has been blocking and banning numbers that use the unofficial WhatsApp API, even without bulk messaging, and today small volumes can already take an account down. My main number stayed banned for a month. If you depend on WhatsApp to sell, the official API costs more per message, but it gives you stability, and that's worth more than the savings.

I used to defend the unofficial API. If you search my YouTube channel, you'll find videos of me defending it. I used it for cost reasons, plain and simple. Until I got hit with a massive block on my main number.

This article is an account of what happened, what I learned and what I recommend today to anyone still on the unofficial API.

What happened

I wasn't running a campaign. I wasn't sending anything in bulk. My virtual assistant was just replying to people who messaged, in real time. At a moment when several people messaged at once, the message flow got high, Meta identified that I was using the unofficial API and banned me.

It was the number I promote on YouTube, on social media, everywhere. For almost a month I couldn't even see who was messaging me, because everything died. Some people found me on Instagram, others reached my personal phone somehow. Most didn't.

It was the worst month of my year. And then the math became clear: one month of revenue is much bigger than what I spend today on messages with the official API. I migrated.

Why the unofficial API is getting blocked so much

Meta is working to eliminate the unofficial API

The direction is clear: Meta wants to charge for messages and has been disconnecting anyone who uses an unofficial API, from any system, even without automation. There are cases where just connecting gets you blocked. There's no fixed rule.

The tolerated volume has plummeted

I used to be able to send far more messages per hour without any trouble. Today, in the operations I follow, sometimes just a few messages in a row already trigger a block. Even with an interval of several minutes between them.

I myself was running a follow-up automation where an AI reads the conversations, writes a personalized message for each person and sends one every 5 minutes, only during business hours. I still got blocked.

Bulk messaging tools were built for the official API

Many CRMs send in large batches because they were designed for the official API. When you use that bulk sending on an unofficial connection, Meta reads it as a bot, flags it as spam and you lose the number. The block doesn't come from the CRM, it comes from Meta.

Adding an interval between messages helps, because it makes it harder to identify as bot behavior. But it reduces the risk, it doesn't eliminate it.

Reports take anyone down

If someone blocks or reports your number, no tool will save you. That applies to any connection.

What about a SIM card farm?

The alternative a lot of people use is the "farm": several SIM cards and phones connected, knowing you'll burn through the SIMs at some point. I've done it. Today, honestly, I don't recommend it.

The hard truth

This topic annoys me, but there's nothing to be done. We're using a tool that belongs to them. They own it and they do whatever they want. If we want to stay, we have to follow the rules.

The cost of the official API, in practice

The official API charges per business-initiated message, and prices change often. But look at the cost the right way: if, with a large volume of conversation openings, you can't convert even one customer who pays for the investment, the problem isn't the lead. It's the offer or the approach.

And when you weigh it against the risk of losing your main number, cost stops being the biggest problem.

Checklist: how to reduce the risk starting today

  • Consider migrating your main number to the official API, the one you promote in ads and on social media.
  • Don't use bulk sending on an unofficial connection.
  • Keep a backup number, one at most, so your operation doesn't stop if something goes wrong. More than that gets hard to manage.
  • Move internal communication off WhatsApp. I moved my team's internal notifications to Telegram, which is more tolerant of bots. WhatsApp is now only for customers.
  • Collect email and phone from your contacts. If the channel goes down, you still have a way to reach people.
  • Promote more than one point of contact (Instagram, website, email) so customers can find you.

Frequently asked questions

Can using an unofficial WhatsApp API get my number banned?

It can. Meta has been identifying and banning numbers that use unofficial connections, even without bulk messaging.

How many messages does it take for WhatsApp to block a number?

There's no fixed number. In the operations I follow, I've seen blocks after just a few messages, even with an interval between them.

Does adding a delay between messages prevent a WhatsApp ban?

It reduces the risk, but doesn't eliminate it. And a contact report takes down any number.

Do SIM card farms still work?

I've used one, but today I don't recommend it. You'll burn through SIMs and the operation becomes unstable.

Is the official WhatsApp Business API worth the cost?

If you depend on WhatsApp to sell, yes. The cost per message is predictable; losing your main number isn't.

Keep reading

Want to migrate without stopping your operation?

If you want to understand how your operation would look on the official API, talk to Aurora, our assistant: talk to Aurora on WhatsApp.

WhatsApp banunofficial WhatsApp APIWhatsApp Business APIWhatsApp number blockedWhatsApp Businesscustomer service

Ready to sell more and better?

Chat with Aurora on WhatsApp and find the best solution for your business.