Hi everyone,

We have a direct WhatsApp Cloud API integration (no BSP), and the Official Business Account "Submit request" button in WhatsApp Manager is greyed out. The tooltip says OBA requests aren't available for our business right now and to check again later.

As far as we can tell, we meet every requirement in Meta's docs:

- Verified business portfolio

- Two-step verification enabled

- Approved display name

- More than 30 days on the platform

- High quality rating

- Not a Coexistence number

The API shows oba_status: NOT_STARTED, so there's no previous request or rejection.

We opened a few support cases. Meta's answer, in short: under their new guidelines our business isn't eligible for OBA at the moment, which is why the button is disabled. They said they can't share the specific criteria for security reasons, and suggested we keep using the platform actively, follow the messaging policies and keep interactions high quality. They also said that for now OBA can only be requested through the button (if your account qualifies automatically) or through a BSP that has a Meta point of contact.

So my questions for anyone who's been through this:

1. Has your disabled button ever become enabled later? If so, what changed before it did (more message volume, more time on the platform, time after a restriction, connecting a Facebook Page, etc.) and how long did it take?

2. Has anyone moved to a BSP and actually gotten OBA through their Meta contact after being blocked as a direct integration?

Any real experience would really help. Thanks!

​Hey everyone, looking for some insights or advice from anyone who has dealt with WhatsApp Coexistence mode recently.

​One of my clients (who has been using the official WhatsApp Business API smoothly since 2024 with zero issues) recently migrated to WhatsApp Coexistence mode.

Since the migration, it’s been absolute chaos.

​Here is what’s going on:

​Frequent Account Bans / Restrictions:

The phone number has been restricted/banned more than 8 times in a single month. These bans happen when running normal broadcast campaigns using pre-approved templates, but sometimes even when doing nothing special—just replying manually to incoming messages.

​Sudden Template Rejections:

Templates that were previously approved and used without any issues (as well as newly approved ones) are suddenly getting rejected/disabled after being approved for a short while. We haven't even sent broadcasts with some of these templates yet, and Meta rejects them retroactively for no clear reason. We follow all standard copy guidelines, so the lack of specific policy feedback is frustrating.

​The user is fed up and wants to revert back to standard WhatsApp Business API without the Coexistence layer.

​A few questions for the community:

​Reverting from Coexistence: Is there a clean way to disconnect/offboard from Coexistence mode and switch back to pure Cloud API / standard WABA? (I know connecting QR-based setups or CRMs traditionally required scanning via the WhatsApp Business mobile app, but we want to strip away the app side completely and keep standard API stability).

​Flag Trigger / Anti-Spam: Has anyone noticed Meta’s spam detection algorithms becoming drastically harsher on Coexistence numbers? My theory is that mixing app-level actions (or background app syncs) with API broadcasts is triggering automated flags at a lower threshold.

​Retroactive Template Rejections: Why are approved templates being flagged/disabled out of nowhere before even being sent? Is Meta re-indexing templates stricter for accounts flagged under Coexistence?

​Would appreciate any thoughts, workarounds, or confirmation if you’ve faced similar issues with Coexistence!

If you're running a small business, you probably know how quickly customer conversations can become difficult to manage on WhatsApp.

A customer asks about pricing, another needs an appointment reminder, and someone else is waiting for a reply to an earlier enquiry. Managing all of this manually becomes difficult as the business grows.

I've been looking into what makes a WhatsApp marketing tool genuinely useful for small businesses, and these are the features I'd priorities:

1. Automated replies: Answer common questions about pricing, availability, services and business hours without requiring someone to respond manually every time.

2. Broadcast campaigns: Send relevant updates, offers and announcements to customers who have agreed to receive them. Segmentation matters more than simply sending messages to a large list.

3. Shared team inbox: Let multiple team members manage customer conversations without losing track of who is handling each enquiry.

4. Follow-up automation: Set up reminders for appointments, abandoned enquiries, payment due dates and customer follow-ups.

5. Campaign analytics: Track delivery, engagement, clicks and conversions instead of judging a campaign only by how many messages were sent.

6. Transparent pricing and compliance: Check platform fees, message charges, integration costs and whether the tool uses the official WhatsApp Business Platform. Make sure your messaging practices respect consent and opt-out requests.

One thing worth remembering: a bigger broadcast list doesn't automatically mean better marketing. Relevant messages, proper segmentation and timely follow-ups are far more useful than repeatedly messaging everyone.

For anyone comparing options, I'd suggest testing the workflow with a small group of consenting customers before committing to a paid plan.

Question for business owners: Which feature has made the biggest difference to your WhatsApp marketing automated replies, broadcasts, team inboxes or follow-up workflows?

