r/WhatsappBusinessAPI

Hi everyone,
My business partner and I are launching a new professional services firm in the UK. We want a single, dedicated business number (can be either a local landline or a mobile format) to give to our clients.
Our main requirements are:
1 Shared WhatsApp Business: We need the WhatsApp Business app running on both of our personal mobile phones simultaneously using this single number (via Companion Mode / Linked Devices).
2 Dual Call Forwarding: When a client calls the business number, it needs to ring or route to both of our personal mobiles (simultaneously or via a schedule) so whoever is available can pick up.
3 No extra SIMs: We want to avoid carrying a second physical phone or dealing with dual-SIM setups if possible.

Would be grateful if you could suggest a provider we could look at.

Thanks in advance!

Hey everyone,

I'm building a SaaS platform for private clinics in Turkey (think: AI-powered clinic assistant that handles patient communication via WhatsApp). Each clinic subscribes and connects their own WhatsApp Business number to use the AI agent.

The core problem:

I need each clinic owner to connect their own WhatsApp Business number without leaving my platform — essentially an embedded signup flow. I am NOT trying to use one shared number for all clients. Each client = their own WABA + phone number.

What I've researched so far:

• Meta Tech Provider program — the "correct" path, but 2-4 month approval process, heavy technical requirements, and I'm a non-technical founder
• 360dialog Partner program — has embedded signup ✅ but €500/month flat fee + €49/number. Way too expensive at early stage
• Twilio — explicitly says ISVs cannot use self sign-up, must go through Meta Tech Provider program
• WATI — not designed for reselling API access, per-account model
• ChakraHQ — looks promising (~$3/number/month, official Meta BSP, embedded signup), but based in India and I have serious KVKK (Turkish data privacy law) concerns since I'm handling health-adjacent data
• Desk360 (Turkish BSP) — free platform but no embedded signup, requires manual setup per client which doesn't scale

What I actually need:

1. ✅ Embedded signup — clinic owner connects their WhatsApp number inside my platform in a few clicks
2. ✅ Official Meta Cloud API (no grey-area WhatsApp Web scrapers — accounts getting banned is not an option for clinics)
3. ✅ Multi-tenant API — I manage all connected numbers programmatically via webhooks + REST API
4. ✅ Affordable at early stage (starting with 5-20 clients)
5. ✅ Ideally EU/Turkey data residency or at minimum GDPR-compliant (health data sensitivity)

Questions:

1. Has anyone actually shipped a multi-tenant WhatsApp platform as an ISV without going through the full Meta Tech Provider program? How?
2. Is ChakraHQ's embedded signup flow genuinely smooth for non-technical end users?
3. Any BSPs I've missed that offer embedded signup + ISV/partner API access at a reasonable price point?
4. How are you handling GDPR/data residency when health-related conversations flow through a third-party BSP?

Any advice from people who've actually built on top of WhatsApp Business API at scale would be hugely appreciated. This feels like a problem many vertical SaaS builders must have hit.

our clients are using our gym management software we need to implement a whatsapp integration so that client can send transaction like bills and birthday msg to their clients

For contacts who already had an open conversation with me, it says that my number is no longer on WhatsApp

I had migrated the number to the Official API, and my clients started reporting that they could no longer contact me.

So I moved the number back to the regular WhatsApp app, but now it still appears like this for some contacts.

https://preview.redd.it/21bw9zs9ra2h1.png?width=388&format=png&auto=webp&s=5d484182d6cdb0c4eaf5365dd60ebfc9e800f6bf

For the past few months, I have been trying out various WhatsApp Business API platforms since most companies will eventually encounter limits when scaling conversations, workflows, and team activities.

Most individuals who search for an “AI Sensy alternative” in 2026 are typically looking for:

• improved automation capabilities
• efficient management of campaigns
• clean team inboxes
• more advanced WhatsApp workflows
• cost-effective scalability
• superior API integrations
• reliable broadcasts
• combined CRM & automation features

However, after using many tools, I realised that most of them only concentrate on message sending… but today’s businesses require full WhatsApp operations.

That means:

✅ Shared inbox for teams
✅ Contact management
✅ Broadcast campaigns
✅ WhatsApp automation flows
✅ Lead capture widgets
✅ API access
✅ Follow-up automation
✅ Multi-agent support
✅ SaaS onboarding flows
✅ Conversion tracking

