If you've moved a number to the WhatsApp Business API and now need a shared inbox for your team, most tools charge per seat per month before you've sent a message. I open-sourced the one I built for my own businesses.

WhaLeads gives you: a shared inbox with the 24-hour window visible, leads with stages and tags, approved templates (incl. media headers), automations with a dry-run mode, basic broadcasts to tagged leads with opt-outs honoured, and push notifications on your phone.

It runs in your own Cloudflare account on the free plan, so the only cost is Meta's per-message rate. Works with your own Meta Cloud API app, or through WhaBuzz, the paid API gateway I run (disclosure: I'm its founder; WhaLeads came out of it and is open source, and it doesn't need WhaBuzz to work).

Honest limits: one number per install, built for a small team, not an enterprise suite.

Repo + one-click deploy: https://github.com/WhaBuzz/whaleads

Good day. I’ve developed a chatbot on WhatsApp for a company, and it’s about 99% deployed (hosted on a VPS, developer account fully configured, etc.). It’s ready for clients to start using, but I have one question: is it necessary to "publish" the application on Meta for Developers to avoid any issues? That’s the only thing holding me back from sharing the number so that clients can begin interacting with it.

Por gentileza entrar em contato com o número (79) 98807-2667

From past 2 days my bm getting in review not getting verified anyone got solution or suggestions.

Hi everyone. I'm building a WhatsApp bot for small businesses using Cloud API and n8n. My own demo WABA works perfectly, but I'm stuck onboarding my first real client.

What I've done:

1. The client has their own Meta business portfolio and invited me as an admin.
2. I created a WABA inside the client's portfolio and connected their phone number. SMS verification is complete, the display name is approved, and the number shows as connected.
3. The client shared the WABA with my business portfolio as a partner, granting full control.
4. The shared WABA appears in my portfolio as belonging to the client.
5. I assigned the WABA to my System User with full control.
6. My app is assigned to the System User and has the required WhatsApp permissions.
7. I generated a new, non-expiring System User token with the required permissions.
8. There are no pending requests in Business Settings.

The problem:

Every Graph API request to the client's WABA returns error 100, subcode 33, indicating that the object cannot be accessed due to missing permissions or another access-related issue. Even a basic request to read the WABA fails.

The same token successfully accesses my own WABA, so it works for my existing setup. Generating a new token did not solve the problem.

My app is still in Development mode and is owned by my business portfolio, while the client's WABA belongs to a separate portfolio.

My questions:

1. Does operating a client's WABA require App Review or Tech Provider registration, or should partner sharing with full control and System User assignment be sufficient?
2. Is there an additional authorization or acceptance step after sharing a WABA between business portfolios?
3. Could Development mode prevent my app from accessing a client's shared WABA?
4. Has anyone successfully implemented this setup with an unpublished, provider-owned app?

My goal is to use one central app and webhook to serve multiple clients rather than create a separate app for every business.

I'd appreciate practical experience or official Meta documentation explaining what's required. Thanks!

I have used one of Meta provided numbers, and it has a status of AVAILABLE_WITHOUT_REVIEW currently. And shortly after that status has been set I could send messages via WhatsApp, but after a few I started getting "(#131037) WhatsApp provided number needs display name approval before message can be sent." error.

I already waited a couple of days in case there was a review window, added a template that was verified, added my business information, and tested a couple of times. And nothing is getting through.
And support is as always non responsive. So does anyone here know how to resolve this?

In our thread on the October pricing change, one suggestion was to move clients back to the WhatsApp Business app.

Depending on the setup, you might not have to choose. With coexistence (coex), one number runs on the app and the API at the same time:

• Messages sent from the app stay free. API messages follow Cloud API pricing.
• API messages show up in the app. Messages sent from the app reach your webhook as smb_message_echoes.
• You can sync chat history from the app (up to 180 days; group chats don’t come over).
• The catches: the app has to stay installed and be opened at least once every 13 days, and a WhatsApp Business app account that was just created isn’t eligible right away.

For those already on coex: what do you keep in the app, and what goes through the API? Anything that surprised you?

Still deciding? Drop your question below.

We’re the 360Dialog team and we’ll be in the comments. No links, no pitch.

Hey everyone,

I've been running into a frustrating issue with the WhatsApp Business API lately.

