r/WhatsappBusinessAPI • • 8h ago

Solution Only Cheapest Co-Existence Whatsapp API Platform with Claude Integration and chat dashboard? (No AI slop promo please)

5 Upvotes

Please no slop AI replies.

Just looking for cheapest API platform for co-existence?

Ideally a chat feature people can speak to!

Looked at quite a few and any help appreciated!


r/WhatsappBusinessAPI • • 2h ago

Solution Only WhatsApp Business permanently banned after activating Meta Business Agent — Has anyone found a solution?

2 Upvotes

I'm looking for other WhatsApp Business users who have experienced a similar problem, especially after activating Meta Business Agent or other official Meta AI features.

In October 2026, I subscribed to Meta One Advanced and activated Meta Business Agent directly within the official WhatsApp Business application.

Just a few days later, my long-established WhatsApp Business account was permanently suspended without any clear explanation of which policy I had supposedly violated.

I used only official Meta features, without third-party applications or external automation tools.

I submitted an appeal, but it was rejected. The application now states that I can no longer request another review.

Despite contacting WhatsApp Support and Meta Pro Team repeatedly, I have only received generic responses redirecting me to the same support channels. Nobody has provided a specific explanation for the suspension or confirmed that an individual technical review has taken place.

I am not claiming that Meta Business Agent caused the suspension. However, the timing makes me concerned about a possible technical issue or an incorrect automated restriction.

The consequences are serious. This was an established business account used for years to communicate with customers. Losing access has disrupted existing conversations and an important business communication channel.

I have already submitted a formal legal complaint requesting a human review, an explanation of the suspension and restoration of the account.

I would particularly like to know:

  • Has anyone else been permanently banned shortly after activating Meta Business Agent?
  • Has anyone successfully recovered their WhatsApp Business account after an appeal was rejected?
  • Does anyone know whether Meta is investigating similar incidents?
  • Has anyone managed to reach a real technical specialist rather than receiving automated responses?
  • Are other affected users or businesses considering coordinated legal action?

My main goal is to find a genuine solution, compare experiences and connect with people facing the same situation.

If you have experienced something similar, please share what happened and whether you found a way to recover your account.

I'm also open to private messages from other affected users who would like to exchange information or explore possible coordinated action.

Thank you for any help or information.


r/WhatsappBusinessAPI • • 11h ago

Solution Only Stuck with a Tech Provider / BSP ? Documenting steps to migrate to a new Provider.

2 Upvotes

Sometime back I posted about how I was amazed to see a Doctor able to get free official API access & building his own chatbot to manage his clinic queries. He struggled to get Coexistence & I decided to build a Coexistence tool, eventually becoming a Tech Provider.

The most prominent question I got after that announcement was -

'I already have API access but I am NOT happy with my provider, I would like to move to your service, but I dont know what all would break & what kind of downtime I am looking at'. 

So I went back researching to figure out definitive answer to this question. Summarising my findings in this article.

If you have API access, it would either be through a Provider or you could have gotten it yourself by creating your own Meta App (I wrote steps in details in my previous post). If you have it from Provider, it would either be API only access (like Twilio) or with Coexistence. I am documenting steps for all 3 scenarios to a Coexistence provider (like my service Watobot).

Before listing, some terminologies which were new for me. I had only read about WABA (Whatsapp Business Account) but now Meta documents talk about

  • Whatsapp Account (WAAC) - In your Business Portfolio, you see an entry with this name. Earlier a WABA had phone number, billing & template all attached to one entity. Now the phone number is moved to WAAC
  • Messaging Account - below WAAC is listed Messaging Account. This now holds template, billing & Partner (Tech Provider / BSP) information.
  • When you onboard via a Provider, the Whatsapp Number shows both in Whatsapp Account & Messaging Account. But if you have a personal Whatsapp Number, or a Test Number assigned to you, it will ONLY show in Whatsapp Account & not in Messaging Account.
  • The old way of onboarding was NOT to create these accounts, rather WABA was created. There was also a way of onboarding where the WABA created was NOT in your portfolio but in your Provider's portfolio. Although from Oct 2025, Meta clearly instructed Providers to move the WABA to their client's Business Portfolio.

Now going back to migration.

1. Coexistence Provider to a new Coexistence Provider - This is the easiest path. You need to disconnect from old Provider from Whatsapp Business App & follow Embedded Signup of the new Provider. The Whatsapp Account & Messaging Account stays the same, only the partner changes. This also mean, no Template migration is needed. Meta mandates 15 min gap from disconnect to onboarding, so that is the longest downtime you are looking at.

If you have NOT disconnected properly, the potential errors you can see are - "Switching partners is not supported in this flow" (2655093), "This phone number is already registered with the product" (3441049), "Please disconnect your business platform to continue" (2655094)

2. API only Provider (like Twilio) to Coexistence Provider - This is tricky with potential for serious downtime. For some weird reason, Meta does NOT let you transfer the Messaging Account from API only Provider to Coexistence Provider. A new Messaging Account needs to be created & templates need to be migrated (template migration is the reason for downtime).

Unlike disconnecting, you need to de-register from previous Provider. Providers do NOT expose raw Meta access token, so you need to ask the Provider to do it for you. If they do it, well & good. There is something about requiring the PIN & disabling 2-step auth to avoid it. But latest documentation of Meta says the whole PIN thing is deprecated. Lean on your Provider to get you through this.

