u/Low-Squash-3572

Seeing a lot of content about WhatsApp automation lately, chatbots, automated replies, and broadcast messages.

For those of you actually using it for your business:

• What's it actually replacing? Phone calls? Email? Manual follow-ups?
• Did customers complain about talking to a bot, or did they not care?
• What did it cost to set up, and is it worth it for a small operation?

Not interested in what vendors say. Want to hear from people who've actually used it day-to-day.

Same messages. Different names. Repeated every single day.

The moment I automated my follow-ups, those 2 hours disappeared. Not reduced, gone.

What's the one task in your day that you're still doing manually that you know should be running on autopilot by now?

Three months ago, we were ready to launch a re-engagement campaign for dormant users. Template written, audience segmented, BSP configured.

Meta rejected it. No reason given. Just "rejected."

We rewrote it. Rejected again.

The next six weeks were a loop of guessing, rewriting, and waiting 24–48 hours per submission just to hit the same wall.

Here's what we eventually figured out: nobody tells you upfront:

• "Promotional" triggers are invisible – words like "offer," "exclusive," and "limited" aren't blacklisted, but patterns around them are. The same sentence with a different structure gets approved
• Variable abuse kills templates – we had {{1}} in places Meta apparently flags as high-risk for spam. Too many variables in the CTA section, specifically, were the problem
• Category mismatch is silent death – we submitted a marketing template under "utility" thinking it'd get approved faster. It didn't. And it poisoned the review queue for our next submission

What actually got us through: stripping the template down to the plainest possible version first, getting approval, then iterating from there in separate submissions.

We lost three weeks of the campaign window because we tried to launch with the final version first.

What's the dumbest rejection reason you've run into? And has anyone found a pattern in what actually gets approved on the first try?

We were doing everything manually. Copy-paste broadcasts, one by one, praying our account didn't get banned. Eventually, it did.

After some research, we moved to Waplify.io, a WhatsApp marketing platform built on the official Meta API. Here's what actually matters after using it:

What it does: Lets you run bulk WhatsApp campaigns, automate chatbot flows, manage a shared team inbox, and handle CRM-style lead tracking all without the ban risk of unofficial tools.

Features worth noting:

• Broadcast campaigns to opted-in lists with real delivery tracking
• Visual Flow Builder for chatbot automation (buttons, lists, keyword triggers — no code)
• Shared team inbox so multiple agents work the same number of times
• Contact tags and segments for targeted messaging
• No message markup, you pay Meta's rates directly, platform fee is separate

Pricing model is unusual: they offer a lifetime plan (one-time payment), not just subscriptions. All features are included regardless of tier; the only difference is in seats and message volume.

Not affiliated, just posting because I wasted 6 months on sketchy bulk tools before finding this. WhatsApp open rates genuinely are around 90% compared to email. The channel is real, the tooling just needs to not be garbage.

In this case, we’re using the Meta Coexistence scenario (Business App + Cloud API with the same number as Business App through Embedded Signup), but we encountered an issue that I have yet to see covered extensively online.

Namely, our integration experiences inconsistencies in which messages sent through the Business App do not generate webhook requests in the Cloud API as intended. Meta describes this feature as "Messaging Echoes," where messages sent through the app should reflect in the API inbox. However, messages sent through the Business App occasionally work, and sometimes they do not.

These are actual problems:

• The CRM state falls out of sync silently. The customer claims, "I've already responded to that," but we don't have any record of it
• Our conversation window logic fails since the messages sent from the application cannot open or extend the 24-hour API window, and our bot sends out a template message into what we think is a cold conversation when the agent already has it warmed up
• There's an actual 20 MPS throughput limit for coexistence that's not well-documented. We discovered this one in the developer documentation after hitting it in staging.

Workaround solutions that have been proposed:

• Forced removal of all agents from the Business App (goes against the premise of coexistence)
• Use polling in conjunction with our CRM platform to synchronise states (unreliable, introduces latency)
• Classify all coexistence phone numbers as “unreliable sync” and use manual override instead.

None of these works cleanly. This feature promises to be seamless, but obviously, it is eventually consistent or outright fails in high-volume use cases.

Is there a way of knowing if there is an echo failure or whether to synchronise based on application state vs API state? Have you tried any BSP middleware service provider that does better than a plain vanilla Cloud API service provider? I would be delighted to know if it is just our configuration or if that is all we can do.

Relying upon "Messaging Echoes" in the Coexistence feature and the known 20 MPS limit with regard to the different behaviours exhibited by webhooks sent from applications versus via the API, these are real-life, verifiable frustrations for practitioners.

Six months ago, we ditched our abandoned cart email sequences for WhatsApp.

The results have been disappointing; open rates may be comparable, but the responses are the issue that no one wants to address.

If customers respond, you must have a plan in place, and we didn’t. The first couple of weeks were a disaster of unopened messages and irate customers who felt they had been ignored after receiving their “personal” message.

Here are some things that were more important than the open rate:

• Message timing – too quick makes it seem intrusive, too late, and you lose the meaning
• Message approval issues – the Meta review process killed off three campaigns during rollout
• Customer opt-outs – one mistake can cost you big

Have you set up WhatsApp automation? What was your biggest challenge?

Six months ago, we ditched our abandoned cart email sequences for WhatsApp.

The results have been disappointing; open rates may be comparable, but the responses are the issue that no one wants to address.

If customers respond, you must have a plan in place, and we didn’t. The first couple of weeks were a disaster of unopened messages and irate customers who felt they had been ignored after receiving their “personal” message.

Here are some things that were more important than the open rate:

• Message timing – too quick makes it seem intrusive, too late, and you lose the meaning
• Message approval issues – the Meta review process killed off three campaigns during rollout
• Customer opt-outs – one mistake can cost you big

Have you set up WhatsApp automation? What was your biggest challenge?

We are working on integrating with customers having WhatsApp Business accounts integrated through the sign-up process.

Problem: When we integrate through this route, we do not receive WhatsApp Business Management permissions; therefore, we cannot programmatically retrieve any message templates that the customer may have created.

Therefore, the available choices are:

• Have the client type in the template name, language, and component names, which are prone to errors and destroy user experience
• Find some way around the scope restriction (no clean solution found yet)
• Encourage the client to migrate completely to the API version, which many don’t like

Is there anyone capable of solving the issue of template discovery within an environment with a limited scope? Is there any third-party software or middleware that can fill this void without having the entire business process platform migrated from the present one?

I'm really curious to know how others are coping with this issue.