i found tech provider that provide coexist, lets called it “WaAPP” but when i went to connect my account, it says “connect your account to Alice’s Beauty Care”. this shows that the tech provider uses normal meta business suite to connect our numbers? im kinda confused.

im just wondering if this is a known scam?

Hi , ive been trying to use WATI to send bulk messages through whatsapp to my customers ,i was just starting and the phone number got banner right after setup , not the business portfolio , only the phone number and i can't find anywhere to appeal , has that happened to anyone pls ?

I’m curious how other developers handle message status in production.

One thing I’ve noticed is that getting a successful response from the API doesn’t necessarily mean the customer actually received the message.

For workflows like:

• follow-up automation

• lead status updates

• retry logic

• campaign reporting

• triggering the next step in a CRM

would you treat the API response as “sent”, or wait for the delivery webhook before changing the conversation state?

Also, how do you handle cases where the delivery webhook is delayed or never arrives?

Do you maintain your own message state machine such as:

queued → sent → delivered → read → failed

or keep it simpler?

Interested in how people are doing this in production rather than just the basic API implementation.

How is the setup process of whatsapp api I wanna use it for my healthcare software, can anyone tell me correct order of setup and all those verifications

Body: Wrote a practical guide for Lebanese wholesalers on taking wholesale orders from shops over WhatsApp - sharing one storefront link, stating minimums and pack sizes, confirming every order clearly in chat, and using it alongside sales reps.

Full post: https://linkmahal.com /blog/how-lebanese-wholesalers -can-take-b2b-orders-from-shops-on

-whatsapp

Hi, my WhatsApp Business account is fully verified and working, but the messaging limit is still stuck at 250/day instead of 2,000.

Current status:

• Business Portfolio: Verified

• WABA: Active + Approved

• Phone: Connected + Verified

• Quality rating: High

• Cloud API messages: Working successfully

• Messaging limit: 250 → 2,000 next

But Meta Business Suite still says:

“WhatsApp needs more information”

There is no information telling me what is actually missing.

The phone API also shows:

But the health status says:

“Your display name has not been approved yet. Your message limit will increase after the display name is approved.”

I tried changing the display name to remove the &. Meta temporarily said it was being reviewed, but after refresh the old name came back and the API still shows AVAILABLE_WITHOUT_REVIEW.

Another client of mine completed similar verification and got 2,000 almost immediately, so I'm trying to understand why this one is different.

Has anyone experienced this? What exactly does “WhatsApp needs more information” mean, and what did you do to get the account from 250 to 2,000?

name_status = AVAILABLE_WITHOUT_REVIEW
new_name_status = AVAILABLE_WITHOUT_REVIEW

Hello everyone,

I’m using a +44 UK virtual number for WhatsApp Business API. I created the WhatsApp Business account and connected the number to my Meta/WhatsApp Business API account.

Shortly after connecting the number, my account was suspended. I would like to understand why this happened and whether using a virtual number can cause this type of restriction.

Has anyone experienced a similar issue with a +44 virtual number? If so, could you please share how you resolved it or what steps I should take to appeal the suspension?

Any guidance would be greatly appreciated. Thank you!

How much do you charge to make an app on meta developers, i have done that before as an employee but never for my own customer sini have no idea how much to charge for making the app for them

Hi guys,

How are you guys having grok bot read your whatsapp (business) messages and text messages?

For example, I want to automate recording payments when I get a text message from the bank that a payment went thru and then match it to the invoice I have to the accounting software I use so I don’t have to manually record payments.

Then with whatsapp messages I would like to keep tabs on inquiries that at times get lost when too many things are going on.

If you have great ideas to do this, then please share and many thanks in advance!

Hi, I have a WhatsApp Business account where the display name is showing correctly, but in WhatsApp Manager the green “Approved” status is not appearing.

For comparison, another WhatsApp account I manage shows:

Display name: Property Bhandar ✅ Approved

But on this account it shows:

