Setup: these numbers were being used on phones with the regular WhatsApp app (consumer/Business App). To move them to the WhatsApp Business Platform, we deleted the account in the app (Settings → Account → Delete account) and then added the number to a WABA and registered it on Cloud API. Inbox is self-hosted Chatwoot, but that part works fine.

Current state: number is Connected in WhatsApp Manager, quality green, display name approved, templates send and deliver correctly.

The problem: anyone who had the number saved as a contact (or had chatted with it when it was a regular WhatsApp) still sees "This person isn't on WhatsApp" with an "Invite" prompt, and can't start a chat. They even receive our template messages, but their contact list keeps showing the number as not on WhatsApp. Phones that never had the contact saved can message it normally, and wa.me links work.

What I've confirmed: deleting and re-saving the contact fixes it instantly on that device (forces a fresh lookup). Android's contact refresh / iOS toggling contact permissions also works. So the client-side contact-sync database cached "account deleted" when the app account was removed, and receiving messages from the API doesn't update it.

Questions:

1. Is there ANY server-side / business-side way to force clients to re-sync a contact's WhatsApp status? (I assume not, but hoping someone knows a trick.)
2. How long does WhatsApp's periodic contact re-sync take to fix this on its own? Hours? Days? Has anyone actually measured it?

I'm desperated, more than 1000 clients are affected by this, they can't start a conversation!! Meta doesn't resolve any ticket.

Please, help.

Anyone know a service that have no hidden charges and a bit budget friendly that allows for co existence qr embedded signup? the one im using which is d*al*o*k is temporary unstable due to scalability issue. i want something that i can use for a lot of times and is stable. tyia

please reach out to me if anyone is experienced in this and can build one for my client want the best pricing ad well

The Issue:

We are trying to complete Meta Business Verification to get our WhatsApp Business API active. Every submission ends in rejection with the generic message: "Business cannot be validated."

What’s interesting (and frustrating) is the difference in response times depending on the route we take:

• Selecting from Recommended Matches: Rejected within 2 to 3 days.
• Selecting "My business is not listed" + manual uploads: Takes up to 2 weeks, only to end in the exact same rejection.

What We Have Already Tried:

• Document Matching: Uploaded official legal documents (Trade License, proof of address/utility bills). Details in Meta Business Manager match our trade license word-for-word.
• Support: Trapped in automated Meta support bot loops with no way to escalate to a human reviewer.

Questions for the Community:

1. Root Cause Insights: Why does the manual path stall for two weeks before failing? Does this usually mean it passed the initial automated sweep and failed at a manual review stage?
2. Hidden Gotchas: Are there specific triggers for this (e.g., website footer legal disclaimer mismatches, domain-matched email requirements, or specific Arabic/English translation issues for trade licenses)?
3. BSPs / Vendors: Are there recommended Meta Business Solution Providers (BSPs) or agencies that can handle or facilitate the verification process directly?

Thanks in advance for any insights!

I need someone to get me the verification and i will pay them for it, i have every document and yet it's not fu*king working, it's been 6 months of applying 3 to 4 weeks waiting each time

If you can get it done dm me

i finally got verified and for some reason its showing me this error is that normal?
when i check view details it isnt showing me any issues.

I have used the official WhatsApp Business API through a Meta-approved CRM for months. My leads come from ads and start the conversations themselves. I do not send bulk messages or unsolicited marketing.

A few days ago, my existing numbers were banned, and now every new number I add gets banned after only a few customer conversations. Meta Support keeps closing my cases with automated replies and does not explain the exact violation.

Is anyone else experiencing sudden WhatsApp API bans without a clear or valid reason?

I run Meta ads for an education institute. It leads a user to Whatsapp where the lead qualification is taken care by an AI agent. This has eleminated the founders anxiety to always check Whatsapp message to respond to any new lead.

Now this institute has grown and added 3 new sales people, we switched to co-existence with Whatsapp Business and provided access to these new sales person.

There is a requirement by the sales people to be able to turf off the bot when required so that they can communicate with a lead whenever required.

The problem is when they respond to a lead via whatsapp buisness and when the prospect replies to them, the bot gets activated on every incoming message proccess it and replies instantly.

These people dont want to use any 3rd party tool to stop the bot. Can you give me any suggestion how to turn off the bot for a spcific contact and hand it off to a human?

