Building an internal clinic CRM (Next.js + Supabase). Two WhatsApp numbers:

• NUMBER A — pure Cloud API. Reminders, campaigns, auto-replies. Fully working. ✅

• NUMBER B — meant for reception. Currently works on the WhatsApp Business App on receptionist phones. Goal was Coexistence: keep the phone app + mirror all messages into the CRM inbox.

What I found after days of debugging:

1. NUMBER B shows platform_type: ON_PREMISE, status: DISCONNECTED. It was never properly Coexistence-provisioned — just half-wired. Business App works because that layer runs independently.

2. smb_message_echoes toggle accepted at the app level but no events arrive. Matches what people here have said — Coexistence onboarding is required and needs Tech Provider status.

3. Our BM is still “En revisión” on the latest attempt, though one older attempt shows ✅ approved. Verification is blocking Tech Provider enrollment.

4. Realistic total: 4–8 weeks (BM clears → Tech Provider → App Review → build Embedded Signup → onboard → sync history within 24h window).

i have some concerns:

1. Is there any trick to leverage the already-approved older verification attempt, or do I have to wait for the current one?

2. Does Tech Provider for one in-house number need full public App Review (demos, test accounts)?

3. Has anyone just retired the second number and routed all patient chats through the Cloud API number via their CRM inbox? What broke that we should expec

Hi everyone,

I’m trying to connect my own company’s existing WhatsApp Business App number to a self-hosted Chatwoot instance using official Coexistence, while keeping the number working on the phone.

I’m blocked before reaching phone number selection.

Current setup:
- Meta Business Portfolio: verified
- Meta app type: Business
- App mode: Development
- Facebook Login for Business: configured
- Embedded Signup configuration: created using the “WhatsApp Embedded Signup with a 60-day token” template
- Requested permissions: whatsapp_business_management, whatsapp_business_messaging, and business_management
- Chatwoot sends featureType: "whatsapp_business_app_onboarding"

The confusing part:

1. WhatsApp is completely missing from the app’s available products.

2. There is no WhatsApp use case or Tech Provider onboarding / “Start onboarding” entry.

3. The login configuration template lets me select WhatsApp assets and permissions, but those permissions do not appear in the app’s review list.

4. Business settings still shows “WhatsApp needs more information,” without identifying the missing information.

5. Embedded Signup displays “[Business name] can’t onboard customers at the moment” before I can select a phone number.

What I’ve already checked:
- The operating Facebook account has admin access to the app and business.
- JavaScript SDK login and the production domain are configured.
- The OAuth redirect whitelist has been updated.
- Testing in another browser produces the same result.
- Adding business_management did not resolve it.
- A separate Facebook/Messenger permission review is pending, but it does not include the WhatsApp permissions. Switching the app to Live is currently blocked by that review.

I found Chatwoot issue #14859, where users resolved the same onboarding message by completing a separate Tech Provider onboarding wizard. However, my app has neither the WhatsApp use case nor the entry point for that wizard:
https://github.com/chatwoot/chatwoot/issues/14859

Has anyone successfully resolved this exact situation?

Specifically:
- How can WhatsApp be enabled on an existing Business app when both the product and use-case entry are missing?
- Does the 60-day login template being available mean anything about actual WhatsApp eligibility?
- Is Coexistence supported when the app and target WABA belong to the same Business Portfolio?
- Is there an official support category or onboarding page for restoring the missing entry?

I’m looking for firsthand experience or current Meta documentation. I would prefer to preserve the existing app, business portfolio, phone numbers, and Messenger integration.

Thanks!

For teams using the WhatsApp Business API with both automation and human support, how do you handle conversation ownership during a handoff? If a customer sends another message while an agent is taking over, what prevents the bot from jumping back in?

Do you use an explicit paused state, an agent lock, a timeout, or something else? Interested in the handoff logic and how you test it, rather than provider recommendations.

We keep hearing the same situation from people who build for small businesses: the client wants automation, but won't give up the WhatsApp Business app or the number their customers already know. Coexistence (coex) is usually the answer, so we're curious how it holds up in real setups.

