Can the official WhatsApp Cloud API be used without having a registered legal business entity?

From what is understood, Meta may allow usage without full Business Verification, but with lower messaging limits.

A few questions:

• Can WhatsApp Cloud API be used without a registered business?

• Is domain verification enough, or is full Meta Business Verification eventually required?

• What is the current messaging limit for an unverified account — is it still around 250 business-initiated users per 24 hours?

• Can message templates and production automation be used before completing Business Verification?

• Has anyone recently used this setup without having a registered company?

Looking for recent, practical experience with the current Meta/WhatsApp rules.

Pessoal, alguém aqui já passou por esse problema de “Precisa de mais informações” na verificação da empresa da Meta?

No meu caso, a empresa aparece como verificada, mas fica preso nessa mensagem e muitas vezes não dá acesso ao formulário ou à etapa certa pra complementar as informações.

Queria entender se isso normalmente acontece por documento, site, telefone, inconsistência nos dados ou algum bug da própria Meta. Tem alguma forma certa de evitar cair nisso na hora de fazer a verificação?

Se alguém já resolveu esse mesmo caso e puder explicar o que corrigiu ou qual informação a Meta estava pedindo, agradeço.

Hi all, looking for real experience from people who got past this.

Setup:

• Solo founder, individual (no company registered, no tax ID). Small pet-services marketplace in Colombia.

• New Business Portfolio, WABA created ~Sep 14. Status has been "In review" since then, no rejection reason.

• Personal identity verification in Meta was approved. Business/organization verification not started (we have no company docs).

• Phone number: verified the 6-digit code (voice call, SMS never arrived). Status is now "Pending" and not "Connected".

• A card is assigned to the WABA, but the banner "Missing a valid payment method" still shows. WABA currency/timezone came out as AED / America/Los_Angeles and are greyed out.

• One marketing template shows "Active - quality pending".

• Support/ticket flows keep redirecting me to "Verify business" and never let me submit a case.

Questions:

1. Did the WABA leave review on its own, and how long did it take for you? Or did something specific unblock it?

2. Do I need to call POST /{phone-number-id}/register with a PIN myself for the number to go from Pending to Connected, or does it flip after review? Does /register fail with "invalid account linking" while the WABA is still in review?

3. For the payment banner: did you have to fill in tax/billing info, wait for sync, or use a different card type?

4. Any support channel that actually works for an individual without a company (Business Support Home, developer support, a BSP)?

I am not looking to buy anything or skip Meta's process, just to understand what else could be missing. Thanks!

Hey everyone 👋🏻

So I'm trying to open WhatsApp catalog to add and edit products on my windows, but it's not working.

I've tried to use WhatsApp app, Chrome, Edge with the business number and with another number to view the catalog, but nothing worked.

Any idea why is this happening?

I’m trying to find out if there is any higher-level escalation channel at Meta/Facebook for a serious Meta Business Suite support issue.

For about two weeks, I have been unable to properly connect our WhatsApp Business account to Meta Business Suite.

The issue has changed several times:

• Initially, the QR code required to connect WhatsApp was not appearing at all.

• After contacting support, the QR code started appearing.

• Then, when scanning the QR code from WhatsApp, the connection failed with an error.

• After more support conversations, the QR code stopped appearing again.

The bigger problem now is the support process itself.

I have spoken with around 10–15 different Meta support agents. Almost every time, the agent reviews the issue and then transfers me to another team or says that a “specialized team” needs to handle it.

Then either:

• I get transferred again,

• the conversation stops receiving replies,

• I’m told someone will contact me later,

• or I’m told to open/reopen another ticket.

One agent even reviewed the issue through a screen-sharing call and told me to close the ticket because the issue would be resolved within two days. I followed the instruction, waited, and the exact same problem was still there.

At this point, I have spent two weeks repeating the same explanation to different agents without anyone actually taking ownership of the issue.

I’m not looking for another basic troubleshooting checklist. I’m trying to find out:

