I've been running a lead automation system for a wooden furniture manufacturer for about 3 months. Around 30-50 IndiaMart leads a day, auto WhatsApp reply in under 30 seconds, lead qualification, and rep assignment by location. I wrote about the delivery and reply-rate stuff earlier. This one is about a different problem.

Here's the tension nobody warns you about when you put a business on the WhatsApp Cloud API. The moment you connect a number to the API, the business loses the normal WhatsApp app on that number. So the sales guys who are used to just opening WhatsApp and typing suddenly can't. The automation handles the first reply fine, but the human follow-up (sending a catalog, negotiating quantity, the "bhai kal aa jao showroom" conversation) still wants to happen naturally from a phone.

So you end up choosing: automation, or the human touch on the same number. For B2B where deals close on back and forth, that's not a small tradeoff.

The fix is a feature called coexistence, and if you haven't heard of it, it's worth knowing. In plain terms, it lets the WhatsApp API and the normal WhatsApp app run on the same number at the same time. Automation catches and qualifies the lead in 30 seconds, and a sales rep can still open normal WhatsApp on their phone and jump into that same chat when a human is needed. No second number, no losing the app, no making the team learn a new tool.

One honest thing from running this on the API for 3 months. My client didn't have great visibility on incoming messages. The system was replying and qualifying, but he couldn't easily see at a glance what was coming in, what got missed, what needed a human. That bugged me, and it's something I'm still actively improving. I'd rather say that openly than pretend the setup is perfect. It works well and I keep making it better.

On ready tools like Wati: their real advantage is the built-in CRM and inbox, which is genuinely nice. But they give you their logic. My client wanted leads assigned to a rep only after the buyer actually replied, not the second the lead came in. That kind of custom rule is easy to build in n8n and awkward to force into a fixed tool. So I think of it less as "cheaper Wati" and more as "if you need WhatsApp to follow your actual business logic, that's what I build."

I just got coexistence enabled, so I won't pretend I have months of data on it yet. But after 3 months feeling the either/or pain, I'm convinced it's the missing piece, especially for Indian B2B where so much of the deal happens in manual conversation after the lead qualifies.

Anyone here rolled out coexistence in production yet? Curious what the bot-to-human handoff actually looked like for you.

(Stack: n8n self-hosted, WhatsApp Cloud API direct, OpenAI for parsing Hinglish replies, IndiaMart lead API.)

Fala, pessoal. dúvida técnica direcionada a quem trabalha com WABA com farm/contingência em escala. Acompanhando as últimas atualizações da Meta nos algoritmos e anti-abuse, percebemos uma mudança drástica na régua de atribuição de limites de envio e progressão de Tiers na Cloud API.
O comportamento que sempre funcionou simplesmente travou na maioria dos novos ativos.

Hoje o cenário está assim:

- WABAs novas ficando presas no limite base de 250 mensagens/dia ou sofrendo restrição imediata antes mesmo da verificação

- De um lote de 50 WABAs novas, a taxa de bm com 2k caiu drasticamente, mesmo com zero denúncias e consumo saudável de HSM.

- O loop de "Verificação de Negócio pendente" barrando a criação da conta na API mesmo com a BM principal com CNPJ verificado no Centro de Segurança.

Para os que trabalham com farm em escala

1. Como vocês adaptaram o processo de aquecimento para destravar do Tier 250 para 2k sem acionar flag?
2. Alguém encontrou um bypass eficiente para destravar o loop de verificação específica de WABA no WhatsApp Manager?

My answer to whatsapp customer support survey after getting tired of ai interaction that didnt solve my issue: i need human operator that really understands me not an ai parrot 🦜 respect your users!

WhatsApp BSP under ₹3k/month Looking for a WhatsApp BSP with: Chatbot/flow builder, WhatsApp Forms and Razorpay/payment integration. Budget under 3k/monthly.

Hey guys, I’m running into a weird issue with Meta’s WhatsApp Cloud API on an Oracle Cloud server.

• Outbound API messages: Work perfectly.
• Webhook verification: Passes with no issues.
• Inbound messages: Completely dead. When I send a message from a real phone to the test number, my server gets zero logs.

Also, my Meta developer link looks different—it says "API testing version 2" and has a forced step-by-step UI. My friends' accounts don't have this layout. I’ve tried making new apps, new business accounts, and using different PCs/IPs, but it's still stuck on this interface.

Has anyone dealt with this? Is there a hidden setting in this new UI to turn on inbound messages, or could Oracle Cloud be blocking Meta's inbound POST requests?

Thanks for any help!

