I am used to using WhatsApp daily for work. I mainly use SendApp, and when I discovered Wbiztool, I bought it. I chose it for several reasons, the main one being that it’s an online tool: I can manage everything from my computer, my tablet, at home or elsewhere. SendApp, on the other hand, can only be installed on a Windows or Mac device. Also, Wbiztool’s interface is really well designed.

But here’s the thing—I’m extremely disappointed. Not long ago, I integrated the API into Activepieces and set up an automation to replace SendApp... After a few sends, my number was blocked. I contacted support and got the same explanations as others who criticize Wbiztool. Yet, I don’t send promotional offers, these aren’t spam messages. After 24–48 hours, my number was available again. So I removed the API from that automation.

For the past few months, I’ve only been using the API for a handful of sends, maybe five a day. At this rate, my 20,000-message plan is unlikely to run out. But today, I decided to test the Chrome extension. I clicked to test and send myself a message on my personal phone. It suggested the +91 country code; I clicked to remove it. I entered my number with my country code (France). I wrote my test message…

A window popped up to show what the message would look like when received on WhatsApp. In the preview, +91 appeared before my number… I clicked "back" to check: I had definitely deleted their suggested country code. I thought it was a display bug. I sent the message… And then—I don’t get it. MY NUMBER was blocked. Impossible to use.

I’ve just requested a review from Meta.

So reading over and over again that numbers are blocked due to misuse is really mocking customers. For info: I still use SendApp a lot; I’ve only been blocked once because I misconfigured the delay between each message. Now, I set six seconds between each send and have NO blockages… And I don’t spam; all the people I communicate with have signed up beforehand.

How can you explain that my number was blocked for sending ONE SINGLE message to my personal number? I can accept that some users abuse the system and send unwanted messages… But that’s not the case here. Meta seems to detect that the user is using a third-party platform and blocks the number for that reason—and no other.

This app could be amazing, but instead of developing Google extensions and so on, you should fix the REAL problems that cause Meta to detect your platform when sending messages.

Update: I sent a message to support... And after reading their response, I guess the problem is still the user... and sending between 150 and 200 messages per day... Is this a joke? I sent only one message via the platform with the Google extension... One single message to MY personal number. Here is their response, which does not answer my question at all.

Hi Michael,

We advise following the guidelines outlined in our platform to ensure compliance and safeguard your account.
Send utility-focused updates only to users who have opted in. Do not do cold reachout

Personalise each message (e.g., “Hi Anurag—you’d asked about the Ignite video, so here it is.”).

Most critical is that you send helpful messages:- reminder, confirmation, update etc. Don't do generic promotions which people will mark as spam

Send <150-200 message in a day from one number

If you have completely new whatsapp number - Warm up the numbers for sometime before using it for campaigns

Let me know if you have any questions.

Best,
Ivan

Appsumo no longer seems to allow replies to replies. Here is my response to the message from the app publisher:

Thank you for your reply, but all the messages I send via the API are in response to a registration or appointment request. Moreover, my number has not been blocked as a result of this use. I am telling you that your application leaves +91 as the area code and adds it to the area code mentioned by the customer. Another user mentioned this issue on October 8, 2025, on Discord, but received no response, and it is clear that this issue has not been corrected. Meta probably detects a combination of area codes and seems to block the number. I sent 46 messages via your platform (via the API this month, which can't be considered abuse)... and my number was blocked as soon as I tried to test the Chrome extension. The least you can do is consider that the error may be on your end. Testing your tools before deploying them would also be a plus. If just one person had at least tried to change the area code, you would have found the error. I encourage you to thoroughly test your extension, which blocks the user's number when the area code is changed (since this is not taken into account by your application).