Meta just launched its native Business Agent on WhatsApp. If your core offer is chatbots, this is the week to reposition — not panic. On June 3rd, Meta rolled out the Meta Business Agent globally: a free (for now) generative AI agent that answers customers on WhatsApp, Messenger and Instagram, trained automatically on the business's Facebook page, catalog, website and past chats. I run an automation agency in Mexico — one of the three pilot markets where this has been tested for almost two years, alongside India and Brazil — so I've been digging deep into what this means for those of us whose core is conversational automation. Sharing my analysis because I think every agency here needs a position on this before a client asks "why am I paying you when Meta does it for free?" What it actually kills: the low end. Generic FAQ bots, "what are your hours," catalog questions, basic lead capture. If your offer is a $500 setup of a flow that answers common questions, Meta just made that a free checkbox. That segment is gone — let it go. What it can't touch (and where I'm doubling down): 1. Deterministic business logic. Meta's agent is generative — it guesses plausibly. It can't check real availability in a client's database, enforce booking rules, or guarantee what it says. 2. Deep integrations. The agent doesn't see your client's CRM, calendar, inventory, or internal systems. Meta announced custom connectors on their Business Agent Platform, which I'm testing in a sandbox — but configuring and integrating those is itself a service we sell. 3. Compliance and data sovereignty — this is the big one. Read Meta's own FAQ: messages in AI-enabled chats are collected by Meta to improve Meta AI, even when the agent is muted, and those chats lose end-to-end encryption. For my regulated clients (a notary handling anti-money-laundering data, a law firm, a health clinic), that's not a feature gap — it's a legal liability. My adaptation playbook: - Stop selling "chatbots." Start selling business automation with compliance and integrations. The word "chatbot" is now a commodity Meta gives away. - Add "Meta Business Agent setup & optimization" as a low-ticket entry offer for tiny clients — it's a lead magnet. The moment they want it to actually do something against their systems, they upgrade to your custom build - If you serve regulated verticals (legal, health, finance), lean in hard. That moat just got deeper, not shallower.

Question for people shipping client WhatsApp chatbots right now: With Meta changing things constantly and BSPs coming and going, what's your current go-to path for customer-support bots? I'm building on n8n + WhatsApp Cloud API (direct). Automation works fine, but Meta's business verification has been the real bottleneck — slow and easy to get stuck. Tried YCloud as a BSP earlier and struggled there too. What route are you actually finding most accessible and reliable for client work — direct Cloud API, a specific BSP, or something else? And how are you handling verification so it doesn't stall the project? Appreciate any real-world input 🙏

Hello everyone, is there any easier niche to start with? Like something to gain hands on experience before launching something bigger? Also, what kind of automation? WhatsApp bot, receptionist agent, voice agent, prospection ...? Any recommendations?

60 days building my first AI agency in Mexico 🇲🇽 — here's the mistake that cost me weeks on WhatsApp integration (so you don't make it).I assumed the hard part would be the AI: prompts, RAG pipelines, n8n flows, Claude API. The real blocker was WhatsApp Cloud API !!! After weeks of Meta business verifications, a BSP that wouldn't sync my number, and a phone number stuck in ON_PREMISE state — I learned this the hard way: 🚫 Never disconnect Coexistence from the WhatsApp Business App if your goal is migrating to Cloud API Direct. Doing so permanently degrades your number to ON_PREMISE. There's no public API endpoint to reverse it. Meta won't fix it unless you have Pro Support or a Tech Partner BSP. The number is essentially dead for Cloud API. How I am trying to fix it ? : virgin SIM cards only. Never recycle a number that was previously on WhatsApp Business App or any BSP infrastructure. let´s see how it works, if any recommendation, I would be glad to hear it. Happy to share more on what the Meta verification process looks like for SMBs in LATAM.

Hi! I've used Liam's YouTube tutorial for creating an OpenAI chatbot using the Assistant's API with WhatsApp. The problem I'm facing is that whenever a user sends more than one message to the bot before the bot responds, the second message and any following ones do not get a reply because the bot doesn't account for them. Has anyone else encountered this problem? Can someone help me with it? Thanks!