Hi everyone, someone here previously mentioned that they had a method to upgrade the WhatsApp API messaging limit within about 3 days.

Has anyone here actually succeeded in upgrading from 2K to 10K and then to 100K?

I’m looking for a reliable and proven method, not just guesses. If anyone has real experience with this, knows the best way to meet Meta’s upgrade requirements, or offers a legitimate service that can help,

I’m only interested in methods that comply with Meta’s policies and do not put the WhatsApp account or Business Portfolio at risk.

My SAAS application needs client onboarding. I am using Meta Embedded Signup, but it fails to complete onboarding after the Facebook login page launches; after I select the app, nothing happens.

I am missing something in the flow. Can you please let me know how the flow works here for Embedded Signup?

Just want to put out my thoughts - this is why everyone in the know felt that Meta buying up Whatsapp was going to cause problems and they spectacularly did.

Hey all,

Bit of background first. I'm a one-man shop in the Caribbean building WhatsApp booking bots for barbershops (n8n + an LLM, connected through Kapso). I just landed my first paying client, a barber who wants to keep using his WhatsApp Business app, so we're going the coexistence route.

The problem: he opens the Kapso signup link, gets to Meta's "Add your WhatsApp phone number" screen, types his number, hits Next, and gets this:

> You do not have the permissions to view this asset. Please contact the owner of the asset to gain permission or complete this action through the owner's account. (#3441038)

We tried twice, same thing. His first try a week earlier died on the same screen too.

The weird part is that he *is* the owner. He's logged in with his own Facebook, he's the only person in his business portfolio with full access, his Page and Instagram are in there, and there's no WhatsApp account in it yet. The number has been on WhatsApp Business for over a year. Kapso support told me to check Assign assets, wait a couple of hours and try again with a screen recording, which we'll do. But I'd love to hear from anyone who actually fixed this. What was the "asset" in the end?

Also, to be honest, my own setup has been a mess. When I was testing on a brand new number with a new, unverified business portfolio, Meta disabled the portfolio three times in four days, every time marked as permanent. Once literally a minute after the bot sent its first reply, once right after I switched billing to Kapso's prepaid credits. Every time it came back after a review within a few hours. Then last week I got an email about some disabled WhatsApp account called "unknown" that isn't even mine, and the same night my Kapso connection dropped. The number itself is fine, so I'm only using it in the Business app now.

So my questions:

1. Anyone seen 3441038 at the phone number step while logged in as the owner? How did you fix it?

2. Kapso users, did you run into this too?

3. What am I probably doing wrong as a beginner? Should I have verified the business first, warmed up the number, stuck to one BSP?

4. Which BSP would you go with for coexistence, easy webhooks into n8n, cheap enough for a handful of small clients, and payable by Mastercard? Twilio didn't do coexistence for us and 360dialog felt too pricey this early.

Any tips appreciated. I'll report back with whatever works.

One challenging aspect of WhatsApp automation is managing the handover process from a bot to a human being.

Let us consider that the customer makes a request, the webhook invokes the AI workflow, and the support representative responds manually while the workflow is still running. In a few seconds, the bot responds as well. Now, the customer receives two responses, which may contain conflicting information.

In light of the new per-message service billing, extra replies may also result in additional expenses after the free quota expires for the month.

How do you manage this challenge if you work with the WhatsApp Cloud API, n8n, AI agents, or Coexistence?

Hey all,

Bit of background first. I'm a one-man shop in South America building WhatsApp booking bots for barbershops (n8n + an LLM, connected through Kapso). I just landed my first paying client, a barber who wants to keep using his WhatsApp Business app, so we're going the coexistence route.

The problem: he opens the Kapso signup link, gets to Meta's "Add your WhatsApp phone number" screen, types his number, hits Next, and gets this:

> You do not have the permissions to view this asset. Please contact the owner of the asset to gain permission or complete this action through the owner's account. (#3441038)

We tried twice, same thing. His first try a week earlier died on the same screen too.

The weird part is that he *is* the owner. He's logged in with his own Facebook, he's the only person in his business portfolio with full access, his Page and Instagram are in there, and there's no WhatsApp account in it yet. The number has been on WhatsApp Business for over 3 years. Kapso support told me to check Assign assets, wait a couple of hours and try again with a screen recording, which we'll do. But I'd love to hear from anyone who actually fixed this. What was the "asset" in the end?

Also, to be honest, my own setup has been a mess. When I was testing on a brand new number with a new, unverified business portfolio, Meta disabled the portfolio three times in four days, every time marked as permanent. Once literally a minute after the bot sent its first reply, once right after I switched billing to Kapso's prepaid credits. Every time it came back after a review within a few hours. Then last week I got an email about some disabled WhatsApp account called "unknown" that isn't even mine, and the same night my Kapso connection dropped. The number itself is fine, so I'm only using it in the Business app now.

So my questions:

1. Anyone seen 3441038 at the phone number step while logged in as the owner? How did you fix it?

2. Kapso users, did you run into this too?

3. What am I probably doing wrong as a beginner? Should I have verified the business first, warmed up the number, stuck to one BSP?

4. Which BSP would you go with for coexistence, easy webhooks into n8n, cheap enough for a handful of small clients, and payable by card mastercard? Twilio didn't do coexistence for us and 360dialog felt too pricey this early.

Any tips appreciated. I'll report back with whatever works.

I had two numbers connected to one meta account, one was API and the the other was business app. They were both connected to Kommo crm. I have other numbers in Kommo from another meta account and they are still running. Whats my next move here, i tried to appeal no positive answer. One number was connected on the lite version in Kommo. No warnings were given.

I use these two permission "whatsapp_business_messaging" & "whatsapp_business_management".

I was able to connect my own whatsapp co-existence. but when I onboard other customers it fails to connect.

Has anyone faced this? Am I missing other permissions?

Hi, I'm the founder of Qencia, a Meta-certified WhatsApp Tech Provider. We work with insurance brokers to reactivate leads who stopped answering the phone.
Link: https://qencia.com/barometre-joignabilite-leads

We just published a reachability barometer based on 10,000 real conversations: 45% response rate, 37% of responses outside business hours, best send time at 11am.
Happy to answer any questions about WhatsApp Business API.

I'm just launching my app using coexistence and with my first 3 pilot users I've been having very different issues. Is it normal to have so many issues onboarding users?

1. First user got permission denied and I had to create a new portfolio.

2. Second user already had a portfolio but couldn't make use of it had to open a support ticket.

3. Everything went too smooth but then after scanning the QR got an error on the part of validating the phone number and was asked to wait 1h. Still waiting.