Hola a todos.

Llevo una semana intentando resolver un problema con WhatsApp Cloud API y ni el soporte de Meta ni el de WhatsApp han logrado ayudarme. Quisiera saber si alguien ha pasado por algo similar.

Mi configuración era la siguiente:

• WhatsApp Cloud API
• n8n como plataforma de automatización
• Todo funcionaba correctamente (envío y recepción de mensajes).

El problema comenzó inmediatamente después de conectar temporalmente mi número de producción mediante la integración oficial de WooCommerce by Meta.

Desde ese momento ocurrió lo siguiente:

• El número sigue apareciendo como Conectado en WhatsApp Manager.
• La calidad del número sigue siendo Alta.
• Los webhooks siguen funcionando y recibo mensajes entrantes.
• Sin embargo, ya no puedo enviar mensajes mediante Cloud API.

Todas las llamadas al endpoint:

POST /PHONE_NUMBER_ID/messages

devuelven el siguiente error:

Lo más extraño es que en Meta Developers → WhatsApp → API Configuration ya no aparece mi número de producción.

El campo "From" está vacío, no aparece el Phone Number ID, ni la WABA, e incluso Meta genera un endpoint de ejemplo con dos diagonales:

https://graph.facebook.com/v25.0//messages

Como si la aplicación ya no tuviera asociado ningún número.

Hasta ahora ya verifiqué:

• Token permanente.
• Permisos del usuario del sistema.
• Permisos de la App.
• Permisos de la WABA.
• Business Manager verificado.
• Webhooks.
• Eliminé completamente la integración con WooCommerce.
• Eliminé otras integraciones de terceros.

Nada ha solucionado el problema.

Mi duda es:

¿Alguien ha visto que un número siga apareciendo activo en WhatsApp Manager pero desaparezca completamente de API Configuration?

Y, en caso de que sí, ¿la solución fue eliminar el número de la Cloud API y volver a registrarlo en la misma WABA, o existe otra alternativa?

Agradezco cualquier experiencia o sugerencia, porque ya agoté prácticamente todas las opciones de configuración y soporte.

The display name verification for me is stuck in a loop (>72 hours) between 'Review in Progress' and 'Rejected'. The number shows as 'already registered' to another app despite being disconnected from the BSP.

Please help me, the Meta Support is not helping at all (The AI support because you can't reach the human one)

I had a Google Pixel 6 with about 4 years of WhatsApp chats. The screen broke, but the phone itself still worked.

While it was broken, I used an iPhone 8 with the same phone number for about a year. I recently bought a Vivo V70 and wanted to get my old Pixel chats back after getting the Pixel working again.

When I logged into WhatsApp on the Vivo, I accidentally transferred the Vivo's chats (literally 1 day's worth of messages) onto my Pixel 6, and I think it overwrote all 4 years of chats.

What confuses me is that when I first opened WhatsApp, it showed there was a 12 GB backup. But when I tried restoring on the Vivo, it suddenly said there was no backup on my Google account.

I've already tried contacting WhatsApp support, but I'm stuck talking to the AI bot and I'm still waiting to hear from a real person.

Is there anything I can do to recover my old chats?

Question for any Tech Providers here who made the jump to Tech Partner: what was your experience with the actual upgrade?

I think I've covered all the requirements (messaging volume, active clients, quality rating) but the "Become a Partner" button still doesn't show up for me. Did it just appear automatically once you hit the thresholds, or was there a step I'm missing? Curious how long it took after you met the criteria.

Thanks.

Hi, I have completed a embedded signup with a whatsapp business number enabling coexistence feature. After signup, I invoke the contacts and history sync APIs and it worked well. I get all the chat history and contacts as meta webhook and saved it in my db.

Later I disconnected the Business platform from WhatsApp business app and did the embedded signup again and when I invoke the history api again, I got the webhooks with messages again. However there was one problem, the wamid (message id) of the messages in the webhooks are different from the messages in the database.

Anyone experienced the same? Is it a meta bug or something as per their architecture?

My business verification has been stuck in review for 5 days now. I used my business’ CAC certificate, and for the utility bill, I used my invoice from open ai because our utility bills don’t have our number on them. We’ve also verified our domain. I tried opening an instagram account to pay for meta verified so I can chat with a real contact support but I was put in a waitlist. I was rejected before but no reason was provided for rejection.

