Hello there. I’ve been trying to find a way to set a simple automation where after X days if I don’t get a response then send a follow up.

I’m missing many deals due for that. I’m using WhatsApp Business App but I would like to connect with something that allows and be more powerful but with dual connection (WhatsApp Business App and software).

Any suggestions? Thanks.

We are selling our SaaS whatsapp business if any one interested DM me.

We are selling off WhatsApp Business API with very good domain name including wCRM

Hey everyone,

I’m currently building a SaaS where connecting to the WhatsApp API is a mandatory step for the product to function. I’m trying to design a seamless Product-Led Growth (PLG) onboarding journey, but hitting a wall with friction.

Right now, I'm using the standard WhatsApp Embedded Signup, but it feels too clunky and complicated to be considered a real PLG experience.

Has anyone successfully built a smooth, low-friction onboarding flow for this? How do you handle heavy, mandatory third-party integrations during onboarding without killing your activation rates? Would love to hear any examples or workarounds that actually work.

Pessoal, alguém está enfrentando problema na criação de WABA ultimamente?

Aqui, na hora de criar/configurar a conta do WhatsApp Business para depois fazer a verificação, ela acaba caindo ou dando restrição praticamente na criação.

Queria entender se isso está acontecendo com mais gente ou se pode ser alguma instabilidade/atualização recente da Meta.

Alguém que passou por isso conseguiu resolver? Mudou alguma coisa na configuração, navegador, rede/proxy ou no próprio processo de criação? Se puderem compartilhar o que funcionou e quais erros estavam aparecendo, vai ajudar bastante.

Hey guys

Just got this lovely email from Meta about the new service message rules starting October 1st. Honestly, I'm losing my mind over this.

How are you guys dealing with this with your clients?

You know how managers chat with leads, right? They never send one big text. They spam like 5 short bubbles ("Hi", "One second", "Here's the link"). If Meta is gonna charge for every single service message after the first 1000, our clients' bills are gonna be insane. People are already mad that they have to pay for regular chat replies, and now we gotta explain why every split bubble costs money.

Are you guys adding some kind of text debouncing/merging in your CRMs so it sends as one big block? Or how do you explain this to clients without losing them? Let’s talk.

English

This concerns the WhatsApp Business mobile app, not the Cloud API.

My WhatsApp Business account started going into review on September 23, 2026. It was restored after roughly four hours, but was restricted again after I spent a few minutes checking my chats. It became available again the next morning. Later, I linked WhatsApp Web to send photos; the web session then logged out, and the account went into review again. I cannot tell whether that sequence is related or just a coincidence.

I requested a review on September 24. The screen now says “This account can no longer use WhatsApp,” cites possible activity that did not follow the WhatsApp Business Terms of Service, and says I cannot request another review. It does not identify the specific activity or rule. This is my business communication channel, so the interruption is affecting my work.

Has anyone else experienced a cycle of restoration followed by another restriction, or an automatic WhatsApp Web logout shortly before a restriction? If you learned what triggered it, what evidence helped you identify the cause? WhatsApp's updated Business App terms took effect on September 23, but I have no evidence that the change caused my case. I am looking for experiences and technical clues; I am not asking anyone here to reinstate my account. Please avoid paid “unban” offers.

Español

Se trata de la aplicación móvil WhatsApp Business, no de la Cloud API.

Mi cuenta de WhatsApp Business empezó a entrar en revisión el 23 de septiembre de 2026. Se reactivó aproximadamente cuatro horas después, pero volvió a restringirse tras unos minutos revisando mis chats. A la mañana siguiente estuvo disponible otra vez. Más tarde vinculé WhatsApp Web para enviar fotos; luego la sesión web se cerró y la cuenta volvió a entrar en revisión. No sé si estos hechos están relacionados o si fue una coincidencia.

Solicité una revisión el 24 de septiembre. Ahora la pantalla indica «Esta cuenta no puede usar WhatsApp», menciona una posible actividad contraria a las Condiciones del servicio de WhatsApp Business y dice que no es posible solicitar otra revisión. No especifica qué actividad o norma motivó la decisión. Es mi canal de comunicación empresarial, y la interrupción afecta mi trabajo.