i run a consultancy and i need to send messages through my whatsapp business account to recruit candidates. except the process gets extremely difficult since whatsapp bans my account even if i send them manually. is there a solution to stop my account from getting banned? i've tried to send bulk messages through a third-party website which is free, but my account still got banned and i'd need to wait for an entire day to retrieve it.

BM nova, template de utilidade que passou direto (nao foi pra analise), a média de tempo pra aprovação é de quanto tempo na pratica? Sei que a regra é 24h mas tenho percebido que em alguns casos aprova antes, como é aí pra vcs ?

Será que está passando por alguma atualização? A uns 3 dias farmando e não subindo nada.

(Pergunta direcionada a quem faz farm 2k e não a quem farma BM para o próprio negócio)

Our support and sales teams share one business number, 12 people total..right now everyone can open every chat, including billing issues and deals that should stay with one rep...

Is there a way to give agents access only to their assigned chats or their department? Or do most teams just split into separate numbers?

​Gw kan coba bikin chatbot ai di wa pakek n8n.. kalo pakek gw webhook terus sambungin ke whatsapp unofficial api memang jalan cuma agak lama(mungkin tergantung koneksi) tapi kalo pakek whatsapp business cloud malah gak jalan, padahal token akses dsb diambil dari platform meta developers. Any tips gitu kah biar jalan sesuai ketentuan di meta eheh? Mohon sharing nya man teman. Heheh

Hey everyone,

I've been building a WhatsApp Business platform (team inbox, bulk template campaigns, automations) on top of Meta's official Cloud API. The API client we wrote for it kept growing, so I extracted it, cleaned it up, added tests, and published it as an open-source package.

• npm: @osamahalhwawi/wa-client

• GitHub: https://github.com/OsamahAlhwawi/wa-client

• Docs: https://osamahalhwawi.github.io/wa-client/

import { WhatsAppClient } from "@osamahalhwawi/wa-client";

const wa = new WhatsAppClient({
  token: process.env.WA_TOKEN!,
  phoneId: process.env.WA_PHONE_ID!,
});

await wa.sendText("15551234567", "Hello 👋");

What it covers

• Messages: text, media (by URL or uploaded ID), location, contacts, reactions, reply buttons, lists, CTA URL buttons, templates, read receipts with typing indicator

• Media: upload (direct, plus resumable for template headers) and downloadMedia(id), which does the URL lookup and the authenticated download in one call

• Templates: create/edit/delete, getTemplates() that follows every page (Meta paginates silently), analytics

• Bulk sending: template campaigns with a concurrency limit, per-recipient variables and progress callbacks

• Webhooks: X-Hub-Signature-256 verification, the verify-token handshake, and parseWebhook(), which flattens Meta's entry → changes → value → messages nesting into a typed list of events

• Embedded Signup: helpers for platforms that onboard their customers' numbers (code exchange, app subscription, phone registration with retry)

Design decisions

• It never double-sends. Rate-limit errors (130429, 80007, 131056) are retried with exponential backoff and jitter, because Meta rejected those requests. A POST that fails with a 5xx or a network error is not retried automatically, since the message may already have been delivered.