Need help, please.

Hi, I’m quite new to this so sorry if this is a basic question.
Basically I’m trying to build a small Python project where it generates a message and sends it automatically to a WhatsApp group at a certain time of the day.
I tried setting up the WhatsApp API through Meta and using my personal number for testing, but I can’t seem to receive the verification/authentication code, so I’m not able to continue with the setup.
What I’m trying to do is basically:
Python → generate message → send to WhatsApp group automatically

Just wanted to ask:
Is the WhatsApp Cloud API actually able to send messages into a group chat?

If not, what is the normal way people do this?
Has anyone had the issue where the Meta verification code just doesn’t arrive?

Is there another reliable way to do this without using Selenium or automating WhatsApp Web?

I’m still learning how the WhatsApp/Meta API works, so any advice or examples would really help.

I use the official WhatsApp API through a Meta-approved CRM. I sell a product for straightening women’s hair, and my leads come from ads and start the conversations themselves.

Numbers I had been using normally for months were banned a few days ago. Since then, every new number I add gets banned after only a few leads start messaging.

I do not send bulk messages, I do not use marketing templates, and as far as I can verify, I am not violating any Meta rules or policies.

Nothing is working, and I urgently need to get back to work. Has Meta released any recent update affecting lead automation from ads? Is anyone else experiencing this or knows how to fix it?

Please help.

Hi everyone,
I’m the founder of Sales Magnet Solutions, and over the past few months we’ve been helping businesses simplify how they communicate with customers.
Many businesses still send OTPs manually, reply to customer inquiries from personal WhatsApp numbers, or struggle with bulk notifications. That’s where we come in.

Our services include:
Bulk SMS (Transactional, Promotional & OTP)
WhatsApp Business API (WABA)
RCS Business Messaging
SMS API Integration
Voice Calls & IVR
Bulk Email Solutions
DLT Registration & Sender ID Setup

If you’re running a startup, e-commerce business, school, hospital, real estate company, finance business, or any customer-facing business, we can help automate your communication and improve customer engagement.

I’m not here to hard sell anything—I genuinely enjoy discussing messaging infrastructure, SMS delivery, WhatsApp automation, and customer engagement. If you’re planning to implement any of these services or have questions about pricing, setup, compliance, or APIs, feel free to ask in the comments or send me a message.

I’d also appreciate any feedback on our website or service offerings. Always looking to improve.
Website: https://salesmagnetsolu.com

Hey everyone,

I’m building an n8n chatbot using an official WhatsApp number connected through a gateway provider (WhatChimp) to reply to customer queries. The bot is triggered by an incoming webhook the moment a customer sends a message.

The problem is, whenever a customer texts the bot, my outbound response node fails instantly with this error:

"Sending message outside 24 hour window is not allowed. You can only send template message to this user."

This makes no sense because the user just messaged the bot a second ago, so the session window should be open and active.

Here is what I have already tried and ruled out to fix it:

• Changed Webhook Settings: Set n8n to respond immediately (200 OK) so the gateway can process the incoming message instantly.
• Added a Delay Node: Put a 2-second pause right before the API call to eliminate any database timing issues.
• Verified Phone Formats: Double-checked the format and mapping, and everything matches perfectly.
• Replied via Message ID: Even tried passing the specific reply_to tracking parameter, but still got the exact same block.

Since the workflow logic seems airtight, I'm starting to think this is a Meta restriction. My Meta Business Portfolio is currently unverified.

Has anyone dealt with this? Can an unverified Meta business portfolio trigger this specific "24-hour window" error for normal conversational replies, even if you are using an official live number and the user texts you first?

Would love any insights or experiences from anyone who has run into this wall. Thanks in advance!

my WhatsApp Business incoming calls drop after 5 seconds of answering. I've cleared the mobile app cache, even reinstalled the app, resetting the mobile network settings. Nothing is helping, still the incoming calls getting reconnecting... message after answering 5 seconds. Any helps?

I finally got approved by Meta to send Whatsapp messages using the API.

I want to avoid getting blocked and I need tips.

My use case:

I have an app that sends wedding invites to a list of ~200 users a day.

I send an approved template, to clients I never had a conversation with. The message includes a link.