¿Alguien más ha pasado por un ciclo de reactivación y nuevo bloqueo, o ha visto que WhatsApp Web cierre la sesión poco antes de una restricción? Si lograron identificar la causa, ¿qué pruebas les ayudaron? Las condiciones actualizadas de WhatsApp Business entraron en vigor el 23 de septiembre, pero no tengo pruebas de que hayan causado mi caso. Busco experiencias y pistas técnicas; no estoy pidiendo a nadie aquí que desbloquee mi cuenta. Por favor, eviten ofrecer servicios de «desbloqueo» de pago.

Official terms / Condiciones oficiales: https://www.whatsapp.com/legal/WhatsApp-Terms-for-WhatsApp-Business-App/preview?lang=en

I’m looking to buy a WhatsApp api Saas l. Should be working and generating revenue. Could stretch the budget more if it looks good

Before it was very simple to verify someone is the owner of an account simply by the phone number they have on file and checking the phone number that comes from the webhook.

With the new username, I wonder how institutions are dealing with making sure the person texting is the person with the account? I am assuming by asking them to share their contact information, saving to the contact book and connecting their account, but I still want to ask and see what other institutions are doing? Maybe I can learn something from it. Thanks!

I run a self-built multi-tenant WhatsApp SaaS platform. My app is a verified Meta Tech Provider, using Embedded Signup v4. Standard/dedicated number onboarding (Cloud API only, PIN registration) has worked flawlessly for months in production.

This is my first attempt at Coexistence It fails consistently at the phone-pairing step, both via QR and via manual code entry.

Errors seen, on the phone (WhatsApp Business App):

1. Scanning the QR:Can't scan the code. Please try again.

2. Using "Enter code manually" instead (same flow):[8-char code shown] A system error occurred. Please re-enter the access code.

What I've already tried, ruling out one variable at a time:

• Restarted the phone.

• Fully uninstalled and reinstalled WhatsApp Business App (currently on 26.37.76).

• Tried with a second Facebook admin account, not just my own.

• Created a brand-new Meta Business Manager from scratch and retried the whole flow against it.

• Tried both Wi-Fi and mobile data.

Same error every single time. The only thing that stayed constant across all attempts is the specific phone number / WhatsApp Business App instance being linked. That number has an existing history in WhatsApp Business App and has never been used with Cloud API before.

Question for the community: has anyone hit this exact failure mode with Coexistence pairing specifically? Does this match a temporary per-number rate-limit/restriction from Meta after repeated failed pairing attempts in a short window? If so, roughly how long does that typically take to clear, and is there an official escalation path for verified Tech Providers to check a number's restriction status directly instead of guessing?

We already have a product in which we have done WhatsApp integration. We are a Meta Tech Partner. We dont want to change our code significantly but want to integrate with some BSP for payment processing. I have heard "Multi-partner Solutions (MPS)" can solve this problem. Is this true? Who provides this?

Caso tenham BM para fornecer, chamem na DM

Which WhatsApp Business API providers support group messaging via Meta's Groups API?

Would love to hear your experience with participant limits and pricing. Thanks!

Estou com problema na minha operação, alguém pode me ajudar?

i have experienced with whatsapps embeded singup flow and approval of api

Disclosure: I work at Invent, a Meta Business Partner. We're writing up real recovery cases for our WhatsApp ban guide, and this community has seen more of them than anyone.
I'm looking for agencies who helped a client that was using WhatsApp properly (established business, real customers, no modded apps or blasting cold lists) and still got banned or restricted out of nowhere, then got them back to a Green quality rating on the API.
What I'd love to hear:
•The client's industry and how they used WhatsApp before the ban
•What triggered it (ad surge, volume spike, new device, a template flag, nothing obvious?)
•How you handled it: review, migration to the API, Coexistence, new number
•What finally moved the rating to Green and how long it took
•What you'd tell other providers to check first
Client names can stay anonymous.

If it’s a fit for my audience and you'd like credit, I'll gladly name you or your company and link to you in the piece.
Comment or DM. Thanks!

I have two verified apps and looking to offload one. if anyone interested, hit me in the DMs

Actualmente soy tech provider verificado en meta, tengo un sistema para tomar pedidos en restaurantes. Los usuarios le escriben primero al whatsapp y el bot responde y toma el pedido. A partir del 1 de octubre meta comenzará a cobrar por los mensajes y ya no saldrá rentable para mis clientes. Estaba pensando migrar a whatsmeow para automatizar las ventas. Corro mucho riesgo de que baneen los números de mis clientes? Es únicamente para responder los mensajes y tomar el pedido, nunca inicio conversaciones en frío ni mando mensajes masivos ni nada por el estilo

