▲ 30 r/WhatsappBusinessAPI+1 crossposts

Is Meta setting up the death of every platform that built its business on WhatsApp?

I have a thesis that will probably annoy a lot of people in this industry:

Meta’s rising messaging costs, tighter rules, and the arrival of native AI agents inside WhatsApp Business are only the beginning.

I think Meta ultimately wants to capture a much larger share of the conversational commerce and customer service market that third-party companies have spent the last 5–7 years building on top of WhatsApp.

For years, something extremely convenient happened for Meta.

Thousands of SaaS companies built customer support platforms, WhatsApp automation, chatbots, conversational CRMs, sales tools, AI assistants, marketing automation and support workflows.

They did the hard work.

They convinced businesses that WhatsApp should become a commercial channel.

They integrated the APIs.

They onboarded companies.

They trained the market.

They built dashboards and workflows.

They got businesses comfortable with selling, supporting and operating through chat.

And all of that happened on infrastructure they never actually controlled.

Now Meta has the users, the businesses, the distribution, the infrastructure and increasingly powerful AI.

And Meta has already made it clear that its ambition goes far beyond simply providing messaging.

They want WhatsApp Business and their business AI infrastructure to become much more deeply connected to the systems companies already use — CRMs, commerce platforms like Shopify, product catalogs, payments, customer data and business operations.

And that raises an uncomfortable question:

If Meta connects directly to your CRM, Shopify store, catalog, payments and customer data — what exactly is the sustainable advantage of many of the companies sitting in the middle?

Why would a business need three or four additional SaaS layers if Meta can increasingly provide the distribution, conversation layer, AI agent and integrations itself?

That is the part I think the market is underestimating.

If Meta can eventually provide natively:

  • AI sales agents
  • customer support
  • CRM connectivity
  • Shopify/e-commerce integrations
  • product catalogs
  • payments
  • follow-ups
  • recommendations
  • abandoned-sale recovery
  • campaigns
  • customer context
  • analytics
  • automated workflows

then a huge number of companies whose product is essentially “WhatsApp + AI + integrations + a dashboard” suddenly look extremely vulnerable.

And this is the part I genuinely don’t understand.

How did so many founders build entire companies while strategically depending on a single corporation that controls the API, the channel, the pricing, the rules and the end user?

You don't own that distribution.

You're renting it.

Meta can change pricing and destroy your margins.

It can change a policy and kill a core feature.

It can launch a native feature and erase an entire product category.

It can restrict automation.

It can prioritize its own agents.

It can connect directly to the same CRMs and commerce systems you were using as your competitive advantage.

And eventually it can turn WhatsApp Business itself into the platform that many of these SaaS companies currently sell.

This creates an even bigger strategic problem:

How can an entire industry continue depending on Meta while simultaneously competing with Meta?

Your supplier is also becoming your competitor.

Your distribution channel is also becoming your competitor.

The company controlling your API economics is also becoming your competitor.

That is an incredibly dangerous position to build a business around.

I don't think literally every company in this space will die.

Companies with proprietary technology, deep enterprise workflows, real omnichannel infrastructure, vertical specialization, unique data, or an intelligence layer that exists independently of WhatsApp can absolutely survive.

But companies that are basically sophisticated wrappers around WhatsApp should probably be very worried.

My suspicion is that Meta spent years allowing an external ecosystem to educate the market, prove the business use cases and massively expand WhatsApp as a commercial channel.

Thousands of startups effectively helped Meta prove that businesses wanted conversational commerce.

And now Meta can start moving upward into the highest-value layers itself.

If that thesis is correct, today's pricing changes and WhatsApp AI agents aren't the main event.

They're just the first signals.

And maybe the real long-term escape route is RCS.

Not because RCS is magically better, but because the industry desperately needs a truly global conversational channel that doesn't leave almost the entire ecosystem strategically dependent on one company.

The problem is that RCS adoption internationally has been painfully slow.

So I genuinely hope it reaches virtually every country, carrier and business ecosystem in the world.

Because otherwise we may end up in a bizarre situation where thousands of conversational AI companies claim to be independent SaaS businesses…

while their entire existence is ultimately determined by Meta.

Am I overestimating what Meta is trying to build?

Or are we watching an entire industry slowly realize that it built its companies on rented land?

reddit.com
u/Pretty-Giraffe-3203 — 3 days ago

Nobody in latam has a plan B for WhatsApp and meta knows it