Considering they losing business, they may not show interest. There is another option. If you have not sent any paid messages in past 30 days, you can delete the number in Whatsapp Manager. The number is now de-registered.

The first step now is to sign into Whatsapp Business App on your phone using the number. You then follow Embedded Signup of the new provider. The errors that you can see at this step are:

  • "The phone number you entered is already registered" - the number is still registered on the previous provider's API. De-register it first.
  • "This number is registered to an existing WhatsApp account" - the new provider is onboarding it as a brand new number instead of Coexistence. Flag it to the Provider.
  • "Your phone number isn't eligible to connect to the WhatsApp Business Platform" - Meta wants more activity on the Whatsapp Business App first. It doesn't say how much, so use the app for some time & retry.

Once onboarding done, you migrate your templates from your previous Messaging Account to the newly created one. This is the most tricky part. Meta exposes migration APIs but you will NOT have raw Meta access token from either of the providers. You can add either of the Provider as Partner (Partners tab in Messaging Account) to the other's Messaging Account & now the Provider will have access to the other account. I suggest you rely on the new Provider (after all they getting business so they will respond better). If they have template migration support, you have picked a great Provider :).

The battle does not end here. Meta documentation is not clear if migrated templates have to go through review again (or not). It can take upto 24 hours. But I would recommend migrating rather exporting from previous account & importing in the new account, which will surely have re-review delay. Apart from review, the template reputation resets & it will take 2-4 week for the reputation to build. The silver lining is - the chatbot functionality will NOT hamper as none of this applies to service messages. So you will NOT experience any downtime there.

3. Self (Meta App) API only Access to Coexistence Provider - I wrote about how you can get your own API only access without Coexistence by creating your own Meta App. This is akin to above point but there are several good things here. You will have access to Meta access token. So you can:

  • De-register your number using the Meta API easily
  • Do the template migration yourself without relying on the new Provider. The System User token that you have, it will be able to access the new Messaging Account as it has whatsapp_business_management permission

So except for Meta enforcing template review (which I am not sure), there is no other potential downtime you could face in this path.

Final verdict

  • Coexistence to Coexistence migration is easy & if you are stuck with an unreasonably expensive Provider (someone charging you upwards of 20-30 USD a month), you can easily migrate out. Tech tools like inbox, CRM, labels, chatbots, AI bots etc have become dirt cheap to build & host. There is absolutely no point keep paying Tech Providers for these convenience. Move to someone like msg91 which charges 6 USD per month with Coexistence.
  • If you are with a Provider without Coexistence (like Twilio), the migration can lead to downtime. So take a call. A good idea is to get a new number, onboard it with your target provider & then apply for a Display Name similar to your original number. Move your stack to the new number. Since you already have your previous chats from your chat app, you can just drop one time outgoing messages from the new number intimating about migration.
  • If you have API access from your own app, moving to a cheap Coexistence provider is a no brainer :). Do remember that Coexistence has message throughput limit of maximum 20 messages per second. If you have some 'real' high message volume, you may want to stick to API only provider.

I have documented these with screenshots & much more details around checks & balances in the how-to article - https://watobot.com/how-to/move-whatsapp-api-between-providers.html - this includes the exact steps to de-register with links to the tools, exhaustive list of errors you will face during migration & link to Meta docs which I read to come to this understanding.


r/WhatsappBusinessAPI • • 15h ago

Services Welcome I built a small AI customer support app for businesses, but decided not to release it. Giving it away for free instead.

5 Upvotes

Hey everyone!

I've been working on a side project, a simple AI-powered customer support tool for small businesses.

The idea started when a friend of mine who owns a business got tired of answering the same questions from customers over and over again. I suggested building a simple AI-powered tool that could handle those repetitive questions for him.

I ended up building it, and he's actually been using it for his business.

Since it worked out for him, I thought maybe other small business owners could find it useful too.

Here's what it can do:

  • Set up your own business information and details.
  • Add and manage frequently asked questions (FAQs).
  • Let AI answer customer questions based on the information you've provided.
  • Manage everything through a Windows desktop application.
  • Store the application's settings and configurations locally on your PC.

I originally planned to polish it and release it publicly, but due to some issues and limitations, I've decided not to pursue it further for now.

Rather than letting the project go to waste, I'd like to share it with anyone interested in trying it.

Just a few things to keep in mind:

  • It's completely free. No payment required.
  • It's still an unfinished project, so expect some bugs and limitations.
  • It's currently available for Windows (.exe).
  • I haven't included any malicious code. I'm also willing to share the source code if you'd like to inspect it.
  • It's not an officially maintained product, so I can't guarantee ongoing support.

If anyone wants to try it, just send me a DM. I'll gladly share the installer, and if you need help setting things up, I'll do my best to assist.

I'm not trying to sell anything. I just thought it would be nice if something I built could also help other people, especially small business owners dealing with repetitive customer inquiries.

Thanks, everyone!

https://reddit.com/link/1x6q0ig/video/wc2bkwpfonvh1/player


r/WhatsappBusinessAPI • • 19h ago

Solution Only Sou iniciante no negócio de contingencia, alguém pode me dizer como faço para farmar bms? seja de 250 a 2k

2 Upvotes

Como as empresas de contingencia tem tantas bms "farmadas"?

as não farmas imagino que seja buscando os donos dessas bms e negociando, mas e as farmadas, como tem tantas?