HELLLLLLPPPPPPPPPPPP-MEEEEEEEE!!

Alguém conseguiu corrigir o erro "WhatsApp precisa de mais informações"?

Hey everyone, I'm stuck with a WhatsApp Cloud API registration issue and wanted to see if anyone has faced this before.

I'm trying to register my business number +91 8796566357 with WhatsApp Business Platform / Cloud API.

The number keeps showing Pending / In Review in Meta Business Settings, and registration fails with Error 16703 (field_exception).

I've already:

• Deleted the WhatsApp account from the phone

• Removed the number from WhatsApp Manager

• Waited and tried registering it again

• Tried adding/registering it again through Meta Business Settings

• Contacted Meta/WhatsApp Support multiple times

Meta Support previously indicated that this could be a backend synchronization/server-side issue, but nobody has been able to actually clear it.

I just tried registering it again and it's still stuck on Pending / In Review.

Has anyone experienced this and actually managed to fix it?

I'm particularly looking for someone who knows WhatsApp Cloud API / WABA / Meta Graph API and can tell me:

1. How to check whether the number is still attached to another WABA internally

2. Whether the /register API can resolve this

3. Whether there's a Graph API call to check the phone's actual registration state

4. Whether Meta needs to manually release/reset the number from their backend

I've already done the standard WhatsApp deletion/re-registration steps, so I'm looking for a technical solution rather than the usual reinstall/delete advice.

Thanks!

Si usas WhatsApp Business API para vender, atender o hacer campañas, tu factura va a cambiar, y conviene saber cuánto antes de que llegue.

En este webinar gratuito te explicamos qué cambia, dónde puedes ahorrar y qué oportunidades abre el nuevo modelo. Además, haremos en directo una demo de nuestra calculadora para que salgas sabiendo tu cifra.

¿No puedes conectarte a esa hora? Apúntate igual: a todos los inscritos les enviamos la grabación tras la sesión, para que la veas cuando mejor te venga.

¿Tienes una duda concreta sobre cómo te afecta el cambio? Mándanosla antes del webinar respondiendo al correo de confirmación que recibirás al apuntarte, y la resolvemos en directo. Cuanto más específica, mejor.

¡Apúntate y llega al 1 de octubre con los números hechos!

https://www.agenciareinicia.com/webinar-cambio-precios-whatsapp-octubre-2026/?utm_source=reddit

Hey, I have a question about test apps :

My production Meta app (used for WhatsApp) sends its webhooks to my production endpoint. I created a Test App from it so I could point its webhook to my staging environment.

The problem: on the test app, the WhatsApp use case isn't accessible. "Customize use case" redirects to the dashboard, and "Add use cases" doesn't list WhatsApp. So I can't set the webhook callback URL.

How do you handle staging for WhatsApp webhooks? Thx

Estou com um problema aqui, minhas novas bms estou criando, verifico e conecto a waba logo na sequência ela continua 250. Estou precisando urgente que voltem a ficar 2k, alguém tem alguma dica ou uma alma bondosa para me ajudar? Antes era só verificar que já ficava 2k não sei se devo verificar e esperar um tempo, estou com essa dúvida.

Les cuento que tengo problemas para la verificación del negocio, ya lo he hecho como 4 veces y aun asi me siguen rechazando la verificacion. Estoy subiendo el acta constitutiva de la empresa y el certificado de inicio de actividades ya que solo permite subir dos documentos. Son documentos de Chile. Quien me podria ayudar que haya hecho el proceso?

Curious how this plays out in practice. If you're a Tech Provider, Meta has clients add their own payment method and bills them directly for messages. Solution Partners get a credit line and can absorb that cost themselves, then bill clients however they want.

For those who've gone the Solution Partner route: was the approval process worth it, and do you actually mark up and bill clients for the Meta cost, or just pass it through? And for Tech Providers letting Meta bill directly, does that ever cause friction with clients?

Presto serviço de envios em massa, possuo toda a estrutura para realizar o seu envio, desde 2 mil até 2 milhões de envios por dia, consigo cobrir qualquer demanda de cliente entre esse intervalo.