Been running WhatsApp API for a few businesses since the per-conversation days and honestly this latest change is bugging me more than the price itself.

Quick recap for anyone who missed it: starting Oct 1 Meta charges for service messages. Yes, replying to a customer WHO MESSAGED YOU FIRST now costs money. Utility messages inside an open window too. And their new AI agent already bills per token since August.

The rate is small, whatever. A couple cents. That's not my point.

My point is the pattern. Per conversation billing → then categories → then service goes free in 2024 (everyone celebrated lol) → then per message billing → now nothing is free anymore. Every step made the billing more granular, and they can adjust rates 4 times a year. You don't build that machinery to leave it idle.

And here's what really gets me: I work mostly with latam clients. Here WhatsApp isn't "a channel", it IS the phone. Brazil, Mexico, Argentina, India... no plan B exists. When your only supplier learns you can't leave, prices go one direction. We all know this.

So genuine question to this sub: why is nobody seriously pushing RCS?

I know, I know. RBM costs money too, carrier support is a mess in some countries, aggregators take their cut. Not claiming it's magic. But it's an open standard, Google pushes it, Apple finally supports it, and it hits the phone number instead of an app owned by the same company that just repriced your entire support operation.

We don't need RCS to kill WhatsApp. We need it to exist as a real threat, because that's the only thing that will ever keep Meta's pricing honest. Regulators sure won't.

I'm already moving OTPs and shipping notifications off WhatsApp. Anyone here actually running RCS traffic in latam or India? Curious how bad (or not) carrier coverage really is.

reddit.com
u/Pretty-Giraffe-3203 — 1 month ago

Telegram not working with Hermes Agent (sending broken, receiving OK)

Steps taken

  1. Created a Telegram bot with BotFather.
  2. Verified the token twice by calling getMe — it returned HTTP 200 with valid bot data, so the token is valid.
  3. Confirmed the user can send messages to the bot (/start, plain text) from Telegram Desktop; the app shows delivered/read ticks.
  4. Called getUpdates to check incoming messages: the first time it returned the user’s message, so incoming messages are received.
  5. After that, every request to getUpdatesgetWebhookInfo, and sendMessage started returning HTTP 404 — from both Hermes and the system terminal.
  6. Tested from multiple angles: bash terminal, Python (urllib), Python (requests), curl, and browser-based GET. All return 404.
  7. Tried a second bot (new token) to rule out a bot-specific issue: exact same behaviour.
  8. Checked Hermes’ messaging panel: “Messaging gateway” was shown as stopped, with the Enabled toggle off.
  9. After starting the gateway and loading the token in config, the same pattern continued: getMe returns 200, but all interaction endpoints return 404.

Exact results

  • getMe: works (200 OK); bot exists and token is valid.
  • getUpdates: returned the user’s message once, then switched to permanent 404s.
  • sendMessage: 404 every time. Response body is: {"ok":false,"error_code":404,"description":"Not Found"}
  • getWebhookInfo: 404.
  • The user sees sent messages as delivered in Telegram, but the bot never replies and stops receiving updates after the first successful poll.
  • Reproduced with two different tokens/bots, so it is not a bad token or a single-bot issue.

User behaviour

  • Sent /start and normal text messages to the bot from Telegram Desktop.
  • Blue ticks confirm the messages leave the app normally.
  • Bot remains silent.

Possible causes investigated

  1. Ghost webhook: if a webhook was previously configured and not fully cleared, getUpdates can fail with 404 until it is deleted with deleteWebhook. Could not verify because getWebhookInfo also returns 404 (possibly an intermediate state from Telegram).
  2. Partial regional/ISP block: some ISPs/countries throttle Telegram API traffic, but getMe worked, so it is not a complete block.
  3. Telegram restriction on new bots/new accounts: sometimes the API is not fully enabled immediately.
  4. Hermes gateway issue: gateway was shown as stopped in the UI. After forcing it on, receiving worked once but sending still 404s.

Bottom line

  • Receiving from Telegram works.
  • Sending to Telegram is consistently broken (404 on everything except getMe).
  • Not a token problem, not a single-bot problem, and not an obvious client-side misconfiguration.
  • Next steps: check whether a stale webhook exists on Telegram’s side, and review Hermes gateway logs for outbound request handling.

Can anyone help me please?

¡Thanks!

reddit.com
u/Pretty-Giraffe-3203 — 3 months ago