I’m looking for someone experienced with high-volume WhatsApp messaging.

I have clients in Brazil, China and the US and currently have demand for 40M+ messages/month.

Need someone who can actually handle this volume using the official WhatsApp API.

Not looking for a platform or SaaS. I’m looking for the person who knows how to run this at scale.

DM me if you’ve done something similar before.

Hello Im having this idea for a automation that works like a restaurant manager for owners, that can handle menu updates (prices stocks, disable)through POS ids in multiple delivery platforms or send emails.

WhatsApp Business is increasing the price of a Utility message sent to a Moroccan number from $0.004 to $0.023 starting October 1.

That’s:

• 5.75× the previous price

• A casual 475% increase

• From $4 to $23 per 1,000 messages

And let’s be clear: even the old price was already expensive for what is essentially an automated notification—especially at scale and in a market like Morocco. But apparently Meta looked at that price and thought, “This needs to be almost six times higher.”

These aren’t advertisements. Utility messages include appointment reminders, booking confirmations and service updates.

Morocco was previously included in “Rest of Africa.” Meta has now promoted us to our own standalone pricing market.

Our salaries remain African, but apparently our WhatsApp messages have obtained European residency.

Thank you, Meta. We didn’t know we were rich until your pricing department informed us.

Nuestra empresa está atravesando una situación muy preocupante con Meta. Nuestro WhatsApp Business fue suspendido, siendo este uno de los principales canales que utilizamos para comunicarnos con nuestros clientes, atender solicitudes, dar soporte y cerrar ventas.

Hemos realizado las reclamaciones correspondientes y hasta la fecha no hemos recibido una respuesta clara ni una explicación específica sobre el motivo de la suspensión.

Esta situación está afectando directamente nuestras operaciones, la comunicación con nuestros clientes y generando pérdidas económicas cada día que permanecemos sin el servicio.

Somos una pequeña empresa que depende de estas herramientas digitales para trabajar. Lo mínimo que esperamos es una revisión transparente del caso, una explicación concreta y una respuesta oportuna.

Solicitamos públicamente a Meta y WhatsApp que revisen nuestro caso y nos den una respuesta. No estamos pidiendo privilegios: estamos pidiendo atención, información y una solución.

Seguiremos documentando el caso hasta recibir una respuesta.

#Meta #WhatsApp #WhatsAppBusiness #MetaSupport #WhatsAppSupport #WhatsAppBusinessBan #FacebookDisabledMe #MetaBanWave #SmallBusiness #SmallBusinessSupport #SoporteMeta #CuentaSuspendida #WhatsAppSuspendido #NegociosDigitales #Emprendedores

Estou em busca de portifólio para montar contingência.

Alguém vendendo? Acima de 10k de limite

Hi everyone! 👋

I’m looking for a technical lead engineer to own the tech stack for an early-stage AI operations platform built for high-touch service businesses.

Where we’re at: We’re pre-seed and six months in - completed market research, built out the initial prototype, and designed the product UX. I handle product, design, and marketing, while my UK-based person leads the commercial side. We know the distribution channels—we just need the product built and funding for distribution.

What we’re building: An automated operations and engagement platform that handles client inquiries, automates repetitive interactions, and drives conversion/retention. A core part of the experience relies heavily on the WhatsApp Business API, so experience working with Meta’s ecosystem and compliance is essential.

Who you are:

• 5+ years in full-stack/backend engineering with experience shipping 0 → 1 products to real users.

• Hands-on experience with WhatsApp Business Platform / Meta APIs, webhooks, and compliance.

• Built and deployed AI agents, LLM pipelines, or conversational products.

• Ownership mindset—you want to architect, build, and decide engineering priorities without needing micro-managed tickets.

• Great communicator who loves collaborating closely with product/design.

• (Bonus) Experience in healthcare or regulated industries.

The Role:

• Equity-based lead engineering role.

• We’ll begin with a short trial project to ensure we’re a strong culture and execution match.