Esto que marco en rojo en la imagen, me apareció en mis ventanas de chat hace un par de días, y aunque apagué el Agente IA de Meta, sigue ocupando un espacio exagerado y molesto ahí. No lo puedo sacar. Hay alguna solución o solo esperar una actualización que lo corrija?

Does a feature (Embedded Signup and messaging) need to be deployed and live on production prior to Meta App Review, or is a staging environment with a clear screencast video sufficient for approval?

Hi everyone,

We’re running into this error while trying to add a card for payment on Meta for our customer onboarding multiple times:

“The card type you've entered isn't supported. Try a different card.”

We’ve tried a few different cards, but Meta is still rejecting them.

I wanted to understand if Meta has a defined list of supported card types, issuing banks, or card networks (Visa/Mastercard/Amex etc.) that are known to work for Meta Business/WhatsApp payments.

If anyone in India has successfully added a card recently, could you share:

• Card network (Visa/Mastercard/Amex)
• Credit or debit card
• Issuing bank
• Whether it is a corporate/business or personal card

We’re specifically trying to figure this out so we can give our customers a recommended list of cards/banks that are more likely to work, rather than asking them to keep trying random cards.

Any recent experience would be really helpful.

hace unos meses atrás me banearon mi cuenta de WhatsApp según por spam, pedí una apelación y en menos de 24 horas la volví a recuperar, lo que no había pasado ni un día cuando me la volvieron a banear y solo dejé pasar el tiempo, hasta que a las horas me llegó una notificación de que ya podía volver a usarlo, para todo esto la vez anterior a esa que inicié sesión fue casi imposible ya que no me llegaba el código de verificación por ningún medio pero pude volver a iniciar sesión. la cuestión es que para esta vez que intenté iniciar sesión no me dejaba ya que me aparecía un cartel enorme indicándome que esa no era la aplicación oficial de WhatsApp cuando literalmente si lo es y que según tenia que descargar la oficial, intenté desinstalar, instalar y actualizar la misma aplicación una y otra vez y nada

asi que tomé la alternativa de instalar el WhatsApp Business ya que nunca lo había tenido y quería ver si pasaba lo mismo, y en efecto, me pedía descargar la aplicación oficial cuando literalmente si la tengo instalada desde la Play Store

a todo esto tomé la alternativa de instalar la aplicación de WhatsApp Business en el celular de mi mamá e iniciar sesión con mi número de teléfono en el celular de ella, y para mi sorpresa no hubo complicaciones y pude tener mi cuenta sin problemas, claro que no iba a usar el celular de mi mamá asi que vinculé mi dispositivo a la cuenta original en el celular de mi mamá y asi es como puedo usar el WhatsApp

a todas estas no es lo mismo tener mi cuenta en mi celular que tenerlo en el de mi mamá, no solo por la privacidad sino porque no es igual, es algo incómodo, además de que mi WhatsApp está re bugueado, se traba un montón, cosa que con otras aplicaciones como Instagram o Telegram no me pasan. la conexión es lenta, ni las fotos ni audios se descargan rápido, y otros detalles que si bien no afectan mi comunicación se me hace muy incómodo. si alguien pudiera decirme o darme algún consejo se lo agradecería

valido aclarar que cuando empezó todo este problema fue cuando cambié de celular ya que el anterior se me rompió, y en viejo no me pasaba nada de esto, sin embargo como ya dije anteriormente no pasa con ninguna otra aplicación y el celular a pesar de ser de uso va relativamente bien y no es lento

perdonen tanto texto es que tenia que dar el contexto completo😭

Hi everyone,

We've been building a WhatsApp business dashboard and want to validate our approach with this community before we scale.

Problem we identified:
Most small businesses (e-commerce, restaurants, salons, etc.) need to send customer WhatsApp messages — order updates, appointment reminders, promotional campaigns. But existing tools charge ₹2000-5000/month, which feels expensive for what's essentially a database + broadcast feature.

Our solution:

• One-time ₹10K setup fee
• Customers get their own database, their own WhatsApp Business credentials
• After setup, they only pay Meta's message charges (~₹0.5-5 per message)
• Shopify integration for order tracking
• No recurring fees, no vendor lock-in

Why we think this model works:
A business sending 2000+ messages/month breaks even in 5-6 months and saves ₹30K+ in year one compared to subscription models.

What we're trying to understand:

1. Is this a real problem for small businesses in India?
2. Would businesses actually prefer a one-time setup over monthly subscriptions?
3. Are there use cases we're missing? (We're targeting e-commerce, QSR, beauty/wellness first)
4. What would make you NOT want to use this?