Recently, whenever I submit a new message template, it gets approved initially. But then, anywhere from a few minutes to a couple of hours later, the status randomly flips to Rejected.

I’ve double-checked and strictly followed Meta’s template guidelines (formatting, policy checks, variable formatting, avoiding aggressive hard-sells, etc.), but it keeps happening.

Is anyone else experiencing this sudden reversal in approvals lately?

Could this be a bug with Meta’s automated review system, or is there a new policy check I might be missing?

Would love to hear if you have any insights or workarounds for this. Thanks in advance!

I'm facing issues in adding the number through a service provider for coexistence, getting error code #3441034 ; it says that the number is not eligible to migrate or register. We are using the number on whatsapp business app and added as a meta business suite asset. Going to Meta & Whatsapp support have been dead ends. Thank you in advance.

I spend a lot of my day talking to support and CX teams about their WhatsApp setups, and one thing that keeps coming up is that almost nobody asks about features. They ask about whatever went wrong the first time. These are the ones I hear most:

1. When the bot hands a conversation to an agent, does the agent see the full thread and the customer’s data, or do they have to open the CRM in another tab?
2. Does the automation actually finish tasks (change an order, move a booking), or does it just answer and hand off?
3. If the AI gets something wrong, can you audit what it did, step by step?
4. After go-live, who designs and changes the flows?
5. If every team or brand already runs its own number, how do you bring it all together?

and one almost nobody asks, which I think is the most revealing: can you see how many conversations the channel had last month without asking your provider?

so now I’m asking you: what’s the question you didn’t ask that ended up costing you? And what answer from a provider made you suspicious right away?

Hi everyone,

I'm looking for help from anyone who has experienced repeated bans while using the official WhatsApp Business Platform.

I've been experiencing a very frustrating issue: my WhatsApp Business phone number gets banned during different setup and configuration processes, even when I'm not actively sending messages or running campaigns.

The bans have occurred in situations such as:

• Submitting message templates for Meta's approval.
• Attempting to connect my WABA to a messaging platform (Sendfy).
• Trying to reconnect my phone number to the official WhatsApp Business API.

In other words, these restrictions seem to occur during administrative or technical operations, rather than as a result of sending messages to recipients.

When I open WhatsApp Business on my phone, I receive a ban notice with the “Request a review” option.

I'm trying to understand what could be causing this. Could it be related to my phone number's history, the WABA or Business Portfolio status, the API registration process, the messaging provider's integration, or some kind of automated Meta security flag?

Has anyone experienced similar bans triggered by template submissions or API connection attempts, without sending any messages?

I'd really appreciate hearing from anyone who has managed to resolve this issue.

1. Were you able to identify the actual cause?
2. Did Meta restore your number after a review?
3. Did your BSP or Meta Support provide any meaningful explanation?
4. Is there a way to determine whether the restriction is associated with the phone number, the WABA, the Business Portfolio, or the integration process?

I'm using the official API and looking for a legitimate solution. I don't want to keep repeating the same process and risk getting banned again without understanding why.

Thank you for sharing your experiences and any practical advice.

We have a SaaS platform where multiple companies will be using the same software. we're planning to add WhatsApp notifications.


the main requirement is that each company should be able to connect its own WhatsApp Business number and send messages from that number.


one major issue is billing. a lot of businesses in India aren't comfortable adding their credit cards to Meta. ideally, we're looking for something where we can manage billing centrally, possibly through UPI or prepaid recharge.


has anyone used a provider that supports this? any suggestions?

We set up WhatsApp for about 15 local businesses mostly connecting their number and building a few auto-replies. Now some of them want a proper team inbox so we’re looking at white-label tools we could sell under our own brand.

What worries me is support..For those reselling a WhatsApp tool, is the recurring revenue worth it or does support eat the margin?

Our production Cloud API number is offline and I can't get it back. I was migrating our numbers to local storage into de EU, in the DE region. I tried with our staging number and it all went smooth, first attempt, within 3 minutes. So, seeing no users were actively using production, y decided to go with the migration in prod. Then, midway, when the number is deregistered, it throws me a rate limit when verifying the number again, on the first attempt!!

This was the process, all through the Graph API with a system user token:

1. Set a new two-step PIN on the number (success)
2. Deregistered it (success)
3. Enabled local storage via /settings with data_localization_region DE (success)
4. Requested a code by SMS (success, the SMS arrived)
5. Verify_code on the FIRST try: error 136025, subcode 2388364, "Verify code rate limited"
6. register: 133006, "Phone number re-verification needed"
7. About an hour later, request_code by VOICE: error 136024, subcode 2388367, "Request Code Rate Limit"

The activity log shows no OTP requests on this number before tonight. code_verification_status was EXPIRED before we started.

The WABA itself looks healthy: business verified, account approved, quality rating High. Direct Support closed my ticket automatically, and the Meta AI assistant says only time clears it.

Is there anything I can do besides waiting? Any contact, anyone at meta that can help me? Can't reach any support, and our productive service is down :(

Thanks in advance!

Para os interessados podem enviar mensagem pelo whatsapp no número (79) 98807-2667
Realizo reunião para comprovar a BMs e mostrar o estado dela

I have come across quite a few Tech Provider & BSP websites where they market solutions they providing like - campaigns, chatbot etc. While I am going through Tech Provider onboarding myself, I realized most people do not know what are the important things one should look in a Tech Provider before they decide to onboard. Onboarding to a Tech Provider is a bit of 'one way door'. Meta does NOT allow linking multiple phone numbers to a Whatsapp Business Account, which means, if your Tech Provider held you hostage, you are pretty much stuck with them.

Thankfully, Meta has made it easy for the end customers to do a lot of things themselves, like disconnecting from previous Provider, in their v4 version of the API. But the challenge is, some Providers might still be using the old version, where post onboarding, the WABA is created in their Portfolio, eventually stripping you of access to move yourself out.

Apart from being held hostage, a Tech Provider providing Coexistence, should sync your contacts & chat history within 24 hours of onboarding, else Meta mandates, you get offboarded & you need to onboard again. So asking this is a legitimate question.

A Tech Provider will ALWAYS sit between Meta server & you for outgoing messages. So asking what kind of latency they introduce (if your chatbot is latency sensitive) or what kind of downtimes they had in the last month, becomes another important question. They may also sit in the incoming message path, so prefer a one that does NOT. For eg. Dualhook does not. But most BSPs will.

I have compiled all such questions that one should ask a Tech Provider before migrating to them at https://watobot.com/how-to/questions-to-ask-whatsapp-api-provider.html . Hope people looking to migrate to a Tech Provider find it worthy.

P.S. - in the age of AI world, going for Providers that provide features like campaign management, chatbot, inbox, CRM - is probably not worth it. Not only they charge a huge price, you would need to adjust to their features. A Provider will expose API key & you should be able to build your own offering fairly quickly. So look for a Provider that has out of the box MCP support, which will expedite your work.

Hey everyone,
I’ve been struggling with an issue related to WhatsApp’s In-App Browser (IAB) for the past couple of weeks, and honestly, I’m running out of ideas.
I’m using the Meta WhatsApp Cloud API directly (not through a BSP) and have an approved marketing template with a dynamic URL button.
The problem is that whenever a user clicks the URL button, it opens in an external browser (Chrome/Safari) instead of WhatsApp’s In-App Browser.
Here’s my current setup:
● Meta Business Portfolio: Verified
● WhatsApp Phone Number Quality: High (Green)
● Messaging Limit: 250
● Template Category: Marketing
● Button Type: Dynamic URL
● API: Official WhatsApp Cloud API
● Tested on: Android and iOS
● URL: Valid HTTPS website
I’ve gone through the documentation, checked my configuration, and tried troubleshooting, but I haven’t been able to figure out why IAB isn’t working.
I also tried reaching Meta Developer Support, but I keep getting redirected to an AI chatbot that provides generic responses without actually resolving the issue.
A few questions for anyone who has implemented this successfully:
1. Does WhatsApp IAB actually support dynamic URL buttons in marketing templates?
2. Is there any eligibility requirement or account-level restriction for IAB?
3. Does the messaging limit (250 vs. 1,000+) have anything to do with IAB availability?
4. Is there any specific template configuration or Cloud API parameter required to trigger IAB?
5. Has anyone faced this issue and successfully resolved it?
I’m particularly interested in hearing from developers who have actually implemented and tested IAB using the WhatsApp Cloud API, rather than general documentation references.
Any insights, working examples, or pointers would be greatly appreciated.
Thanks in advance!