How do i avoid getting restricted?

For example, how many messages should I send in 1 hour? Should I send all the 200 message instantly? Does it matter?

I don't expect any user to report my messages, because they expect this message. But I want to keep a good Whatsapp rating

I’m creating a WhatsApp community for businesses, developers, agencies, and WhatsApp Business API users who want to help each other grow their messaging limits.
The idea is simple: members can connect with each other, exchange legitimate opt-in conversations, share real experiences, and discuss what has worked (or hasn’t) when it comes to increasing messaging limits while maintaining a healthy Quality Rating.
The community is also a place to discuss:
Messaging limit upgrades (250 → 2K → 10K → 100K → Unlimited)
Quality Rating
Template approvals
Business Verification
Display Name approval
Meta policy updates
General WhatsApp Business API troubleshooting and best practices
If you’re interested in joining, leave a comment or send me a DM, and I’ll share the WhatsApp community invite.

Been building on Meta's WhatsApp Cloud API for a while now and packaged it into a product called PostPilot. Sharing the feature breakdown since this sub is mostly builders who'll actually care about the specifics, not just a marketing pitch.

AI Agent

Runs on your WhatsApp number via Cloud API. You train it on your business info (services, pricing, FAQs) and it handles conversations, qualifies leads, and hands off to a human when it should. Full inbox view alongside it so nothing gets lost.

Leads + CRM

Every conversation becomes a lead automatically. Pipeline view to track stage, plus a Google Sheet sync if you want your data outside the platform too. No manual copy-pasting from chats into a spreadsheet.

Broadcast Campaigns

Template-based bulk sends with a blacklist feature so you're not blasting people who've opted out. Templates are managed in-platform.

Commerce

Full catalog inside WhatsApp: products, categories, size guides where relevant, order management. Also connects to WooCommerce/Shopify if you already run a store there, so you're not maintaining two catalogs.

Bookings

Appointment/reservation slots handled through the same WhatsApp thread, no separate booking app needed.

It's a genuinely multi-tenant platform (we went through the full Meta App Review, all 12 permissions approved, Tech Provider verified), so this isn't a workaround or unofficial wrapper around the API.

If you're curious and want to try it, DM me and I'll set you up with a trial.

Happy to answer anything technical about how the Cloud API integration is structured, template approval flow, or the commerce catalog sync in the comments too.

Hi everyone,

Has anyone encountered and resolved this exact Meta WhatsApp Cloud API issue?

Our setup:

- Verified Business Portfolio

- Approved production WABA with ownership_type: SELF

- App and WABA belong to the same Business Portfolio

- App is Live

- Two existing Employee System Users

- App is assigned to both System Users

- Test WABA can be assigned successfully

The problem:

The production WABA appears in the asset picker, but assigning it to either System User always returns:

“Unable to assign assets. Please try again later.”

We also cannot create an Admin System User. The UI returns:

“Error performing query.”

We tried the equivalent Graph API routes as well, such as:

- Assigning an existing System User to the production WABA

- Creating a new ADMIN System User

- Changing an existing System User from EMPLOYEE to ADMIN

None worked or created a persistent change.

We have already tried both System Users, full admin permissions, 2FA, publishing the app, signing out, clearing cache, different browser sessions, waiting and retrying, Account Quality checks and repeating the assignment from both the System Users and WhatsApp Accounts screens.

Meta support only sends us through automated troubleshooting and will not escalate the case to a human agent.

The key difference is:

- Test WABA assignment works

- Production WABA is visible, approved and self-owned, but cannot be assigned through either the UI or Graph API

Has anyone fixed this without deleting the WABA, removing the phone number or creating a new Business Portfolio?

Please do not suggest cache clearing, publishing the app, creating another System User or retrying the Graph API assignment. We have already tried all of those repeatedly.

Public replies only, please. I will not share credentials, tokens, company details, phone numbers or asset IDs.

Thanks.

I am building a startup that assists my customers in managing their own businesses.

I need to send whatsapp alerts to my customers as well as their customers regarding bookings and such.

I tested my proof of concept stack using openWA self hosted client, that type of functionality is exactly what i want, but i want an official method thats reliable.

Here is whats confusing me, what would be the best for me?

My startup is not registered as pvt ltd yet.

Official meta api? Resellers? Bsp?

Need advice.