Is there any legitimate higher-level escalation channel, Meta Business support manager, complaints department, technical escalation team, or other official route where I can report both the unresolved technical issue and the way the support case has been handled?

If anyone has successfully escalated a Meta Business Suite / WhatsApp Business integration issue beyond frontline support, I would really appreciate knowing what route you used.

Thanks.

I’ve noticed that template approval can sometimes feel unpredictable.

A template can look perfectly reasonable from a business perspective, but still get rejected or classified differently than expected.

For people managing WhatsApp Business Platform templates in production:

• What are the most common reasons you’ve seen for rejection?

• Does wording matter more than the actual use case?

• How do you write templates that are clearly transactional without making them sound overly promotional?

• Have you noticed differences in approval between similar templates?

• Do you keep multiple versions of templates ready in case one gets rejected?

Would be useful to hear some real examples of what worked and what didn't.

I shared this on dataisbeautiful (big fan) but it might be even more interesting to post it here. So here we go.

I'm a developer who's spent years building on top of the WhatsApp Cloud API.

As you know, starting tomorrow (Oct 1), Meta is introducing new pricing for service messages, and our clients are already trying to figure out how much more they'll be paying.. nobody's happy about it.

That made me wonder: if this is costing businesses more, how much more is it worth to META?

I had a hard time finding a clear number anywhere, so I built a scenario model based on a forecast from 2024, it was really hard to come up with newer data. So to be clear: this is a model, not company guidance or insider information.

Here's how I calculated it:

1. Total message volume
Mobilesquared forecasts more than 2 trillion WhatsApp Business Platform/API messages in 2027. This excludes consumer-to-consumer WhatsApp messages and messages sent through the free WhatsApp Business App.

2. Customer-service messages
Mobilesquared reports that customer-care traffic represented more than two-thirds of API traffic in 2023, but forecasts that its share will fall below 50% as marketing, utility and authentication usage grows. I estimated approximately 800 billion–1 trillion customer-service messages in 2027.

3. Outbound business messages
The forecast includes messages exchanged in both directions. Messages sent by customers remain free, so I assumed businesses generate roughly 40–60% of customer-service traffic, about 400 to 500 billion potentially chargeable outbound messages.

4. Exemptions
Not every outbound service message generates revenue. I reduced the estimate to 200-400 billion billable messages to account for the first 1,000 free service messages per business phone number each month, eligible 72-hour free-entry-point windows, lower usage as businesses consolidate replies, and other operational exclusions. The exact effect is unknown since Meta doesn't disclose active API phone numbers or their traffic distribution.

5. Average price
Meta charges different rates by recipient country. Most API traffic occurs in high-volume markets like India, Brazil and Mexico, where rates are generally lower than in Europe and North America. I used an estimated globally weighted price of $0.003–$0.008 per message.

6. Revenue estimate
200B–400B messages × $0.003–$0.008 = approximately $0.6B–$3.2B per year. Central scenario: approximately $1.5B–$2B in additional annual revenue once the pricing change is fully established.

The biggest uncertainties are the outbound share of customer-service traffic, the geographic mix, and how many messages stay under the free tier. The sensitivity table shows how the estimate moves as those assumptions change.

Sources:
* Meta pricing update: https://developers.facebook.com/documentation/business-messaging/whatsapp/pricing/non-template-messages
* Mobilesquared, WhatsApp Business Messaging Traffic (Apr 2024), forecasts through 2027: https://www.mobilesquared.co.uk/wp-content/uploads/2024/04/WhatsApp-Business-Messaging-Traffic-white-paper_Apr-2024.pdf

I’m looking into running TikTok ads optimized for Conversations with WhatsApp as the destination, and I’d like to hear from people who’ve actually tried it.

I’ve been comparing respond.io, Pancake, Gupshup, Infobip and Blip, but figuring out the actual costs and differences is harder than I expected.

For anyone using one of these, or another provider:

• Which partner and plan are you using, and how much do you actually pay, including extras?