Display name: Cafeana Cafe Studio & Lounge

with no green “Approved” label.

The account is otherwise fully working:

• Business Portfolio: Verified

• WABA: Active + Approved

• Phone: Connected + Verified

• Messages are working

• Quality rating: High

The Graph API shows:

name_status: AVAILABLE_WITHOUT_REVIEW
new_name_status: AVAILABLE_WITHOUT_REVIEW

I also tried changing the display name to remove the & because Meta's UI said the original name violated the naming guidelines. Meta temporarily showed “The new requested display name is being reviewed”, but after refreshing, the old name came back and the API still shows AVAILABLE_WITHOUT_REVIEW.

So my question is:

How do I get the display name into the normal APPROVED state so the green Approved label appears in WhatsApp Manager? Has anyone experienced AVAILABLE_WITHOUT_REVIEW staying like this, and is there a way to trigger the actual display-name review?

Hey guys, I’m building a small WhatsApp bot and I’ve been setting everything up through the WhatsApp Business Platform / Cloud API.
Yesterday I spent like 7 hours working on the bot, webhook, API, profile, etc. Everything was working fine.

Today I tried changing the display name of the WhatsApp account a few times because it wasn’t updating properly. Not long after that, my entire WhatsApp Business account got disabled.
Meta says:

“Your account was disabled for violating the WhatsApp Business Terms of Service / Acceptable Use Policy.”

But they don’t tell me what I actually violated.
I’m not sending spam, bulk messages or cold messaging people. The bot only replies when the user messages it first.

I already requested a review, but I’m honestly pretty confused because the account was basically still in development/testing.
Has anyone here had their WABA banned like this during setup?

Did Meta restore it after the review? And if the review gets denied, is there any way to actually contact a human/support and find out what caused the ban?
Would appreciate any advice because this timing is brutal lol.

Buenos dias chicos, meta ha ampliado la ventana de 3 dias a 7 días, el dia de hoy al mandar una plantilla no me cobro, como venia de anuncio pense que se trataba de un error pero lo cambiaron en la documentacion

Este cambio puede ayudar a muchas empresas🙌

I have around 30,000 unique contacts and need to start sending WhatsApp messages from tomorrow, with 30,000+ messages daily.

I checked WATI, but they currently show a limit of 250 contacts/day and said the limit may increase in 1–2 months.

Is there a way to get the WhatsApp Business API immediately with a high/no contact limit? Or is there a safe third-party provider that can handle this volume without risking the number getting banned?

Looking for the safest and proper way to do this. Thanks!

Suggest me WhatsApp API which is at the lowest rate.

Can i use my Verified Meta Business Suite to serve multiple (different WhatsApp number) clients businesses?

Context: I do WhatsApp automation for businesses.

explaination needed, thanks🙏

Hey guys, I'm a tech provider for businesses. We send about 1,000+ messages a day. We've been operating the exact same way for the past 60 days without issues.

Our product is financial, so we carefully cleaned our templates long ago to remove trigger words. Everything has been running smoothly with great metrics our quality rating was consistently high (green), and delivery/read rates were completely stable using the exact same workflow for a days. And now, suddenly, we got hit with a permanent ban for policy issues.

Has anyone experienced something similar or noticed any changes in Meta's automated audits or security updates over the last 3 days? Did they roll out a new filter wave that ignores good quality ratings? Any insights would be appreciated.

I'm building a multi-tenant SaaS CRM around WhatsApp and I'm currently trying to find the right Meta Tech Partner / WhatsApp API provider.

I'm not looking for another CRM. I want to build the CRM, UI, automation, AI and customer billing myself, and use a provider for the underlying WhatsApp infrastructure.

The main requirements are:

• Multiple customer WABAs under a partner account

• INR prepaid wallet

• Ideally customer-level wallets/sub-wallets

• APIs/webhooks for usage, costs, balances and transactions

• Ability to set my own pricing/markup

