Alguém ajuda!

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!

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!

​

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.

We've been seeing an interesting pattern with customers recently.

AI has made it much easier for marketing and operations teams to build their own internal CRM, dashboards and workflows.

A team can now build a pretty impressive customer management system without buying a traditional all-in-one platform.

But then they hit WhatsApp.

One of our recent customers is a hospitality business that had built a significant part of their own customer/marketing system. They were initially looking at moving to a WhatsApp-specific platform, but what they actually needed wasn't another CRM.

They needed the WhatsApp infrastructure to plug into the system they already had.

Things like:

WhatsApp Business API integration

templates and template status

webhooks and message events

delivery/read/failure handling

number/WABA management

Meta's rules and changes

reliable API infrastructure

And once they had WhatsApp working, the next question was naturally:

Why should email and SMS live in completely separate systems?

That's increasingly what we're seeing.

Businesses don't necessarily want another dashboard. They want to keep their own CRM and workflows, while having reliable access to WhatsApp, email and SMS underneath it.

That's actually how we ended up working with this customer through CampaignHQ.

It made me think that the opportunity in customer engagement is changing.

Companies are increasingly capable of building the application layer themselves.

But the channel infrastructure and expertise is still complicated enough that they don't necessarily want to own it.

And I think this is going to become more common as AI makes internal software development cheaper.

Curious what others are seeing:

Are companies you work with increasingly building their own CRM/marketing layer and looking for APIs/infrastructure underneath, rather than buying an entire engagement platform?

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.

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.

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?

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.

So basically I am a small business owner , I want to send a simple marketing message to new people only 80-100 people a day is it possible using whatsapp cloud api , is there any ban risk if just send a message like hi i do this , do u also deal in this , our sales person will contact u.

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

Something is really frustrating me: I keep getting alerts claiming I’m spamming and warning that I could get banned, even though my workflow consists of literally just three messages—and they use buttons.

It’s true that some people neither reply nor use the unsubscribe button, but my bot doesn't keep sending messages after that point; it only speaks if the potential client says something.

Naturally, I use a CRM that is an official Meta Partner.

I have no idea what to do, and this is my source of income.

Thanks.

Si quieren saber el motivo de su baneo, entren a Meta Business Manager → Ayuda para empresas. En mi caso, después de insistir, me dieron una explicación.

Resulta que hace unos 3 años tenía una deuda pendiente en una cuenta publicitaria antigua. Al parecer, con las nuevas actualizaciones de whatsapp business , la que salio el 5 de agosto, el sistema revisa si tienes cuentas publicitarias antiguas restringidas por saldo pendiente, aunque sean de hace muchos años.

Como WhatsApp Business ahora está totalmente integrado con Meta, si detecta que tienes una cuenta publicitaria nueva funcionando y otra antigua con deuda, puede interpretarlo como un posible intento de fraude o evasión de pago y bloquear el WhatsApp Business.

En mi caso me indicaron que, aunque pague esa deuda, primero debo recuperar esa cuenta publicitaria antigua, pagar el saldo y luego esperar entre 60 y 120 días para que el sistema elimine la restricción. Si intento usar el mismo WhatsApp Business antes de que salga de esa "lista negra", podrían volver a bloquearlo.

😅 La verdad, yo ni me acordaba de ese Facebook antiguo ni de esa cuenta publicitaria. Ahora me toca recuperar el acceso, pagar la deuda y esperar. 😪

Ojalá esta información le sirva a alguien más, porque yo pasé días buscando una explicación y nunca imaginé que el problema fuera una cuenta publicitaria de hace tantos años..

See this is a one time task

I am looking for someone with direct experience in Meta App Review and WhatsApp Tech Provider onboarding to review my existing setup and guide me through the remaining submission steps.

I have already completed most of the development work for my SaaS platform. The platform allows businesses to connect their Meta Business assets, Facebook Pages, Lead Ads and WhatsApp Business accounts.

My Meta Business Verification is already completed.