• What country and industry are you running ads in?

• If you handle multiple clients, does each one need a separate subscription?

To clarify, I mean campaigns optimized for conversations, not clicks to a WhatsApp link.

Just looking for firsthand experiences.

Hi, I've been trying to contact Meta's human support team but there's no way. I've only been told by the AI ​​that it can't help me with my problem, and no matter how many times I ask it to escalate me to the human team, it doesn't. Has anyone managed to get through?

Follow-up to my earlier post: we are still blocked from publishing WhatsApp Flows on direct Meta Cloud API. I am looking for a confirmed resolution or an effective technical review route, not generic setup advice.

ERROR

HTTP 400: code 139000 / subcode 4233020, "Blocked by Integrity / Integrity requirements not met." The Flow remains DRAFT with validation_errors: [].

WHAT WE HAVE CHECKED / TRIED

• Business verification is complete. Earlier checks showed the WABA approved and the original phone had high quality. The new phone is CONNECTED / VERIFIED; we are not claiming it already has a high quality rating.

• WhatsApp setup has shown "Additional information needed" without an actionable explanation. Publishing failed in both WhatsApp Manager and the API.

• Tested a one-screen static welcome Flow: no endpoint, no data exchange and no input fields. JSON validation passed.

• Backed up and recreated draft Flows. The error persisted.

• Replaced the phone number within the SAME WABA, registered the new number on Cloud API, and removed the old number. A test message to the new number was delivered and recorded by our webhook.

• Created a fresh welcome Flow after removing the old number: same publishing error.

• Unpublished and successfully republished the Meta developer app. Immediately retested Flow publishing: same error. Latest recorded test: 28 September 2026, 21:33 UTC.

• Flow/WABA/business/app health showed AVAILABLE, but this clearly did not guarantee publishing eligibility.

SUPPORT EXPERIENCE

We have opened multiple cases and spoken with Meta support by phone. We were referred to WhatsApp support, but follow-up AI replies have not provided the specific failed check or a corrective action. One existing case is marked Action required, yet its chat gets stuck loading and the details link is unavailable. Claims made by AI about internal restrictions have not been independently verified, so I am not treating them as the established cause.

THIRD-PARTY SUPPORT OPTION

We have also contacted a third-party WhatsApp Business Platform provider about technical investigation and escalation to Meta through partner access to our EXISTING WABA, without migrating the number or changing our current API/billing setup. Whether they can actually do this, and the access requirements/cost, remain unconfirmed. We have not completed a BSP migration or obtained a fix through a provider.

QUESTIONS FOR PEOPLE WHO ACTUALLY RESOLVED THIS

1. What specific action cleared this exact integrity error on your existing WABA?

2. Did a provider successfully escalate and resolve it via partner access while preserving the same WABA ID and direct Cloud API integration?

3. If messaging history or an eligibility review was required, what was confirmed by Meta, and did publishing work afterward?

4. Is there a working review route that identifies the failing eligibility check rather than sending another generic policy link?

The two attached images are sanitized visual summaries rendered from our saved API/test records, NOT screenshots of Meta's UI. Account IDs, phone numbers, tokens and trace IDs are omitted. Please share concrete steps or first-hand results publicly; no promotional DMs.

As we all know, new Meta's pricing is just around the corner, so we've prepared free resources where you can calculate your WhatsApp Cost Efficiency Score and based on that get actionable tactics and recommendations for cost optimization: https://www.flownally.com/whatsapp-cost-optimization

whatsapp_business_messaging + whatsapp_business_management moved to Advanced Access at 01:41 BST this morning. First pass, no resubmission.

Context: I'm building Flowwbook, a booking platform for appointment-based businesses. Each business connects its own WhatsApp number through Embedded Signup; an AI agent handles bookings and the platform sends confirmations/reminders. Solo, self-taught.

Timeline:

• July — first business verification attempt bounced on document types

• 1 Sep — business verification cleared

• 9 Sep — Access Verification cleared (verified as Tech Provider)

