r/WhatsappBusinessAPI

hi everyone! im having a problem where my whatsapp messenger is showing a screen saying “use [my whatsapp business number] for Whatapp Messenger?” it then gives an option to click that number or use a different number. when i click use different number and put in my regular whatsapp, it sends an SMS verification code, but it never arrives. it gives me the option to voice call but that doesn’t work either (I don’t have problems with my SMS carrier). then it just shows a pop up saying “you recently connected“

how do i fix it? nothing is working, i just want my regular whatsapp account back and my business one seperate.

also a couple days before that it said that my account was under review or something.

Hello everyone. I'm building an app for my company that is essentially a backend dashboard. The basics of the app are:

If an employee doesn't reply within a certain amount of time, an AI agent will reply to the customer. When the employee comes back, the AI will fall back.

All chats between the customer and the employee will be monitored. (I'm not sure if this violates any privacy policies.)

Of course, to achieve this, I need access to the API. However, as far as I know, the normal API doesn't allow you to access the Business App unless Coexistence is being used.

So my question is: How do I implement Coexistence? Do I need to become a Tech Provider? I read through the Embedded Signup docs, but I'm a bit confused.

Como está a questão pra subir 2k pra vocês? Normal? Travado?

Conocen alguna plataforma que me genere bot de WhatsApp que se integre con api a mi saas vibe coding usaba zernio pero lo veo obsoleto para bot WhatsApp

Solo building a CRM aimed at small business owners and founders who don't have a dedicated sales/ops team — the core idea is: connect your WhatsApp in a couple clicks, and every lead coming in across WhatsApp, calls, and web forms lands in one place instead of scattered across tools, with no two people on a team accidentally chasing the same lead.

It actually started as an internal tool I built for a dental clinic, and I'm now generalizing it to work for other small businesses — clinics, D2C brands, real estate, coaching institutes, etc.

Before I put more time into this, I'd rather hear the honest "this won't work because..." than build in a vacuum. So, genuinely:

- Does this sound like a real problem worth solving, or does it feel like a crowded space that's already been done well enough?

- If you've built or worked on something similar, what tripped you up — technically, or just in terms of getting people to actually switch from what they're using?

- Would you personally use something like this, or know someone who would?

Not sharing a link or asking anyone to sign up for anything, just want real feedback before going further. Appreciate any thoughts, positive or brutally honest.

​

I’m building a WhatsApp-based AI system for my company, and I’m calling the core system the WhatsApp Chatbot Brain.

The basic WhatsApp messaging is now working. The goal is to go beyond a normal chatbot that simply sends an LLM response.

The idea is to build a persistent business brain that can understand and remember:

Company information

Products and services

Customers and leads

Previous conversations

Business knowledge

FAQs and internal information

Context from previous interactions

Different businesses/clients using the same underlying system

The larger system I’m working on also includes CRM and automated lead-research components.

My current thinking is:

WhatsApp → WhatsApp Cloud API → Webhook/Backend → Chatbot Brain → Knowledge/CRM data → AI response → WhatsApp

I’m interested in making the Brain more structured rather than just putting everything into a vector database and hoping the LLM retrieves the right information.

I’d especially like feedback from developers who have built:

WhatsApp AI agents

Persistent AI memory systems

Business knowledge systems

AI + CRM integrations

Multi-tenant chatbot platforms

What would you change in this architecture?

Would you use a combination of structured database + vector search + conversation memory, or would you approach the “business brain” differently?

I’m particularly interested in practical architecture advice from people who have built this in production.

Can I migrate WhatsApp Coexistence from WATI to Make without losing eligibility?
I have an existing WhatsApp Business App number currently connected to Cloud API through WATI using Coexistence.

I want to eventually remove WATI and connect the same number directly to Meta Cloud API through Make.com, while keeping:
the same phone number
WhatsApp Business App active
Coexistence

When I try Make’s Coexistence onboarding now, Meta shows my existing number but marks it “Not eligible”, presumably because WATI is already the Coexistence/API partner.

Has anyone actually migrated a live Coexistence number from one provider to another?
Specifically:

Can WATI → Make/direct Cloud API be migrated without deleting/re-registering the number?
After offboarding WATI, does the number become immediately eligible for Make’s Coexistence onboarding?
Has anyone experienced a cooldown or temporary loss of Coexistence eligibility?
Is there a proper partner-to-partner migration process instead of disconnecting and re-onboarding?
I’m trying to avoid disconnecting WATI and discovering afterward that the number is stuck or ineligible for weeks.

I have a thesis that will probably annoy a lot of people in this industry:

Meta’s rising messaging costs, tighter rules, and the arrival of native AI agents inside WhatsApp Business are only the beginning.

I think Meta ultimately wants to capture a much larger share of the conversational commerce and customer service market that third-party companies have spent the last 5–7 years building on top of WhatsApp.

For years, something extremely convenient happened for Meta.

Thousands of SaaS companies built customer support platforms, WhatsApp automation, chatbots, conversational CRMs, sales tools, AI assistants, marketing automation and support workflows.

They did the hard work.

They convinced businesses that WhatsApp should become a commercial channel.

They integrated the APIs.

They onboarded companies.

They trained the market.

They built dashboards and workflows.

They got businesses comfortable with selling, supporting and operating through chat.

And all of that happened on infrastructure they never actually controlled.

Now Meta has the users, the businesses, the distribution, the infrastructure and increasingly powerful AI.

And Meta has already made it clear that its ambition goes far beyond simply providing messaging.

They want WhatsApp Business and their business AI infrastructure to become much more deeply connected to the systems companies already use — CRMs, commerce platforms like Shopify, product catalogs, payments, customer data and business operations.

And that raises an uncomfortable question:

If Meta connects directly to your CRM, Shopify store, catalog, payments and customer data — what exactly is the sustainable advantage of many of the companies sitting in the middle?

Why would a business need three or four additional SaaS layers if Meta can increasingly provide the distribution, conversation layer, AI agent and integrations itself?

That is the part I think the market is underestimating.

If Meta can eventually provide natively:

• AI sales agents
• customer support
• CRM connectivity
• Shopify/e-commerce integrations
• product catalogs
• payments
• follow-ups
• recommendations
• abandoned-sale recovery
• campaigns
• customer context
• analytics
• automated workflows

then a huge number of companies whose product is essentially “WhatsApp + AI + integrations + a dashboard” suddenly look extremely vulnerable.

And this is the part I genuinely don’t understand.

How did so many founders build entire companies while strategically depending on a single corporation that controls the API, the channel, the pricing, the rules and the end user?

You don't own that distribution.

You're renting it.

Meta can change pricing and destroy your margins.

It can change a policy and kill a core feature.

It can launch a native feature and erase an entire product category.

It can restrict automation.

It can prioritize its own agents.

It can connect directly to the same CRMs and commerce systems you were using as your competitive advantage.

And eventually it can turn WhatsApp Business itself into the platform that many of these SaaS companies currently sell.

This creates an even bigger strategic problem:

How can an entire industry continue depending on Meta while simultaneously competing with Meta?

Your supplier is also becoming your competitor.

Your distribution channel is also becoming your competitor.

The company controlling your API economics is also becoming your competitor.

That is an incredibly dangerous position to build a business around.

I don't think literally every company in this space will die.

Companies with proprietary technology, deep enterprise workflows, real omnichannel infrastructure, vertical specialization, unique data, or an intelligence layer that exists independently of WhatsApp can absolutely survive.

But companies that are basically sophisticated wrappers around WhatsApp should probably be very worried.

My suspicion is that Meta spent years allowing an external ecosystem to educate the market, prove the business use cases and massively expand WhatsApp as a commercial channel.

Thousands of startups effectively helped Meta prove that businesses wanted conversational commerce.

And now Meta can start moving upward into the highest-value layers itself.

If that thesis is correct, today's pricing changes and WhatsApp AI agents aren't the main event.

They're just the first signals.

And maybe the real long-term escape route is RCS.

Not because RCS is magically better, but because the industry desperately needs a truly global conversational channel that doesn't leave almost the entire ecosystem strategically dependent on one company.

The problem is that RCS adoption internationally has been painfully slow.

So I genuinely hope it reaches virtually every country, carrier and business ecosystem in the world.

Because otherwise we may end up in a bizarre situation where thousands of conversational AI companies claim to be independent SaaS businesses…

while their entire existence is ultimately determined by Meta.

Am I overestimating what Meta is trying to build?

Or are we watching an entire industry slowly realize that it built its companies on rented land?

Hey everyone,

I'm trying to run real end-to-end (E2E) tests for a WhatsApp Cloud API integration.

Meta blocks me from using my phone number because it's registered to the same Business Portfolio that hosts the Meta App.

How am I supposed to test my app without creation a burner portfolio + WhatsApp account ?

Thanks!

Been running WhatsApp automations in production for a while now (Business API + n8n, self hosted) and I want to share some stuff I learned the painful way. Mostly because none of this shows up as errors. Your executions stay green. Everything looks fine. And then results just quietly die.

1. The 24 hour window

Once a customer's last message is older than 24h you can't send free-form replies anymore, only pre-approved templates. My bot was "replying" to expired conversations for days. n8n showed success on every run. WhatsApp was just silently not delivering. Now I store last-inbound timestamp per chat and route expired windows to a template flow. Boring fix, saved my life.

2. Lists that were "definitely opted in"

Client swears the list is opted in. It never is. Every block and report tanks your quality rating and enough of them gets the number restricted. My rule now: if I didn't see the opt-in mechanism with my own eyes, the list doesn't exist. I run a re-confirmation flow before any campaign. Costs one extra message, saves the number.

3. Templates that read like ads

Meta rejects half of them in review, and the ones that pass get reported by users anyway. Same ending, longer route. Writing them like a normal human text with variables (name, order, context) fixed both problems.

4. Sending without handling replies

Fired 500 messages once, \~40 people replied, nobody was watching the inbox. They blocked us. Rating took the hit. Every outbound flow needs an inbound path now, even a dumb one.

5. Quality rating

Nobody watches this number until it arrives as a support ticket. Your daily messaging limit is tied to it and it can drop overnight mid-campaign. I check it before every send now and warm up new numbers slowly.

The common thread: WhatsApp doesn't throw errors for any of this. n8n can't save you from a green log that's lying to you.

Curious what others got burned by. Anyone found a clean way to monitor quality rating automatically? The webhook coverage there feels thin.

Two of us, ~20 messages a day. We're on the WhatsApp Business app, but quick replies only work on the primary phone, linked devices don't get them, so only one of us can actually answer fast.

So I want that same number on the Cloud API too (coexistence): alerts out from our own system, replies landing in a shared inbox I'm coding (claude), with one-tap replies and interactive buttons available to both of us.

Meta's docs say coexistence onboarding is Tech Provider / Embedded Signup only. Has anyone self-onboarded their own number, or is paying a BSP the only route?

I have 2 documents from Singapore, ones business profile for name verification and others accounts verification. The name in accounts verification doesn't have periods in PTE LTD. Name in business profile includes periods like: PTE. LTD. The account verification document issuer says it cant add periods and that shouldn't pose an issue. Will this be an issue in rejection? and how to go about this?

Product: Renotify (https://renotify.app)

Stage: Early Access / Pre-Launch

The Problem:

For years, I built custom WhatsApp integrations for clients (using Cloud API, Sinch, and SendSeven). Whether a client needed bots, scheduled broadcasts, or an inbox, I was repeatedly building standalone systems from scratch with nothing carried over but recycled code snippets.

I built Renotify to consolidate all of this into a single, reusable operations platform.

What Renotify Does:

• Shared Team Inbox: Real-time multi-agent routing, collision alerts (no double-replying), and internal notes.
• Context-Aware AI Agent: Connects to your knowledge base (RAG) and CRM to answer questions, look up records, collect data, and trigger external APIs.
• Visual Flows & Native Forms: Drag-and-drop logic builder + native Meta interactive WhatsApp forms (booking, surveys, product pickers).
• Broadcast Campaigns: Template management, AI translation, audience filters, and live delivery/read analytics.
• Multi-Workspace for Agencies: Manage multiple client numbers and brands with isolated contacts and client-scoped roles.
• Zero Message Markup (BYO): Connect your own Cloud API, Sinch, SendSeven, or Twilio keys and pay raw carrier rates directly.

Target Customer:

Agencies, e-commerce brands, and support teams in WhatsApp-first regions (Europe, Caribbean, LATAM, MENA, APAC).

Business Model:

Flat monthly SaaS subscription per workspace/seats. Zero message markups and no per-conversation fees.

What I Want Roasted:

1. Scope: Does bundling an inbox + AI agent + visual flows + broadcasts feel like a cohesive operations hub, or does it trigger "jack of all trades" skepticism?
2. BYO vs. All-in-One: Does keeping direct carrier rates win you over, or would you rather pay extra for a tool that sells you the phone number directly?
3. Self-Hosted / On-Prem: If you self-host tooling for data compliance (GDPR/privacy), is this something your team requires for customer chats, and how do you budget for on-prem licenses?
4. Dealbreakers: If you run operations on WhatsApp today, what’s the #1 reason you’d hesitate to switch to this?

Be blunt. Tear it apart: https://renotify.app

Looking for a WhatsApp API provider for my SaaS. Customers use their own WABA/number but send/receive entirely through my platform. Need multi-WABA, Embedded Signup, API + webhook, reseller/SaaS support, and reasonable pricing. Any recommendations or real-world experience?

Hi everyone,

I'm testing a WhatsApp Cloud API POC using Meta's own test number, and I'm stuck with an Unsupported POST Request error.

The test number and recipient are configured, and the webhook has been successfully verified. My local Express server and public HTTPS ngrok endpoint are also working.

The problem happens specifically here:

Meta Developer Dashboard → WhatsApp → API Setup → Try it out → Send message

After selecting my registered recipient and clicking Send message, Meta returns:

Unsupported POST Request. Object with ID '1322635814259623' does not exist, cannot be loaded due to missing permissions, or does not support this operation.

The ID is the Phone Number ID displayed by Meta.

I've already verified:

• Test number is configured
• Recipient is registered
• Webhook verification succeeds
• Local endpoint works
• Public HTTPS endpoint works
• The error happens from Meta's own "Try it out" interface

I also contacted Meta Business Support. They reviewed the case but couldn't identify the issue and directed me toward the Developer Community / WhatsApp Solution Providers.

Has anyone encountered this with Meta's test number recently?

I'm mainly trying to determine whether this is a Phone Number ID provisioning/registration issue, a WABA association issue, a permissions/token issue, or a Meta-side problem with the test number.

Any ideas would be appreciated.