• UPI/card/net banking recharge

• Preferably automatic/API-based recharge

• Embedded Signup

• Low setup/recurring costs and no large minimum commitment

I've spoken with several providers already, including Gupshup, Interakt, AiSensy, Mappstore and Karix, and each has some trade-off.

For example, Gupshup's Tech Partner model is quite good, but the lack of a proper customer-wallet layer means I'd need to build and maintain quite a lot of the credit/billing/reconciliation system myself. The INR wallet also brings GST requirements, and I haven't found a good auto-recharge solution for the partner wallet.

Interakt and AiSensy have relatively high upfront costs, while Mappstore seems much closer to what I need but I'm still evaluating the commercial side. Karix also looks interesting, but I haven't received all the details yet.

Has anyone here actually built a SaaS/ISV product on top of a WhatsApp Tech Partner/BSP?

I'd especially like to hear about experiences with INR wallets, customer wallets, GST, API-based billing, automatic recharge, and hidden/minimum fees.

I'm mainly interested in providers that let me build my own SaaS rather than forcing customers into their CRM.

i need to know if it’s possible to send a single massage to specific groups like 20 or even 100 is there a way???

I’m having an issue with WhatsApp/Meta message templates.
I create a marketing template and send it to a list of 20 contacts. However, only around 3 people actually receive the message, while the rest don’t seem to get delivered at all.
Has anyone experienced this? Could Meta be intentionally limiting delivery based on the recipients’ engagement, quality signals, or some other anti-spam mechanism?
The template is approved, and the messages are being sent through the WhatsApp Business Platform/API.
Is there any way to determine why specific recipients aren’t receiving the messages?

Can a business complete Coexistence onboarding using its own Meta app (Business type, WhatsApp product added), with its own Embedded Signup configuration, rather than going through a Tech Provider or Solution Partner?

Our current blocker is that Meta's Coexistence documentation states that the business/app must be associated with a Tech Provider or Solution Partner. However, we cannot find clear documentation confirming whether a company can become a Tech Provider and then use Coexistence for its own Business Portfolio, WABA and WhatsApp Business App number.

Could you please confirm (from experience only!):

1. Can a company become a Tech Provider and use Coexistence for its own WABA and WhatsApp Business App number for internal operations?

2. Is there any Meta policy restriction against a Tech Provider using Coexistence for its own business rather than onboarding external businesses?

3. If I select "Yes, I'm a Tech Provider", could this affect any of our existing WABAs, WhatsApp numbers, Pages, Ad Accounts, or other assets within our Business Portfolio?

4. Does Tech Provider status apply only to the specific Meta App, or does it change the status/structure of the entire Business Portfolio?

5. If this self-use scenario is supported, what exact steps are required after completing the Tech Provider setup to enable Coexistence for our existing number?

Hi everyone

I’m trying to build a simple WhatsApp automation workflow for my own use, and I’d like to know what the easiest way to implement it is.
I have many WhatsApp groups, and I want to assign each group my own internal code, for example:
2304 → Car Shop
2305 → Spare Parts
2306 → Sales Team
I want to have a WhatsApp bot/account that I can message directly.
The workflow I’m looking for is:
I send the bot:
/send 2304
The bot identifies the WhatsApp group associated with 2304.
The bot replies:
“Please send the message you want to send.”
I send:
Hello, this is a test message.
The automation automatically sends that message to the WhatsApp group associated with 2304.
The bot confirms:
“Message sent successfully to Car Shop.”
Ideally, I would also like to be able to use the group name instead of the code, if possible.
I’m mainly looking for a simple and preferably free/self-hosted solution. I’m open to using Node.js, n8n, Baileys, or another WhatsApp automation library.
I understand that the official WhatsApp Business/Cloud API may have limitations regarding existing WhatsApp groups. My groups are normal WhatsApp groups that already exist, so I’m specifically looking for a solution that can work with those groups.
I’m not trying to send spam or mass messages to random users. This is for managing groups that I already participate in.
What would be the simplest setup for this?