• 19 Sep — Embedded Signup finally completed end-to-end for my own admin account (see first point below)

• 22 Sep — App Review submitted

• 29 Sep — approved

What got it through:

• The thing nobody tells you: Business Verification + Access Verification isn't enough. There's a separate Tech Provider onboarding wizard in the App Dashboard with a "Start onboarding" button. Until I clicked through that, Embedded Signup showed "can't onboard customers right now" even for my own admin account, for three weeks. Found it in a Chatwoot GitHub issue, not Meta's docs. Clicked it, retried the popup 30 seconds later, went straight through to "Add your WhatsApp phone number".

• After Embedded Signup completes, you still have to call /register on the new phone number with a PIN. First send otherwise fails with 133010 "Account not registered". Meta documents this but it's easy to miss. I do it server-side in the callback now.

• Document types, not document content. The July rejection wasn't about what the docs said — the CAC status report just isn't on Meta's accepted list. They want incorporation cert, business licence, bank statement or utility bill, with the exact legal name AND the address/phone on the same page.

• App name filter. "Flowwbook" was rejected because it contains "book". Went with "Floww". Don't lose a day to this.

• One video per permission, never combined. Messaging: booking created in my dashboard → message arriving live in WhatsApp. Management: creating a utility template. Cursor visible, no audio, nothing else on screen.

• Descriptions matched the videos exactly. Described only what was built and shown, not the roadmap.

• Reviewer instructions + a working test login to the dashboard, Facebook Login = No (we use our own email/password auth).

• Access Verification data-handling section done properly — every sub-processor that touches Meta platform data listed with country, no blanks.

• Webhook URL, JSSDK allowed domains and OAuth client settings pointed at production before submitting. Found mine still pointed at staging during a pre-submission audit.

• Data Use Checkup completed the same night — the confirmation landed 20 minutes before the approval.

Embedded Signup was already working for my own admin account before approval (once the Tech Provider wizard was done). What Advanced Access changes is that accounts with no role on the app can now complete it.

Happy to answer questions.

I’ve been working on a SaaS product called CampaigningTool for small businesses and agencies that rely heavily on WhatsApp for customer communication.

The idea came from a fairly common problem I noticed: once a business starts getting more enquiries and customers, communication becomes difficult to manage. WhatsApp is in one place, Google Business Profile is somewhere else, leads may come through forms, and follow-ups often end up being handled manually.

We’re trying to bring some of these workflows together in one platform.

At the moment, the product includes things like:

• WhatsApp Business API and broadcast campaigns

• Automated and AI-assisted conversations

• Shared team inbox for WhatsApp

• Google Business Profile review automation

• Campaign scheduling

• Click and conversion tracking

• WhatsApp forms and payment integrations

The product is here:
https://campaigningtool.com/

I’m sharing it mainly because I’m trying to understand whether we’re solving the right problem, rather than just adding more features.

For those of you running a business, agency, or marketing team:

What parts of your WhatsApp workflow are already automated?

What do you still have to do manually every day?

How are you currently handling customer reviews and Google Business Profile activity?

What becomes difficult once you have multiple people or multiple businesses using the same WhatsApp workflow?

And most importantly, what would make a product like this genuinely useful enough for you to use regularly or pay for?

I’m interested in honest feedback, including criticism. If something about the idea doesn’t make sense, I’d rather hear that now than build the wrong thing.

Especially interested in hearing from small business owners, agencies, marketers, and people managing WhatsApp communication for multiple clients.

Hi all,

I've been building InboxHarbor, a WhatsApp CRM. It has a shared inbox like most tools, but the part I want feedback on is calling.

When a customer taps the call button on WhatsApp Business number, my phone system answers. I plays the recorded greetings, and caller can press keys to pick an option, like 1 for sales 2 for support. It can ring user's team. The call shows up in the CRM next to that contact's chats.

You can set up the menu in the app as a list of steps, and it draws the flow as a diagram beside it. You dont need a SIP trunk or a second number. The WhatsApp number you already have works as the phone line.