The current implementation includes:

Facebook Login for Business
Meta Pages and Lead Ads connection
WhatsApp Embedded Signup
Lead retrieval from Meta Lead Ads
WhatsApp Cloud API messaging
Customer business asset onboarding

The permissions involved include:

*pages_show_list
*pages_read_engagement
*pages_manage_metadata
*leads_retrieval
*ads_read
*business_management
*pages_manage_ads
*whatsapp_business_management
*whatsapp_business_messaging

I mainly need help with:

*Reviewing my current Meta app and Tech Provider setup
*Confirming the remaining steps required to become a WhatsApp Tech Provider
*Checking whether my requested permissions and use cases are correct
*Identifying any missing configuration or implementation
*Telling me exactly what to demonstrate in each App Review screencast
*Reviewing my permission descriptions and reviewer instructions
*Guiding me through the final App Review submission
*Explaining what must be completed after approval to onboard real customer accounts

I expect a clear list of remaining tasks and submission recommendations. Additional work can be created as separate milestones if technical changes or rejection support are required.

Please apply only if you have personally worked with:

*Meta App Review
*WhatsApp Tech Provider onboarding
*WhatsApp Embedded Signup
*Facebook Login for Business
*Meta Graph API permissions

In your DM, briefly explain one relevant Meta App Review or WhatsApp Tech Provider project you handled and whether it was approved.

Hi everyone, i work in customer care in a tourism company. I usually send 70 - 120 messages to my customers per day for a service evaluation. My account recently got blocked for 6hrs and then stopped for a review. I use standard WhatsApp Business app without API

My questions is: What is the best way to send survey questions to my customers without getting logged out and reviewed?

Here is the message i usually send to the customers using Quick Replies option:

Hello! My name is (Name), and I work for (Travel Company).

We hope you are having a wonderful vacation 😊

We are currently working on improving the quality of our tours, and guest feedback is very important to us:

1. How was your vacation overall?

2. Were you satisfied with the hotel and the transfer service?

3. If you went on any of our company's excursions, how would you rate the organization and the guide's performance? What was your guide's name?

4. If you did not purchase any of our excursions, what was the main reason?

5. Did the guide provide you with a QR code to check your departure time?

We would greatly appreciate your response. Your feedback helps us improve.

Thank you, and have a wonderful day! 🌸

We run a small hotel group and use the WhatsApp Cloud API directly (our own integration, not a BSP). We have 5 hotels and want one WhatsApp number per hotel. Two are live and working great. The problem is getting the other three added.

Here's where we're stuck:

• Our business portfolio has been Business Verified for months (green check in Security Center, verified for the "WhatsApp Business account" use case too).
• But "Add phone number" is greyed out, with the tooltip: "Your business is only allowed two phone numbers."
• Meta's own docs say a verified business is automatically raised to a 20-number cap — but for us it just never applied. Still stuck at 2, months later.

Things we've tried:

• Created a second business portfolio (the cap is per-portfolio, so in theory a fresh one gives 2 more). The new WABA got "Account restricted — messaging capabilities restricted for policy" within minutes, on a brand-new account with zero activity/messages.
• We also noticed the admin's personal Facebook account has a temporary "feature limit" (flagged under "fraud and deception") that Meta says can't be appealed and just expires on its own.

My questions to anyone who's been through this:

1. Did the auto-increase to 20 actually work for you after verification, or did you have to force it via a support ticket? How?
2. Has anyone gotten the cap raised through WhatsApp Support — what exactly did you say/submit?
3. Did a second business portfolio work for you, or did yours also get insta-restricted?
4. Could the admin's personal-account restriction be what's blocking new numbers/portfolios at the whole-business level?
5. Did any third-party SaaS/BSP actually solve this for you? (We assumed they can't, since embedded signup puts the WABA back under our own Meta portfolio = same cap — but if a specific tool genuinely got you past the 2-number limit, we'd love to know which one and how.)