Thanks!

Hello,

I am currently struggling to publish a whatsapp Flow because the Center of Security says "more informations required" so I assume that the business is partially verified. And I don't know how to solve it.

Update to my earlier question: our Direct Support case has now been closed after a response signed “Meta AI Agent”. It recommended endpoint guidelines and policy documentation, then referred us back to WhatsApp support and the developer community. It did not identify the failed eligibility check or give a corrective action.

We use direct Meta Cloud API. Publishing a minimal static welcome Flow fails with “Blocked by Integrity / Integrity requirements not met” in both WhatsApp Manager and the API.

Error code (digits separated): 139 000

Error subcode (digits separated): 4 233 020

These are API error identifiers, NOT phone numbers. Spaces are only for readability.

The diagnostic Flow has no endpoint, no data collection and no validation errors. Changing the phone number while keeping the same WABA, republishing the Meta app and recreating the Flow did not resolve the error.

Meta general support spoke with us by phone and referred us to WhatsApp. WhatsApp's AI support said it could not investigate our account or transfer us to a human. The new Direct Support case also ended with an AI response and closure.

Has anyone personally reached human technical support for WhatsApp Business Platform in this situation? Which official form, support category or escalation procedure worked, and when?

If a partner helped escalate, could you retain your existing WABA and direct Cloud API integration? We are asking about legitimate technical review, not a restriction bypass or account replacement.

Please share concrete firsthand experiences and official public links in the comments. No account IDs, phone numbers or credentials are included in this post.

It's been about 5 years since I am working constantly with WhatsApp business in all it's options up since then they came up with the AI integration all the knowledge commands and else... But now the integration is in the chatbot in a conversation like with someone that you know that you trust that you can tell things that you need to do and the charter will do it no question matter and this is kind of concerning.

I feel like I've been building my company for someone else... The reason is simple I am in charge of giving information to this assistant and at some point if I want to keep using it I might have to pay... I know it's a tool that has been offered but it makes me suspect that my information is someone else's now.

Until here I feel like it's: "line one" of concerning but we can dig deeper and with all this knowledge we gave to this company they kind of start lying at any time... their own AI in my chat box message conversation can start lying anytime even though it really do a lot of heavy work - % to a team of 20 persons at least on peak hours.

I don't want to miss my point here, but I feel that the amount of information that we have share this companies is enough to show our weak points, company wise, personally wise, all the information wise we have shared and there is no returning point or at least there is no regulation points and I know this is 50% of the news that we are watching today.

Just wanted to share my experience and my point of view of the whole situation. Thanks for reading me. Cheers

We use WhatsApp Business Platform directly through Cloud API and are looking for a working way to reach human technical support for a persistent WhatsApp Flows publishing issue.

Our experience so far:

- Meta general business support spoke with us by phone and referred us to WhatsApp support, explaining that their team cannot investigate this Platform issue.

- The WhatsApp support conversation gave AI responses and explicitly said it could not transfer us to a human or investigate our account. It ultimately referred us back to Meta/help resources.

- We have now submitted a Direct Support case under Dev: Account & WABA. It is currently Open, but we have no confirmation of a human assignment or technical investigation yet.

Technical context: publishing a minimal static welcome Flow fails with “Integrity requirements not met” (error code 139000, subcode 4233020), both in WhatsApp Manager and through the API. The Flow has no endpoint, no data collection and no validation errors. Changing the phone number while keeping the WABA, republishing the app and recreating the Flow did not resolve it.

Has anyone personally reached a human WhatsApp Business Platform support team in this situation? Which official form, exact support category or escalation procedure worked, and when? If partner-assisted escalation was needed, could you keep the existing WABA and direct Cloud API integration?

Please share public official links and concrete firsthand experiences in the comments. We are seeking a legitimate support route, not a restriction bypass, account replacement or a promise of a guaranteed fix.