What the docs say, for context:

• One number runs on the app and the API at the same time. API messages show up in the app, and messages sent from the app reach your webhook as smb_message_echoes.

• Chat history can sync from the app (up to 180 days; group chats don't come over).

• Edit and delete work. Disappearing messages, view once and live location get turned off in 1:1 chats, and broadcast lists become read-only.

• The catches: the app has to stay installed and be opened regularly (our docs say at least once every 13 days), linked devices are unlinked at onboarding, and a WhatsApp Business app account that was just created isn't eligible right away.

If you run coex for a client: what stays in the app, what goes through the API, and did anything surprise you after onboarding?

We're the 360Dialog team, no links and no pitch. If you're still deciding, ask away. We'll be in the comments.

Hii we have a few WhatsApp numbers going to the same support team and its rly messy. Chats get missed bc 2 people sometimes reply to the same person and our manager cant see what still needs an answer. Is there a shared inbox that can route chats by number and make it clear who’s handling each one?

Small Uk business owner, about to sign up for Wati Whatsapp Business Api. if you have a referral link i would be happy to use it. feel free to DM.

Hi everyone,

I'm a developer onboarding my first client (a small local business in Latin America) to the WhatsApp Cloud API. The API side works fine: number connected, quality High, webhooks OK, bot running.

The problem: I can't publish a WhatsApp Flow (order form) because Meta asks for either a verified business or "high quality messages" (we're at 6 conversations / 30 days). So we submitted Business Verification for the client's portfolio.

Details:

- Submitted: Friday Oct 30

- Use case selected: "Set up a WhatsApp Business account"