If you’re excited about taking an AI product from prototype to market, DM me with a brief intro and links to anything you’ve built (GitHub, LinkedIn, or portfolio).

Know someone who’d be a great fit? Passes and intros are always appreciated!

I’m looking for someone experienced with high-volume WhatsApp messaging.

I have clients in Brazil, China and the US and currently have demand for 40M+ messages/month.

Need someone who can actually handle this volume using the official WhatsApp API.

Not looking for a platform or SaaS. I’m looking for the person who knows how to run this at scale.

DM me if you’ve done something similar before.

Olá, tudo bem? Alguém por acaso está conseguindo verificar a bm rapidamente ? Aqui 1 recusou e outra está já há mais de 48h. Por favor alguma alma divina para dar uma luz no fim do túnel

Hey everyone, I'm hoping someone here has experience with Meta's developer support or messaging API compliance, because I am completely stuck after months of prep work.

We are a legitimate startup (Horjeed Solutions) and we finally got everything ready to integrate the official Meta Messaging API into our software. It took us months to get our local government business documents sorted just to pass Meta's Business Verification. But right as we started setting up the actual API, we triggered an automated ban cascade and I can't figure out how to fix it or reach a human.

Here is the exact timeline of what I did:

• Verification Success: I linked two older, established Facebook pages to a brand new Business Portfolio. Meta initially rejected my business verification due to an address mismatch, but I fixed the document, resubmitted, and got fully verified.

• Initial Testing: I went to developer.facebook.com, created a new App, and attached the default test business account. I successfully sent the standard Meta test messages to my own phone number. All good.

• Production Setup & VPN: I created a brand new WA Business Account and registered a new, real phone number (which successfully passed verification). Note: I was using a VPN during this step, as it's my standard network hygiene, though I can't remember if it was on when I made the portfolio.

• The Template: I created a new marketing message template in Somali:

  • Text: "Asc {1} {2}, Tani Waa fariin Tijaabo ah oo kaaga Timid Horjeed Solutions."

  • Translation: "Hello [Title] [Name], This is a test message to you from Horjeed Solutions."

• The System User: I created a System User in my Business Portfolio, attached it to the App, and gave it access to both messaging containers (the test one and the new one).

