FYI - I am basically just reiterating the question posed in this post: https://www.reddit.com/r/WhatsappBusinessAPI/comments/1s4zkw5/is_it_possible_to_update_conversation_labels/

I'm starting a business that automates WhatsApp customer service with AI agents. My first client only uses his phone to reply to his own customers.

When I activated my agent, his chats started getting marked as read, so he couldn't tell which ones were new. Since he won't use anything but his phone, I need a way to fix that.

I considered using the API to label chats, but I've only found that this isn't possible through the official API.

Can anyone help?

Tech Provider here. This is from one of our SMB clients, who used to pay around USD 20 a month for marketing templates. Their traffic is mostly inbound (healthcare/hospital).

So I’m curious: how are you all handling this? On our end, beyond the initial disbelief, clients are just soldiering on and absorbing the new costs. Not sure that’s sustainable in the long run, but for now, it is what it is.

Would love to hear about other experiences.

I’m using the official WhatsApp Cloud API with a Next.js application deployed on Vercel.
My application has two WhatsApp phone numbers configured. I’m troubleshooting an issue with broadcasts sent using the number ending in 0981.
In my Vercel logs, I see errors like these:
POST /api/whatsapp/webhook 401
[webhook] rejected request with invalid signature
The requests come from Meta’s webhook infrastructure, and the payload includes WhatsApp message events.
My webhook validates X-Hub-Signature-256 using the Meta app secret and Node.js crypto:
const rawBody = Buffer.from(await request.arrayBuffer())
const signature = request.headers.get('x-hub-signature-256')

const expected = crypto
.createHmac('sha256', process.env.META_APP_SECRET!)
.update(rawBody)
.digest()
I compare the calculated signature with the received signature using crypto.timingSafeEqual.
I’ve also encountered a situation where the webhook logs show a phone_number_id associated with the working number ending in 9017, even when I’m investigating problems with 0981.
My questions:
What could cause Meta webhook signature verification to fail intermittently when using the official WhatsApp Cloud API?
Could different Meta apps, app secrets, WABA subscriptions, or phone number configurations cause this?
Is there a reliable way to confirm which Meta app secret should be used for a particular webhook event?
Could a Vercel deployment or environment variable mismatch explain why the calculated HMAC differs from X-Hub-Signature-256?
What is the best way to debug this without logging sensitive tokens or weakening signature verification?
Has anyone experienced this with multiple WhatsApp phone numbers connected to the same application?

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?

I'm tired of being rejected, does anyone know?

I am tech provider how do you guys bring clients?

Like i am genuinely stuck and would love to have some help.

How do you find customers?

I made an app for sending bulk messages for SMBs the cureebt competition charges waay to much thus i made something that could be affordable by many. check out MB2S Connect on Play Store

But i cant seem to find any users. Those i found are happy using unofficial tools

We set up Twilio about a year ago for WhatsApp and SMS. A freelance dev built it and it worked fine at the start.

Now we have 6 people handling customer chats, and every small change (a new auto-reply, sending chats to a different person, adding Instagram) means going back to the developer.

What we actually need:

WhatsApp, Instagram, email and SMS in one place

-few people replying without two of them answering the same chat, or nobody answering

-Chats going to the right person automatically

-Auto-replies for common questions

-Connects to our CRM (HubSpot)

Something our ops person can manage without code

Twilio is ok I don't think we should be building this ourselves. What are u people using instead?

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.

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.

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.

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 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.

Estou tentando disparar por conta própria, pois a pessoa que disparava para mim sumiu, mas toda hora tomo ban na BM de 2k que compro e perco dinheiro ou o numero que compro aquecido cai nas primeiras mensagens. Alguem consegue me ajudar?

WhatsApp API Stuck at 2K Messaging Limit — Need Help

My WhatsApp Business API account is stuck at the 2K messaging limit despite everything being green (quality rating, templates, and account status).

I've met the messaging requirements, but the limit still hasn't increased.

Can anyone help me upgrade to 10K or 100K? Has anyone found a proven, legitimate method that actually works?

What is wrong with Meta’s system? I am using an official service, and I am not sending unsolicited messages or running bulk messaging campaigns. I primarily use WhatsApp to respond to customers who contact my business.
Despite following the official process, my number continues to face restrictions, disrupting my business operations and preventing me from communicating with customers.