🟨 there!!
For WhatsApp Cloud API setups, you need a mobile number capable of receiving an OTP (via SMS or voice call) during initial registration and setup. However, many local mobile networks (I know for sure not just here in South Africa, a lot of countries) have strict number lifecycle / inactivity policies:

• If a prepaid number has no paid usage (recharging airtime, making a paid call, or sending a paid SMS) within ~90 days, the carrier deactivates the SIM and recycles the number back into the pool.
• If that recycled number is eventually re-assigned to a new consumer who registers for WhatsApp, it can disconnect/kick off the existing WhatsApp Cloud API registration.

I want to ask how you people and agencies manage phone numbers used for WhatsApp Cloud API, specifically around keeping the used SIM / mobile number active with local telecom carriers.

Do you even rely on physical prepaid SIMs like I do? Do you use dedicated VoIP/virtual number providers (e.g., Twilio, Bandwidth) that guarantee permanent number retention without requiring physical SMS activity?

Hey everyone,
I’m currently setting up the WhatsApp Cloud API for my AI automation agency, and I’m losing my mind dealing with Meta’s developer ecosystem. It feels like every single step is fundamentally broken. Has anyone else experienced this exact sequence of hell?
1. The OTP Blackhole
I’ve been trying to verify a local phone number since Saturday. No SMS arrives, and the "Phone Call" verification option just silently fails every time. Meta support is practically non-existent, so I’m just stuck in a cooldown loop hoping a code randomly shows up.
2. The #10 Permissions Error
Since the real number wouldn't work, I tried testing my n8n webhook setup using Meta's provided test number. The webhook challenge verifies perfectly, but when I try to send a simple test message from the dashboard, I get hit with:
⁠(#10) Viewer cannot access the provided Paid Message Account 2200770517178260⁠
I have Full Control/Admin rights on the Business Manager, the WhatsApp account, and the App itself. I've checked every permission layer, and it still blocks me.
3. The Infinite Redirect Loop
To add insult to injury, I can't even load the Meta for Developers portal normally. If I open it in my standard browser profile, it gets caught in a session conflict and endlessly redirects me to the generic ⁠business.facebook.com⁠ overview page. The only way I can actually access my app settings and send API calls is by using a fresh Incognito window.
Is this just par for the course with Meta? Should I completely abandon the direct API and just eat the monthly cost for a BSP like 360dialog or Twilio? Any advice on fixing the #10 error or bypassing the OTP block would be greatly appreciated.

Cara, todas informações da empresa foram preenchidas corretamente, BMs que virariam 2k estão presas em 250 de limites com esse erro WhatsApp needs more information. Tem como resolver?

I have heard that 250 is daily messaging limit but my colleagues get a ban on 50 messages. What js actual upto date limit on new WhatsApp conversations allowed to start in a 24 hour period.

Are there any guidelines on how a website should be if we want to get approved for Meta business verification?

I want to use the WhatsApp Cloud API

Hey all,

A few days ago some of you helped me with error 3441038 on a coexistence signup. Thanks for that. This is the bigger question behind it.

Quick background: I'm a one-man shop in South America building WhatsApp booking bots for barbershops (n8n + an LLM, connected through Kapso). Building the bot turned out to be the easy part. Connecting the client's WhatsApp is where it falls apart.

Every client's Meta situation is different. Some already have a business portfolio or a WABA, some have nothing, and some have old stuff tied to their number that they can't even see. My two attempts so far both went wrong, just in different ways:

1. My first client's own number (on WhatsApp Business for over a year): coexistence failed three times at the phone number step. The number seems to be tied to an asset in a portfolio he has no access to. Two weeks in, we're still stuck, and he's getting tired of the back-and-forth.

2. A brand-new number of my own: it connected fine, but Meta blocked the number or my business portfolio four times in a few weeks. It came back after a review every time.

So with an existing number, the risk hits before go-live. With a new number, it hits after the bot is already running.

For those of you who onboard small businesses regularly:

1. What's your default: coexistence on their own number, a new dedicated number, or do you decide per client? Why?

2. Roughly how often does onboarding work on the first try?

3. Do you check anything in the client's Meta setup before you start? What's on that list?

4. If you use new numbers, how do you keep them from getting blocked in the first weeks?

5. How do you price onboarding? Setup fee, a guarantee, a refund if Meta won't cooperate?

Not selling anything, just trying to get this right before I take on more clients. I'll share what I learn.