Back to blog

How to avoid blocks in mass WhatsApp campaigns

Five practices that prevent WhatsApp Business account blocks in mass campaigns: segmentation, opt-in, throttling, content and metrics.

Mass WhatsApp campaigns break for the same five reasons, always: base without opt-in, volume without warm-up, miscategorized template, no variants and metrics nobody watches. This post lists the five practices that prevent blocking, ordered by impact. It's the checklist any marketing or collections lead should review before pressing "send".

The cost of a block isn't just losing the account. It's losing the operation that depended on that account — collections, support, sales. Recovery takes weeks at best, never at worst. Prevention is 10x cheaper.

Principle 1 — Segmentation before volume

500 right contacts is better than 5,000 random ones. Segmentation reduces opt-out, improves reply rate and tells Meta you know what you're doing. An account that sends to defined segments with reasonable reply rates looks like a legitimate operation. One that fires the same to everyone looks like spam.

How to segment well:

By customer type. Active vs. inactive vs. churn. Each segment gets a different message.

By recent behavior. Whoever bought this month gets something different from someone who hasn't bought in six months.

By location. Hours, holidays, available products vary by country and region.

By consent. Whoever opted in for marketing receives campaigns. Whoever only opted in for transactional service doesn't.

If your base can't be segmented — because it's an Excel sheet with nothing more than the phone number — it's not a base, it's a list. Before launching a campaign, spend time enriching it.

Principle 2 — Verifiable opt-in

Each contact in your base must have a record of how and when consent was given. If asked — and in LATAM, regulators do ask — you should be able to show it in minutes. Without opt-in, everything else matters less: the account goes to a block sooner rather than later.

Valid opt-in has three components:

How it was obtained. Checkbox on a web form, spontaneous message from the customer, checkbox during purchase, registration at a physical counter. Each path has legal nuances per country, but all are acceptable if documented.

When it was obtained. Timestamp. Data protection laws typically require temporal recording of consent.

What was consented to. If the customer opted in for "after-sales service", you can't send marketing. The declared purpose limits use. Per-country details in WhatsApp Business compliance for LATAM companies.

What is not valid opt-in:

  • Purchased or swapped database with another company.
  • Base extracted from public directories without express consent.
  • "Implicit opt-in" because the customer bought once without checking anything.
  • Generic opt-in for "all types of communication" without specifying the channel.

Principle 3 — Progressive throttling

Send speed matters. A new account that fires thousands of messages in the first hour is an immediate red flag for Meta. Throttling — capping the send rate — is what keeps the account healthy.

Typical progression for a new account:

First week. Low volumes, utility messages (not marketing), preferably as replies to customer-initiated interactions. This builds real history.

Second and third weeks. Ramp volume gradually. Start small campaigns to warm segments (customers with recent relationship).

From the fourth week. With stable metrics (low opt-out, reasonable replies), you can operate at full volume respecting the limits of the tier Meta assigns to the account.

What matters isn't the exact number. It's the pattern: gradual ramp, stable metrics, no sudden spikes. Meta classifies accounts into tiers based on history and quality. The tier defines how many unique customers per day you can contact. WhatsApp Business Platform documentation on messaging limits details how tiers work.

Sudden spikes are a problem signal. If an account was sending 200 daily messages and suddenly sends 5,000, Meta notices.

Principle 4 — Approved templates with variants

Have 2-3 approved variants per message type. If one falls mid-campaign, immediate pivot. Without variants, a drop is a stopped campaign and possibly an account at risk.

Variants are built like this:

Variant A — main version. The one that converts best after initial tests.

Variant B — alternative. Different phrasing, same structure. Approved in parallel.

Variant C — conservative fallback. More utility, less call-to-action. If the first two fall, this one sustains.

Variants also help A/B testing. Test two versions on small segments and see which generates better response before sending to the big universe.

Without variants, the operation depends on a single template. Any quality degradation means stopping and waiting for a new approval, which can take hours to days. More on writing and approval in official WhatsApp Business templates.