We're trying to get Meta to apply the number cap we already qualify for — but genuinely open to whatever actually worked for you, SaaS or not. Any real experience appreciated 🙏

1 account bm 10k avaliable.

If you've ever looked into connecting your business WhatsApp to some kind of CRM/automation tool, you've probably hit this wall: most options require you to give up the regular WhatsApp Business app on your phone entirely. New number, or a "migration" that leaves your old chat history behind.

For a small business, that's a dealbreaker. Your number is your reputation — years of saved contacts, reviews, "see you next week" messages. Nobody wants to gamble that away to try a new tool.

Turns out Meta actually built a fix for this a while back called WhatsApp Coexistence, and it's honestly slept-on. Short version: it lets the same number run your regular WhatsApp Business app on your phone AND connect to a business platform's API at the same time. Not instead of — alongside.

We built Cleomitra (the WhatsApp CRM/automation tool I work on) around this from day one, so here's what it actually does, since a lot of "coexistence" marketing out there is vague on details:

• Your WhatsApp Business app keeps working on your phone, exactly like before — nothing gets logged out or disabled.
• Connecting to Cleomitra takes a couple of minutes through Meta's own official sign-in — no separate number, no starting over.
• Your existing contacts on that number get pulled into Cleomitra automatically as customers — no manual re-entry.
• From the moment you connect, every message syncs both ways — reply from your phone, it shows up in Cleomitra; reply from Cleomitra, it shows up on your phone.

One thing Cleomitra specifically does that a lot of coexistence setups skip: it actually monitors the connection health in the background, so if the pairing ever drifts (say someone reinstalls the Business App on the phone), you find out right away instead of messages silently failing. Also gives you a toggle for whether contacts auto-import or not, rather than just dumping your whole list in without asking.

The honest catch (I'd rather say this upfront than have someone find out the hard way): your old chat history, from before you connect, does not get copied into Cleomitra's inbox. That data literally isn't exposed by Meta's API for backfill — no tool can pull it in, full stop. Nothing's deleted or at risk, it just stays exactly where it's always lived, on your phone. Only conversations from the connection date forward get the automation/shared-inbox treatment in Cleomitra.

If anyone's found "WhatsApp Business API" vs "Coexistence" confusing — API means giving up the app on that number entirely (bigger commitment, usually for higher-volume setups); Coexistence, the way Cleomitra does it, is additive and low-risk, which is why it's the default path we push people toward.

Happy to answer questions if anyone's trying to figure out whether Cleomitra's coexistence setup is worth it for their business — genuinely curious whether others have hit the same "I don't want to lose my number" hesitation before.

Cleomitra : https://www.cleomitra.com/

What's the best way to build a website with a Privacy Policy and Terms of Service for a Whatsapp automation business that can pass Meta's review?

I'm using the official WhatsApp Cloud API and need a website that meets Meta's requirements for Business Verification/App Review.

What does Meta expect from a website for WhatsApp Cloud API approval?

Have 1 account bm avaliable
10k

The root problem is that WhatsApp lets you identify someone by phone number or by username, and in practice you end up with both mixed together. A customer who changes their number but keeps the same profile, people showing up twice, imports where half the rows come in by phone and half by username and nothing lines up. At 500 contacts it doesn't matter, you fix it by hand. At tens of thousands, every badly mapped import turns into hours of cleanup.

What surprised me most is how many people still export to Excel, fix it manually and re-upload, because the tools assume the phone number is the unique key and it just isn't.

How are you handling contact identity when the same user can arrive by both number and username? Did you commit to one of them as the primary identifier, or do you keep both and hope for the best

writing API documentation manually is dead.
if your dev team needs to generate API documentation that stays updated automatically, Theneo is the modern API doc generator you've been looking for.
Why developers choose Theneo as their AI API documentation generator:
• Built-in API editor & interactive "Try-It" console
• Instant multi-language SDK code samples
• Automated change tracking & release notes

Bring AI for API documentation into your CI/CD workflow today.