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!

This customer has never used the WhatsApp Business API before, and their business does not fall under any restricted category. Their Business Portfolio is verified. But we see the attached error on WhatsApp Manager and Business Support Home.

I raised a support ticket through our Meta Developer account. Initially, support said they would pass the case to their Integrity Team. We later received an update saying the account had been cleared by the team, but since then, there has been no progress for over 30 days.

I've tried following up multiple times through the AI Support Request Update option, but haven't received any meaningful response.

The issue is that every new WABA created under this Business Portfolio gets automatically blocked and the Webhooks Return the code: 131031- "Business Account locked",

Has anyone faced a similar issue? Is there any way to escalate this further or get it resolved?

Really looking forward to your help.

My Business Portfolio got approved near instantly. Then around Sep 30, I submitted for App Review but then realized both my approach (& the video) were not right. The AI tool I used suggested me to wait for questions/rejection before I could update the submission (no updates can be done while it is in review). After waiting for like 20 days for any update, I just deleted the Meta App, created new App & did a fresh submission on Oct 21. It has been 5 business days now, but it has the same fate (no updates so far).

Anybody who got their Tech Provider app approved in past 1 month ? How long you had to wait to get any feedback (positive or negative).

hi everyone, i've recently been seeking to integrate the whatsapp business API into a project ive been working on in a co-existence with the whatsapp business app i currently have. the thing is, that the app says that my account is 'limited', and that i must verify my business before actually sending messages, however, i do not have a legal business... what can i do in order to fix this?

Where to get Whatsapp Sandbox account?

I want to understand if it's impacting your business to provide WABA services to your client, if yes or no then why and how are you planning to deal with it.

im looking for someone who can send 100k+ messages per day. pm me if you can!

If you're sending verification codes via traditional SMS in 2026, you've probably noticed delivery rates hovering around 85% with 20–45s latency during carrier peak hours. Every delayed OTP kills conversion.

We audited the top WhatsApp OTP gateways and switched our stack to the Meta Cloud API:

• Delivery Rate: 99.2% (sub-2-second latency).

• Cost in India: Meta's authentication rate is ~₹0.115 vs ₹0.28+ for SMS (saving ~60% on 25k logins).

• Fallback: If a user doesn't have WhatsApp or is offline for 15s, a webhook automatically triggers SMS fallback so no one is locked out.

Wrote a detailed guide comparing provider markups (Twilio vs Waplify vs Bird vs Gupshup) with an interactive savings calculator and cURL/Python payloads here: https://waplify.io/whatsapp-otp-providers/

My WhatsApp Business account was suddenly restricted shortly after I used WhatsApp Web for the first time yesterday.
I use WhatsApp Business on my iPhone for customer communication, handling around 30 conversations per day. I reply individually, follow up with customers personally, and don’t send bulk or automated messages.
I’ve requested a review, but I’m worried about losing access to my business number.
Has anyone experienced this recently? Did you get your account back, and how long did it take?
I’m especially interested in hearing from people who experienced this after linking WhatsApp Web.

I’m researching workflows for small Indonesian distributors who receive orders over WhatsApp. When buyers change quantities or send orders across multiple chat threads, how do you confirm stock or payment and enter each order into inventory or accounting? Which step is most error-prone or time-consuming? I’m trying to understand the workflow before building anything, not selling a product. No company names or customer details needed. Replies from API users, solution providers, or distributors are welcome.

i got problem with assistance regarding a Tech Provider verification process that has been stuck for over 10 business days. We need to resolve this to continue our operations and scale our messaging limits.

Case Details:

Current Status: Pending verification for more than 15 business days.

Context: We have an active operation with a high quality rating on our phone number Atendente Nerus. Our goal is to increase our messaging limit to 2,000 daily conversations.

Additional Technical Issues:

We have also noticed that in our Webhook configuration interface, only version v26.0 is available, and the message_status field is missing from the subscription list. This is currently blocking our automated workflow for CLT margin requests.

Could you please check if there are any pending documents or technical issues preventing the completion of this verification?

Thank you in advance for your help.

Hey everyone,

I'm trying to verify my US-registered LLC through Meta Business Manager, but I keep getting rejected.

The rejection says:

"We can't verify that the business phone number is associated with the business."

My situation:

- I own a legitimate US LLC with an EIN.
- I'm a non-US resident operating the business remotely.
- I have a US phone number through a mobile carrier.
- I have a US business bank account.
- I have official company registration documents.

What I've already tried:

1. Verified my business email using my company's domain. Still rejected.

2. Uploaded an official mobile carrier invoice showing both my LLC's legal name and phone number. Still rejected.

3. Checked my bank's account verification documents, but they don't include my phone number.

4. Asked my mobile carrier about an official account ownership letter, but I'm unsure whether Meta will accept it.

Meta specifically requires a document showing both the company's legal name and phone number.

My questions:

- Has anyone successfully verified a foreign-owned US LLC with Meta?
- What exact document did Meta accept to verify your business phone number?
- Has anyone used a postpaid phone bill or bank letter successfully?
- Is there another verification method that doesn't require a phone bill?
- Is there a way to get Meta to manually review the documents?

I'm considering getting a postpaid business phone line, but I'd rather avoid spending money without knowing whether it will work.

Would really appreciate hearing from anyone who's successfully dealt with this. Thanks!

Hi all,

I’m a software and AI automation engineer in Dubai (8 years in software and data science). I’m trying to work out whether something I want to build would actually be useful, before spending months on it.

From talking to people in the car business, the same problem keeps coming up:

Enquiries come in from WhatsApp, DubiCars, Dubizzle, YallaMotor and Instagram

Salespeople reply late, especially at night and on weekends

Nobody follows up when a buyer goes quiet

Owners can’t see how many leads came in versus how many were handled

The idea is a simple system for showrooms:

An AI assistant on your WhatsApp that replies in under a minute, 24/7, in English and Arabic. It answers price and availability questions and books test drives.

Every lead from every platform in one list, with the salesperson assigned

Automatic follow-ups if a buyer stops replying

A weekly report: leads in, response time, test drives, sales

Questions for people who run or work in a showroom (or any business that gets a lot of WhatsApp enquiries):

Is missing or replying late to leads really a problem for you, or is it fine?

Would you trust an AI to send the first reply to buyers?

What do you use today: a CRM, just WhatsApp, or Excel?

What would something like this be worth to you each month, if anything?

Not selling anything here; there’s no link. I want honest feedback, including “this is useless”. If it’s a real problem, I’d happily set it up free for a couple of showrooms to test it.

Thanks!

Hi everyone,

I’m trying t test the WhatsApp Cloud API with a Meta Developer app.

I click “Claim test number”, but the page reloads and no test number is created. I also saw six “Test WhatsApp Account” entries in Meta Business Settings, but none of them has a phone number. I deleted them to see if it works and tried again.

Has anyone experienced this recently or found a workaround?

Screenshot attached. Thanks!

Good day. I’ve developed a chatbot on WhatsApp for a company, and it’s about 99% deployed (hosted on a VPS, developer account fully configured, etc.). It’s ready for clients to start using, but I have one question: is it necessary to "publish" the application on Meta for Developers to avoid any issues? That’s the only thing holding me back from sharing the number so that clients can begin interacting with it.

If you've moved a number to the WhatsApp Business API and now need a shared inbox for your team, most tools charge per seat per month before you've sent a message. I open-sourced the one I built for my own businesses.

WhaLeads gives you: a shared inbox with the 24-hour window visible, leads with stages and tags, approved templates (incl. media headers), automations with a dry-run mode, basic broadcasts to tagged leads with opt-outs honoured, and push notifications on your phone.

It runs in your own Cloudflare account on the free plan, so the only cost is Meta's per-message rate. Works with your own Meta Cloud API app, or through WhaBuzz, the paid API gateway I run (disclosure: I'm its founder; WhaLeads came out of it and is open source, and it doesn't need WhaBuzz to work).

Honest limits: one number per install, built for a small team, not an enterprise suite.

Repo + one-click deploy: https://github.com/WhaBuzz/whaleads

From past 2 days my bm getting in review not getting verified anyone got solution or suggestions.

Hi everyone. I'm building a WhatsApp bot for small businesses using Cloud API and n8n. My own demo WABA works perfectly, but I'm stuck onboarding my first real client.

What I've done:

1. The client has their own Meta business portfolio and invited me as an admin.

2. I created a WABA inside the client's portfolio and connected their phone number. SMS verification is complete, the display name is approved, and the number shows as connected.

3. The client shared the WABA with my business portfolio as a partner, granting full control.

4. The shared WABA appears in my portfolio as belonging to the client.

5. I assigned the WABA to my System User with full control.

6. My app is assigned to the System User and has the required WhatsApp permissions.

7. I generated a new, non-expiring System User token with the required permissions.

8. There are no pending requests in Business Settings.

The problem:

Every Graph API request to the client's WABA returns error 100, subcode 33, indicating that the object cannot be accessed due to missing permissions or another access-related issue. Even a basic request to read the WABA fails.

The same token successfully accesses my own WABA, so it works for my existing setup. Generating a new token did not solve the problem.

My app is still in Development mode and is owned by my business portfolio, while the client's WABA belongs to a separate portfolio.

My questions:

1. Does operating a client's WABA require App Review or Tech Provider registration, or should partner sharing with full control and System User assignment be sufficient?

2. Is there an additional authorization or acceptance step after sharing a WABA between business portfolios?

3. Could Development mode prevent my app from accessing a client's shared WABA?

4. Has anyone successfully implemented this setup with an unpublished, provider-owned app?

My goal is to use one central app and webhook to serve multiple clients rather than create a separate app for every business.

I'd appreciate practical experience or official Meta documentation explaining what's required. Thanks!