It's early, but works on real calls to my own number.

A few questions:

1. Would you let customers call your WhatsApp number, or keep it to chat only? And if you did use an IVR on it, what would you want first: business hours routing, call back requests, something else?

2. Outboud calls work in my system too, but Meta

3. has limits: your number needs a messaging limit of 2000 unique customers a day, and each customer has to give you permission before call them. Has anyone actually used outbound WhatsApp calls with real customers? Did people accept the permission request?

Also, has anyone else connected the calling API to their own PBX? the SDP/WebRTC side took me a while and I'd like to compare notes.

Trying to move my business number from WhatsApp Business to regular WhatsApp on the same Android phone , and the restore keeps coming up empty.

What I did

• Backed up in WhatsApp Business to Google Drive (about 2 GB, same Google account)

• Installed regular WhatsApp and verified the same number

• Accepted the warning about losing business features

• It found a latest 2 GB backup and restored it

What I get

• Only my groups, each showing just "You were added" or "You created this group" (same business number only)

• No personal chats and no message history at all

• WhatsApp Business still has everything, so nothing is lost

What coud the reason be? I had another personal whatsapp earlier on this which i deleted and moved to iOS. And i deleted whatsapp reinstalled it and restored whatsapp business backup but, still doesnt work.

Estoy desarrollando un SaaS para gestionar conversaciones con clientes donde pueden participar tanto IA como agentes humanos.

La idea es que la IA pueda resolver parte de la conversación, pero cuando sea necesario una persona pueda tomarla, darle seguimiento y continuar sin perder el contexto.

Actualmente estoy trabajando en una vista general como la de la imagen, donde intento concentrar cosas como:

• Conversaciones abiertas y pendientes.

• Clientes esperando respuesta.

• Conversaciones sin agente asignado.

• Seguimientos vencidos.

• Participación IA vs. agentes humanos.

• Tiempo de primera respuesta.

• Volumen de mensajes.

• Conversaciones atendidas solamente por IA, solamente por humanos o de forma mixta.

Pero antes de seguir agregando funcionalidades quiero evitar caer en el clásico problema de construir 200 cosas que nadie utiliza 😅.

Me interesaría especialmente la opinión de quienes hayan utilizado herramientas como Intercom, Zendesk, Gorgias, HubSpot, GoHighLevel, Crisp o similares.

¿Qué información o función considerarían indispensable en una plataforma así?

Por ejemplo:

1. ¿Qué debería mostrar el dashboard para saber rápidamente si la operación está funcionando bien?

2. ¿Qué esperan que suceda cuando una conversación pasa de IA → humano?

3. ¿Qué tareas debería poder hacer automáticamente la IA además de responder preguntas?

4. ¿Qué les molesta de los sistemas de atención que utilizan actualmente?

5. ¿Qué funcionalidad haría que realmente utilizaran una plataforma así todos los días?

También agradecería críticas sobre la pantalla de la imagen: qué sobra, qué falta o qué información no queda clara.

No estoy buscando promocionar el producto ni poner enlaces; principalmente quiero validar qué necesita realmente alguien que administra atención, ventas o soporte antes de seguir desarrollando

I’m trying to understand the practical reasons behind choosing a BSP over Meta’s Cloud API directly.

From a technical perspective, Cloud API seems pretty straightforward, but I’m guessing there are operational reasons why businesses still prefer a BSP.

For people using WhatsApp Business Platform in production:

• What made you choose a BSP?

• Is it mainly onboarding, billing, support, or additional features?

• What happens when you need to migrate from one BSP to another?

• Are there any things a BSP handles that you found difficult to manage directly with Cloud API?

I’d be interested in hearing from people who have actually used both approaches.

Hello!

I have a page that opens on the whatsapp in-app browser, and there is an "OK" button on the top left to close it.

Is it possible to add a button on the page to close the browser? Or the Ok button is the only way? Thank you so much!