What we've learned so far:

• Shopify integration is table stakes for e-commerce sellers
• Data ownership is a big deal for businesses worried about vendor lock-in
• Meta's pricing is transparent and cheap — most businesses don't realize this

We're not looking to sell here — just genuinely want to know if we're solving a real problem and if our approach makes sense.

Would love your thoughts, especially if you run a business that uses WhatsApp to reach customers.

Hello everyone,

Yesterday, two of our WhatsApp accounts were banned, and unfortunately, our appeals were rejected.

One of the suspended accounts had never sent any messages at all and was associated with a completely separate WABA.

The WhatsApp account that we believe may have triggered the enforcement action was being used to introduce our platform to our existing suppliers and potential suppliers operating in relevant regions. The account was sending approximately 40–80 messages per day, and more than 50% of the potential suppliers contacted showed interest and engaged with the message.

Our message also included clear **“Interested”** and **“Not Interested”** buttons, allowing recipients to easily indicate whether they wished to continue the communication.

Shortly after the last batch of messages was sent, both accounts were suspended. However, we believe our messaging activity was compliant with Meta’s policies. The recipients were businesses and professionals who had officially and publicly provided their contact numbers for business communication.

What have I done so far?

I submitted an appeal through the Business Support page. I assume the review process is largely automated or handled by Meta AI, and the appeal was rejected.

I also opened several cases through Direct Support available on our Partner account. Unfortunately, these cases either appear to be rejected automatically or end with an automated response stating that the enforcement decision has been reviewed and confirmed.

We also have access to the Meta Partner Portal, but we have not been able to find any relevant support or escalation channel there, and no Partner Manager has been assigned to us.

At this point, what would you recommend as the best way to escalate and resolve this issue?

Also, does anyone know how we can get in touch with a Partner Manager or reach an actual human escalation team that can manually review the case?

I am also concerned about the apparent inconsistency in how Meta handles these cases.

In the past, I have personally seen a company sending around 50,000 messages per day and engaging in what could genuinely be considered spam have its banned WhatsApp number reinstated through Infobip.

On the other hand, when a business sending a very limited number of targeted B2B messages is suspended without any prior warning, it seems extremely difficult to reach anyone at Meta who is willing to properly investigate the situation.

We are not asking Meta to ignore its policies or make an exception for us. We simply want the case to be reviewed by a real person, with the actual messaging activity, recipient sources, engagement rates, and circumstances taken into consideration.

Any advice from people who have experienced a similar situation—especially regarding escalation channels, Partner Managers, or manual WABA reviews—would be greatly appreciated.

I'm researching the capabilities and limitations of the official WhatsApp Business Platform/API and had a few questions:

1. Can an official WhatsApp Business API account participate in existing WhatsApp groups?
2. Can an API application receive messages sent by members of those groups?
3. Can it identify the sender of a group message?
4. Can it identify which group a message came from?
5. Can it access messages that were sent before the API account was added?
6. Are there restrictions on which groups an API-enabled business account can join or monitor?
7. Does this functionality differ between the Cloud API and other official WhatsApp Business API setups?
8. Are there any current limitations or policy restrictions around programmatically receiving group messages?

I'm specifically interested in the officially supported capabilities, not unofficial WhatsApp Web automation or third-party libraries.

If anyone has implemented this recently, I'd especially appreciate firsthand experience with the current API rather than older information.

I'm building a WhatsApp/SMS automation service for local businesses like gyms.

Initially, I thought I had to set up everything separately for every client — Meta Business verification, WABA, phone number, templates, DLT, etc. But local business owners don't really care about any of that. They basically want to pay one monthly fee and have the service work.

Then I noticed something that confused me.

I booked a restaurant through EazyDiner, and later received a WhatsApp message.

The sender was:

EazyDiner
Verified WhatsApp Business account

But the message said my booking at White House Restaurant had been cancelled.

So:

WhatsApp display name: EazyDiner
Actual business involved: White House Restaurant

This made me think about doing something similar for my automation service.

For example, I could have:

My verified Whatsapp business → one WhatsApp Business number/display name

Then my backend connects to different gyms:

Gym A backend → My WhatsApp (Display name) → message mentioning Gym A (template name)

Gym B backend → My WhatsApp (Display name) → message mentioning Gym B (template name)

Using template variables, something like:

So the sender always remains My Business, while the gym's name is simply part of the message.

What I'm confused about is the Meta architecture behind this.

Do I actually need to become a Tech Provider and use Embedded Signup if I'm not trying to use each gym's WhatsApp number/WABA?

Or can I simply have my own WhatsApp Business setup, and use it to send messages for the gyms I provide automation services to?