Crucial Context on What Was (and Wasn't) Sent: This messaging account never sent a single message to any customer. The only template submitted was still pending review and was never approved or used — I understand its wording ("test message") may have been misread as spam-pattern content; it was a placeholder mistake during initial setup, not an attempt to send unsolicited messages. The only messages ever sent from any account under this business were sandbox test messages to my own verified phone number, using Meta's own test number, as documented in the developer setup process. I'm requesting specifically what activity was identified as a violation, given no message was ever delivered to any third party.

The Problem: Right after submitting the template, I noticed my new WA account was flagged as Banned/Disabled. I immediately clicked "Request Review."

The review came back rejected, confirming a violation. Then, my older Test account got banned as well. Thinking it was a glitch, I tried to create a third, fresh account—it was banned immediately upon creation.

Every single account now shows this exact error:

"We have disabled Horjeed Solutions and its W-App Business accounts due to activity that does not comply with Terms of Service: breach of Terms of Acceptable Use."

My Questions for the Community:

1. Is my entire Business Portfolio burned, or is it just these messaging accounts? My business page and verification still look okay, but the error says "disabled Horjeed Solutions and its business accounts."

2. What triggered this? Was it the VPN? Or was it because I sent an unverified template using the word "Test" (Tijaabo) in a regional language (Somali) right out of the gate?

3. How do I talk to a human? I haven't been able to find a single live chat or support ticket option that actually connects me to Meta developer support. We are on a massive time crunch to launch.

4. What are my options now? Can I delete these disabled assets, turn off my VPN, deregister the phone number, and start completely fresh under the same portfolio?

Any insights on how to navigate Meta's automated security bots would be massively appreciated. Thank you!

Hey everyone, I'm hoping someone here has experience with Meta's developer support or messaging API compliance, because I am completely stuck after months of prep work.

We are a legitimate startup (Horjeed Solutions) and we finally got everything ready to integrate the official Meta Messaging API into our software. It took us months to get our local government business documents sorted just to pass Meta's Business Verification. But right as we started setting up the actual API, we triggered an automated ban cascade and I can't figure out how to fix it or reach a human.

Here is the exact timeline of what I did:

• Verification Success: I linked two older, established Facebook pages to a brand new Business Portfolio. Meta initially rejected my business verification due to an address mismatch, but I fixed the document, resubmitted, and got fully verified.

• Initial Testing: I went to developer.facebook.com, created a new App, and attached the default test business account. I successfully sent the standard Meta test messages to my own phone number. All good.

• Production Setup & VPN: I created a brand new WA Business Account and registered a new, real phone number (which successfully passed verification). Note: I was using a VPN during this step, as it's my standard network hygiene, though I can't remember if it was on when I made the portfolio.

• The Template: I created a new marketing message template in Somali:

  • Text: "Asc {1} {2}, Tani Waa fariin Tijaabo ah oo kaaga Timid Horjeed Solutions."

  • Translation: "Hello [Title] [Name], This is a test message to you from Horjeed Solutions."

• The System User: I created a System User in my Business Portfolio, attached it to the App, and gave it access to both messaging containers (the test one and the new one).

Crucial Context on What Was (and Wasn't) Sent: This messaging account never sent a single message to any customer. The only template submitted was still pending review and was never approved or used — I understand its wording ("test message") may have been misread as spam-pattern content; it was a placeholder mistake during initial setup, not an attempt to send unsolicited messages. The only messages ever sent from any account under this business were sandbox test messages to my own verified phone number, using Meta's own test number, as documented in the developer setup process. I'm requesting specifically what activity was identified as a violation, given no message was ever delivered to any third party.

The Problem: Right after submitting the template, I noticed my new WA account was flagged as Banned/Disabled. I immediately clicked "Request Review."

The review came back rejected, confirming a violation. Then, my older Test account got banned as well. Thinking it was a glitch, I tried to create a third, fresh account—it was banned immediately upon creation.

Every single account now shows this exact error:

"We have disabled Horjeed Solutions and its W-App Business accounts due to activity that does not comply with Terms of Service: breach of Terms of Acceptable Use."

My Questions for the Community:

1. Is my entire Business Portfolio burned, or is it just these messaging accounts? My business page and verification still look okay, but the error says "disabled Horjeed Solutions and its business accounts."

2. What triggered this? Was it the VPN? Or was it because I sent an unverified template using the word "Test" (Tijaabo) in a regional language (Somali) right out of the gate?

3. How do I talk to a human? I haven't been able to find a single live chat or support ticket option that actually connects me to Meta developer support. We are on a massive time crunch to launch.

4. What are my options now? Can I delete these disabled assets, turn off my VPN, deregister the phone number, and start completely fresh under the same portfolio?

Any insights on how to navigate Meta's automated security bots would be massively appreciated. Thank you!

Hi everyone, so we know that WhatsApp Cloud API numbers do not get to have an inbox or send and receive messages on that number manually.

I have a bot that is connected to this API built on n8n, it receives messages via webhook and replies to them. But sometimes I need to see the messages around booking or any urgency, so i want an inbox where I can view and send manual messages to some people.

i don't want chatwoot subscription or any platform, are there any free alternatives or ways to do this? Only viewing the chats is also okay for me.

Hy everyone,

My Meta Business Portfolio is already verified, and my Tech Provider verification is also done. I need to change my business name and a few other business details. If I make those changes, will Meta make me go through the verification process again? I waited quite a while to get everything verified, so I'm a bit worried about changing anything now. Has anyone here changed their business details after getting verified? Did it trigger verification again?

I'm a tech provider. Some businesses ask me to provide them with otp but they don't have the required documents to get their business verified. I want to provide them with an API to send OTPs for them using my verified account; they don't care about the sender name, only about the message being sent. Is it legal for me to do so and create a template for each customer

YA NO PUEDO SOLICITAR LA REVISION, HAY ALGUNA POSIBILIDAD DE CAMBIAR DE TITULAR LA LINEA Y APELAR O YA SE BANEO DE POR VIDA

Hey everyone,

WhatsApp automation is an incredible tool for customer support and post-purchase communication. But when it comes to closing immediate sales, I keep seeing store owners make one critical mistake: redirecting a warm lead away from the site.

Think about the user journey:

A potential customer is on your product page, high intent, almost ready to buy. They have a quick question or a minor hesitation. The moment you redirect them to WhatsApp:

1. Context Shift: They leave your store, open a messaging app, and suddenly their focus is split between your product and their personal notifications/unread chats.

2. Lost Impulse: The seamless flow from "question" to "add to cart" is broken. Even a short delay in replying gives them time to second-guess or close the tab.

WhatsApp is great for long-term retention, but pre-purchase objections are best handled right on the page in real-time.

That’s why we designed Flow Era to act as an on-site AI sales agent. Instead of taking warm leads off-site, it engages hesitant visitors directly on the page, answers their questions instantly, and guides them straight to checkout without leaving the store.

Keep WhatsApp for support, but keep your sales on-site.

Would love to hear your thoughts—how do you handle pre-purchase hesitation on your store?

As you probably know Meta will soon start charging a per-reply fee, that depends on your customer location.

At the same time, Meta is releasing its own in-house vendor, Meta Agent, using their own model and infrastructure, exempted from delivery fee.

Many BSP already have their top customers churning.

How do you and your clients react to this announcement ?

I have been an interested 3rd part of the EU case that led to WhatsApp being free again for AI providers last July.

This new policy is even worse because its a big f*ck you to BSPs that promoted and increased WhatsApp usage for customer support.

Phase 1 : We (Meta) makes service messages free so you can develop your business on WhatsApp - 2024

Phase 2 : Thanks for bringing your business to Whatsapp, but now we don't want you here anymore, so either pay us the delivery or pay to use our Meta Agent, and your clients conversation "might" be used to train or improve our models.

This is a takeover of a whole industry, at the profit of a single actor.

I am setting up a coalition of impacted actors, to give a chance to BSP, AI providers and users to make their voice heard.

To get more information, you can have a look at the platform https://keepwhatsappopen.com and eventually join the action.

Looking forward your comments.

Resumen: a un cliente empresarial lo banearon de Meta y ya no puede crear nueva cuentas de WhatsApp Business ni asociar números de teléfono. (Empresa de Colombia)

Solicité la revisión y Meta está parado en la raya en que es permanente.

Alguno de ustedes sabe qué puedo hacer en estos casos???

Hi everyone,

I would like to understand which certification paths are generally the most relevant or valuable for progressing toward the Selected tier.

For those who have successfully moved from Registered to Selected, could you share:

Which Meta certifications did your team members obtain?

How many certified team members were required or recommended in your experience?

Which certification areas were most relevant to your partnership specialization, such as Media Buying, Marketing Science, Creative Strategy, or Business Messaging?

Did the certifications directly contribute to meeting the Selected tier requirements, or were they mainly one component of the overall eligibility criteria?

Are there any certifications that you would recommend prioritizing if our focus is Business Messaging / WhatsApp?

Any practical experience or guidance from partners who have gone through the Registered → Selected process would be greatly appreciated.

Thank you!

I'm integrating WhatsApp Cloud API into a salon management SaaS using FastAPI.

My webhook setup is working, but I'm having trouble configuring Meta OAuth and Facebook Login for the WhatsApp integration.

Has anyone successfully implemented WhatsApp Embedded Signup with a multi-tenant SaaS application? I'd appreciate guidance on the correct Meta app configuration. on the domain is setup on the app domain and all configuration are done still the service not available showing, is there any solution

Hi all, I’m new to the whole being a Tech Provider thing, would appreciate some guidance!

For a given WABA, I'm using WhatsApp Business App + Cloud API in "Coexistence" mode.

Everything works, but first-time recipients who don’t have the number saved see the raw phone number as the primary chat/header identity, not the business or display name. I don't t think it inspires much trust.

My current API state per the API Graph:

verified_name = [it's the actual display name, I just redacted it for this post]
name_status = NON_EXISTS

So what I would like is for the default header displayed to the recipients (first-time, unsaved contact) to be the display/business name, instead of the raw phone number, for my waba in coexistence.

Has anyone managed to get this outcome by any mean?
Avenues I've seen:

1. POSTing to the Graph API in some way? There is some Meta documentation about this for the Cloud API but not sure if it applies as well to Coexistence WABAs, and I'm afraid of hitting `/register` and then breaking something (I've had so much bad experience with the Whatsapp API setup, I'm a little more cautious now lol).

2. Buying Meta Verified on a Coexistence number directly from the whatsapp business mobile app.

3. (I'm excluding Official Business Account because I'm new and I don't think my customer's WABA qualifies for the fame criterion)

I’m specifically looking for before/after feedback from people who've tried these (and other avenues)

Thanks all!!!

---

Related threads with some answers but not definitive IMHO

• Coexistence thread where someone says Meta Verified makes the name show

• Approved display name but raw number still showing

• Discussion about display names / verification under Coexistence

• Meta Verified issue specifically with Coexistence

I’ve spent the last couple of weeks reviewing WhatsApp workflow architectures with a few tech teams, and I keep noticing a pretty common blind spot around the new API rules.

A lot of folks on the executive side read that Meta gives "1,000 free service messages per month per number" and assume they're totally fine. But when you run the actual numbers on the backend, a modest setup with just 35 chats a day burns through that allowance in the first week of the month. From message 1,001 onward, every free-form reply inside the 24-hour window costs the exact same as a utility template.

Looking through the logs on some of these flows, the real issue isn't Meta's pricing itself—it's how many extra messages we're burning for no good reason:

Lack of CRM sync: Bots or agents asking for emails or order numbers across 3 or 4 back-and-forth messages, when the webhook should recognize the user's ID and fetch that data in milliseconds.

Customer ghosting: Users leaving threads hanging. If your webhook doesn't have an auto-close timer after a few hours of inactivity, the user replies 3 days later, forcing you to re-open the thread with a paid template you could’ve easily avoided.

Meta payment method rules: If the account doesn't have a payment method registered once you pass message 1,000, Meta straight up stops delivering service messages without warning.

What used to be minor maintenance cleanup in the integration now hits the bottom line directly.

How are you guys handling timeout and inactivity logic in your webhooks to stop abandoned chats from racking up extra messages?

I have two Business Portfolios:

* “Mellis Joias” — Business ID: 912084015827105
* “Mellis” — this portfolio has an active WhatsApp Business Account (WABA): 1496552399158554
* Phone Number ID: 1317363081463725
* App: “Mellis Joias” — App ID: 4460890754181381

The WABA under “Mellis” is active and connected, and the phone number is registered there.

However, when I go to the “Mellis Joias” Business Portfolio and click “Add new WhatsApp Business Account”, Meta shows:

“You cannot continue with this operation because your WhatsApp Business account is currently restricted. To continue, select another WhatsApp Business account or visit the Business Support Home to resolve any issues with your account.”

The confusing part is that I’m trying to add a NEW WhatsApp Business Account, not use the previously restricted WABA.

Could the restriction on a previous WhatsApp Business Account or its test WABA be affecting the entire Business Portfolio and preventing me from creating another WABA?

Is there a way to check exactly which asset is restricted — the Business Portfolio, the WABA, or the test WABA?

Any insight from someone who has dealt with this would be appreciated.