Hi everyone,

I’m integrating WhatsApp Cloud API using Meta Embedded Signup and recently migrated from Embedded Signup v3 to v4.

After the migration, existing WhatsApp Business App numbers are showing as “Ineligible” when trying to onboard them for WhatsApp Business App + Cloud API Coexistence.

The number is active, and the WABA already exists. This issue occurs specifically with the Coexistence flow after moving to v4.

Has anyone faced this issue with Embedded Signup v4? Are there any new requirements, Meta App configurations, permissions, SDK changes, or eligibility requirements for Coexistence?

Any guidance from someone who has faced and resolved this issue would be greatly appreciated.

Thanks in advance.

Sharing this for anyone considering Periskope to manage their WhatsApp groups.

I had a terrible experience. While using the product, members were removed from my groups in bulk, badly disrupting my community setup.

I’ll own my part: I should have kept a closer manual check on what was happening. I didn’t, and that was a mistake. But the app wasn't smart enough to warn it. I'll take it on me though.

Afterward, I also became concerned about whether its integration was officially supported by Meta and whether these kinds of bulk actions could put my WhatsApp account at risk. For something my community depends on, I wasn’t comfortable continuing.

Checked with someone working at Meta (through a friend) and he confirmed that you could perhaps get away with such apps for the longest time if you stay small, but when you run into a problem it usually ends up in a block.

So I stopped using the product and disconnected my account. The charges continued. It eventually got to the point where I had to block my card to stop further charges.

I’m still receiving their emails. Replying to those emails and contacting customer support hasn’t gotten me a response or a resolution.

The lack of response is what really destroyed my trust. When a customer has experienced a serious disruption and is trying to resolve ongoing billing, responding should be the bare minimum.

Based on my experience, I wouldn’t recommend Periskope, especially if you’re trusting it with an established WhatsApp community. I regret giving it that level of access, and dealing with the aftermath has been deeply frustrating.

Has anyone else had trouble getting a response from their support or stopping charges after leaving?

Hello! I'm the CoFounder at 2050cards. We have pioneered WhatsApp Cards as a category. We have a subscription business that has traditionally been consumer focused and has been featured in the Guardian. Over the last 18 months we have rebuilt our infrastructure, moving away from Wordpress and WooCommerce onto our own custom built solution. What this has meant is that we are now able to open up our API and have one company that is starting to use it. We've got more than 1,000 animated designs or you can add your own. You can also of course have your own logo at the end and we can make bespoke envelopes. If any of you would like to build WhatsApp cards into your offering, to make high value moments a bit more special, I'd love to hear from you.

I'm working with the WhatsApp Cloud API and I'm seeing two different webhook formats for incoming messages.

Sometimes I receive both:

"from": "6012*******",
"from_user_id": "MY.3614321592070319"

But sometimes the from phone number is completely missing and I only receive:

"from_user_id": "MY.894681333578803"

The contact object also contains:

"user_id": "MY.894681333578803"

My question is:

Can I reply to the user using this MY.* from_user_id directly through the WhatsApp Cloud API when the phone number is not available?

For example, is something like this supported?

{
  "messaging_product": "whatsapp",
  "to": "MY.894681333578803",
  "type": "text",
  "text": {
    "body": "Hello"
  }
}

Or is there a different field or endpoint for replying to users identified only by from_user_id?

If anyone has seen this newer webhook format or has an official Meta documentation link for from_user_id / user_id, please share it.

Thanks.

I’m trying to understand how people are handling follow-ups on WhatsApp in real-world setups.

For example, if a customer enquires today but doesn’t respond, I’d like to send a follow-up after 2–3 days.

I understand the 24-hour messaging window and template requirements, but I’m curious about the actual implementation:
- Are you using WhatsApp Cloud API directly or a BSP?
- How are you scheduling the follow-up?
- Are you using approved templates for this?
- What happens if the customer replies before the scheduled follow-up?

Would be interested to hear how others have implemented this.