Weflux runs broadcast campaigns on the official WhatsApp Business API. Approved templates, real delivery reporting, and none of the ban risk that comes with unofficial bulk senders.
Build, submit and track Meta message templates from the dashboard. Text, images, video, documents and interactive buttons are all supported.
Every campaign reports what Meta reports back: how many messages were accepted, delivered, read, and how many people replied or opted out.
Messages go through Meta's own Cloud API, the same infrastructure Meta operates for every WhatsApp Business Platform provider.
A WhatsApp broadcast is a message sent to many recipients at once, where each person receives it as an individual one-to-one chat rather than a group. Recipients cannot see each other, and replies come back to you privately, into the same thread they would use for any other conversation.
That last part is what separates a broadcast from an email blast. A broadcast is not a one-way announcement. Anyone who receives it can reply, and when they do, a 24-hour window opens in which you can respond with ordinary free-form messages. Most of the commercial value of WhatsApp broadcasting sits in those replies, not in the send itself, which is why a broadcast tool without a decent inbox behind it tends to disappoint.
On the official WhatsApp Business API, a broadcast to people who have not messaged you recently must use a message template approved by Meta in advance. You cannot compose a fresh paragraph and blast it to 5,000 people. This constraint is the whole reason official broadcasting is sustainable: it is also why the numbers sending it do not get banned.
If you have searched for a WhatsApp bulk message sender, you have seen tools promising unlimited messages from your personal or Business App number, usually for a one-time fee. They work by automating the WhatsApp app itself, which violates WhatsApp's terms of service. Numbers using them get banned in waves, and a banned number is generally not recoverable.
The honest comparison:
| Official WhatsApp Business API | Unofficial bulk sender | |
|---|---|---|
| Permitted by WhatsApp | Yes | No, violates the terms of service |
| Risk to your number | Normal policy risk, appealable | Ban in waves, usually permanent |
| Message content | Pre-approved templates for the first message | Anything, no review |
| Sending volume | Tiered messaging limit that grows with quality | Advertised as unlimited until the ban |
| Delivery reporting | Delivered, read and failure states from Meta | Sent from the device, little more |
| Green tick eligibility | Possible | No |
| Cost shape | Platform fee plus Meta's per-message charge | One-time or subscription fee |
The template requirement is the trade. You give up the ability to send arbitrary text to strangers, and in exchange your number keeps working, your delivery is measurable, and you can apply for verification. Weflux runs entirely on the official Cloud API. We do not offer an unofficial mode, and any provider that offers both is worth asking hard questions about.
Once your number is connected, a campaign is five steps.
Meta sorts every template into a category, and the category determines both what you are allowed to say and what the message costs. Choosing the wrong one is the most common reason a template is rejected.
| Category | Use it for | Examples |
|---|---|---|
| Marketing | Anything promotional, or anything whose purpose is to bring someone back | Offers, launches, cart recovery, re-engagement, newsletters |
| Utility | A message about a transaction or request the customer has already made | Order confirmations, shipping updates, payment receipts, appointment reminders |
| Authentication | One-time passcodes and account verification, nothing else | Login OTP, transaction verification |
Marketing is the most expensive category and the most scrutinised. Utility is cheaper, but it only applies where a real transaction exists: dressing a promotion up as an order update gets the template rejected, and repeated attempts affect your account standing. Authentication templates have a fixed shape and cannot carry marketing copy.
Meta sets and periodically revises the per-message rates by category and destination country. Weflux passes those charges through at cost, so the current rate is whatever Meta publishes for India, and every invoice line shows it.
When a customer sends you a message, a 24-hour window opens. Inside it you can reply with ordinary free-form messages: text, images, documents, whatever the conversation needs, with no template and no approval. When the window closes, you can only reach that person again with an approved template.
This single rule shapes how good WhatsApp teams work. It is why a shared inbox matters more than it looks like it should, and why response time is a commercial metric rather than a service nicety. A reply that lands nine hours late may still be inside the window. One that lands twenty-six hours late costs you a template message and a great deal of goodwill.
Weflux stores contacts with tags, custom attributes and a lead stage, and any combination of those can define an audience. In practice the segments that earn their keep are unglamorous: customers who bought in the last ninety days, leads who replied but never converted, people in one city, people who abandoned a cart this week.
Opt-outs are handled for you. When someone asks to stop, they are excluded from future campaigns automatically rather than left for someone to remember. That is both a compliance requirement and a quality-rating protection, since blocks and reports are what push a number's quality rating down.
Every campaign reports accepted, delivered, read, replied and opted-out, sourced from Meta's own delivery webhooks rather than inferred. Failures are itemised with the reason Meta gave, which matters because the common failure modes have different fixes: an invalid number is a data problem, a template pause is a content problem, and hitting your messaging limit is a pacing problem.
Read rates on WhatsApp are genuinely high compared with email, and it is tempting to stop there. Replies and opt-outs are the more useful pair. A campaign with a high read rate and a high opt-out rate is not a success, it is a warning about the next one.
Meta assigns every WhatsApp Business number a quality rating based on how recipients react, principally blocks and reports. It also assigns a messaging limit, the number of unique customers you can start conversations with in a rolling 24 hours. Limits step up as you send consistently to people who want to hear from you, and step down when they do not.
What keeps a number healthy is not clever tooling, it is restraint:
Weflux paces sends to your current limit and surfaces the quality rating in the dashboard, but no platform can protect a number from a bad list. The tool cannot want your customers' consent on your behalf.
Two separate charges. Weflux bills a monthly platform fee by plan, starting at zero. Meta bills per message, by template category and destination. Weflux adds no markup to Meta's charges and shows Meta's rate on every invoice line, which means the number you see is the number Meta charged us.
The practical consequence: as volume grows, the platform fee stops being the interesting number and the Meta charges dominate. That is exactly when a markup would start costing you real money, and exactly why we do not take one. Full detail on the pricing page.
Connect a number, get a template approved, and send to a segment that asked to hear from you. The free plan is enough to try the whole loop.