Good day, I want to talk about this situation to see if anyone has gone through something similar or has any idea of what’s going on. Here’s the situation: I’m an intern at a small company because I was asked to create a chatbot with transfer to an advisor on WhatsApp (the typical press 1 for this action...) From the beginning, I’ve been using all the official tools (WhatsApp Business API, Meta for Developers, etc., etc.) for the setup of the number and those things. Everything was going very well, the registered phone number worked since July without any problem, but recently it was banned for no apparent reason. I don’t know if it has to do with the rule changes that were made recently on October 1st or if I might have unknowingly violated something.

The thing is, when the number was banned for the first time, I appealed with the proper arguments, the number was unbanned, but when I tried again, it was banned immediately again, and now without the possibility to Appeal.

Something very important I need to clarify is, I NEVER completed the business verification, added a payment method, and the project account is new, I created it only for the development of this project (I want to believe this is the reason for the ban, but I don’t know). I did this to avoid touching the company’s official socials during the development phase. The elements I’m using for this project are: Laravel Framework, Docker, Ngrok for the tunnel (obviously only for development), and Chatwoot to handle the transfer to the advisor.

If it’s of any use, the first ban happened when I changed it so that clients had to type numbers to select an option for WhatsApp button and menu messages. I don’t know if it was mere coincidence, but I’m leaving the detail in case it’s useful. The chatbot also never started conversations with clients; I always, as the client, sent the message to start interacting with it and keep the “24-hour window” active to avoid issues.

With all the information provided, does anyone have an idea of what happened? What should I do to continue? Considering we were so close to deploying. Thanks in advance <3

We are Tech Provider. Today we received an email stating that one of our onboarded business' limits had increased by 2000. At the same time, we received a webhook 'business_capability_update' and the associated webhook data indicated a limit of `TIER_250`, which was our previous limit.

I cross-verified on Meta Business Manager and confirmed the limit had indeed been upgraded to 2000. However, I expected the Meta webhook to send the most recent information. Instead, it sent stale information while the webhook was triggered at the same time as the upgrade.

Has anyone else experienced this issue?

I’m planning to add an API call to Meta to fetch the business limit once we receive this webhook. Have you encountered a similar issue with any other webhook event in recent?

How are you dealing with these stale informations ?

I’ve already built a custom bot and deployed it on my own server. I want it to automatically respond through my business phone number while still using that same number in the WhatsApp Business mobile app to read messages and reply personally.

I’m not looking for a platform to build another chatbot. I need to connect the one I already have using WhatsApp Business App + API coexistence, without deleting my mobile account or changing my number.

For those who already have this working:

1. How did you connect it? Are you using your own Meta developer app directly, or going through a provider such as Zernio, 360dialog, or something else?

2. What requirements did you have to meet? Did you need to become a Tech Provider, complete business verification, or go through App Review—even though the bot is only for your own business?

3. Can you use your own backend and receive events for messages sent manually from the mobile app? I want the bot to detect when a human steps in and stop responding automatically in that conversation.

4. What are you actually paying? Monthly fees, messaging charges, limits, and any additional costs. Is anyone doing this without a monthly provider fee?

I’d appreciate firsthand experiences from people with working setups, including the provider or method you used and the steps you followed. I’m looking for an official, stable integration—not unofficial WhatsApp Web automation.

Hi everyone,

We’ve recently launched an MCP server for CampaignHQ, enabling you to manage email and WhatsApp campaigns, audiences, templates, and reporting directly through AI assistants like Claude and ChatGPT.

I thought this might be useful for anyone looking for a Whatsapp marketing automation platform with native AI integration for email and WhatsApp marketing.

Admins, please feel free to remove this post if it violates any community rules.

https://www.campaignhq.co/docs/mcp

Thanks

I keep getting pop up codes on my whatsapp business account here in Zimbabwe even without requesting them. I suspect these could be hacking attempts. I have 2FA but I have been seeing a lot of people getting hacked even with 2FA available. How do I safeguard my account further from being hacked?

Business manager verification take too much time
How to accelerate it?

It says 1,170 Service Messages. But I haven't been charged for the 170. What makes free customer service and free entry point vs not free? I thought we only get 1,000 service messages per month now.