In my opinion, the major change that will be taking place in 2026 is:

It is not enough for businesses to just have “a WhatsApp sender”.

They need an entire WhatsApp Growth Stack.

In particular,

• SaaS firms
• agencies
• ecommerce businesses
• coaching services
• lead generation for local businesses
• support teams

What are you all currently using?

What is your AI Sensy alternative in 2026?

And what made you change?

https://preview.redd.it/q5960hfh182h1.png?width=1448&format=png&auto=webp&s=d1030f2ed3d7b09e91acdddcd5e08ac4d9701410

Another coexistence update from Meta, and this one is genuinely nice. They published a new guide called "Reconnect offboarded coexistence clients" and it covers a pain point a lot of us have hit.

The old problem

When a coexistence client switched phones, reinstalled their WhatsApp Business app, or re-registered their number, their Cloud API companion got offboarded. Getting them back on meant manual intervention. Clients had to go through onboarding again, you had to handle it on your end, and the whole thing was more friction than it needed to be.

What changed

Reonboarding is now automatic. Here's the full flow:

1. Client switches devices, reinstalls, or re-registers
2. Cloud API companion is offboarded. You get an ACCOUNT_OFFBOARDED webhook
3. During the WA Business app registration flow, client sees a pre-checked opt-in listing all their previously connected Cloud API products
4. If they don't opt out, reonboarding runs in the background automatically
5. Within a few minutes, you get an ACCOUNT_RECONNECTED webhook and Cloud API messaging resumes

Nothing required from you or the client beyond them completing registration.

Two new webhooks to handle

ACCOUNT_OFFBOARDED fires when the companion gets offboarded due to device change or re-registration:

{
  "entry": [{
    "id": "<WABA_ID>",
    "changes": [{
      "value": {
        "event": "ACCOUNT_OFFBOARDED"
      },
      "field": "account_update"
    }]
  }],
  "object": "whatsapp_business_account"
}

ACCOUNT_RECONNECTED fires once reonboarding completes:

{
  "entry": [{
    "id": "<WABA_ID>",
    "changes": [{
      "value": {
        "event": "ACCOUNT_RECONNECTED"
      },
      "field": "account_update"
    }]
  }],
  "object": "whatsapp_business_account"
}

What to do when you get ACCOUNT_OFFBOARDED

Pause any pending Cloud API message sends for that client. Messages will fail while reonboarding is in progress. Then just wait for ACCOUNT_RECONNECTED before resuming.

What stays up during reonboarding

Your partner access to the WABA stays intact and webhook subscriptions keep firing. Cloud API messaging is suspended during the window, but since reonboarding typically finishes within a few minutes the gap is minimal.

A few things to note

Only the Cloud API companion is restored automatically. If your client used WhatsApp Web or other companion devices, they have to re-link those manually. Also, if a different partner or coexistence product onboards the WABA during the reconnection window, eligibility for reonboarding is cleared.

The prerequisite is that your app needs to be subscribed to the account_update webhook field. If you already handled the PARTNER_REMOVED changes from last week, you're already in the right place.

Can I create an app in meta with my company number and integrate with our dashboard? I dont want to send ads to our customers, just answer from the dashboard itself and get better kpis. This is ok with meta policy?

Hello everyone,

We are building a WhatsApp automation app for ecommerce brands, and one of our biggest blockers right now is onboarding customers through WhatsApp Embedded Signup.

We initially started with Gupshup APIs and had a joint solution with them. However, over the last few months, we noticed issues in their Embedded Signup flow. At one point, a different 3rd party entity name started appearing in their Embedded Signup, which made us cautious about depending fully on them.

Because of this, we built a direct Meta connection to onboard new customers. But now we are seeing drop offs due to Meta related issues during onboarding:

1. Some customers do not have a GST / Tax info to add in Business Details
2. Some customers face issues adding payment method. For some it works after few hours of adding Business Names and for some it fails even after few days.
3. Some customer use invalid display names even after sending the guidance, so we have started handholding onboarding to enusre they use correct names as displayed on their website, but that means scheduling a call with everyone in different timezones.
4. Each issue adds friction, and customers are more likely to abandon the setup. Every time we solve for a issue, something else shows up next time.