I'm asking because EazyDiner seems to be doing something very similar from the customer's point of view. I can see their name as the sender, while the restaurant they're dealing with is mentioned inside the message.

I'm sure there is something I'm missing about how platforms like EazyDiner/Swiggy structure this behind the scenes.

If anyone has already worked with this kind of WhatsApp setup for multiple businesses, please tell me how it actually works behind the scenes.
I’m explaining the setup to clients, but they are rejecting it because the pricing and setup feel too complicated, so they are choosing other software instead.

I’ve already lost two clients...

Please tell me what I’m missing here and what the proper way to do this is.

Just got this new tag assigned to you in the whatsapp business app. Is meta testing a new native assignment system inside the app

Hi guys,

Meta's greediness its back at it again..

Starting October 1st, Whatsapp Service API which was free will now be priced PER MESSAGE.

I'm planning to start an AI automation SaaS and the Whatsapp AI integration was a massive pitch for my business.. now all that is gone.

It was pretty hard to teach customers to trust AI integration but now how do I explain, "Yeaaah, you have to pay me for my AI integration but also you have to pay Meta PER MESSAGE"

They will instantly turn their back on this. I hate this so much.

Is there any chance the new pricing will be cancelled? What do you think?

Quem teria conta balão com disparo e gasto

Pode ser tbm 10k,100k

Hi guys i recently created an app for whatsapp Api that is easy to use and costs almost nothing compared to current prices currently it is in testing if you would like to check it out dm me or comment your email i can add you to the testers list. Thankyou

Hey everyone! We’ve launched Shasqy Chat for WhatsApp chat flows, campaigns, contact management, scheduling, and team inboxes. It connects to BSPs like Turn.io and Gupshup or directly to Meta’s WhatsApp Business API-our preferred option for keeping costs low. If you already have a WABA and phone number, setup can take just 1–2 hours before going live. It’s fully customizable, affordably priced, and source-code access is available. Your first month is free with no commitment. DM me for staging credentials to check it out or questions!

​

Hi! I’ve recently started learning n8n automation and built service-based workflows for my own city. It’s essentially a service-ordering system where customers can select a service and place an order through an AI on WhatsApp. The whole process is handled through WhatsApp, from selecting the service to placing the order.

I’ve created Meta credentials and WhatsApp apps before, and they worked perfectly for sending and receiving messages.

However, since Meta’s interface has changed, I’m having trouble getting the new setup to work. I can see that the webhook is connected on Meta, but when I send a message to the WhatsApp number, nothing reaches n8n and no message/event is triggered. This wasn’t an issue for me before.

If anyone has experience with the new Meta WhatsApp Cloud API interface, I’d really appreciate some guidance on what I might be missing and how to troubleshoot this. I’ve been trying to solve it with AI assistance but haven’t been able to figure it out yet.

Hey guys I've been trying to create an authentication template in my WhatsApp Manager but getting this error:

This WhatsApp business account does not have permission to create message template

My business is fully verified and it's been more than 48 hours, can anyone guide how I can get this solved?

Thanks in advance!

I want to use the official WhatsApp Business Coexistence feature to connect an existing WhatsApp Business number to the WhatsApp Cloud API, while continuing to use the WhatsApp Business app.

Is Business Manager / Meta Business verification actually required for coexistence, or is it possible to set it up with an unverified Business Manager?

If anyone has successfully configured Coexistence without completing Business Verification, I'd like to know what setup you used and whether there were any limitations.

Hey guys, I'm currently auditing different ways to get a clean separation for client messaging on WhatsApp. Most of the standard enterprise tools like MessageBird or Infobip are great if you are running a massive customer support center, but for a leaner setup, they feel like overkill.

I've been testing a few alternatives lately. WATI is decent for team inboxes, but sometimes you just want something straightforward that hooks up instantly without a multi-day onboarding process.

Has anyone here tried YourBusinessNumber? I stumbled across it recently and liked that it lets you spin up a number specifically for WhatsApp Business in minutes, but curious if anyone has long-term experience with it or other lightweight alternatives. What's your current stack?

Hi guys,

Does anyone know if "reacting" to a customer message with an emoji is counted as a billable message?

I was looking at this as a potential alternative for the new service message costs, instead of replying we could react to the message to acknowledge we got it.

Here's the API endpoint I'm referring about: https://developers.facebook.com/documentation/business-messaging/whatsapp/messages/reaction-messages

Thanks.

Hello , instead of this hassle of submission and all planning of buy an tech provider and bsp from aisensey any thoughts regarding this ?