Principle 5 — Monitor opt-out and reports

If opt-out per campaign crosses 2-3%, message or segment needs adjustment. It's not a metric to check at the end — it's a metric to watch in the first hours and cut the campaign if it spikes.

Critical metrics to monitor in real time:

Opt-out rate. Messages with negative response or exit keyword over messages sent. Acceptable is below 2%.

Spam reports. Messages flagged as spam by the recipient. Any rise triggers an alert.

Delivery rate. If below 95%, there's a base quality issue (outdated numbers).

Template quality. Meta scores each template. A drop from "High" to "Medium" is an early warning.

Overall account quality. Same. A drop to Medium or Low requires immediate analysis.

A serious operation has these metrics on a visible dashboard and someone reviews them at least once an hour during active campaigns. It's not overkill — damage can accumulate fast if nobody is watching.

Account warm-up — what it is and how to do it

A new account with zero history is like a new user on any network trying to make something viral. It needs to accumulate real interactions, replies, outgoing and incoming messages in various formats before scaling volume.

Recommended process:

Days 1-3. Configure the account. Verify the company's identity with Meta. Approve the first utility templates.

Days 4-10. Low volume, mostly replies to interactions initiated by existing customers. Utility messages (reminders, confirmations). No marketing yet.

Days 11-21. Add small campaigns to very warm segments. Ideally customers who replied in the last 30 days.

Days 22+. Normal operation, with stable metrics. Only here are broader campaigns justified.

Skipping this process is the most common cause of early blocking. Companies that start by blasting 5,000 contacts on day one almost always end up with a limited account in the first week.

Typical mistakes leading to ban

Buying a base. Without opt-in, opt-out ratio is immediate and high. Meta detects it within hours.

Day-one blast to the whole universe. New account with no history, high volume. Impossible to pass the quality check.

Same template to 5,000 contacts without personalization. Even with opt-in, sending identical text feels robotic. Low reply rates. Meta penalizes.

Ignoring opt-out replies. If the customer writes "don't contact me" and gets another message, they'll report as spam. Few mistakes are more heavily penalized.

Empty promotional language. "LAST CHANCE!!!", all caps, multiple exclamation marks. Auto-filtered.

24/7 operation with no pause. Sending at 22:00, 23:00, 2 AM. Reports come in fast and the account degrades.

How Pacunex applies this

The agent respects configured throttling, alternates templates among pre-approved variants, measures opt-out per campaign and alerts the team if a variant drops in quality. The company doesn't have to stare at WhatsApp dashboards — the agent alerts when action is needed.

The first campaigns are planned with the customer along with a warm-up curve, prior segmentation and baseline metrics. The goal is for the account to reach full operation without scares, not to be squeezed from day one.

The general compliance framework (Meta, local law, industry) is covered in WhatsApp Business compliance for LATAM companies.

Pre-launch campaign checklist

Before pressing send, review point by point.

Database. Does each contact have opt-in recorded with how and when? Is segmentation clear and defensible? Is the contact volume reasonable for the account's warm-up state?

Template. Is it approved by Meta? Do you have at least one alternate variant also approved? Does the declared category match the message intent?

Calendar. Does the time respect business hours per contact's country? Does it fall on a national or regional holiday? Is it within the monthly contact cap per customer?

Technical setup. Is throttling sized for your account? Is there a fallback variant configured if the first one fails? Are metrics ready for real-time monitoring?

Team. Is there someone dedicated to watching the campaign the first hours? Is it clear what to do if opt-out or spam reports spike? Who decides to cut the campaign if something goes wrong?

Compliance. Is the privacy policy published and accessible to the customer? Does opt-out work and process immediately? Are records kept per the retention policy?

If all six points are covered, launch. If any is missing, don't.

Next steps

If you have a campaign planned and want to review the plan before launching, let's talk on WhatsApp. We'll help you verify segmentation, templates, throttling and metrics to track before pressing the button. No commitment, in a short conversation.