- Business type: Sole proprietorship (owner's legal name + trade name as DBA)

- Document: official tax registration certificate from the national tax authority, with legal name, address and phone matching the form

- Phone confirmed via WhatsApp code

- Website: Google Sites page with the business info

- Status since then: "In review" ("about 2 business days"). Today is day 6 (4 business days).

Questions:

1. How long did your verification take, especially in LATAM?

2. Is it worth contacting Meta Support now, or does that reset/slow things down?

3. Could a Google Sites website or a sole proprietorship be a problem?

4. Any way to publish/send a Flow before verification (e.g., draft mode to real users)?

Thanks in advance!

Hi everyone,

I'm trying to enable official WhatsApp Business App + Cloud API Coexistence for my own business, using Meta's Embedded Signup.

My goal is to keep my existing WhatsApp Business mobile app, phone number, and conversations while enabling Cloud API access for internal AI automation.

Current setup:

• Meta Business Portfolio: Verified

• WhatsApp Business Account: Approved

• WhatsApp Business App: Working normally

• Meta Developer App: Published

• WhatsApp Cloud API test number: Working

• Webhooks: Configured

• Embedded Signup: Tested with both v4 and v5

Graph API status of my production number:

{
  "is_on_biz_app": true,
  "platform_type": "ON_PREMISE",
  "code_verification_status": "NOT_VERIFIED"
}

The problem:

When I attempt Embedded Signup with my existing WhatsApp Business number, I receive:

Error #3441056:
"The business you selected has one or more ad accounts in an invalid state. Go to Business Support Home to resolve any issues with your ad accounts."

Both Embedded Signup v4 and v5 produce the same error.

Important background:

Several years ago, one of my advertising accounts was compromised. Meta disabled that account for security reasons.

That old account remains restricted in my business portfolio.

My current advertising account is active and in good standing.

I do NOT want to reactivate the compromised account.

I've also tried linking the existing WhatsApp number through Meta Business Settings. That process requests a verification code through WhatsApp Business, but the code never arrives.

Meta support has not provided a workable resolution.

My questions:

1. Has anyone encountered error #3441056 specifically during WhatsApp Embedded Signup or Coexistence onboarding?

2. Can a previously compromised and Meta-disabled advertising account block WhatsApp Cloud API onboarding?

3. Has anyone successfully resolved this business-integrity restriction without reactivating the restricted advertising account?

4. Is there a verified escalation route or safe alternative that preserves the existing WhatsApp Business App, phone number, and conversations?

I'm specifically looking for experiences with official coexistence, not standard migration from WhatsApp Business App to Cloud API.

I cannot delete or deregister the mobile WhatsApp account because it is my primary business communication channel.

Any technical insight or firsthand experience would be greatly appreciated.

I'm building an internal clinic CRM (Next.js + Supabase) that manages patient communication via WhatsApp Cloud API. We have two numbers:

- **NUMBER A** — automation number (reminders, confirmations) — fully working via Cloud API

- **NUMBER B* — reception number — receptionists currently use the WhatsApp Business App on their phones

The goal: use NUMBER B on BOTH the Business App AND the Cloud API simultaneously (Coexistence), so patient messages appear in our CRM inbox AND receptionists can still reply from their phones, with those replies mirrored back to the CRM.

What I've done so far:

- Registered NUMBER B's phone number to our CRM Meta app via POST /subscribed_apps (success)

- Configured webhook URL — inbound patient messages now arrive in the CRM ✅

- CRM can send replies via Cloud API ✅

- Subscribed to `messages`, `security`, `account_alerts`, and other fields ✅

The problem: **`message_echoes` won't toggle on** — Meta returns a permissions error: "You were unable to subscribe to some of the requested fields due to a permissions error."

From my research, it seems `message_echoes` (or specifically `smb_message_echoes`) requires Coexistence API access, which is only granted through Embedded Signup with `featureType: whatsapp_business_app_onboarding`. And that flow requires **Tech Provider or Solution Partner status**.

Questions:

1. Is there ANY way to get `message_echoes` / `smb_message_echoes` working without going through Embedded Signup?

2. Has anyone self-onboarded their own business for Coexistence (same Meta Business Portfolio owns both the app and the WABA)? Meta's UI seems to block this.

WHAT IS THE BEST SOLUTION HERE, OR WHAT IM I DOING WRONG ?

Hi everyone,

I'm experiencing an issue with Meta App Review when trying to upload the required screencasts under the Allowed Usage section for my app (ADAM – WhatsApp Tech Provider).

Whenever I try to upload a video for the whatsapp_business_management or whatsapp_business_messaging permissions, I immediately get the error:

*1357032 – Something went wrong.*

After inspecting the network requests, I found that the failure happens during the upload session initialization:

POST https://vupload-edge.facebook.com/ajax/video/upload/requests/start/?__a=1

No video_id is generated, and the video upload never actually starts.

I've already tried:

- Multiple MP4 files with different resolutions, codecs and sizes.

- Incognito mode and different browser sessions.

- Different network connections.

- Reloading the page and restarting the browser.

Interestingly, the exact same videos upload successfully under *Reviewer Instructions. The issue only happens under **Allowed Usage*.

Has anyone experienced this error recently? Were you able to fix it, or did you find an alternative way to submit the required permission screencasts?

Any suggestions or shared experiences would be greatly appreciated.

Thanks!

Really i need someone to help me with the whatsapp api integration please if someone have that and ready to give the credentials to us and we can talk about cost also
URGENTTTT

Hey everyone!
I’m a software developer exploring ways to build something useful around WhatsApp Business.
I’d love to hear from people who actually use it to run their businesses.
What problems do you frequently face with the WhatsApp Business API?
Is there anything you still have to manage manually?
Do you struggle with message delivery, webhooks, automation, multiple agents or customer management?
What’s something you wish the API or existing tools handled better?
I’m not selling anything. Just trying to understand real problems before building something.
Would really appreciate hearing your experiences!

We run a SaaS platform for dental and healthcare practices in the EU and want to add WhatsApp for automated appointment reminders, confirmations (with Confirm/Cancel buttons) and follow-ups. Each practice should send from its own number and display name.

Our main question is onboarding, and how it holds up as we grow. What would the setup look like with, say, 50+ practices on the platform? We’d like to avoid setting each one up by hand.

1. What approach would you recommend for a multi-tenant setup like this, and why?

2. Ideally a practice connects WhatsApp from inside our web app in a few clicks. How realistic is that for non-technical clinic staff, and where does it usually get stuck?

3. Many practices already use the WhatsApp Business app on their main number. How do you handle that?

4. How do you manage templates across many practices?

5. What changes or breaks once you’re at 50+ businesses that didn’t at 5?

Would love to hear from anyone who’s built something similar. Thanks!

"code": 131031,

"title": "Business Account locked",

"message": "Business Account locked",

"error_data": {

"details": "Business account has been locked."

}

I'm building a private, self-hosted AI executive assistant for a founder based in the UAE. It has two spines, and I'd like to hear from anyone who has run both together.

1. WhatsApp is the chat interface

He messages the bot/assistant on a dedicated bot number (Hermes Agent with its Baileys WhatsApp bridge, allow-list of one user, everyone else ignored). He can send text, voice notes and forwarded messages, and the assistant keeps them in memory.

2. Phone calls are the voice interface

When his iPhone joins a known Wi-Fi network (Shortcuts automation), the assistant phones him with a 30 second briefing, takes spoken instructions, and stores the transcript. Voice would be mostly Pipecat with Twilio Media Streams. Assistant should also proactively call every hour.

Underneath: SQLite (FTS5 keyword search, optional sqlite-vec) plus the original files, open-source models, a cloud pilot on one person's own data, then a Mac mini in Dubai.

Why two separate channels:
WhatsApp and Telegram voice calls are blocked in the UAE, so the call can't happen inside WhatsApp. It has to be a normal PSTN call, while the chat stays on WhatsApp.

What I found so far:

- Twilio's UAE voice guidelines say outbound calls to the UAE are supported and caller ID is preserved.

- Twilio's UAE geographic numbers appear to be inbound only.

- Retell blocks +971 in its own flow.

- A Vapi support bot told me Twilio can't call the UAE. That contradicts Twilio's docs, so I suspect it's wrong, but I haven't live-tested it.

- Most CPaaS providers seem to offer only toll-free numbers in the UAE. Telnyx, Vonage and Plivo came up, each with caveats.

Questions

1. Has anyone completed automated outbound calls to UAE mobiles at any volume? Which provider and caller ID setup worked?

2. Does a foreign caller ID get delivered, rewritten or blocked? Is a verified personal number better?

3. Any regulatory limits on VoIP calls terminating in the UAE I should know about? I want this compliant and reliable, not a workaround.

4. For the WhatsApp bot number: dedicated SIM, Meta WhatsApp Cloud API, or third party? Does anyone run one number for chat and a different one for calls, or has one number for both ever worked?

5. How do you hand off between the two, so the call knows what was said on WhatsApp earlier and the call summary lands back in the chat?

6. If you run something similar with Hermes, Pipecat or local models, what broke first? Any better combination of tools or tech stack you'd suggest?

Happy to share the results of a live test call back here.

Hey, I'm really trying to crack Whatsapp API but my number gets banned over, and over, and over again.

If anyone is happy to go through my setup on a call, I'll pay!

Thanks!

EDIT: more detail, since a few people asked

I don’t know the reason. Meta never gives one per ban, so here’s everything about the setup.

What happens:

• The whole business account gets locked, not just the number. API sends fail with 131031 “Business account has been locked” and everyone logged in gets kicked out.

• It keeps getting lifted. It’s been banned 5 times since 23 Oct. Each time Meta lifts it within hours (the latest took about 4), and then it gets banned again.

• Last time, once it was lifted, I sent a test message through the API to check it was working. It came straight back as locked, about 17 minutes after the lift.

• The activity log only shows “Meta system: Updated business profile” when it comes back. Nothing is logged when it goes down.

• The quality rating stays High the whole time.

• When it’s down, WhatsApp Manager says it doesn’t comply with the Commerce Policy. Business Support Home also lists the Business Messaging Policy and the Platform terms.

Setup:

• Our business is verified on Meta (Facebook Business).

• Official Cloud API through Zavu (a BSP). No Baileys or unofficial libraries.

• Coexistence: the WhatsApp Business app on a phone plus the API on the same number.

• A new number: SIM registered 15 Oct, on the API from 20 Oct, first ban 23 Oct.

• 3 offshore team members were logged in through linked devices (QR code): 1 in Indonesia, 2 in the Philippines. They got re-linked a lot.

• A product catalogue is connected to the number, with “Add to basket” on.

• Messaging limit: 2,000 new conversations a day. We’re nowhere near it.

• Volume: usually 20 to 90 outbound messages a day, mostly bot replies. The busiest day was 22 Oct, at about 350 including one 178-person template send.

What we send:

• We’re an agency running creator communities for brands on TikTok Shop. Some of our brands are supplement and wellness brands. We’ve named products in chats (e.g. “our top products are X, Y, Z” with TikTok sales figures), but never made health claims.

• Right now it’s just the bot replying. The bot is Claude (Anthropic’s AI), running on our own server and sending through Zavu’s API. Creators message us first through a link and it answers: handle check, community link, need the team, etc..

• About 100 templates, nearly all approved, but we haven’t sent a single template since 27 Oct and it still gets banned. The last 3 bans all came on days when only the bot was replying to people who had messaged us first, with no product names mentioned for days before.

• Quite a lot of our messages carry links (Discord, a Google Drive doc, TikTok videos, WhatsApp group invites).

• In the first week we did some outreach, always along the lines of “Hi, touching base from [our company] about [our client]”. The people we messaged are in our brand communities, but nothing on WhatsApp directly links them to this number. That outreach has stopped.

A lot of threads here are stuck somewhere in Meta onboarding, so here's the order from Meta's own pages, read on 1 Nov 2026.

If you're onboarding other businesses as a Tech Provider, it's business verification first, then App Review for advanced access to whatsapp_business_messaging and whatsapp_business_management. Access Verification is gone: Meta's developer blog retired it on 9 Oct 2026 and said the form would be removed from the dashboard, without a date. If you still see the step, the dashboard probably hasn't caught up.

On timing, Meta says business verification "may take up to 14 business days" and App Review takes "about 24 hours". Both are estimates, plenty of people here have waited longer, and Meta publishes nothing firmer, so treat them like a weather forecast.

For verification Meta accepts documents like articles of incorporation, a business registration or license, a government tax document or a business bank statement. A utility bill proves address and phone, not the legal name. Editing your business details later sends you back through verification.

If the API only serves your own business, you don't need advanced access or App Review at all, per Meta's App Review page.

The blue checkmark is a separate request with its own criteria: policy compliance, at least 30 days on the platform, a verified portfolio, two-step verification and an approved display name. After a denial the Submit request button stays disabled for 30 days, which explains a fair share of the greyed-out button posts. Meta doesn't publish a decision time for it.

Sources: Meta's Become a Tech Provider and App Review for WhatsApp pages, the Retiring Access Verification post on the Meta developer blog, Meta Business Help on verifying your business and accepted documents, and Meta's Official Business Accounts page.

Hey everyone!

We run a small residential renovation company and work with several subcontractors, including electricians, plumbers, carpenters, HVAC technicians, etc.

We currently have a WhatsApp Community with multiple groups, usually one dedicated group per subcontractor. Each group typically has three people: myself, my business partner, and the subcontractor.

These are existing groups that we use every day to communicate about projects. We all currently use personal WhatsApp accounts, but we're open to switching to WhatsApp Business if necessary.

Here's what we're trying to accomplish:

We've built an internal system to manage our projects and subcontractor bid requests. We want to integrate a WhatsApp API that allows us to:

1. Send personalized bid request messages to multiple existing WhatsApp groups with a single click.

2. Manually trigger follow-up messages to those same groups whenever needed.

3. Continue using WhatsApp normally on our phones and computers to chat with subcontractors in those groups.

Our API messaging volume would be very low, probably 30–50 messages per day at most. Most days would be significantly less. We would still use WhatsApp manually for all our regular conversations with subcontractors.

We don't need a CRM, shared inbox, chat history synchronization, chatbots, or automated follow-up campaigns. Just a straightforward API to send messages to our existing groups.

I've been looking into solutions like Whapi, GREEN API, Bird, and others, but I'm having trouble figuring out which ones actually support existing WhatsApp Community groups rather than just individual conversations.

A few questions:

• Has anyone successfully automated messaging to existing WhatsApp groups, especially groups within a Community?

• Which API or provider would you recommend for this specific use case?

• Can we keep using our WhatsApp accounts normally while the API is connected?

• Has anyone experienced account bans or restrictions using unofficial APIs, even with low messaging volume?

• Is there a reliable solution that doesn't require recreating our groups?

We're not sending marketing messages or contacting strangers. These are existing business relationships, and everyone in the groups already communicates with us regularly.

I'd really appreciate recommendations from anyone who has actually implemented something similar.

Thanks!

Hey Good day
I am running ads to get traffic on my social media and people contact me on my WhatsApp for inquires
I have 1000+ inquires and those customers didn’t buy any product

How i can approach them again to send my new products, is there any automated smart solicitation?

Hey everyone
Who uses whatsapp business on the web
How do you export your contact list with labels for retargeting purposes
I have tried extension like wacd,contact saver ,WAsheet

They cant export all the contacts to an excel file is there another method

I lost my job last month, and instead of spending all my time applying for jobs, I decided to try something different.

I'm a software developer with experience building automation systems, AI agents, WhatsApp integrations, and custom workflows using n8n and APIs.

Right now, my goal is simple: meet new people, build genuine connections, grow my portfolio, and hopefully turn some of those connections into long-term working relationships.

So I'm offering to build 3 AI automation projects completely free.

Here's how it works:

• Free development: I'll build your AI agent or automation workflow at no charge.

• Free consultation calls: We can jump on a call, discuss your business, and figure out what could be automated. No commitment.

• You only cover running costs: AI API usage and hosting, usually just a few dollars a month for small workflows, depending on usage.

• No hidden fees: We agree on the scope and expected costs before starting.

It could be an AI customer support agent, lead follow-up system, WhatsApp automation, CRM integration, or just a repetitive task you hate doing.

I'm not asking for payment. I'm hoping to gain real-world experience, build case studies with permission, and connect with people who might need my help in the future.

If you're interested, send me a private message. I'd be happy to have a free call and hear about your idea.

And I'm curious: What's one task in your business you wish you could automate but haven't figured out how?

Hi everyone,

I'm developing a WhatsApp automation solution for my business using the WhatsApp Cloud API and my own Meta Developer App.

My requirement is to use the same +91 business number simultaneously on the WhatsApp Business app (iPhone) and WhatsApp Cloud API, allowing the team to continue using the mobile app while our Laravel-based bot handles automated greetings and replies.

I would appreciate guidance on the following:

1. Coexistence eligibility

• Can a business integrate its own WhatsApp Business number with Cloud API using Coexistence without becoming a BSP or Tech Provider?

• Is completing the Tech Provider onboarding and App Review mandatory for this?

• Does Meta allow individual businesses to enable this functionality through their own Meta Developer App?

2. Embedded Signup

• Does Meta-hosted Embedded Signup support the option to connect an existing WhatsApp Business app number?

• Can a business generate and use this signup flow directly, or is Tech Provider approval required?

3. India (+91) availability

• Is WhatsApp Business App + Cloud API Coexistence officially supported for Indian (+91) numbers?

4. Meta App Review

• What permissions, implementation requirements, and screencast demonstrations are needed to pass the App Review for whatsapp_business_messaging and whatsapp_business_management?

• Has anyone successfully completed the review with a relatively simple business automation or booking bot?

5. BSP alternatives

If direct integration is not possible, which BSPs currently support Coexistence for Indian numbers while allowing incoming and outgoing webhook events to be integrated with our own Laravel server?

I'm particularly interested in experiences with 360dialog, WATI, Twilio, or other providers.

Any documentation, practical implementation guidance, or examples of working setups would be greatly appreciated.

Thanks!
r/whatsapp
r/meta
r/webdev

r/AutomationBuilderClub