I wanted to ask a few specific questions:

1. Have you switched between working with BSPs and a direct Meta connection for your WhatsApp SaaS? What worked better for you?
2. Do you schedule onboarding calls and guide customers through the process, or do you keep it fully self serve with documentation and videos?
3. What does your onboarding success rate look like for WhatsApp API setup?
4. How do you handle display name rejection, payment method issues, and tax registration related blockers?
5. Would you recommend going back to a BSP to reduce onboarding friction, or is it better to keep improving the direct Meta onboarding flow?

Our onboarding success rate is currently less than 50 percent. I am trying to understand whether we are doing something wrong, or if this level of friction is common with WhatsApp API onboarding.

Any suggestions or experiences would be very helpful.

As tech partner how to find the meta representative who can support us. We have to onboard 1000 WhatsApp mobile app number and business has limit. Looking forward to have it like something in bulk as going through the ui flow 1000 times would be difficult and especially coordinating with each user as well. Tried raising case and live chat they mentioned not possible.

Hi all. I need help to figure out why Meta is classifying my account as sending spam to clients.

I'm using the official WhatsApp API to send template messages to every new customer that registers on my website. The volume is not that big, something like 200 templates sent per day. In my Terms of Service, there is a clause that states users will receive messages through WhatsApp.

The problem is that my account is being classified as sending spam, but I don't understand why. I've tried different approaches, such as sending marketing and utility templates, adding CTA or opt-out options, but nothing really works.

Has anyone been through something similar? How do you deal with it? Thanks!

hey guys, i’m looking for a genuine seller or provider for WhatsApp Business API with unlimited tier messaging, or the highest messaging tier available.

need it for a proper business use case, not spam. client already has consent based users and wants a stable setup with clear details, pricing, requirements, and support.

if anyone here provides this or knows a trusted seller, please DM me or drop details below.

I’m currently exploring WhatsApp Cloud API for a SaaS/TSP-style use case and honestly feeling a bit overwhelmed by the ecosystem.

Our primary use case is utility-category notifications, with possible future support for things like document sharing and customer interactions.

From the technical side, the direct Cloud API integration itself seems manageable. But after reading a lot of Reddit discussions and articles, I keep seeing people strongly recommend using BSP providers instead.

I’m struggling to understand whether:

BSPs are actually necessary for this kind of setup

or whether the real complexity comes later from operational/business workflows rather than the API itself

Some areas where I still lack clarity:

Embedded signup flow

WABA ownership model

Opt-in / opt-out handling

Multi-tenant webhook architecture

Template lifecycle management

Customer engagement workflows

Meta support/escalation realities

At what scale BSPs become worth it

Would really appreciate beginner-friendly but practical resources/blogs/videos/repos covering things like:

Real-world WhatsApp Cloud API architecture

SaaS/TSP implementation considerations

Direct Cloud API vs BSP tradeoffs

Common mistakes/pain points teams discover later in production

Would especially appreciate insights from people who actually implemented this in production rather than marketing articles.

TL;DR:

Trying to understand whether direct WhatsApp Cloud API is realistically manageable for a SaaS/TSP notification platform, or whether BSPs become necessary due to operational complexity. Looking for practical learning resources and real-world experiences.

I was recently informed that Meta is rolling out Business AI for Messenger and WhatsApp.

So far, I’ve only been able to get it working on Messenger. I still haven’t successfully integrated it with WhatsApp Business Accounts (WABA).

Has anyone here already integrated Business AI on WhatsApp successfully? Any tips, requirements, or setup guidance would be greatly appreciated.

I’m looking into WhatsApp tools for an ecommerce store and came across Wati.

Main use cases would be customer support, order updates, abandoned cart follow-ups, and maybe some basic automation. I haven’t used it before, so curious if anyone here has tried it.

How was the setup, pricing, integrations, and overall experience?

F in the chat for all the startups

We have been built on Twilio up til now but want to avoid the fees, so we are going direct to the API. I am not sure how to take care of giving people a number they can use for verification if we are going straight to API. It seems it might be best to get the numbers from Twilio or similar and then port them onto WhatsApp. Any advice welcome !

[removed]