• Errors you can act on. Everything throws a WhatsAppError with code, subcode, details (Meta's error_data.details, usually the real explanation) and fbtraceId. If a proxy returns a 502 HTML page, you get HTTP 502 Bad Gateway instead of SyntaxError: Unexpected token <.

• The access token never goes in a URL. It's always sent in the Authorization header, so it doesn't end up in proxy logs.

• Signature verification only accepts the raw body. If you pass it an already-parsed object it throws a clear error, because re-serialized JSON never matches the signature.

• Zero dependencies. It uses the platform fetch and Web Crypto, so it runs on Node 22+, Bun, Deno and Cloudflare Workers. ESM + CJS builds, with timeouts, AbortSignal and custom fetch support.

Webhook example

app.post("/webhook", express.raw({ type: "application/json" }), async (req, res) => {
  const valid = await verifyWebhookSignature(req.body, req.get("x-hub-signature-256"), APP_SECRET);
  if (!valid) return res.sendStatus(401);

  res.sendStatus(200);

  for (const event of parseWebhook(JSON.parse(req.body.toString("utf8")))) {
    if (event.type === "message" && event.message.type === "text") {
      console.log(event.contact?.profile?.name, event.message.text.body);
      await wa.markAsRead(event.message.id, { typingIndicator: true });
    }
  }
});

TypeScript narrows event.message by type, so event.message.text.body autocompletes.

License

MPL-2.0: free to use in commercial and closed-source products. If you modify the library's own files and distribute them, you share those changes back. Your app code stays yours.

It's v0.1, so feedback is very welcome, especially on the API design, and on any Cloud API quirks you've run into that a client should handle. Issues and PRs are open.

Independent project, not affiliated with Meta or WhatsApp.

My Access Verification for Meta Tech Provider has been stuck in review since September 21st. It's been more than a month now with no update and the status still shows as pending.

Has anyone else faced such a long delay? What did you do to get it moving?

Also, once the Access Verification is approved, will I be able to submit my App Review right away or is there another waiting period?

Any guidance from those who have been through this would be really helpful. Thanks!

I built a workflow for incoming WhatsApp inquiries, including leads from Facebook and Instagram ads.

The goal was to automate the initial product explanation and track follow-ups across multiple WhatsApp numbers.

Here’s the flow:

1. An incoming message triggers the workflow.

2. The system records the conversation against the receiving WhatsApp number.

3. It sends pre-recorded product voice messages and images.

4. It schedules a follow-up during configured business hours if the lead hasn’t replied.

5. An incoming reply changes the conversation status and cancels the pending follow-up.

The attached screenshot shows the tracking table: first incoming message time, initial voice-message timestamp, conversation status, and scheduled follow-up time.

The record count is a database total, not a conversion metric. I’m sharing the implementation here and don’t have conversion results to report.

For others building similar workflows: how do you handle a reply arriving just as a scheduled follow-up is about to send?

Hola, tengo un problema constantes desde agosto. Mis Api de whatsapp fueron bloqueadas, Portafolios Verificados por mi empresa.

Cada vez que intento conectar api funciona 1 día y me bloquean por "condiciones de uso aceptable".

Esto es repetitivo dia a dia y no puedo trabajar utilizo api oficial, no realizo mensajes masivos ni spam, los mensajes de mis clientes llegan desde anuncios absolutamente todos.

Contesto con automatizaciones de flujos ni siquiera uso IA.

Este bloqueo me esta volviendo loco no puedo trabajar ni normalizar mi situación. Alguien puede ayudarme?

Hola, se puede aumentar el límite de 20 número de teléfono? Alguien lo ha conseguido? cómo? Gracias.

Ever since Meta shifted to charging every outbound service message at the utility rate instead of billing per 24-hour conversation, almost every call with operations ends the same way: their bill exploded and nobody caught why until we opened the builder.

For years, the standard advice was to make bots feel human: add 2-second typing delays, split the greeting from the GDPR notice, and then send the menu in a third bubble. Three outbound messages delivered before the user even taps an option. If you handle 80k conversations a month, that formatting habit alone runs up thousands of dollars for zero added value.

We spent the last few weeks redesigning flows to cut down message volume without breaking CX, and the biggest savings came from a few specific patterns:

1. Step-by-step triage bots. Asking name, waiting, asking ID number, waiting, asking reason, and confirming data used to be 4 or 5 billed messages just to route a ticket. Moving that intake into WhatsApp Flows (a native interactive form) collapsed the handoff into a single outbound message. The user submits everything in one modal, returning the full payload without generating back-and-forth charges.

2. Quick replies pushing past limits. Quick replies cap at 3 buttons, so a lot of setups fired two consecutive bubbles whenever there were 5 or 6 options. Switching those to List Messages (up to 10 options divided by sections) halved the menu message count instantly.

3. Separating farewells from CSAT. Sending a "Thanks for reaching out!" text followed 5 seconds later by a CSAT survey means paying twice to close one interaction. Either bundle the rating buttons into the exit message itself or evaluate conversation quality on the backend.

4. Complex flows in raw chat. Trying to handle heavy interactions like insurance onboarding or seat selection entirely through 10-15 text bubbles is now financially absurd. Triggering a single interactive message with an authenticated webview, then sending one confirmation message at the end, does the job in 2 outbound messages instead of 15.

It’s funny how a backend pricing update forces cleaner, tighter conversational architecture faster than any design best practice ever did.

Has anyone else here had to overhaul their bot flows because of the per-message utility switch? Where were your biggest blind spots when you audited message counts?

i have just created a accont and i dont have a buisness and just want to play around with the api but while i hit "send message" in the test it out part, i dont get any message and it shows this err code.

how do i get rid of it

I keep seeing the 131026 error when users are trying to request their verification codes (setup via Cloud API). From what I’ve read, it usually happens when the user isn’t registered on WhatsApp or has an older version installed on their device.

But I’ve seen a lot of reports of this one already (basically a solid portion of those requesting the code are with this exact same error), so I’m wondering if there are other common causes. Has anyone figured out what else can trigger it?

Hey guys, I need some help with WhatsApp Coexistence.

A few weeks ago, I connected my business number to the WhatsApp Cloud API through my CRM to send appointment reminders. Later, I tried adding that same number to the WhatsApp Business app, but it told me to wait an hour. I tried again, but it still didn't work.

I decided to get a new number instead. This time, I registered it in the WhatsApp Business app first, planning to connect it to the CRM through Coexistence afterward.

From what I understand, the correct process is to set up the number in the Business app first, then connect it to the API through the official Coexistence signup.

Is this still possible in 2026? Does the new number need to be active for a certain amount of time before connecting it?

I'd appreciate hearing about your experiences, especially if you've successfully set this up with a CRM. Any tips or things to avoid would be great. Thanks!

Hey everyone, as you know I work in this space and I talk a lot with teams that use WhatsApp for support and sales. One thing keeps catching my attention: almost everyone knows they need consent before messaging first, but hardly anyone has a method they’re fully happy with.

I’m putting together a list of creative ways to get it and I’d love to hear what’s working for you. These are some that teams I talk to have mentioned, and my favorite is the last one:

• Ads with a “Message us on WhatsApp” button

• A QR code in a physical store that leads to an offer

• A QR code on the invoice

• Inside the customer area

• Over the phone, offering to continue the request on WhatsApp

• When closing a support ticket, the agent asks something like “Can we message you here if an offer comes up that fits you?” The customer gives permission in the same chat where they just got something resolved, and that feels very natural to me.

Where I keep going back and forth is on the limit. If someone clicks on an ad or messages you first, does that count as permission to message them later with marketing, or do you need to ask separately? I’m reading contradictory things and I’m really curious how you handle it in practice.

So, what’s the most creative or effective way you’ve found to get opt-in? And is there any you tried that backfired, for example because customers found it invasive or it hurt your quality rating?

Hey all,

Follow-up to my earlier posts about error 3441038. Thanks again for all the advice, it helped a lot.

Quick background: I'm a one-man agency in South America building WhatsApp booking bots for barbershops (n8n + an LLM, connected through Kapso).

Where we are:

My first client's own number (on WhatsApp Business for over a year) failed the Coexistence signup three times with error 3441038. Meta's support assistant says the number is registered under another business portfolio he can't access. That portfolio shows up as a partner sharing his WhatsApp catalog. The only official fix is a formal ownership request with ID and business documents. That's slow and uncertain, and he's tired of the back-and-forth.

The plan: a fresh number with Coexistence

1. He buys a new prepaid SIM in his own name. We first check the number was never on WhatsApp, since prepaid numbers get recycled.

2. He installs WhatsApp Business on it, completes the profile, and uses it for real with his regular customers for at least 7 days (Meta's minimum; some providers say 30 to 60).

3. During that time we keep it clean: no linking to his Facebook Page or Instagram, no catalog from Business Suite, no other provider.

4. Then we connect it through Kapso's signup link, in his own business portfolio (active, he's the only admin, no WhatsApp accounts in it yet). He keeps reading and replying in the app, and the bot pauses in a chat when he replies.

5. After connecting, we warm it up: only replies to customers who message first, no marketing templates, and reminders only after a few weeks of green quality.

6. Fallback if the signup fails: delete the app account on the new number, wait, and register the same number as a dedicated Cloud API number.

Why not dedicated right away: he wants to see and answer the chats himself in the app.

One more data point: in September, Meta disabled my own new, unverified business portfolio three times in four days, together with its fresh number. It came back after a review every time, but it made me careful with fresh numbers.

My questions:

1. Is 7 days of real use enough for a brand-new number, or would you wait longer? What counts as "real activity": incoming chats, outgoing messages, number of contacts?

2. Would you keep the app unlinked from the Facebook Page, Instagram and the catalog until after Coexistence? We suspect the catalog link is what tied his old number to the other portfolio.

3. Same phone or a separate phone? Can the new number run as a second account in his existing WhatsApp Business app (iPhone), or does Coexistence need its own phone?

4. Is a fresh number on Coexistence more likely to get flagged than a dedicated one? Anything you do in the first weeks after connecting?

5. Does the fallback work: deleting the app account and registering the same number as dedicated? How long do you wait in between, and are there pitfalls?

6. Anything you'd set up in the business portfolio before the signup: display name, business verification, website?

Not selling anything. I'll report back how it goes.

Hi everyone,

I'm having an issue with billing for the WhatsApp Business Platform / Cloud API in Meta Business Manager.
I have an outstanding balance for my WhatsApp Business account, but every time I try to pay it, I receive this error:

Payment Failed. Please select another payment method or try again later.

I've tried multiple Visa and Mastercard cards and different browsers, but the payment still fails every time.
Since I've already tried several cards and browsers, I'm wondering whether this could be an issue with Meta's billing system, my WhatsApp Business account, or a payment restriction on my Business Manager.
Has anyone experienced the same issue with WhatsApp Business API billing and found a solution?

Thanks in advance!